
Pre-Revenue Sales: Building Before You Have a Product
You don't need a finished product to start selling. You need a clear guess and the patience to test it through honest conversations.
Here's a myth I'd love to retire: that you need a finished product before you can sell anything. You don't. What you need is a clear guess about who has a problem, what that problem costs them and whether they'd pay to make it go away.
Selling before you have revenue isn't really about closing deals. It's about testing that guess through honest conversations. And I believe it's one of the most valuable things a new founder can spend time on, because what you learn will shape your product, your pricing and your message.
Here's a simple three-step way to do it, plus the one mistake that trips up almost everyone.
Early selling is really careful listening
When you don't have a product yet, the goal of a sales conversation changes. You aren't trying to convince anyone. You're trying to learn.
That takes some pressure off. You can be curious instead of persuasive. You can ask how people handle the problem today, what it costs them and what they've already tried. And you can let them do most of the talking.
The founders who skip this step often build in a quiet room and launch to silence. Their product might be fine. They just never checked whether it solved a problem people truly cared about.
Start by proving the problem is real
The first step is all about the problem, not your idea. Reach out to people you think might have it and ask open questions:
- What's the hardest part of this for you right now?
- How are you handling it today?
- What have you tried that didn't work?
- What would make this feel solved?
Resist the urge to pitch. If people struggle to describe the problem, or shrug when you ask about it, that's useful news. It may mean your guess needs to change, and it's much better to learn that now than after months of building.
Talk with enough people that patterns start to show up. When you keep hearing the same frustration in the same words, you're onto something.
Then test your idea for solving it
Once you understand the problem, describe how you plan to solve it. Keep it simple - a sketch, a short description or a rough mockup is plenty.
Then ask questions that invite honesty:
- Would this make a real difference for you?
- What would stop you from buying it?
- What would you expect to pay for something like this?
Listen for hesitation as much as excitement. The worries people raise now are a gift. They tell you what to build, what to explain better and what to leave out.
Ask for a small real commitment
The last step is the one most founders avoid. Ask for something real: a signed letter of intent, a small deposit or an agreement to try an early version.
It isn't about the money. It's about the signal. Kind people will say nice things about your idea all day long. A commitment shows they mean it.
Interest sounds like let me know when it's ready. Intent sounds like sign me up today.
This is where many founders get tricked. Interest sounds like let me know when it's ready. Intent sounds like sign me up today. Both feel good in the moment, but only intent tells you there's demand.
A quick picture of early selling done well
Imagine a founder in Provo with an idea for simple booking software for mobile dog groomers. Before writing much code, she calls groomers across the valley and asks how they schedule clients today. She hears the same frustration about last-minute cancellations again and again. She sketches a solution, shows it to the groomers who cared most and asks a handful of them to pay a small deposit for early access. Now she's building for real people who have already said yes.
Try this this week
- Write down your best guess about who has the problem and what it costs them.
- Make a list of ten people who might have that problem and reach out to three.
- Draft four open questions about the problem that don't mention your idea at all.
- Decide what small commitment you'll ask for once someone shows strong interest.
