A verbal yes is a signal, not a commitment
A deal is not committed because the buyer says yes. A deal is committed when buyer behaviour demonstrates priority, power, process and progress.
A verbal yes tells you the buyer may prefer you. It does not tell you whether the project will outrank the other initiatives competing for the same budget, executive attention, legal capacity or signature.
The playbook therefore manages six things simultaneously — priority, power, plan, commercials, paper and signature — rather than treating proposal → negotiation → signature as automatic progression.
Entry gate — is this actually a signature deal?
Do not put every positive opportunity into a closing motion. Before treating a deal as late-stage, confirm all eight:
| Question | Required evidence |
|---|---|
| Problem | Buyer agrees there is a problem worth solving |
| Solution | Buyer considers us a viable / preferred solution |
| Power | Economic buyer / signer is identified |
| Money | Budget exists, or the path to budget is known |
| Priority | Project is sufficiently high on the customer's internal priority list |
| Timing | There is a buyer-side reason to act |
| Process | Decision and approval process is understood |
| Champion | Someone inside is actively helping move the deal |
Progress should be based on what has been obtained from the buyer, not simply on which seller activity happened next — power agreement, commercial agreement and vendor approval are distinct gates.
Never accept these as sufficient evidence
- “They really like us.”
- “The demo went great.”
- “They said we're their preferred vendor.”
- “They want to do it this quarter.”
- “My champion says the CFO is aligned.”
- “Legal has the contract.”
- “They said they will sign.”
These are signals. They are not commitments.
Discover the second competition: their priority list
Most sales teams investigate us vs competitor A vs competitor B. Late-stage deals are often actually competing against our project vs the ERP implementation vs hiring 20 people vs cost reduction vs doing nothing.
You need to know not only where you rank in the buying process, but where the project ranks in the buyer's portfolio of priorities. Deals go from expected signature to “on hold” in days when ownership reprioritises.
“What are the other two or three projects competing for budget or executive attention with this one?”
“If something had to move out of this quarter, what would determine which project moved?”
“Who can reset that priority order?”
Capture
| Field | Answer |
|---|---|
| Our current priority | #___ |
| Competing initiative 1 | — |
| Competing initiative 2 | — |
| Competing initiative 3 | — |
| Person controlling priority | — |
| Last priority reset | — |
| Next likely reset | — |
You know everything about your competition but cannot name the customer's competing internal initiatives.
Map power and multi-thread the deal
Never allow a meaningful late-stage opportunity to depend entirely on one person. Map at minimum:
| Role | Person | Engaged? | What they care about |
|---|---|---|---|
| Champion | — | — | — |
| Economic buyer | — | — | — |
| Business owner | — | — | — |
| Finance | — | — | — |
| Procurement | — | — | — |
| Legal | — | — | — |
| IT / Security | — | — | — |
| Executive signer | — | — | — |
| Potential blocker | — | — | — |
Gong's analysis of 1.8 million opportunities found successful deals had roughly twice as many buyer contacts as unsuccessful ones, and its executive-selling research puts $50K–$250K won deals at ten or more stakeholders. Treat those as directional vendor research rather than universal benchmarks — but the operational implication is strong: single-threading is deal risk.
Multi-threading does not mean bypassing your champion
Use your champion to orchestrate access: champion → power → functional stakeholders → approval stakeholders. Help them make introductions; ghostwrite the internal email if necessary.
If my champion disappeared tomorrow, could this deal still close? If the answer is no, the deal is fragile.
Establish the buyer's real timeline
Never open with “Can you sign by September 30?” Start with “When do you need the solution operational?” — then understand why. Anchor dates around the buyer's compelling event, not the seller's quarter.
Common real drivers: an existing contract expires, a regulatory deadline, budget expiry, a project launch, a hiring wave, a board commitment, a migration deadline, accumulating operational cost, or a commercial incentive that genuinely expires.
Timeline strength
“Contract expires + €40k/month cost of inaction” is far stronger than “we would like to implement in Q4”.
Build the mutual action plan
A MAP is not your sales checklist shared with the prospect. It is the buyer's path from decision to successful implementation, jointly managed by both organisations. Outreach reports 26% higher win rates when AEs engage buyers with a MAP — again, directional vendor data.
The critical implementation point: the buyer must edit the plan and participate in building it. Otherwise it becomes a seller document the customer ignores.
Start with the outcome
[Customer] wants to achieve [outcome] by [date] because [business reason].
Then the milestones
| Milestone | Buyer owner | Seller owner | Due | Status |
|---|---|---|---|---|
| Business case confirmed | — | — | — | — |
| Economic buyer approval | — | — | — | — |
| Final scope | — | — | — | — |
| Commercial agreement | — | — | — | — |
| Security review started | — | — | — | — |
| Security approved | — | — | — | — |
| Procurement onboarding | — | — | — | — |
| Contract first redlines | — | — | — | — |
| Contract final redlines | — | — | — | — |
| Legal approval | — | — | — | — |
| PO / vendor setup | — | — | — | — |
| Signature | — | — | — | — |
| Kickoff | — | — | — | — |
| Go-live | — | — | — | — |
Keep it practical — roughly 6–20 meaningful steps, not a 30-step bureaucratic project plan.
Every milestone has one outcome, one owner, one date. No owner = not a plan. No date = not a commitment.
Work backwards from signature
Do not forecast forward — “legal has it, so hopefully we'll have it next week”. Reverse-engineer the date. For a target signature of 24 September:
Treat the week before end of quarter as the practical signature deadline and keep the final week as buffer.
The close date is an output of the buying process, not an input from the seller's forecast.
If the remaining approval process takes four weeks, a close date two weeks away is fiction unless something in that process changes.
Get commercial agreement before procurement destroys value
Commercial agreement means the person with power has agreed that the solution, scope and commercial structure are worth the money. It does not mean “we sent them pricing”.
Before deep contract negotiation, know: scope, quantity, contract duration, price, billing structure, payment timing, implementation, material commercial exceptions and target signature date.
“Before I take this internally, are there any other commercial terms you expect your team to ask us for?”
This reduces death by a thousand cuts.
Negotiate with get–give, not give–hope
Never make an unconditional concession. If they want a lower price, better payment terms, a shorter commitment, free implementation, expanded scope, a special SLA or a liability change — receive something in return.
Exchange currencies
Not this
“Okay, I can probably get you 10%.”
This
“If getting closer to that price is important, there are a few things we can change. If we move to annual prepayment and a two-year commitment, I can see what flexibility that gives us.”
Never pay the buyer for a promise. A discount in exchange for “we'll try to sign this month” is not an exchange.
Open the paper process early
“Walk me through everything that must happen internally between saying yes to the commercial proposal and someone signing the contract.”
Then probe
- Whose paper do we use?
- Does procurement need competitive bids?
- Is there vendor onboarding?
- Security questionnaire? DPA? DPIA? InfoSec review?
- Legal review? Finance approval? PO? Board approval?
- Who signs, and are there signature thresholds?
- Are any approvers on holiday?
- How long did the last similar purchase take?
The biggest mistake is discovering these sequentially.
Run vendor approval in parallel
Bad: commercial → security → procurement → legal → signature. Better:
agreement
→ Signature
Four workstreams opened concurrently, not sequentially
Assign separate threads
- AE ↔ Champion
- Legal ↔ Legal
- Security ↔ Security
- Finance ↔ Finance
- Procurement ↔ Procurement
The AE remains the orchestrator.
Create redline deadlines
“Legal is reviewing it” is not a status. Break contract execution into milestones, and schedule the legal-to-legal meeting in advance so outstanding disagreements have a forcing event rather than drifting through email.
This is an example, not a universal SLA — enterprise, regulated and public-sector processes may require far longer.
Put dates on the components of legal review, instead of one date on “contract signed”.
Control the last 72 hours
Once all substantive approvals are complete, explicitly verify signature mechanics.
“Once the document reaches [signer], is there anything else that can prevent them from executing it?”
“When exactly should they receive it?”
Do not discover at 16:30 on Friday that the CFO signs contracts only on Tuesdays.
Inspect every late-stage deal weekly
A MAP nobody inspects becomes documentation rather than control. Inspect weekly, and act the same day an agreed milestone slips.
| Dimension | The question |
|---|---|
| Priority | Has customer priority changed? |
| Power | Has the economic buyer acted? |
| People | Are we sufficiently multi-threaded? |
| Plan | Did the last MAP milestone happen? |
| Paper | Which approval workstreams are open? |
| Timing | Is the signature date still mathematically possible? |
| Risk | What new fact could kill the deal? |
| Action | What must happen next, by whom, by when? |
Stall protocol
A missed MAP milestone is not merely an admin issue. It is information.
| Event | Response |
|---|---|
| First miss | Contact the owner the same day. Ask what changed. |
| Second miss | Requalify priority, timeline, power and competing projects. Bring in senior stakeholders where appropriate. |
| Repeated miss | Move the forecast, unless there is new buyer-side evidence. |
Do not compensate for declining buyer behaviour by increasing seller activity. Ten follow-up emails do not equal progress.
Forecast from evidence
Replace rep confidence with buyer evidence. Strip verbal intent out of committed forecasting and require buyer-side actions instead.
Strong buyer evidence
- Economic buyer attended
- Buyer introduced procurement
- Security review launched
- Legal exchanged redlines
- Customer edited the MAP
- Implementation date agreed
- Budget approved
- Signer identified
- PO created
- Buyer completed agreed milestones
Weak evidence
- “Sounds good”
- Verbal enthusiasm
- Repeated promise
- Seller-generated proposal
- Rep forecast category
- Number of follow-ups
- Discount requested
Deal signature score
Score each signal 0 or 1. Tick what the buyer has actually demonstrated — not what you expect them to do.
Interpretation
| Score | Band | What it means |
|---|---|---|
| 14–16 | Signature path is strong | Execution risk remains, but the deal has evidence. |
| 11–13 | Closeable but exposed | The manager should know exactly which gaps remain. |
| 8–10 | At risk | Do not trust the stated close date. |
| 0–7 | Not a signature deal | Move it out of commit unless exceptional evidence exists. |
This scoring is an operating framework synthesised for this playbook, not a benchmark validated by the cited research.
CRM minimum data
Do not create 40 mandatory properties. For late-stage opportunities, track these four groups.
Deal control
- Target signature date
- Buyer compelling event
- Economic buyer
- Champion
- Signer
- Current priority
- Competing initiatives
- Last buyer-side action
- Next buyer-side action
- Next action date
Approval process
- Commercial agreement: Y/N
- Security status
- Legal status
- Procurement status
- Vendor onboarding status
MAP
- MAP active: Y/N
- MAP last milestone
- MAP next milestone
- MAP next milestone date
- MAP slipped: Y/N
Risk
- Primary deal risk
- Days since meaningful buyer action
- Number of buyer stakeholders engaged
Manager deal review
Do not ask “what's happening with Acme?”. Ask these twelve.
- Why must they act?
- Why now?
- Who has power?
- Where does this project rank internally?
- What other projects compete with it?
- What has the buyer done in the last 14 days?
- What is the next buyer commitment?
- What remains in procurement, security and legal?
- Who signs?
- Show me the work-back math to the signature date.
- What happens if the next milestone slips?
- What fact would make us move this out of commit today?
A manager should be able to reconstruct the close path without the AE saying “I feel good about it”.
The one-page signature plan
Maintain this for every material late-stage deal.
Customer
- Company
- Deal
- Value
- Target signature
- Target go-live
Why they buy
- Business problem
- Expected outcome
- Cost of inaction
- Compelling event
Priority
- Project priority
- Competing initiative #1
- Competing initiative #2
- Competing initiative #3
- Who sets priority
Power
- Champion
- Economic buyer
- Signer
- Finance
- Procurement
- Legal
- Security
- Blocker
Commercials
- Scope
- Price
- Term
- Payment
- Open negotiations
- Potential give
- Required get
Paper process
- Security
- Procurement
- Legal
- PO / vendor setup
- Signature mechanism
Work-back
- Date
- Milestone
- Owner
- Status
Risk
- Biggest deal risk
- Latest buyer-side evidence
- What would cause the deal to slip
- Replacement / mitigation
The signature commandments
- Verbal yes ≠ commitment.
- Vendor preference ≠ project priority.
- Know the buyer's internal competition, not only your competitors.
- Never depend on one champion.
- Get to power before the final week.
- Anchor timing to a buyer outcome, not your quarter.
- Co-build the MAP; never just send one.
- Every critical step gets an owner and a date.
- Reverse-engineer the close date.
- Run security, procurement and legal in parallel.
- Put deadlines inside the legal process.
- Trade concessions; don't donate them.
- Inspect buyer behaviour, not seller effort.
- A slipped milestone is a qualification signal.
- Forecast what the buyer has done, not what they said.
- A deal isn't done until the signature is actually executed.
In one line
Do not chase a signature. Orchestrate the buying process until signing becomes the natural final step.
Where this comes from
This playbook synthesises published sales-process material from 30MPC (late-stage gates, work-back scheduling, redline deadlines, parallel vendor approval, the four commercial levers), Gong (buyer-contact and stakeholder-count research), Outreach and Salesforce (mutual action plans anchored on the buyer's compelling event), and GTMcraft (co-authored MAPs, weekly inspection, step count). Vendor-published win-rate and stakeholder figures are directional research from parties with a commercial interest, not universal benchmarks — treat them as an argument for the behaviour, not as a target. The 16-point signature score is an operating framework assembled for this playbook and has not been validated against outcome data.