The Minimum Viable Sales Playbook for SaaS Founders

Why 'just wing it' stops working around deal five

Early sales conversations for a new SaaS product tend to go fine on instinct. The founder knows the product cold, the prospect is usually warm (a referral, a waitlist signup, someone who found the product themselves), and the call is really just two people talking shop. This works for the first handful of deals and then quietly stops working.

The failure shows up as inconsistency: some calls run 20 minutes and close, others run 90 minutes and go nowhere, and there is no way to tell in advance which is which. That inconsistency is not a talent problem. It is the absence of a playbook — a repeatable set of questions, criteria, and stage definitions that turn selling from an improvised conversation into a process you can run, measure, and eventually hand to someone else.

Discovery questions are a filter, not small talk

The purpose of a discovery call is not to describe the product. It is to determine, as quickly and honestly as possible, whether this prospect has a problem worth solving, a way to pay for the solution, and a plausible path to a decision. Every question on the call should map to one of those three things.

A minimum viable set covers: the specific problem and its cost today (in time, money, or risk), who else is affected by it, what they have already tried, who is involved in deciding, what budget or approval process exists, and what would need to be true for them to move forward. If a call ends and you cannot answer these six things, the call did not do its job, regardless of how pleasant it was.

Qualification criteria: writing down what a 'good deal' means

Most early-stage founders qualify prospects on vibes — enthusiasm on the call, a fast reply, a senior-sounding title. Vibes correlate poorly with deals that actually close. Qualification criteria replace vibes with a short, explicit checklist applied the same way to every prospect: does the problem match what the product actually solves, is there budget authority in the room or a credible path to it, is there a timeline driven by something real, and is the company a shape the product currently serves well.

Writing these criteria down does two things. It stops the pipeline from filling up with deals that feel active but are not, and it gives you language to disqualify politely and early instead of dragging unlikely deals through six weeks of calls.

Pipeline stages should describe the buyer's commitment, not your activity

A common mistake is naming stages after what the seller did ("Demo sent," "Proposal emailed") rather than what the buyer has actually agreed to. Activity-based stages make the pipeline look busy and tell you almost nothing about whether a deal will close. Commitment-based stages track what the prospect has committed to, which is a much better predictor.

A basic five-stage structure works for most early SaaS pipelines: Discovery Booked, Qualified, Solution Agreed, Commercials in Review, Verbal Commit. Each stage should have a one-sentence definition of what must be true for a deal to sit there, which removes the guesswork of "is this really a Stage 3 or am I being optimistic."

Defining 'next step' so deals stop going quiet

The single biggest cause of stalled pipelines is a vague or missing next step. "They're going to think about it" is not a next step — it has no date, no owner, and no defined action. A real next step names a specific action, a specific date, and a specific person responsible, on both sides.

Build this into the playbook as a rule, not a preference: no call ends, and no deal stays in a stage, without a next step that meets that bar. If a deal cannot produce one, that is itself useful information — it usually means the deal is not as real as it looks and should be marked stalled or disqualified rather than left to rot in the pipeline. Use the Sales Playbook & Discovery Toolkit to put these stage definitions, questions, and follow-up templates in writing before your next call.