How to Sell Before the Product Is Built

TL;DR: You sell before the product is built by selling the problem, not the software — running deep customer discovery, signing paid design partners, and de-risking the buy with staged pilots. Based on 200+ founder interviews on the PMF Show, the founders who do this best interview dozens of buyers before writing a line of code (one did 80), charge design partners from day one, and offer proofs-of-concept in production to prove confidence. The product follows the commitments, not the other way around.

After interviewing 200+ founders on the PMF Show, one counterintuitive truth keeps surfacing: the strongest startups secure customer commitment before the product exists. Selling before you build isn't a trick — it's a discipline of discovery, design partnerships, and risk reduction that turns a vision into signed pilots. This post lays out exactly how five founders sold the problem, got paid pre-product, and let real customers shape what got built.

Why should you sell before the product is built?

Because building before you've validated demand is the fastest way to waste a seed round. According to Omar Haroun, founder of Eudia, the single biggest lesson from three startups and fifteen years of building is that selling and validating should come first.

"I spent the next few months interviewing eighty chief legal officers before even writing any code and figuring out the product. Market timing is the most important factor in your success and the one that's the least in your control." — Omar Haroun, founder of Eudia

Eighty customer interviews before a single line of code is not analysis paralysis — it's how Haroun confirmed both the "why" and the "why now" of his market. He extended that discipline into the company itself, deliberately resisting the urge to scale until the value was undeniable.

"Way more startups die from prematurely scaling than from really deeply understanding what they can uniquely provide that their customer is desperate for. We spent basically the entire seed round helping five to ten customers with their real problems. We would spend three to six months with them before even they were a customer." — Omar Haroun, founder of Eudia

Key stat: Eudia conducted 80 chief-legal-officer interviews before writing any code, and spent 3–6 months working with each customer before they ever paid.

How do you get customers to commit without a finished product?

You sign paid design partners and let the contract enforce collaboration. Helen Hastings raised $4.7M for Quanta while still pre-product and pre-revenue, then onboarded design partners before the real software existed — by partnering with another firm behind the scenes to deliver the actual work.

"The best way to get started with design partners is not by having everything built first, but getting that MVP, that working experience. So we started building while also partnering with another firm behind the scenes." — Helen Hastings, founder of Quanta

Crucially, those design partners paid from day one, and the contract obligated them to give feedback. Hastings structured the relationship so commitment ran both ways:

"Paying for sure. Paying from the beginning. I think that is really important to make sure that the customer says this thing is valuable enough for me to pay. But in the contract, there was also a clause that the design partner is committed to giving feedback — a bi-weekly call or a monthly call — and there is a discount for being a design partner, but the discount had a time limit." — Helen Hastings, founder of Quanta

The structure is worth copying: payment proves value, a feedback clause guarantees the learning loop, and a time-limited discount rewards early risk without permanently underpricing the product.

Key stat: Quanta raised $4.7M pre-product and pre-revenue, and signed paid design partners on contracts that required bi-weekly or monthly feedback calls.

How do you make a pre-product enterprise buyer believe you?

You shrink the risk of every step they take. Surojit Chatterjee, founder of Ema, found that the hardest part of selling pre-proof was overcoming an enterprise buyer's natural skepticism about an unfinished product touching their data.

"The first few customers was probably the biggest hurdle. Why should I believe you? Is your product fully built? Unless I touch your data, I can't really show you a product. So we'll show you the product using lots of proxy data, then very contained POCs and pilots, then maybe a few production systems and keep the blast radius small." — Surojit Chatterjee, founder of Ema

Ema sequenced belief in escalating, low-stakes steps. Bhaskar Sunkara of Bicycle AI took the boldest version of this approach in his AppDynamics days, offering a proof-of-concept directly in the customer's production environment — something competitors considered reckless.

"Why don't we do a POC in production? That was the biggest thing that got people to take notice. Because they're like, they're this sure of what they built. We had nothing to lose." — Bhaskar Sunkara, founder of Bicycle AI

That confidence paid off when Netflix put the product on one of its 100-plus production servers and ran a head-to-head test: the server with the software installed was indistinguishable in performance from the one without it. A pre-product company can't out-credential an incumbent, but it can out-courage one by absorbing the buyer's risk.

