Nearly every founder we talk to has a list of features. Accounts, dashboards, notifications, an admin panel, a mobile app, integrations, AI. It's all reasonable. It's also usually far too much for a first version.
The fastest route to customers is a smaller product, not a faster team.
Start with one job
Ask: what is the one job a customer would pay us to do? Not the five jobs the product will eventually do. The one that's valuable enough on its own.
For Sprout Lessons, the core job was clear: a teacher or parent types a topic and gets a complete, curriculum-aligned lesson back. Everything else built on that.
Write a one-page scope
Before talking to any developer, answer these on a single page:
- Who is it for? Be specific. "Small businesses" is too broad. "Independent physiotherapy clinics with two to five staff" is useful.
- What job does it do? One sentence.
- How will they pay? Subscription, per use, one-off?
- What does success look like after launch? Sign-ups, paying customers, a specific behaviour?
- What are we deliberately leaving out? This list matters as much as the feature list.
Sort features into three piles
| Pile | What goes in it |
|---|---|
| Version one | Only what's needed for the core job and for customers to pay |
| Soon after | Features that improve the experience once people are using it |
| Later, maybe | Ideas worth revisiting once you have real usage data |
Be ruthless. If a feature doesn't help a customer complete the core job or pay for it, it belongs in the second or third pile.
What version one still needs
A small product still has to be a real one. Version one usually needs:
- sign-up and login
- the core job, done well
- payments, if you're charging from day one
- a simple admin view so you can run it without a developer
- the basics for being found: a clear landing page and good metadata
What it usually doesn't need: a native mobile app (a fast web app works on every phone), complex reporting, every integration, or an AI feature that doesn't directly serve the core job.
Build in the open
The best first versions are built on a live link you can click within weeks, with feedback going in as you go. Put it in front of early users before the official launch and watch what they actually do, which is often different from what they said they'd do.
Our product development work runs exactly this way: a fixed scope for version one, a live link early, and real users before launch.
