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.
94 views
Replies
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
What did the simplified version include when those larger accounts arrived?
Was an owner and member role enough, or did one specific permission become essential?
@al_kub owner/Admin/Member was more than enough to begin with. In our research we discovered that 90percent of larger accounts simply wanted a clear separation of who pays controls billing (owner) versus who actually runs jobs views outputs (Member).
The one permission that became immediately critical was workspace billing isolation ensuring members couldnot invite external people or change plan tiers without Owner approval.
That makes the boundary clearer
Members running jobs can still affect the bill though. Did you handle that with a workspace spending cap or alerts for the owner?
I’d leave integrations for later. No point spending days connecting tools nobody has asked for yet.
Would you wait for several people to request the same integration, or build it for one user if it blocks their main workflow?
That seems like the harder call than skipping the ones nobody has asked for
Accounts. The tracker works signed out; data stays in the browser; sign-in is only for sync. It cost me a fancy onboarding flow and gained me the first ten people who would never have made an account for a timer. The thing I added, then removed, was tasks. A weekly hours tracker with a task list stops being a tracker.
Letting someone start the timer before asking for an account makes sense
With the history stored in the browser did you add an export option too? I would want a way to keep those hours without turning on sync
Yes. Menu (top right) > Download my data. JSON, no sign-in needed. Sync is only if you want it on another device.
Aleksandr, which one are you leaning toward cutting for Inquir Compute? Billing seems easy to delay if the first users are just testing..
For Inquir I would put extra integrations behind getting that first app deployed
Billing is a harder cut for compute since testing still uses resources. I would simplify the payment flow before dropping spending limits