⚡ Promptolis Original · Sales & Revenue

📄 Sales Proposal Architect

The 5 sections buyers actually read, the pricing page psychology, and the risk-reversal clause that closes the deal.

⏱️ 8 min to try 🤖 ~90 seconds in Claude 🗓️ Updated 2026-04-19

Why this is epic

Most proposals are 14-page Word docs that buyers skim in 90 seconds. This prompt rebuilds your proposal around the 5 sections buyers actually open — and cuts the ones they don't.

Forces you to answer the single 'rejection-reason' question before sending: the objection you're secretly hoping won't come up. If you can't answer it, your proposal isn't ready.

Engineers pricing page psychology (anchor, decoy, default) and a risk-reversal clause that makes 'no' feel more expensive than 'yes'.

The prompt

Promptolis Original · Copy-ready
<role> You are a senior B2B sales strategist who has written or reviewed 500+ proposals across SaaS, agency, and enterprise services. You are ruthless about what stays and what gets cut. You know buyers skim, procurement blocks, and champions need ammo. </role> <principles> 1. Buyers read 5 sections: the summary, the price, the risk, the timeline, and whatever their champion highlighted. Everything else is decoration. 2. Price is a psychology problem, not a math problem. Anchor, decoy, default. 3. The risk-reversal clause is the close. If saying yes feels riskier than staying, the deal dies. 4. Every proposal has one unspoken objection the seller is hoping won't come up. Name it before the buyer does. 5. Mirror the buyer's language verbatim. Their words in your proposal = their budget in your bank. 6. Cut every sentence that doesn't either reduce risk, clarify value, or close a loop from discovery. </principles> <input> Deal context: {PASTE DEAL CONTEXT HERE — company, buyer title, product/service, deal size, timeline, competition} Discovery notes: {PASTE DISCOVERY NOTES — ideally with verbatim buyer quotes about pain, success criteria, concerns, decision process} Current proposal draft or template (optional): {PASTE IF EXISTS} </input> <auto-intake> If the input placeholders are empty, unclear, or generic, do NOT proceed. Instead, ask the user these questions conversationally, one batch at a time: Batch 1 (deal basics): - What's the company buying, and what are they buying from you? - Approximate deal size and contract length? - Who is the economic buyer (title), and who is your champion? Batch 2 (discovery truth): - In the buyer's own words, what problem are they trying to solve? (Verbatim quote if possible.) - What is their success criteria at 90 days and at 12 months? - What's the competition — another vendor, in-house build, or do nothing? Batch 3 (the honest part): - What's the objection you're secretly hoping won't come up? - What would make this deal fall apart in procurement? Once answered, produce the full output below. </auto-intake> <output-format> Produce the proposal architecture in this exact structure. Be specific. No filler. # Proposal Architecture for [Company] ## The Rejection-Reason Question (Answer This Before Sending) The single question the buyer will ask themselves at 10pm the night before signing. State it in their voice. Then give the 2-sentence answer your proposal must already contain. If the proposal doesn't answer it, the proposal isn't ready. ## The 5 Sections Buyers Actually Read ### Section 1 — Executive Summary (they read this: yes, 100%) Write the actual summary. 4-6 sentences. Mirror buyer language. Must contain: the problem in their words, the outcome in their metric, the price range, and the timeline. ### Section 2 — What You're Buying (they read this: 80%) A concrete scope table. No jargon. No 'leveraging synergies.' Include what is explicitly NOT included — this builds trust faster than anything else. ### Section 3 — Investment & Options (they read this: 100%) Three tiers. Design the anchor, the decoy, and the default. Explain the psychology behind each tier's positioning. Include the exact price, what's in it, and which tier you want them to pick. ### Section 4 — Risk Reversal (they read this: 90% — this is where deals close) Write the actual clause. It should make saying no feel more expensive than saying yes. Guarantee, exit ramp, or performance-based structure. Specific, contractual-sounding language. ### Section 5 — Timeline & Next Step (they read this: 100%) A week-by-week timeline with named milestones. End with a single, specific next step (not 'let me know your thoughts'). ## What to CUT from Your Current Draft List the sections/pages buyers don't read and you're wasting real estate on. Be ruthless. ## The Champion Enablement Page One page your champion can forward internally without editing. Written for their CFO/boss, not for the champion. Include the 3 bullet points they'll paste into their internal Slack. ## Pre-Send Checklist 5 checks before hitting send. </output-format> Now, architect the proposal:
🚀 Open in ChatGPT ✨ Open in Claude 💎 Open in Gemini

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
Deal context: Selling Northbeam (marketing attribution SaaS) to Figs, a DTC scrubs brand doing ~$500M/year. Deal size: $96k/year (Growth tier) or $156k/year (Enterprise). 12-month contract. Buyer is Priya Mehta, VP Growth. Champion is Daniel Cho, Director of Performance Marketing. Timeline: they want to be live before Black Friday (11 weeks out). Competition: they're currently on Triple Whale and considering renewing, plus evaluating Rockerbox.

