Getting to $1 million in ARR with a product doesn’t mean that same product can take you to $10 million. It got you this far because you solved a specific problem for a small group of customers who needed a solution badly enough to overlook the product’s shortcomings. Getting to $10 million means reaching a much broader market, including customers who have more options and far less patience for a product that still needs work.
Most founders don’t see this coming because the thing that worked is still working. Revenue is growing. Customers are mostly happy. So they keep building more of the same, and growth quietly flattens. The challenge is that your next set of customers may have different expectations, different workflows, and different reasons for buying. The features your earliest customers loved won’t necessarily be the ones that convince a broader market.
The fix is not a new strategy deck. It’s a tighter, faster, more honest customer feedback loop, and it has to run through every decision you make: who you hire, who you build with, what you put on the roadmap, and what you kill. Let’s go through it.
Technical founder vs. GTM founder: different superpowers, different blind spots
How you respond to that challenge often depends on the kind of founder you are. Technical founders and GTM founders tend to approach growth differently, and those strengths can become liabilities as the company scales.
If you’re the technical founder, your risk is building in a vacuum. You’ll hear a customer complaint and have a fix deployed by dinner, which feels like a feedback loop but often isn’t. You’re solving the problem they described, not the problem they have, and you’re skipping the part where you ask why.
If you’re the GTM founder, your risk is promising things you can’t evaluate. You hear the customer clearly, but you can’t tell whether their request takes two days or two quarters. So you either over-promise and burn trust, or you become a ticket-taker who hands engineering a list of feature requests with no context.
These blind spots become more expensive as the company grows. At $1M, a founder can often rely on personal relationships and instinct to understand what customers need. At $10M, you’re serving a much broader customer base, and those instincts need to be supported by a process that connects what customers are saying to what the company builds.
Here’s what to do about it:
- Technical founders: put yourself on sales calls. Every week. No exceptions. Not demos where you show off, but discovery calls where you listen. Your goal is to hear the problem before you’re allowed to think about the solution.
GTM founders: don’t hire a technical cofounder; find one who already cares about your customer. The best test is to bring them to three customer conversations before you talk equity. If they’re asking about the customer’s workflow, great. If they’re asking about the tech stack, keep looking. - GTM founders: never outsource your v1 to an agency and call it a product. You can use contractors to prototype, but someone with real ownership of the code has to be in the room when customers react to it. Feedback that doesn’t reach the person writing the code is just noise.
- Both: share one feedback system. One place where every call note, support ticket, and churn reason lands. If the technical founder and the GTM founder are reading different versions of the customer, you don’t have a feedback loop. You have two opinions.
And don’t just count requests. Weigh them. Ten requests from customers outside your ideal profile may matter less than one from the segment you’re trying to grow into. The goal is to understand which problems represent your next stage of growth. The $1M company often runs on one founder’s gut. The $10M company runs on both founders hearing the same customer and arguing about it productively.
Design partners: yes, you need them. No, you shouldn’t pay them.
A design partner is a customer who agrees to build the product with you. They have early access in exchange for real usage, real data, and brutally honest feedback. They are the most concentrated feedback loop you will ever have. Treat them that way.
Do you need one? If you’re pre-product or entering a new segment on your way from $1M to $10M, yes. The customers who got you to $1M will tell you how to make the current product better. Design partners in your next segment will tell you what the next product needs to be. Those are very different answers.
Should you pay them? My take: don’t pay them in cash. I want design partners who have a real stake in whether the product works. Ideally, they’re paying something, even if it’s heavily discounted. That gives you a stronger signal of whether the problem is important enough to spend money solving. Give them steep discounts, locked-in pricing, roadmap influence, direct access to the founders, and their logo on the case study when it works.
Timing matters. Bring them in before you write production code for anything new. If you’re bringing in design partners after you’ve built the thing, they’re beta testers, not partners.
How it looks in action:
- Pick 3-5 people, not 15. You need depth, not breadth. More than five and you can’t give each one real attention.
- Recruit for pain, not logos. The best design partner has the problem badly enough to change how they work. A famous brand that’s mildly curious will waste your time.
- Write down the deal. A one-page agreement: what they get, what they owe you (weekly usage, a biweekly call, permission to see their data), and when it ends (usually 90 days).
- Set a conversion date up front. Agree on day one what happens at the end: they convert to a paid contract at a pre-agreed price, or you both walk away. No conversion means no validation.
- Run a fixed weekly cadence. Same day, same time, 30 minutes. Show them what changed because of their last feedback. When they see their input in the product, they give you more.
The last point is the whole game. A design partnership is a feedback loop with a visible return. If they can’t see their fingerprints on the product, they’ll stop showing up. This is also where founders have to be willing to hear something uncomfortable. The customers they’re trying to reach next may need a different product experience than the one their earliest customers loved. That’s exactly what a good design partnership should help uncover.
Your 12-month roadmap is fiction. Plan in 6-week bets.
In the AI era, the ground moves under you every few months. A capability you spent a quarter building ships as a free feature in a foundation model. A competitor that didn’t exist in January raises a Series A in June. Your customers’ expectations reset every time they try a new tool.
That breaks the traditional roadmap in three ways. Building is cheaper, so the hard part is no longer can we build it but should we. Features commoditize fast, so whatever you ship has a shorter shelf life. And customers ask for “AI” without knowing what problem they want it to solve.
The danger for a growing company is spending months extending the product that got it to $1M while the market is moving toward something else. A roadmap built around last year’s customer requests can keep the team busy without moving the business closer to $10M.
Here’s how I’d run it:
- Commit to problems, not features. Your long-term roadmap should be a list of customer problems ranked by pain and revenue impact. The solutions stay flexible because the best solution in March may be obsolete by September.
- Plan in 6-week cycles with a hard review at the end. Each cycle is a bet with a stated hypothesis: “If we ship X, customers will do Y, measured by Z.” At the end, you check Y and Z against real customer behavior, then double down or kill it.
- Ask “what happens when the model gets better?” for every bet. If a better model makes your feature irrelevant, don’t build it. If a better model makes your feature more valuable, that’s where you invest. Build on your proprietary data, workflow, and customer relationships, not on a temporary gap in model capability.
- Never take “we want AI” at face value. When a customer asks for AI, ask what they’d do with the hour it saves them. The answer is the actual feature. Usually it’s less flashy and more valuable.
- Ship rough, measure fast. Because building is cheap, the expensive mistake is polishing something nobody uses. Get a working version in front of design partners within days, watch what they actually do with it, and let usage tell you what deserves polish.
The roadmap stops being a promise and becomes a learning system. Every cycle should end with the team knowing something new about the customer that it didn’t know six weeks before.
Two more rules I’d hold firm on:
- Watch what they do, not just what they say. Customers are great at describing pain and terrible at designing solutions. Use their words to find the problem and their behavior to judge the solution.
- Talk to the customers who left. Churned customers are the most honest feedback you’ll get, and the most ignored. Every churn gets a 20-minute conversation, run by a founder until you’re past $10M.
What Gets You to $10M
Getting to $1M is about finding a problem a few customers care about desperately. Getting to $10M is about finding out, again and again, what the next set of customers needs, and being willing to rebuild the product you love to give it to them.
The founders who make that jump aren’t the ones with the best first product. They’re the ones with the best feedback loop.
