How Do You Validate a New Product or MVP Before Scaling?
TL;DR
Recruit 5–10 design partners before you build more or scale outbound. Design partners validate your product mechanism and hand you the customer's actual vocabulary — in our campaigns this outreach gets a 10–20% warm reply rate versus 2–7% for standard outbound. It turns "guessing at scale" into a validated, evidence-backed GTM motion.
The Evidence: Why "Learning Before Scaling" Outperforms Generic Outbound
Scaling outbound before you have design partners is a fast way to burn your reputation with your Ideal Customer Profile (ICP). Most "decent" outbound campaigns see a 1–2% warm reply rate, while exceptional ones hit 7%. Design partner outreach, however, operates on a different mechanism: curiosity and collaboration rather than a hard sell.
In our analysis of early-stage GTM motions, the difference in engagement is stark:
| Metric | Standard Outbound Campaign | Design Partner Validation |
|---|---|---|
| Warm Reply Rate | 2% – 7% | 10% – 20% |
| Primary Goal | Direct sale / demo | Problem validation & feedback |
| Core Message | Value prop (e.g., "save 10 hours") | Concept validation & "Try for free" |
| Long-term Asset | Sales pipeline | Verified language and use cases |
What "Validation" Actually Means (It's Not a Survey)
Most founders validate by asking "would you use this?" — and everyone says yes, because saying yes is free. Real validation has a higher bar. A product, MVP, or feature is validated when three things happen on a live call:
- The prospect describes the problem unprompted, in their own words, before you pitch anything.
- They engage with the mechanism — they ask how it plugs into their stack, not whether it's "interesting."
- They commit something — time for a second call, access to their data, or a spot on your early-adopter list.
If you can't get five people to do those three things, the feature doesn't need to exist yet. That's the answer to "how do I validate if we need this feature" — not a roadmap vote, not a survey, five calls.
The Mechanism: Capturing the "Exact Sentences" of the Buyer
The real value of a design partner isn't just the early feedback on your MVP — it's the linguistic data they provide. Founders often guess at the "pain" their product solves, but during design partner calls, potential users hand you the exact sentences they use to describe their problems.
When you take those exact phrases and put them into your outbound messaging and blog posts, you stop sounding like a content marketer and start sounding like a peer. This shifts your outreach from a "guessing at scale" exercise into a targeted strike on a verified pain point.
Identifying the right partners
Don't just aim for "Decision Makers." Find the direct users of your product.
- If you are building a customer service tool, talk to first-line reps.
- If you are building a data visualization tool, talk to middle management.
The "Kill the Word" outreach strategy
The shorter the message, the better the reply rate. Your outreach should be written below a C1 level — simple, extremely skimmable, and focused on the product's function rather than high-level "value". People don't read outbound; they skim it.
Takeaway: Validate the Vocabulary Before You Validate the Roadmap
Before you build the next feature or increase your outbound volume, review your current messaging. If your copy is filled with "transformative" or "unlocking potential," you are using marketing-speak, not buyer-speak — which means your validation is built on your words, not theirs.
Schedule five design partner calls this week. Don't sell. Just demo the MVP and listen for the specific phrases they use to describe their friction. Those sentences are your validation evidence — and your next six months of high-converting ad copy.
Frequently Asked Questions
How do I validate if we need a specific feature?Run five design partner calls and demo the feature in context. If prospects describe the problem unprompted and ask implementation questions ("does it sync back to the CRM?"), build it. If they say "interesting" and change the subject, kill it.
How many design partners do I need to validate an MVP?Five to ten. Below five you're pattern-matching on noise; above ten you're delaying the decision. The signal you're looking for — repeated problem language and unprompted mechanism questions — usually appears by call four or five.
What is the main goal of a design partner call?It accomplishes three things: instant feedback for product implementation, validation that the idea is worth your time, and a "ready-to-buy" list of early adopters for when the MVP goes live.
How do I position the product to a design partner?Position what the product is doing (the mechanism) rather than the broad value. Instead of saying "save 10 hours a week," explain how the tool "plugs into the CRM and allows you to build data charts in seconds".
Why is the reply rate higher for design partner outreach?Because you aren't asking for money; you're asking for expertise and offering a chance to shape a solution for free. It lowers the barrier to entry for a busy professional to say "yes" to a call.
Can I use design partner feedback for content marketing?Absolutely. The exact language your design partners use to describe their struggles should become the subheadings and hooks for your blog posts and LinkedIn content.
If you want the specific outreach templates we use to hit those 20% reply rates, I'm happy to share them – just reach out :) ~ Will