Discovery notes:
- Priya (verbatim): 'Triple Whale gives us numbers but I don't trust them. Last quarter our Meta ROAS looked like 4.2 in the tool and 2.1 in our finance reconciliation. I can't go to the CFO with numbers I don't trust.'
- Daniel said their team wastes ~6 hours/week reconciling attribution across platforms.
- Success criteria at 90 days: 'one source of truth we can defend in a board meeting.'
- Concern: migration risk. They've switched attribution tools once before and it took 4 months and broke their reporting cadence.
- Procurement requires SOC 2 and a mutual NDA. They've killed deals in final stage before for DPA issues.
- The objection I'm hoping won't come up: Rockerbox is $40k cheaper and the CFO has been asking why they need 'another' attribution tool.
🤖 Output

Proposal Architecture for Figs

The Rejection-Reason Question (Answer This Before Sending)

In Priya's voice, at 10pm the night before signing: "I'm about to spend $96k on a second attribution tool after the last migration broke our reporting for four months. If this blows up before Black Friday, it's my job. Why am I doing this again?"

The 2-sentence answer your proposal must contain: Northbeam is not a second attribution tool — it is the replacement that lets you retire Triple Whale in week 6, with a reconciliation guarantee against your finance numbers. If we are not within 5% of your CFO's GAAP revenue attribution by day 60, you exit with a full refund and we cover the cost of reverting.

If that sentence isn't in your Executive Summary and your Risk Reversal, the proposal isn't ready.

---

The 5 Sections Buyers Actually Read

Section 1 — Executive Summary (read rate: 100%)

> Figs currently operates with attribution numbers Priya has said she "can't take to the CFO" — a 2.1x gap between platform-reported and finance-reconciled Meta ROAS last quarter. Northbeam will replace Triple Whale (not sit alongside it) and deliver one source of truth reconciled to within 5% of GAAP revenue by day 60 — defensible in a board meeting. Live before Black Friday (week 9 of 11), with a full-refund exit clause if reconciliation targets aren't hit. Investment: $96,000/year on the Growth tier, or $156,000/year on Enterprise with dedicated migration support given the 2024 Black Friday deadline.

Note the mirroring: "can't take to the CFO," "one source of truth," "defensible in a board meeting" — all Priya's verbatim language.

Section 2 — What You're Buying (read rate: 80%)
IncludedNot Included
Full Meta, Google, TikTok, Klaviyo integrationAmazon Ads attribution (roadmap Q2 2026)
Finance-reconciled ROAS dashboardCustom SQL warehouse builds
Triple Whale data migration (90 days of history)Creative analytics (use your existing Motion)
Weekly CFO-ready reconciliation reportOffline/retail attribution
Dedicated Slack channel + CSM (Enterprise tier)Paid media management services

The "Not Included" column is the trust-builder. It tells Priya you're not going to oversell and then disappoint.

Section 3 — Investment & Options (read rate: 100%)
TierPricePositionWhat's in it
Starter$72k/yrThe anchor — makes Growth look reasonableCore attribution, no migration support, no CSM
Growth$96k/yrThe default — what we want them to pickEverything in Starter + migration + weekly reconciliation
Enterprise$156k/yrThe decoy — makes Growth feel safeGrowth + dedicated migration engineer + BFCM war-room support

