Proposal design — from verbal yes to countersigned.

What a proposal actually is

A proposal is a written summary of what was already agreed verbally. It is not a pitch. It is not a negotiation document. It is a restatement of the commercial agreement reached on the prior call, with the contract attached.

A buyer who has verbally committed does not need to be re-sold. They need to see, on the page, what they already agreed to, with the legal terms beneath it, and a signature block at the end. The proposal that does this advances. The proposal that tries to do more regresses.

The single most common cause of a deal lost at the proposal stage is the introduction of a claim, price, term, or condition that was not part of the verbal agreement. Introducing a new commercial term produces a 30-50% probability of deal loss at this stage. The buyer identifies the discrepancy, escalates internally with new doubt, and either reopens negotiation or quietly drops the deal.

The proposal-as-summary architecture

The proposal structure that converts at the 70-90% rate has five sections, in this order, with this content:

1. Cover note (3-5 sentences)

A short paragraph at the top, in the customer's language, summarizing what the agreement covers. Not the vendor's product description — the customer's stated problem, the agreed solution, and the explicit next step. The cover note is the one section the economic buyer reads with full attention; everything below it is scanned for discrepancy.

A correctly written cover note references the verbal conversation explicitly. Phrases like "following our call on the 14th" and "as discussed" anchor the document as a restatement rather than a new proposal, and reduce the buyer's instinct to scrutinize each term for departure from prior conversation.

2. Business terms

Price, contract term, payment cadence, and success criteria. One page maximum. The four numbers a procurement officer will extract and enter into their approval system. If the verbal commitment was $60K annual on a 12-month term, this section reads $60K annual on a 12-month term — not $5K monthly, not any restatement that requires the buyer to re-do the arithmetic.

3. Legal terms

The standard contract clauses. Limitation of liability, indemnification, termination, intellectual property, confidentiality, data protection, governing law. Attached as a separate document or appended as an addendum. This is the section the buyer's legal team will review — and it is best presented as a complete, self-contained document rather than embedded in the commercial narrative.

4. Implementation summary

The 30-day post-signature plan. Week one: kickoff, account provisioning, integration setup. Week two: data ingestion, first user training. Week three: production rollout. Week four: first success-criterion checkpoint. This section converts the abstract commitment to a concrete timeline and signals operational seriousness to the technical buyer and end users.

5. Customer-specific addendum

The per-deal customizations agreed verbally. A custom integration requirement, a data residency commitment, a named-account-team request, a phased rollout schedule, a non-standard pilot clause. The addendum exists precisely so the standard business and legal terms above it remain unchanged.

The per-clause architecture

The standard contract clauses appear in every proposal of a given ACV tier and segment. The operational discipline is the negotiable-vs-non-negotiable distinction, established before any proposal goes out:

• Non-negotiable clauses. Limitation of liability cap at prior-12-month fees. IP ownership of the platform. Governing law in the vendor's jurisdiction (for ACVs below approximately $100K — above that, jurisdiction becomes negotiable). Standard data processing addendum for any deal involving PII.
• Negotiable clauses with explicit fallback positions. Termination for convenience (default: not permitted; fallback: 90 days notice with prorated refund). Indemnification scope (default: IP infringement; fallback: third-party data claims). Payment terms (default: net 30; fallback: net 45 enterprise; net 60 executive approval only). Auto-renewal (default: 12-month auto-renew, 60-day opt-out; fallback: opt-in renewal).
• Per-deal customizations. Anything the customer has explicitly requested verbally — captured in the addendum, never silently inserted into the standard clauses.

Pre-classifying every clause compresses the legal review cycle by a factor of two to three. A sales team that walks into review without this classification negotiates each clause as if it were novel, and the deal sits in redlines for 30 to 90 days.

The pricing transparency question

A recurring decision: present the price as a single bundled quote, or as a detailed line-item breakdown. Bundled pricing performs better below approximately $50K ACV, line-item breakdown performs better above approximately $100K, and the $50K-$100K band is segment-dependent.

The mechanism: below $50K, the buyer is typically a department head with discretionary budget authority who wants a single number to approve. Line-item breakdown invites scrutiny of components that are not separately purchasable. Above $100K, the buyer is routing through procurement, which requires line-item breakdown to map against budget categories. A bundled $150K quote that procurement cannot decompose into seat licenses, integration fees, professional services, and support is functionally unapprovable.

Multi-year commitment pricing