Key stat: Bicycle AI's in-production POC was validated when Netflix found zero measurable performance difference across its 100+ live servers.

What do you actually sell when there's no product to demo?

The vision — and then you let the customer build it with you. Omar Haroun of Eudia discovered that his earliest customers had thought more deeply about the future than his own team had, so the winning move was to listen rather than dictate.

"Part of it was realizing the vision that they had more than we had. The chief legal officers were the ones who had really spent the last few years thinking deeply about how to transform their teams. The biggest wins we've had is when we listened rather than, oh, we know what's best for you." — Omar Haroun, founder of Eudia

This reframes pre-product selling entirely: you're not pitching a roadmap you invented, you're co-authoring it with buyers who are desperate for the outcome. Ema learned the same lesson the hard way, having first tried to sell a horizontal platform with the wrong showcase applications before listening their way into the use cases that resonated. Selling the problem keeps you flexible enough to follow the demand to where it actually is.

Key stat: Eudia's biggest product wins came from co-designing with customers — the founders treated buyers as the source of the vision, not just validators of it.

How do you know pre-product selling is working?

When discovery conversations turn into commitments and buyers start pulling. The clearest signal in our interviews is a paying design partner who agrees to a feedback cadence — as Quanta structured — because money plus a recurring meeting proves both value and engagement. The second signal is when a contained pilot succeeds so cleanly that the buyer expands on their own, the way Ema's "small blast radius" pilots built confidence step by step until customers trusted production access. The pattern across all 200+ interviews is the same: pre-product selling is working when the customer is doing some of the selling for you — committing budget, committing time, and asking for more.

Key stat: Across the PMF Show's 200+ interviews, the most durable pre-product commitment is a paid design partner bound by a contractual feedback cadence.

Key Takeaways: How to Sell Before You Build

1. Validate before you build. Eudia ran 80 customer interviews before writing code — more startups die from premature scaling than from over-researching. 2. Charge design partners from day one. Quanta required payment from the start because a paying customer proves the value is real. 3. Put a feedback clause in the contract. Quanta's design-partner deals mandated bi-weekly or monthly calls, guaranteeing the learning loop. 4. Use a time-limited discount, not permanent underpricing. Reward early risk-takers without anchoring your price too low forever. 5. Shrink the blast radius. Ema staged trust from proxy data to contained POC to production so every customer "yes" was low-risk. 6. Offer to prove it in production. Bicycle AI's willingness to run a live POC inside the customer's environment beat more cautious incumbents. 7. Sell the vision and let customers co-author it. Eudia's biggest wins came from listening to buyers who'd thought harder about the future than the founders had.

FAQ: Common Questions About Selling Before the Product Is Built

Q: How do you sell before the product is built?

A: You sell the problem and the vision, not the software. The PMF Show founders who do this well run deep customer discovery, sign paid design partners, and de-risk pilots with staged proofs-of-concept. Omar Haroun of Eudia interviewed 80 chief legal officers before writing any code.

Q: Should design partners pay before the product exists?

A: Yes. Helen Hastings of Quanta charged design partners from day one because payment is the proof that the value is real. She paired payment with a contractual feedback clause and a time-limited discount to reward early commitment.

Q: How do you convince an enterprise to buy an unfinished product?

A: Reduce their risk at every step. Ema moved buyers from proxy data to contained pilots to limited production access — a "small blast radius." Bicycle AI went further and offered POCs directly in production to prove confidence.

Q: Isn't it risky to sell something you haven't built?

A: The bigger risk is building something nobody wants. As Omar Haroun put it, far more startups die from prematurely scaling than from deeply understanding what their customers are desperate for. Selling first tells you what to build.

Sources: Listen to the Full Founder Stories

• Omar Haroun, Eudia (Season 5) — Eighty customer interviews before any code, and why deep discovery beats premature scaling.
• Helen Hastings, Quanta (Season 5) — Raising $4.7M pre-product and structuring paid design-partner contracts with feedback clauses.
• Surojit Chatterjee, Ema (Season 5) — Staging enterprise trust with proxy data and a "small blast radius" of contained pilots.
• Bhaskar Sunkara, Bicycle AI (Season 5) — Winning enterprise deals by offering proofs-of-concept directly in production.

Last updated: June 2026