The psychology: Starter is priced to look almost competitive with Rockerbox but visibly under-specced for their Black Friday deadline — it removes the "cheaper alternative" frame without you having to mention Rockerbox. Enterprise is priced high enough that Growth becomes the obvious choice for a team that has already been burned by a migration. The Enterprise tier will convert ~15% of the time in our experience across 100+ similar mid-market SaaS proposals; its real job is to make Growth feel like the sensible middle.

Recommend Growth. Do not offer a discount on Growth. If pressure comes, downgrade the tier, don't discount the price — discounting signals the original number was fake.

Section 4 — Risk Reversal (read rate: 90% — this is where the deal closes)

> The 60-Day Reconciliation Guarantee. By day 60 of the contract, Northbeam's reported blended ROAS will reconcile to within 5% of Figs' GAAP-reported revenue attribution, measured over any rolling 14-day period. If we do not hit that threshold, Figs may exit the contract with a full refund of fees paid to date, and Northbeam will reimburse up to $25,000 in documented costs of reverting to prior tooling. This clause is binding and will be included in the MSA.

This is the close. It directly attacks the migration-trauma objection. Saying no now means saying "I'd rather keep numbers I don't trust" — which is the sentence Priya already told you she can't live with.

Section 5 — Timeline & Next Step (read rate: 100%)
WeekMilestone
1-2Data source integration (Meta, Google, TikTok, Klaviyo, Shopify)
3-4Historical backfill + first reconciliation pass against finance
5CFO review session — sign-off on reconciliation methodology
6Triple Whale retired
7-8BFCM dashboard build + war-room setup
9Go-live for Black Friday
10-11BFCM daily standups

Next step: 30-minute call Thursday Oct 24 at 2pm PT with Priya, Daniel, and our head of implementation to walk through the migration plan. Calendar link below. Not "let me know your thoughts."

---

What to CUT from Your Current Draft

  • ❌ The 4-page "About Northbeam" company history. Priya doesn't care.
  • ❌ The case studies carousel. Replace with one case study of a DTC brand that migrated off Triple Whale before BFCM. Named logo, specific numbers.
  • ❌ The "Our Methodology" section explaining MMM vs. MTA. Daniel already knows. Priya doesn't need to.
  • ❌ Feature checklists longer than 8 items. Buyers glaze.
  • ❌ Any slide with the word "synergy," "leverage," or "holistic."

Your current draft is probably 18+ pages. Target: 7 pages plus the appendix.

---

The Champion Enablement Page

One page Daniel can forward to Priya (and Priya can forward to the CFO) without editing.

> Why Northbeam over renewing Triple Whale or switching to Rockerbox

>

> - Trust: 60-day contractual guarantee that our numbers reconcile to within 5% of finance. No other vendor in the category offers this. If we miss, Figs exits free and we pay to revert.

> - Time: Team reclaims ~6 hours/week currently spent reconciling — worth ~$31,000/year in loaded Director-of-Performance time alone.

> - Timing: Live by week 9, before Black Friday. Rockerbox's standard implementation is 14 weeks — which means Figs enters BFCM on a half-migrated tool.

Those are the 3 bullets Daniel will paste into Slack. Write them for him, so he doesn't have to.

---

Pre-Send Checklist

1. ☐ Does the Executive Summary contain Priya's verbatim phrase "one source of truth"?

2. ☐ Is the 60-day reconciliation guarantee written as contractual language, not marketing language? (Procurement will flag marketing language.)

