The graveyard of indie products is full of things that got to 10 customers and stayed there. Ten customers proved the product works. Now prove the business works.
Scaling is not one activity. It is five levers you pull repeatedly. At any given time, one of them is your bottleneck. Your job is to figure out which one and focus there.
Keep the customers you have. This is the most important lever and the one most builders ignore.
A customer who stays 12 months is worth more than 3 customers who churn in 2. Track churn monthly. When someone cancels, ask why. Build a system for collecting feature requests and actually shipping the ones that come up three or more times.
Action: Send a check-in email to every customer you haven't heard from in 2+ weeks.
Make more from what you have. This is not about raising prices arbitrarily — it is about matching your price to the value you deliver.
If your product saves someone 4 hours a week and you charge $19/month, you are underpriced. Run pricing experiments: try $49 for new customers while keeping existing ones at $19. Track conversion rates at each price point.
Action: What would happen if you doubled your price for new customers? Test it this week.
Systematize how new customers find you. By now you know which channels work from your Sprint data. Double down on the top performer.
If direct outreach got you 7 of your first 10 customers, do not suddenly pivot to paid ads. Build a system around what works: set a weekly outreach target, write templates, track response rates.
Action: Send one referral ask to your best customer today.
Build the right next thing. Not the feature you think is coolest — the feature your customers keep asking for.
The framework: does this feature retain existing customers or attract new ones? If neither, skip it. Your feature backlog should be a ranked list of customer requests, not a list of things you personally find interesting.
Action: What feature have 3+ customers requested? Build that next.
Run it without it running you.
Do a time audit: how many hours per week does this product take? Break it into categories: support, development, sales, admin. If support is eating your life, build self-service tools or a FAQ page. If sales takes too much time, automate your outreach sequence.
Action: Track your hours this week by category (support, dev, sales, admin).
Each milestone changes what you should focus on. Know where you are.
| Milestone | What it means | Focus on |
|---|---|---|
| $100/mo | Proof of concept | Keep building, keep selling |
| $500/mo | Something real | Retention + pricing experiments |
| $1K/mo | Ramen profitable | Systematize acquisition |
| $2.5K/mo | Growing | Hire first contractor or automate |
| $5K/mo | Half a salary | Operations + time audit |
| $10K/mo | Real business | Everything compounds from here |
When revenue gets real, the business needs to get real too. Roughly in order:
Write it down before you implement it: hypothesis, result, decision. Every change is an experiment. One variable at a time so you know what worked.