9
3 Comments

I launched my MVP without the features I advertised. And it was fine.

Recently, I built and launched a new commenting tool for the Ghost platform. (IH page)

On launch day, I had three paid plans laid out, but only a fraction of the features advertised were actually available.

I was 100% comfortable doing this, even though it seems a bit counterintuitive.

Normally, you should really only be selling features that exist. But this early, a) I was confident I could add most of the features within a few weeks, b) I wouldn't have a lot of users, and c) no-one would care if some features weren't quite ready.

It was far more important to launch and be able to show potential users what Cove does and the solution it offers. If some parts of the service weren't ready, that shouldn't stop me telling people about it.

Some things to think about when launching a product with paid plans:

  • At this early stage, the product is brand new and your plans (both strategy and your subscription offerings!) can and will easily change.
  • Don't get bogged down with what features each plan has. You can easily move things around (I did).
  • Definitely launch with some defined plans.
  • Use the opportunity of having plans to show the value your product has. A simple list of features tied to a monetary value is powerful.
  • Categorising features into different tiers shows a weighted value ("feature A is great, but feature B will be a lot more useful because I need to pay X more for it"). Take advantage of this.
  • Anyone who signs up early may not expect to use features in higher plans, so do those last.
  • Utilise a free trial to give yourself some wiggle room (if they're not paying, they don't need your paid features yet)
  • Launch with some sort of billing system in place. If someone does want to pay you, you must let them! 😊 I made sure users could view and sign up to plans in the app before Cove launched.

The point of this post is to tell you it doesn't matter what you launch with. Focus on getting your product out there and flesh it out later.

Creating pricing plans and the features they contain is very helpful as you start on a product, but not everything has to be ready for launch.

(This post is based on a tweet: https://twitter.com/dr/status/1260798016442691584)

posted to Icon for group Product Development
Product Development
on May 14, 2020
  1. 2

    Great insight @dr. Just goes to show that you never really need to have a polished product ready for launch. Learning to iterate based on initial feedback and building out what customers really want is the key. Love that you are proof of this!!

  2. 2

    Your landing page looks great! From your domain name, I thought that you were a some kind of competitor to my FAQ widget startup. It turns out that you are not. Anyway, best wishes ahead.

  3. 1

    This comment was deleted 3 years ago.

Trending on Indie Hackers
I built a WhatsApp AI bot for doctors in Peru — launched 3 weeks ago, 0 paying customers, and stuck waiting for Meta to approve my app User Avatar 52 comments Fixing broken scrapers instead of working on my actual product. So I made it my problem. User Avatar 44 comments I built an open-source PII masking layer for LLM APIs — early traction, looking for design partners User Avatar 33 comments How to see revenue problems before they get worse User Avatar 29 comments From broke and burned out as a PM, to launching my SaaS and optimizing my health User Avatar 27 comments I kept starting projects and dropping them. So I built a system that wouldn’t let me User Avatar 23 comments