What did you deliberately leave out of your first version?
A first version can do one job well and still feel unfinished.
There is always something else you could add:
Team accounts
Billing
Integrations
A better onboarding flow
Each one sounds reasonable, but together they can move the launch further away.
I am preparing Inquir Compute for launch, and I am curious how other makers draw that line.
What did you deliberately leave out before your first users arrived?
Was it something they later asked for, or something you never needed to build?
Share one feature and the reason you skipped it.
29 views
Replies
Billing was the one we cut. We shipped with no paid plan and wired Stripe up about a week after the first real users showed up, since nobody pays for something they haven't gotten value from yet. The one I'd be careful cutting is onboarding, you can bolt on team accounts later, but if the first session doesn't land there's nobody left to sell them to.
We chose not to implement multi seat team management and fine-grained role permissions for our V1. on paper it was an obvious must have but it would have delayed launch a month to build it early. our first cohort of users did not even ask for it interestingly they just wanted the core pipelinee to work reliably. we only built a simplified version of it four months later, when larger accounts actually started asking for it