A 2-year commitment typically receives a 10-15% per-year discount; a 3-year commitment, 15-25%. Presenting the 1-year price alongside the 2-year and 3-year tiers, with the discount applied at the per-year line, increases close rate by approximately 10-20 percentage points and shifts 20-40% of deals into multi-year commitments. The mechanism is not that multi-year is intrinsically more attractive — the presence of the 2-year and 3-year tiers anchors the 1-year as a premium option, functioning as a pricing-floor anchor as much as a multi-year close lever.

The procurement-navigation pattern

Approximately 30-60% of B2B SaaS deals above $25K ACV require procurement approval. Procurement is operationally distinct from the buyer, the legal reviewer, and the executive approver — a separate workflow with its own SLAs, document requirements, and gating criteria.

The operational handoff: at the point of verbal commitment, the seller asks who handles procurement for contracts of this size, requests an introduction to that contact, and establishes the per-organization procurement timeline. The empirical range across mid-market and enterprise: 14-60 days from proposal sent to procurement clear. Compressing this below 14 days requires either a pre-existing vendor relationship or an explicit executive override.

The procurement-question response template: most procurement teams ask the same 15-25 questions across every vendor onboarding. SOC 2 status, data residency, sub-processor list, security policies, insurance certificates, W-9, banking details, business continuity plan. A vendor that maintains a pre-built procurement response packet — covering 80%+ of standard questions — clears procurement at roughly half the median timeline of a vendor that responds to each question individually.

The legal-redlines process

Per-organization legal review is the second longest-pole step in the workflow. Median: 7-14 days for departmental legal review at mid-market companies, 21-45 days for enterprise review with outside-counsel involvement.

The redline cadence that compresses this timeline: receive redlines, respond within 48 hours with accept/counter/decline per clause, schedule a 30-minute call with the buyer's legal contact to resolve any remaining points. The single-pass redline-then-call pattern resolves approximately 80% of standard mid-market deals. Deals that require a second round are typically the ones where the vendor inserts per-deal custom terms into the standard contract body or where the customer's legal team is reviewing the contract category for the first time.

The explicit-fallback positions established in the per-clause architecture are operationally critical here. A redline the seller can respond to without escalation — because the fallback was pre-approved — turns around in hours. A redline that requires internal escalation to the vendor's general counsel or founder-CEO turns around in days to weeks.

The e-signature handoff

The signature mechanic is not commercially neutral. A contract routed through a managed e-signature platform — the DocuSign-class category — closes at approximately 15-25 percentage points higher rate than a contract sent as a PDF for the buyer to print, sign, and scan. The effect holds across deal sizes and segments.

The mechanism: an e-signature platform routes the signature by role, enforces field completion, tracks per-signer status, and sends automated reminders to non-responding signers. A PDF-and-print flow has none of this and decays at every step — the buyer downloads the PDF, forgets, the signer is on PTO, the scanned copy is missing a page, the document needs to be re-sent.

Routing-by-role is the underestimated lever. A contract sent in explicit sequence — technical reviewer, then legal, then economic buyer — closes at a higher rate than the same contract sent to all three simultaneously. Simultaneous routing produces ambiguity about who signs first, and the deal stalls on the role with the longest queue.

The proposal-expiration date

Every proposal includes an explicit expiration date, typically 14-30 days from sent. The expiration is not a contractual mechanism — pricing rarely actually expires — it is a decision-forcing function. A proposal with no expiration sits indefinitely. A proposal with an expiration 14 days out produces a signature event or an explicit extension request within that window. Proposals with expiration dates close at approximately 15-25 percentage points higher rate than identical proposals without, and median time-to-signature compresses from approximately 35 days to approximately 18 days.

The proposal follow-up cadence

The first 14 days after a proposal is sent are the highest-leverage signature window. The per-day pattern that performs:

• Day 0. Proposal sent. Confirm receipt via separate channel (text or short email).
• Day 1. Light follow-up — one sentence, asking if any questions emerged on first read.
• Day 3. Substantive follow-up — offering to schedule a 15-minute proposal-review call with the champion or the legal contact.
• Day 7. Status check — explicit ask: where is the document in the internal review process.
• Day 10. Escalation prep — if procurement or legal is silent, ask the champion who to ping directly.
• Day 14. Expiration reminder — surface the expiration date, offer to extend if the buyer needs more time.

After day 14, the cadence transitions to a weekly status check, with escalation to the executive sponsor at day 30 if the document has not advanced. Deals not signed by day 45 close at 20-30% conversion, compared to 70-90% in the first 14 days.

