Presales playbook
Definition
Presales playbook
A presales playbook is the written, repeatable motion a technical sales team runs before a contract exists: qualify the deal, run discovery, design a solution, prove it works, price it and submit. It stops at signature, where the delivery team takes over.
It is narrower than a sales playbook, which covers the whole commercial relationship, and it is not implementation. Presales owns the questions a buyer asks in the window between first interest and a signed agreement.
The value is consistency. Two engineers facing the same requirement should produce the same architecture, the same assumptions and the same price, or your win rate is measuring luck.
Key takeaways
- The playbook covers qualification through proposal and stops at signature.
- Qualification is the highest value step, because the cheapest bid is the one you decline.
- Every stage needs a written exit test, or deals drift forward unqualified.
- Reusable artefacts, not individual heroics, are what make the motion repeatable.
How it works
A presales playbook works by giving every stage an owner, an artefact and an exit test. Nothing moves forward because somebody feels optimistic; it moves because a named condition has been met and written down where the next person can read it.
| Stage | Artefact | Exit test |
|---|---|---|
| Qualify | Scored opportunity record | Budget, authority and timing confirmed |
| Discover | Requirements and current state notes | Buyer agrees the problem statement |
| Design | Solution outline and assumptions | Technical risks named and owned |
| Prove | Demo or proof of concept plan | Success criteria met in writing |
| Price | Cost model and approvals | Margin inside policy |
| Propose | Proposal and draft scope | Buyer can evaluate it as written |
Artefacts are the asset, not the process diagram. A reference architecture, a question bank, a standard assumptions list and three worked pricing cases do more for a new engineer than any training course — and they survive staff turnover.
The exit tests are what stop the drift. Without them a deal reaches the proposal stage because the calendar moved, not because anybody confirmed a budget, and that is the expensive kind of failure.
Pricing deserves a stage of its own, because it is where presales and finance disagree. Fix the approval path before a live deal needs it, not during.
Qualification is where the playbook earns its keep. An opportunity qualification framework turns that step into a score rather than an opinion, and a score can be audited later.
Upstream, a marketing qualified lead is only a signal. The lead qualification rate tells you how many of those signals survive first contact with a presales engineer.
Downstream, the quote to close rate shows where the motion leaks. A high quote volume with a low close rate usually means qualification is being skipped.
The last artefact is a statement of work (SOW), where presales assumptions stop being optimistic and become contractual.
Public buyers publish the rules a bidder has to answer. Federal Acquisition Regulation subpart 15.3 requires that proposals be evaluated based solely on the factors in the solicitation, which makes the solicitation itself the scoring sheet.
The weighting is published too. Title 41 of the United States Code requires an agency to disclose whether non price factors combined outweigh cost or price, so a bidder can tell whether to compete on capability or on money.
Commercial buyers rarely publish anything that clear — which is why discovery exists at all.
Private tenders borrow the shape without the discipline. You often get a scoring matrix with no weightings attached, which makes the discovery conversation the only place to learn what actually matters.
Examples
Three settings show the same motion at different levels of formality: a United States federal bid, a Philippine contact centre tender, and an enterprise software proof of concept. The stages do not change, only how much of the scoring is published.
United States federal bids. The solicitation lists the evaluation factors and subfactors, and those factors must support meaningful comparison between competing proposals.
A presales team that writes to its own structure rather than the published one loses points it never sees deducted.
A Philippine contact centre tender. A buyer asks six providers for a 200 seat programme.
The playbook decides which questions are answered in writing, which are held for the site visit, and which assumptions enter the pricing model before any discount is discussed.
Enterprise software proof of concept. Success criteria are agreed in writing before the environment is built, with a named buyer sponsor who signs them off. Without that, a proof of concept runs until someone loses interest.
Set a time box and name the exit condition in the same document — a proof that cannot fail is not a proof of anything.
Related terms
- Close plan: the joint schedule of steps to signature, which picks up where the playbook ends.
- Average sales cycle length: the elapsed time this motion is trying to shorten without cutting steps.
- Opportunity qualification framework: the scoring method behind the first stage of the playbook.
- Quote to close rate: the measure that exposes whether qualification is actually being applied.
- Statement of work (SOW): the document where presales assumptions become contractual obligations.
FAQ
How is a presales playbook different from a sales playbook?
A sales playbook covers the whole commercial relationship, including renewal and expansion. A presales playbook covers only the pre-contract motion: qualification, discovery, solution design, proof and proposal. They share artefacts but answer to different measures.
Who owns the playbook?
Usually a presales or solution consulting lead, with sales operations maintaining the artefacts. Ownership matters because an unmaintained playbook is abandoned within two quarters. Give it a review date like any other controlled document.
What goes in a qualification score?
Budget, decision authority, timing, fit against what you actually deliver, and a named internal sponsor. Score them consistently and the pattern in your losses becomes readable within two quarters.
Should every deal get a proof of concept?
No — and offering one by default simply teaches buyers to ask. Reserve it for deals where a specific technical doubt blocks signature, and agree the success criteria in writing first.
How do you keep it current?
Review it after every large loss and every quarter end. Losses tell you which exit test was skipped.
Set out how your presales team works in the Outsource Accelerator provider hubs so buyers can compare it.
Independent