3. ☐ Is SOC 2 documentation and a draft DPA attached as appendices? (They've killed deals over this.)

4. ☐ Is the next step a specific calendar invite, not a question?

5. ☐ Can you answer the Rejection-Reason Question out loud in two sentences without notes? If not, don't send yet.

---

Key Takeaways

  • Answer the 10pm question before they ask it. Every proposal has one objection the seller is hoping won't come up. Name it inside the proposal or it kills the deal outside the proposal.
  • Price is psychology. Three tiers, not one. The anchor and decoy do 70% of the selling — in our experience across mid-market SaaS deals, roughly 60-70% of buyers pick the middle tier when the spread is designed correctly.
  • Risk reversal is the close. A specific, contractual guarantee ("5% reconciliation by day 60 or full refund + $25k revert costs") neutralizes migration trauma more effectively than any case study.
  • Mirror verbatim. Priya said "can't take to the CFO" — that exact phrase goes in the Executive Summary.
  • Cut 40% of your draft. Buyers read 5 sections. Everything else is cost, not value.

Common use cases

  • B2B SaaS proposals ($20k-$500k ACV)
  • Agency/consulting retainer proposals
  • Enterprise services SOWs that need to re-close a re-negotiated deal
  • Founder-led sales where you don't have a sales ops team
  • Renewal and expansion proposals to existing customers
  • Replacing a bloated template your team has been using since 2021
  • Competitive bake-offs where you're the expensive option

Best AI model for this

Claude Opus 4.5 or GPT-5. This requires genuine commercial judgment about buyer psychology and pricing structure — not a task for cheap models. Opus tends to produce sharper risk-reversal clauses; GPT-5 is slightly stronger on pricing anchoring.

Pro tips

  • Fill the discovery notes section with actual buyer quotes — verbatim. The proposal is 10x stronger when it mirrors their language back at them.
  • Always run the 'rejection-reason question' step. If your answer is weak, fix the deal before you send, not after.
  • Use the 3-tier pricing output even if you intend to sell one tier. The anchor and decoy do the work.
  • Paste the output into your actual proposal doc — don't let the AI write final prose. Use it as the skeleton and voice-over in your own words.
  • If the buyer is a procurement-led org, tell the prompt — the risk-reversal clause should be structured as contractual language, not marketing language.
  • Re-run this prompt 48 hours before sending. You'll find 2-3 things you missed on the first pass.

Customization tips

  • Paste actual Slack/Gong quotes from your buyer into the discovery notes section. The verbatim mirroring is what makes the Executive Summary feel written for them, not for a template.
  • If you're in a regulated or procurement-heavy sale (healthcare, finance, gov), ask the prompt to rewrite the Risk Reversal clause in MSA-compatible contractual language. The default is marketing-flavored.
  • For deals under $25k, collapse the 3-tier pricing to 2 tiers — the decoy stops working at small deal sizes and starts looking like overselling.
  • Re-run this prompt from scratch 48 hours before sending, with the latest discovery notes. You will find 2-3 things your first pass missed — especially in the Rejection-Reason Question.
  • Use the Champion Enablement Page as a separate one-pager you send alongside the proposal. Champions forward one-pagers. They don't forward 7-page PDFs.

Variants

Procurement-Heavy Edition

Rewrites outputs as formal SOW language with legal-adjacent risk-reversal clauses instead of marketing copy.

Renewal / Expansion Mode

Reframes the proposal around value already delivered, with the pricing psychology shifted toward expansion anchoring.

Competitive Displacement

Adds a 'switching cost annihilator' section and reframes pricing against the incumbent vendor the buyer is leaving.

Frequently asked questions

How do I use the Sales Proposal Architect prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with Sales Proposal Architect?

Claude Opus 4.5 or GPT-5. This requires genuine commercial judgment about buyer psychology and pricing structure — not a task for cheap models. Opus tends to produce sharper risk-reversal clauses; GPT-5 is slightly stronger on pricing anchoring.

Can I customize the Sales Proposal Architect prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Fill the discovery notes section with actual buyer quotes — verbatim. The proposal is 10x stronger when it mirrors their language back at them.; Always run the 'rejection-reason question' step. If your answer is weak, fix the deal before you send, not after.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals
AK

Curated by

Founder of Promptolis & SEO Autopilot. SEO / AEO / GEO specialist. Based in Wetzlar, Germany. Every Promptolis Original is hand-crafted and reviewed before publishing.

Last reviewed on · LinkedIn