The proposal-customer-review meeting

A 30-minute review of the proposal with the customer's core team — champion, legal contact, procurement contact when available — scheduled within the first 7 days of proposal sent increases close rate by approximately 10-20 percentage points and reduces total proposal-to-signature timeline by approximately 30%.

The structure: 10 minutes on cover note, business terms, and implementation summary. 15 minutes for legal-terms questions. 5 minutes to confirm next steps and timeline. The meeting is not a re-pitch — it is an alignment step that surfaces objections before they become redlines and signals to the customer that the seller is available to clear blockers in real time.

The lost-in-procurement pattern

A recurring failure mode: the deal advances cleanly through verbal commitment and proposal-sent, then enters procurement and goes silent for 30-90 days. The champion stops responding because they are not the active reviewer. Procurement is unresponsive. The deal is not lost — but it is not advancing.

The recovery pattern: at the 14-day silence mark, the seller pings the champion with a single specific operational question — current procurement queue position, named reviewer, outstanding document. The question is operational, not commercial; it asks for status visibility, not internal re-selling. Champions reliably respond to operational questions even when they have stopped engaging on commercial ones. The status response identifies the actual blocker, which is then addressable directly.

At the 30-day silence mark, the seller offers to email the procurement contact directly, with the champion CC'd, with a single specific document request. This converts approximately 40-60% of deals lost-in-procurement back to active status.

Common operator failures observed in production

• Proposal-as-pitch. The proposal introduces new commercial claims, pricing tiers, or feature commitments not discussed verbally. Produces 30-50% deal loss at this stage.
• No expiration date. The proposal sits in the buyer's inbox indefinitely. Median time-to-signature extends from 18 days to 35+ days; close rate drops 15-25 percentage points.
• No procurement-navigation plan. The seller sends to the champion and assumes the champion will route internally. The deal enters a procurement silence pattern that takes 30-60 days to recover from.
• No per-clause negotiable-vs-non-negotiable mapping. Every redline produces internal escalation. Legal review cycles extend from 7-14 days to 30-60 days.
• No follow-up cadence. The proposal is sent and the seller waits passively. The 14-day decision window passes without operational pressure. Close rate drops 20-30 percentage points.
• PDF-and-print signature flow. The contract is sent as a PDF rather than routed through a managed e-signature platform. Close rate drops 15-25 percentage points and median signature time doubles.
• Sending the legal contract late. The seller sends the commercial proposal first and the legal contract only after verbal approval of business terms. The legal review then occurs after the buyer has emotionally committed and produces escalated tension on standard clauses that should have been raised earlier.

The pre-proposal checklist

• Verbal commitment confirmed on the prior call — price, term, payment cadence, success criteria all explicit
• Champion identified and confirmed as the internal routing owner
• Procurement contact identified and per-organization procurement timeline estimated
• Legal review contact identified and per-organization redline turnaround estimated
• Per-clause negotiable-vs-non-negotiable mapping pre-classified with explicit fallback positions
• Procurement-response packet ready (SOC 2, data residency, sub-processor list, insurance certificates, W-9)
• E-signature platform configured with role-based routing
• Proposal-expiration date set 14-30 days out
• Follow-up cadence scheduled in CRM through day 30
• 30-minute proposal-review meeting offered within first 7 days

Where this fits in the broader motion

Chapter 04 established multi-thread engagement as the prerequisite for converting champion enthusiasm into organizational commitment. The proposal stage is where multi-thread engagement pays off: deals with engaged technical, economic, and legal threads move through proposal-to-signature in 14-30 days; deals with only a champion thread stall in legal or procurement because no one else has operational urgency.

Chapter 06 covers the founder-led sales discipline through the first $1M ARR. The proposal stage is most often delegated prematurely — the founder closes verbally and hands the proposal to ops to draft. Founder-drafted proposals close at 10-20 percentage points higher rate at the pre-PMF and early-PMF stage, because the founder has the per-buyer context to write the cover note in the customer's language and the per-deal context to map customizations correctly. The proposal stage is the second-highest-leverage application of founder time in the sales motion, after the discovery call itself.

The proposal-through-signature workflow — proposal-as-summary, per-clause classification, procurement navigation, redline cadence, e-signature routing, follow-up cadence — is what converts the 50% close rate to the 90% close rate. The differential is not buyer-side. The buyer has already said yes. The differential is entirely produced by the seller's discipline between verbal yes and countersigned contract.