What selling actually is
Most founders dread sales because they're imagining a stereotype: persuasion, pressure, and a script. The version that works for a small software business is much duller. You find people who have a problem you solve, you help them work out whether you solve it for them, and you make the decision easy.
That reframing matters practically, not just emotionally. If the job is helping someone decide, then "no" is a successful outcome — it's a decision reached quickly, at low cost to both of you. If the job is persuasion, "no" is a failure to be argued with, which is how people end up with customers who churn in two months.
The five stages
| Stage | Goal | Done when |
|---|---|---|
| Prospect | Find people who plausibly have the problem | You have a named list, not a category |
| Qualify | Check they have it, and can decide | You know their problem, budget, and process |
| Demonstrate | Show it solving their problem | They've seen their own case, not a generic tour |
| Handle objections | Surface and answer the real hesitation | The unstated worry has been said out loud |
| Close | Make the decision easy | There's a date, a price, and a next action |
The stage founders skip is qualification, because it feels like turning away interest. It's the opposite: an unqualified prospect consumes weeks of demos and follow-ups and then reveals they never had a budget. Ten minutes of questions early saves that entirely.
Demonstrating without touring
The default demo is a tour of features in the order they appear in the navigation. It's easy to give and almost useless, because the buyer has to translate everything into their own situation while you talk.
- Ask what they'd do first, then show that. Nothing else, until it's answered
- Use their data, or realistic data from their world — their client names, their kind of bookings
- Show the thing that goes wrong today, going right. That's the whole demo, and it can take four minutes
- Stop talking after each step and let them ask. A demo with no questions is a presentation, and presentations don't close
- Don't show the roadmap. Selling what doesn't exist creates a customer who's disappointed on arrival
Objections are information
An objection is the buyer telling you what's blocking them. Argued with, it hardens. Asked about, it usually turns out to be something else.
| What they say | Often means | Ask |
|---|---|---|
| "It's too expensive" | I don't see the value yet | "Compared to what?" |
| "I need to think about it" | There's an unspoken worry | "What's the part you're unsure about?" |
| "Send me some information" | This is a polite no | "Is this a no for now, or a not-yet?" |
| "We already use X" | Switching cost feels high | "What does X do well? What's the gap?" |
| "I need to ask my partner" | You're not talking to the decider | "What will they want to know?" |
The last row is the expensive one. Discovering at the close that your contact can't decide means the real conversation hasn't started. Ask early, plainly: "who else is involved in a decision like this?"
Disqualifying is the highest-value move
The scarce resource in early sales is your attention. Every hour spent on someone who will never buy is an hour not spent on someone who would — and worse, a bad-fit customer who does buy costs support time and churns, taking a reference with them.
- They don't have the problem — they have a neighbouring one you don't solve
- The problem is real but small enough that the workaround is fine
- They can't decide and won't introduce you to whoever can
- They want a different product and are hoping you'll build it
- The timeline is "maybe next year", which is a no with a calendar attached
Common mistakes
- Demoing before qualifying, which forces a feature tour
- Arguing with an objection instead of asking what's underneath it
- Selling the roadmap, so the product disappoints on day one
- Discovering at the close that your contact can't make the decision
- Chasing every interested party because turning anyone away feels wasteful
Key takeaways
- Selling is helping someone decide; "no" reached quickly is a good outcome
- Qualification is the stage founders skip and the one that saves the most time
- Show their problem being solved, with their data, in four minutes
- Objections are information — ask what's underneath before answering
Try it yourself
Take your next sales conversation and spend the first ten minutes asking only about how they work today. Notice how much shorter and more specific the demo becomes afterwards.