The Freelancer’s Proposal Vault

A practical playbook for solo service providers

Table of Contents (for the whole book)

You’re reading Set 1 of 4 (~2,500 words): Title + Introduction + Chapters 1–2. The next three sets will continue the book in order.

Introduction

A proposal is not a brochure. It’s a decision tool. If a busy buyer can scan one page on their phone, grasp the outcome, trust the plan, and know exactly how to say yes—your proposal did its job. If they have to ask what you do, or where the price is, or who’s supposed to sign… you’ve given them homework, not help.

Solo providers don’t have extra cycles for sales theater. You need a repeatable system that:

This book is a vault of moves you can reuse. You’ll see the same bones over and over: one buyer, one outcome, one named path; options instead of hourly; ROI math in the buyer’s own numbers; proof that speaks in metrics, not adjectives; risks named and tamed; terms in plain English; a short, polite follow-up rhythm.

How to read this:

You already do good work. The goal here is to make saying yes to you the easiest thing on your buyer’s to-do list.

Chapter 1: Positioning That Makes Proposals Easy

Why this chapter matters

Long proposals are usually a symptom of unclear positioning. When you’re fuzzy about who it’s for and what changes, you compensate with pages of explanation. Buyers don’t reward that; they skim and stall. Sharp positioning lets you write short, decisive proposals that buyers can forward to finance without misrepresenting you.

Think of positioning as the sentence your champion repeats when you’re not there. If it’s specific, measurable, and timeboxed, everything downstream gets lighter: discovery gets targeted, scope stays lean, options make sense, and you stop negotiating on price because the outcome is the anchor.

The FOAM Process (4 steps)

Use FOAM to craft (or tighten) your positioning. It’s simple and hard to wiggle out of—which is exactly why it works.

1) Focus one buyer + one outcome

Pick a single buyer role and one business result you can move quickly. Roles are people with scoreboards: Head of Marketing, Growth Lead, Founder/Operator, RevOps, Product Lead. Outcomes are metrics with dates, not adjectives:

Pick one. If you truly serve two segments, write two separate lines and two separate pages. Do not mash them.

Test: If a CFO asked, “What exactly are we buying?” could your buyer answer in one sentence with a number and a date?

2) Offer a named path

Buyers buy paths, not potential. A 5–7 step sequence—named and repeatable—calms risk and becomes the spine of your proposal and delivery.

Examples you can adapt:

Every step should end in a visible output a non-expert can judge (wireframes, doc, Figma link, staging URL, QA checklist, dashboard). That’s how you avoid “we weren’t sure what we were approving.”

3) Anchor with metrics

Numbers travel where you can’t. Your champion must defend spend to someone whose job is to say no. Anchor your claim to the metrics that person already tracks: conversion, add-to-cart, AOV, visit-to-lead, lead-to-SQL, SQL-to-close, activation %, time-to-value, churn, ARPA/ACV.

Replace adjectives with arithmetic. “+3–4 pp ATC in 30 days” beats “dramatic uplift soon.” Pick one north-star metric for the project. Supporting metrics can appear later; one scoreboard keeps the story tight.

4) Map must-have proof

You don’t need a mural-sized case study. You need two or three proof cards:

Proof cards make your path feel repeatable, not lucky. They also set the expectation that results appear on a calendar, not “someday.”

Build your positioning line (scaffold + examples)

Use this scaffold to avoid throat-clearing:

“I help {buyer role/segment} achieve {metric to target} in {timebox} via {named path}.”

Write three versions. Read them out loud. Keep the one you can say without wincing.

Concrete example (end-to-end)

Starting point (too vague):
“I design modern websites for startups and small businesses.”

Run FOAM:

Final line:
“I help $1–5M DTC brands lift a flagship product page to 5%+ add-to-cart in 30 days via Audit → Copy → Design → Build → Launch → CRO.”

Now everything in your proposal mirrors that sentence. That’s why positioning makes proposals easy.

Five pitfalls (and what to do instead)

  1. Selling to “anyone” → Split into distinct offers by role and outcome. Two sharp lines beat one mushy one.
  2. Adjectives over arithmetic → Write the equation your buyer will reuse: sessions × (target − baseline) × checkout × AOV.
  3. Catalog paths → Trim to the 5–7 steps that move the needle. Save the rest for delivery notes.
  4. Proof without numbers → If you don’t have data, ask the client; failing that, commit to collecting it in your next project and stop using number-less “wins.”
  5. Heroic promises → If your claim requires weekends and caffeine, rewrite it until it matches a normal week.

Positioning scripts (use them in discovery to test your line)

If your line is right, these questions land cleanly. If not, you’ll feel the wobble immediately—fix it before you write.

10-Item Checklist — Chapter 1

Chapter 2: Discovery That Writes the Proposal for You

The point of discovery

You’re not collecting transcripts; you’re collecting decisions. A good discovery call replaces “we’ll circle back” with “we know the numbers, the signers, the deadline, the budget comfort, and the risk points.” With that, your proposal is mostly a mail merge.

The discipline here is SPADE notes: five buckets that capture everything you need without drowning you in paragraphs.

The SPADE Notes (5 steps)

1) Situation — stack, team, deadlines, constraints

What systems are in play (Shopify, GA4, Klaviyo, Webflow, HubSpot, Segment, Mixpanel)? Who’s on the team? What else is shipping? Are there code freezes, holiday windows, brand approvals, security hoops? The goal is to spot dependencies and blockers before they become excuses.

2) Problem — baseline → target; cost of delay

Get the starting metric and the target metric, clean and in writing. Then translate the gap into money or time saved.

When you own the math, your champion can defend you internally.

3) Aim — success as one metric by one date

Pick the scoreboard you’ll be judged on and stamp a date. Everything else is supporting cast.

4) Drivers — why now; sponsor; signers; derailers

Whose idea is this (sponsor)? Who signs (by name or role)? What could derail the plan (brand politics, asset delays, code freeze, IT security)? Capture the emotional drivers too—“paid spend ramps in 3 weeks,” “missed last Black Friday,” “board pressure.”

5) Execution — budget, legal/security, procurement

Money reality check (budget comfort, payment terms), MSA/NDA status, info-sec, purchase orders, invoice cycles, vendor setup. If this stuff surprises you later, the timeline pays the price.

Concrete example — Same-day recap that locks decisions

Subject: Recap & next steps — product page rebuild

Situation: Shopify + Klaviyo; 3-person marketing; dev contractor; potential code freeze Nov 1–3.
Problem: ATC 2.1%; need 5%+ before Black Friday to hit Q4.
Aim: Rebuild flagship PDP in 30 days; launch by Nov 8.
Drivers: CEO sponsor; paid ramps in 3 weeks; brand wants a look.
Execution: Budget to $12k; signers you + CFO; standard MSA; Net-15 OK.

Next: I’ll send a 2-option proposal by 2 PM ET tomorrow with scope, timeline, investment, and next steps. I’ll hold Mon, Nov 3 as the start date for 7 days.

If they reply “Looks right,” you’ve got written confirmation of the metrics, date, budget, and decision path. That email is Exhibit A when someone later asks for “just one more thing.”

Questions that earn real answers (use them verbatim)

These aren’t small talk. They prevent rewrite-and-resent cycles and let you design scope that will actually survive contact with reality.

Scripts and micro-emails you’ll reuse

Calendar + confirmation (send same day):
“Confirming ATC 2.1% → 5% by Nov 8, budget up to $12k, signers you + CFO, code freeze Nov 1–3. I’ll send a 2-option proposal by 2 PM ET tomorrow and hold Nov 3 for kickoff (7-day hold).”

Pre-pricing temperature check (if the range looked tight):
“If we present Essentials and Plus (adds analytics + tests), does that map to your risk tolerance? Keeps us out of rewrite land.”

Access request (prevent slow starts):
“To keep momentum, please grant Shopify theme + GA4 access now. We won’t change anything; it just accelerates audit.”

Assets nudge (avoid creative bottlenecks):
“Flagging that product images are needed by Day 3 to maintain the 3-week timeline.”

Discovery pitfalls (and the fix)

Edge cases you should cage in discovery

  1. Multi-language sites
    • Risk: infinite copy/design scope.
    • Containment: “This project includes EN only; localization is a separate change request per language (copy + QA bundle).”
  2. Brand-heavy teams
    • Risk: subjective loops.
    • Containment: “Two edit passes per milestone; decisions against yardsticks: clarity of USP, objection coverage, mobile readability, LCP under 2.5s.”
  3. Code freeze collisions
    • Risk: missed revenue window.
    • Containment: build on a feature branch; soft-launch to a segment post-freeze; hard launch within 48h.
  4. Asset dependency (photos/video)
    • Risk: blocked build.
    • Containment: “If assets aren’t delivered by Day 3, we’ll ship with placeholders and schedule a content swap as a post-launch change.”
  5. Security/legal review
    • Risk: timeline drift.
    • Containment: start audit + wireframes (no PII) while legal reviews; log any security work beyond X hours as a change.

10-Item Checklist — Chapter 2

Why Chapters 1–2 reduce proposal time by half

When your positioning names one buyer, one outcome, one path—and your discovery captures SPADE decisions in writing—your proposal becomes assembly, not invention. The one-page summary matches your line. Milestones mirror your path. Options show calibrated risk/speed. ROI uses their numbers from the recap. Terms reflect the constraints you already surfaced. That’s how a solo provider ships a clean, forwardable proposal in under an hour and actually enjoys delivery.

Chapter 3: Scoping & Pricing Without Regret

Why this chapter matters

Scope decides margin. Options decide deal size. The wrong scope paints you into a corner; the right options keep you out of discount wars and let buyers choose their own risk level. When scope is visible, bounded, and tied to milestones, delivery runs calm and you get paid on time. This chapter gives you a simple way to turn raw discovery notes into a clean plan with three options and plain rules for changes and payments.

The COPE-P Process (5 steps)

  1. Cap the outcome
    Every proposal should pursue one business result. If the buyer wants multiple outcomes (“rebuild PDP and overhaul checkout and stand up email”), split into phases or put extras into higher options. One outcome = shorter doc, clearer acceptance, fewer “while you’re in there…” requests.
  2. Outline milestones (visible outputs + acceptance)
    Break the work into 5–7 milestones. End each milestone with a deliverable non-experts can inspect (wireframes, copy doc, Figma comps, staging URL, QA matrix, launch note). Attach an acceptance rule to every milestone—most solo providers use 48 hours with default acceptance so projects don’t stall.
  3. Price with options
    Offer Good / Better / Best (or Essentials / Plus / Premium) where each option meaningfully changes risk, speed, or surface area, not just “more hours.” This creates an anchor and reframes negotiation around scope instead of discounts.
  4. Explain assumptions & exclusions
    List the rules that protect the schedule: review windows, day-1 access, single decision owner, asset deadlines. State what’s out (custom app dev, subscription logic, localization, legal copywriting, etc.). Add a change request path so you can say yes to extras without giving away work.
  5. Pick a payment plan
    Tie payments to milestones. Short projects: 50% / 40% / 10% (kickoff, design approval, launch). Larger builds: 40% / 40% / 20%. Rush work (< 2 weeks): 70% / 30% + a 10–20% rush fee. Include a pause rule for late invoices (e.g., “work pauses after 10 business days overdue”).

Concrete example — Scope, options, and terms (paste-ready)

Project: Flagship PDP rebuild to lift add-to-cart from 2.1% → 5%+ in 30 days

Milestones & acceptance

Options (side-by-side)

OptionIncludesInvestmentTimeline
A — EssentialsM1–M6 end-to-end rebuild & launch$7,5003 wks
B — PlusEssentials + analytics overhaul + 2 A/B tests$9,8004 wks
C — PremiumPlus + 2 email flows + 3 ad creatives + 60-day CRO$13,5006 wks

Assumptions

Exclusions

Change requests

Payments

Why this works

Phrasing that keeps scope honest (use verbatim)

What to do when scope collides with reality (edge cases)

10-Item Checklist — Chapter 3

Chapter 4: The Proposal Layout Busy Buyers Approve

Why this chapter matters

Most buyers make up their minds in five minutes. Your proposal must:

  1. let them say “yes” fast, and 2) give enough detail that delivery runs without drama. Think one power page that sells (Executive Summary) plus four supporting pages that defend: Plan & Deliverables, Timeline & Collaboration, Investment & Payments, and Proof/Risks/Terms/Sign.

The SLIM Process (4 steps)

  1. Summary (1 page)
    A forwardable page that a VP can read on a phone and forward to finance. Include: Objective (metric + date), Approach (named path), Expected Outcome (conservative), Options (A/B/C) with one-line differences, ROI Snapshot using their inputs, and Next Steps with dates.
  2. Layout the plan (milestones page)
    Replace promises with inspectable outputs and acceptance rules. Keep jargon out. If a non-marketer can judge “done,” you did it right.
  3. Investment (options + payments page)
    Side-by-side table for clarity. Add a payment schedule and optional rush/retainer callouts so buyers pick speed/continuity consciously.
  4. Make it signable (proof + risks + terms + signature)
    Put your proof cards, top-3 risks with mitigations, Terms Lite, and a signature block with payment instructions. Add a start-date hold to create a natural deadline.

Concrete example — Executive Summary (paste-ready, one page)

Objective
Raise flagship PDP add-to-cart from 2.1% → 5%+ by Nov 8 to unlock paid growth and hit Q4 goals.

Approach (30 days)
Audit → Wireframe → Copy → Design → Build → QA → Launch; analytics re-tag; A/B test #1 in 14 days.

Expected Outcome (conservative)
+3–4 pp ATC based on similar DTC projects.

Options (distinctions in one line)

  • A — Essentials ($7,500, 3 wks): E2E rebuild, QA, launch
  • B — Plus ($9,800, 4 wks): Essentials + analytics overhaul + 2 A/B tests
  • C — Premium ($13,500, 6 wks): Plus + 2 email flows + 3 ad creatives + 60-day CRO

ROI Snapshot (Conservative)
50k sessions/mo; ATC 2.1% → 5.0% = +1,450 carts; 55% checkout × $70 AOV ≈ +$55.9k/mo uplift.
Payback on Option B ($9,800): < 1 week of uplift.

Next Steps (dated)

  1. Choose option 2) Sign 3) Pay kickoff 4) Start Mon, Nov 3 (held 7 days).

Supporting pages — what to show (and what to skip)

Page 2 — Plan & Deliverables

Page 3 — Timeline & Collaboration

Page 4 — Investment & Payments

Page 5 — Proof, Risks, Terms & Sign

Language that moves the deal along (copy/paste)

Visual timeline (example)

QA pass criteria: layout integrity on listed devices; ATC → checkout path; event tags verified.

Proof & risk (include on page 5)

Proof cards

Top risks & mitigations

Terms Lite (plain English, compact)

Why this layout closes faster

10-Item Checklist — Chapter 4

Small touches that compound win rate (add ~2 minutes; save days)

Closing note for Chapters 3–4

You’re not trying to impress; you’re trying to make a safe, fast yes possible. A scoped plan with options and plain rules turns you from “another vendor” into the calm operator buyers remember. When you keep the bones the same and only customize the skin—objective, dates, options mix, ROI inputs—you can ship in under an hour and still look like you thought about every detail.

Chapter 5: ROI, Proof & Risk Reduction (Show numbers, not nerves)

Why this chapter matters

Buyers don’t buy adjectives—they buy probability. Your proposal has to make a CFO think, “This is likely to work, we understand the upside even if it underperforms, and the risks are named with adult mitigations.” When you show ROI using their inputs, proof with metrics + timeboxes, and a risk section that’s honest and operational, approvals move without extra meetings.

The NTR Process (3 steps)

  1. Numbers (ROI & Payback)
    Use the client’s inputs to model conservative uplift and payback time. State your assumptions plainly. If you can, include a tiny sensitivity table (-10% / base / +10%) so the champion can defend the decision under scrutiny.
  2. Trust (Proof Cards)
    Replace narrative case studies with cards: metric + timebox + what changed. That’s what travels inside the company. Two or three strong cards beat ten vague ones. If a small visual clarifies, include one—never more than one per card.
  3. Risk (Name & Tame)
    List the three risks your buyer actually worries about, not theatrical ones. Pair each with a mitigation you run in delivery (review windows with default acceptance, day-1 access checklist, Good/Better/Best creative path, feature-branch releases, etc.). The point isn’t to scare; it’s to show you have a playbook.

ROI—Formulas and guardrails

Common inputs by service type

Ecommerce PDP uplift (worked example)

Sensitivity (show this in a tiny table):

Target ATCIncremental OrdersRevenue/moPayback on $9,800
4.5%660$46,200~6 days
5.0%798$55,860< 1 week
5.5%935$65,450~4–5 days

Guardrails: Label assumptions conservative. Use the client’s numbers (not industry averages). Round to the nearest day / hundred; precision theater backfires.

B2B demo-site uplift (skeleton)

SaaS activation uplift (skeleton)

Proof Cards—what they must contain

Structure

Examples (paste-ready)

Keep cards short. Your buyer will screenshot them.

Risk—three that actually matter (and how you write them)

  1. Approval delays
    • Risk: Review cycles slip → downstream work idles → miss launch window.
    • Mitigation language (use verbatim):
      “Reviews are calendarized; deliverables have 48-hour default acceptance. We proceed unless edits are requested in that window.”
  2. Access and environment
    • Risk: No theme access, broken analytics tags, blocked heatmap, legal gating.
    • Mitigation: Day-1 access checklist; parallel audit using anonymized exports while security reviews.
  3. Creative misalignment
    • Risk: Subjective loops; scope creep disguised as “small tweaks.”
    • Mitigation: Good/Better/Best variants; objective yardsticks (clarity of USP, objection coverage, mobile legibility, LCP under 2.5s); two edit passes.

Optional #4: Code freeze conflicts → feature branch + soft-launch post-freeze.

Concrete Example — Full “ROI + Proof + Risk” page (drop-in)

ROI (Conservative)
50k sessions/mo; ATC 2.1% → 5.0% = +1,450 carts; 55% checkout = +798 orders × $70 AOV ≈ +$55.9k/mo uplift.
Payback (Option B $9,800): < 1 week of uplift.

Proof (relevant)

  • Outdoor DTC: +3.6 pp ATC in 18 days
  • Beauty: +2.9 pp ATC in 21 days
  • Wellness: +31% revenue in 45 days

Risks & Mitigation

  • Approvals → calendarized reviews; 48h default acceptance
  • Access → day-1 checklist; anonymized parallel audit
  • Creative → Good/Better/Best; yardsticks; two edit passes

Objection diffusers (use these lines)

10-Item Checklist — Chapter 5

Ecommerce (PDP/PLP/Checkout) — Three Common Scenarios

A) PDP lift with checkout unchanged
Use when your changes are confined to the product page.

B) PDP + Checkout bundle
Use when you also streamline cart or checkout.

C) Sensitivity under AOV variability
AOV often moves post-change (better cross-sells, trust). Show a simple grid:

AOVOrders (1,021)Revenue/mo
$581,021$59,218
$641,021$65,344
$701,021$71,470

Narrative line: “Even at the low AOV case, payback is < 7 days.”

B2B Lead Gen / Demo Sites — Two Pipes, Two Levers

A) Funnel you control (site → form → demo)

B) When sales cycle is long (confidence vs. cash)
If finance balks at long cycles, show leading indicators as ROI proxies: demo completion rate, show rate, time-to-first-meeting, SDR touch reduction. Tie each to cost saved.

SaaS / PLG — Activation & Retention

Activation-first model

Stickiness bump variant
If your work adds templates/empty-states that reduce early churn: adjust R30 upward in the sensitivity table to show compounding effect.

Local Services — Calls/Bookings Economics

ROI Storytelling: The 3-Sentence Rule

  1. Set the baseline → target with dates (“2.6% → 4.8% by July 15”).
  2. State conservative uplift in dollars and payback time (“≈ $65k/mo; payback in ~5.5 days”).
  3. Name one risk + mitigation (“If approvals slip, 48h default acceptance keeps us on track”).

No more than three sentences. Screenshottable. Repeatable by your champion.

Proof That Persuades Skeptics (turn anecdotes into assets)

Template you can paste to clients post-launch (to secure a quote):
“Quick favor—since we hit {metric} → {metric} in {days}, could I use a 10-word quote like ‘{your words here}’? I’ll pair it with one screenshot and anonymize numbers if you prefer.”

Real-World Risk Register (use what applies)

Chapter 6: Terms, Scope Control & Getting Paid (Plain English, calm delivery)

Why this chapter matters

Terms aren’t for lawyers; they’re for momentum. Clear terms prevent rage-sprints, unbilled “one more thing”s, and end-of-project cash droughts. If you can’t say your terms out loud in under two minutes, they won’t protect you. This chapter gives you Terms Lite language that’s human, enforceable, and aligned to how you actually work.

The PACT Process (4 steps)

  1. Parameters (Acceptance & Change Control)
    Decide how work is accepted and how changes happen. Most solo operators run 48-hour review windows with default acceptance and a one-day quoting SLA for change requests.
  2. Admin (Payments & Pauses)
    Tie payments to milestones (e.g., 50/40/10). Add a late fee and a pause rule (e.g., work pauses after 10 business days overdue) so you don’t bankroll the project.
  3. Control (IP, Confidentiality, Warranty, Liability)
    • IP transfers on final payment.
    • Mutual confidentiality.
    • Warranty is narrow: “works to spec for 30 days,” excludes platform changes.
    • Liability capped at fees paid.
  4. Tempo (Availability & Communication)
    Response times (within 1 business day), weekly 30-minute check-in, channels (Slack for day-to-day, email for approvals, Loom for walkthroughs).

Terms Lite (paste-ready, tweak names)

Acceptance
Deliverables are accepted if no revision request is submitted within 48 hours of delivery. Minor edits are included; new asks go through the change log.

Change Requests
We log each change with ID, scope impact, price, schedule impact; quote within 1 business day; work begins on written approval.

Payments

IP & Portfolio
Final deliverables transfer upon final payment. We may show screenshots in our portfolio unless you opt out in writing.

Confidentiality
Mutual confidentiality; reasonable security practices; no sharing credentials outside the team.

Warranty & Liability
30-day warranty that deliverables function as specified. Excludes third-party/platform changes. Liability limited to fees paid.

Availability
Responses within 1 business day; weekly 30-minute check-in. Slack for day-to-day, email for approvals, Loom for walkthroughs.

How to say your terms out loud (script)

“Here’s how we keep momentum. Every deliverable has a 48-hour review window—if I don’t hear back, we treat it as accepted and move forward. Changes are fine: I log them, price them within one business day, and schedule once you approve in writing. Payments align to milestones (50/40/10). If an invoice goes 10 business days past due, I pause until it’s sorted. IP transfers on final payment. I warranty everything to spec for 30 days, and I’m available within one business day with a weekly 30-minute check-in.”

If you can say that without reading, your terms are ready.

Scope Control—keeping flexibility without free work

Set a change log culture
Create a tiny CSV or table with: ID, Request, Reason, Scope Impact, Price, Schedule Impact, Status, Owner, Due. Every new idea goes here. You’re not saying “no”—you’re saying “this is how.”

Reduce subjective thrash

Unblock dependencies

Payment options (so price holds but cashflow bends)

Concrete example — “Terms + Scope” page you can paste

Acceptance & Reviews
Each milestone includes a 48-hour review window with default acceptance. Two edit passes per milestone.

Changes
We log changes (ID, scope, price, schedule impact); quote within 1 business day; schedule upon written approval.

Payments
50% kickoff (reserves start date) · 40% design approval · 10% launch. Late invoices accrue 1.5%/mo; work pauses after 10 business days overdue.

IP & Portfolio
Final deliverables transfer on final payment. Portfolio use is allowed unless you opt out in writing.

Confidentiality
Mutual; reasonable security; no credential sharing outside the team.

Warranty & Liability
30-day to-spec warranty; excludes third-party changes. Liability capped at fees paid.

Availability & Cadence
Responses within 1 business day; weekly 30-minute check-in; Slack for day-to-day, email for approvals, Loom walkthroughs.

Objection patterns and trades (so you don’t discount)

Admin details that save weeks

10-Item Checklist — Chapter 6

Why Chapters 5–6 raise approvals and reduce drama

When ROI math matches the buyer’s spreadsheet, proof cards show outcomes on a calendar, and risks come with operational mitigations, the champion doesn’t need you in every meeting. When Terms Lite is human and scope control is baked in, you stop bleeding margin at the edges. That’s the point: make the “yes” fast, make delivery boring in the best way, and protect the future relationship by removing avoidable friction.

Chapter 7: Sending, Presenting & Following Up (How “sent” becomes “signed”)

Why this chapter matters

“Sent” emails don’t close deals. Presented proposals do. Your buyer is juggling meetings, metrics, and politics. The more you reduce cognitive load—and the faster you guide them through the decision path—the more approvals you’ll see without extra meetings. Chapter 7 gives you a repeatable rhythm that turns a fresh PDF into a signed project: pre-wire → send → present → trade → follow up. You’re not pushing; you’re making the decision easy.

The PRIME Process (5 steps)

  1. Pre-wire the decision
    Before you ever attach a proposal, confirm who signs, what they need to see, and the start date you’re holding. This isn’t “checking in,” it’s constructing the runway so the plane can land.
    • Ask: “Is it you + CFO signing?”
    • Ask: “What does the CFO care about most—payback or risk?”
    • Offer: “If you want that Mon, Nov 3 start, I’ll hold it for 7 days while you review.”
    Why it works: No one likes surprises. When the buyer knows you’ll keep the cadence tight and hold a date, they organize internally.
  2. Request a walk-through window
    Don’t rely on an open-ended “let me know if you want to discuss.” Book 20–30 minutes with decision-makers and promise a tight agenda: Summary → Options → Next Steps. You’re signaling respect for time and steering away from “death by detail.”
  3. Run the call like a short flight
    Keep your talk track simple:
    • Takeoff (3–5 minutes): repeat their goal in their words (from your recap): “ATC 2.1% → 5%+ by Nov 8.”
    • Cruise (10–15 minutes): show your named path (one slide), the options table (one slide), and the ROI box (one slide).
    • Landing (3–5 minutes): ask, “Which option fits?” and agree on signature/payment timing and the start date.
    Your visuals should mirror the one-page Executive Summary. Fewer slides beat pretty slides.
  4. Trade, don’t discount
    If pushback surfaces, swap scope, schedule, or payment—never value. You can trim an A/B test to hit a date, move analytics to Phase 2 to hit a budget, or split payments to smooth cashflow. Keep the anchor (outcome + path + price logic) intact.
  5. Follow up with a light but firm cadence
    Momentum dies quietly. Use this pattern (you can paste these as-is):
    • Day 0 — Recap: “Here’s what we agreed; signature and payment links included.”
    • Day 1 — Clarifier: “Any last questions before you sync with CFO?”
    • Day 3 — De-risk note: “Option B includes 2 A/B tests; payback < 1 week at conservative inputs.”
    • Day 7 — Release the hold: “I’ll release Nov 3 tomorrow unless you want me to keep it.”
    This cadence is pressure-free but decisive. The start-date hold supplies the natural deadline.

Concrete Example — “From send to sign” (email + call + follow-ups)

Cover Email (send with the PDF)
Subject: Proposal — 30-day PDP rebuild to 5%+ ATC (holding Nov 3)
Body:
“Here’s the 2-option plan we discussed. Page 1 is a one-page summary you can forward; Page 4 compares options side-by-side. I’m holding Mon, Nov 3 as a start date for 7 days. Want a 20-minute walk-through? I’ll keep it to Summary → Options → Next Steps.”

Walk-Through Outline (20–25 minutes)

Day-0 Recap (send right after the call)
“Summarizing decisions: leaning Option B, holding Nov 3 for 7 days. Signature and payment links below. Open questions: none. Next step: sign + kickoff invoice.”

Day-1 Clarifier
“Any final questions before you sync with CFO? I can answer by email if easier.”

Day-3 De-risk
“Option B includes 2 A/B tests to derisk performance. If cashflow’s the blocker, we can split 40/40/20 across milestones.”

Day-7 Hold Release
“I’ll release Nov 3 tomorrow unless you’d like me to keep it. Either way, thanks for the thoughtful review.”

Objections on the call (and how to land the plane)

Keep your tone relaxed and factual. You’re offering trades, not concessions.

The “walk-away” posture (when it’s right to let go)

Sometimes it’s not a fit—timing, culture, or misaligned expectations. You earn respect by naming that calmly.

Counter-intuitive truth: a clear “no for now” often becomes a clean “yes” later.

10-Item Checklist — Chapter 7

CFO-first rooms (numbers > narrative)

CMO-first rooms (brand risk > ops)

Founder room (speed > everything)

Slide-by-Slide Script (3 slides, 8 minutes)

  1. Slide 1 — Executive Summary
    “Your words: 2.1% → 5.0%+ by Nov 8. Path: Audit → Wireframe → Copy → Design → Build → QA → Launch. Payback < 1 week.”
  2. Slide 2 — Options Table
    “A ships fast; B adds analytics + 2 tests. If cash is the blocker, we can split 40/40/20; if calendar is the blocker, we trim one test.”
  3. Slide 3 — ROI & Next Steps
    “Conservative uplift ≈ $55.9k/mo; sensitivity shown. To start Nov 3, sign + kickoff by Friday.”

Then stop talking. Ask: “Which option fits?”

Follow-Up Variations by Buyer Persona

Detail-oriented operator

Hands-off exec

Procurement-heavy org

“Nudges” That Close Gaps Without Pressure

Handling Silence (and saving the relationship)

If the hold expires with no reply:

You’re calm, adult, and still helpful—without chasing.

Chapter 8: Negotiation & Objections (Win without discounting)

Why this chapter matters

Great negotiation isn’t a duel; it’s diagnosis. If you treat every objection like a price fight, you’ll bleed margin and resent the project. If you listen, name the blocker, and trade intelligently, you’ll protect value and still be easy to work with. The moves below keep you anchored while giving buyers ways to say yes today.

The LAST Process (4 steps)

  1. Listen
    Don’t jump in. Let silence work. Take notes. You’re collecting clues: is the core issue budget, risk, timing, or politics?
  2. Acknowledge
    “Fair to ask,” “Makes sense to check,” “I’d ask that too.” This lowers the temperature and prevents the tug-of-war posture.
  3. Simplify
    Mirror the core concern in one calm sentence: “Sounds like cashflow this quarter is the blocker, not scope or timing.” If they nod, you have the problem statement.
  4. Trade
    Offer two trades, then stop talking. Trades are scope (defer/phase), schedule (trim to hit a date), or payment (split). Avoid discounting unless it’s tied to something concrete (e.g., removing a module).

Trade library (paste-ready lines)

Concrete Example — Budget pushback resolved in 90 seconds

Client: “$9,800 is higher than we wanted.”
You: “Totally fair. It sounds like cashflow this quarter is the blocker, not the scope.”
— pause —
You: “Two paths:

  1. Move analytics overhaul to Phase 2, investment $7,500, same date.
  2. Keep full scope and split 40/40/20 so cashflow’s easier.
    Which fits?”

That’s it. You protected the anchor and offered real choices.

What to do when a buyer asks for a discount anyway

Remember: a fast no is better than a slow, underpriced yes.

Language that keeps trust while you hold the line

Your personal rules of engagement (adopt or adapt)

  1. No surprise discounts. If price drops, scope changes.
  2. Two trades max per conversation; otherwise it spirals.
  3. Always write the change (updated options table or change log line).
  4. Protect pacing—no open-ended “we’ll see.” Every trade carries dates.
  5. Be willing to walk—and actually do it if respect slips.

10-Item Checklist — Chapter 8

Roleplay 1 — “Scope feels light for the price”

Client: “This seems thin for $9.8k.”
You: “Fair. We scoped to the fastest path to the metric—that’s why it looks lean. If you want more surface area, Premium adds email flows and creatives. If cashflow’s the blocker, we can keep Plus and split 40/40/20.”

Why it works: You don’t apologize for discipline; you frame it as risk control.

Roleplay 2 — “We have an in-house designer”

Client: “We can do design internally.”
You: “Great—then we can trim the design milestone and keep copy → build → QA → launch. Investment becomes $6.9k. I’ll keep the acceptance rules so we don’t lose pace between handoffs.”

Why it works: You protect pace and acceptance; you don’t fight their org chart.

Roleplay 3 — “Another vendor is cheaper”

Client: “We have a lower quote.”
You: “Healthy to compare. Make sure you’re comparing outcomes and options, not hours. If you share their scope page, I can sanity-check—sometimes the price gap is analytics/tests being excluded.”

Why it works: You invite transparency without trashing competitors.

Roleplay 4 — “Legal wants full redlines”

Client: “Legal will redline the whole doc.”
You: “Understood. We can start audit only while legal reviews. I’ll also prep a one-pager mapping Terms Lite to your MSA so redlines are surgical. Anything beyond X hours of legal is a change request—sound fair?”

Why it works: You keep momentum, protect time, and show respect.

Negotiation Guardrails (sticky notes for your monitor)

Conclusion — Operational Calm Beats Heroics

You’ve now got a full-stack system: positioning that says one thing clearly; discovery that produces decisions, not transcripts; scope with visible outputs and acceptance; a proposal that sells in five minutes; ROI and proof a CFO can defend; terms that keep tempo; a send-present-follow-up cadence; and negotiation that protects value without drama. Use the same bones every time. Improve one tile in the mosaic each week. The compounding happens quietly—more yeses, cleaner projects, better referrals, and a calendar you control.

Resources — Extra Worksheets & Checklists

“One-Liner Refinement” Worksheet (printable text)

Final line (one breath):
“I help {buyer} achieve {metric to target} in {timebox} via {path}.”

“Discovery SPADE” Prompt Sheet (for your screen during calls)

Exit line:
“Great. I’ll send a 2-option proposal by {day/time} and hold {start date} for 7 days.”

“Milestones & Acceptance” Builder

“Options Menu” (drop-ins that change risk/speed)

“Terms Lite” Speak-Aloud Card (keep beside your webcam)

“Deliverables have a 48-hour review with default acceptance. Changes go into a log; I price them in one business day and schedule on written approval. Payments are 50/40/10; work pauses after 10 business days overdue. IP transfers on final payment. There’s a 30-day warranty to spec, and I’m available within one business day with a weekly 30-minute check-in.”

“Follow-Up Cadence” Checklist

“QA Before Send” Quick Pass

Conclusion

A winning proposal is the by-product of a clean upstream. When you run Positioning (one buyer, one outcome, one path), Discovery (SPADE decisions in writing), Scope & Options (visible outputs, acceptance rules), Layout (a forwardable summary plus four pages of defense), ROI/Proof/Risk (conservative math, metric-timeboxed proof, adult mitigations), Terms (plain English, default acceptance, change log, milestone payments), and Send/Present/Follow-Up (walk-through, trades, cadence), you turn selling into assembly.

You’re not negotiating your worth; you’re presenting a safe, believable path to a result your buyer already wants. Keep the system steady. Improve the snippets monthly. Let the vault do the heavy lifting so your calendar—and your head—stay clear.

Resources (ready to paste)

1) Master Proposal Template (Markdown)

# {Client} — {Project} Proposal
Date: {YYYY-MM-DD} • Contact: {Your Name, Email}

## 1) Executive Summary
**Objective:** {metric from X → Y by {date}}
**Approach (timebox):** {5–7 step path}
**Expected Outcome:** {conservative, numeric}
**Options:** {A/B/C one-liners}
**ROI (conservative):** {client inputs; payback line}
**Next Steps:** {choose option, sign, pay kickoff, start date (held 7 days)}

## 2) Plan & Deliverables
- M1 {name} → Output {visible} → Acceptance {48h}
- M2 ...
- M3 ...
- M4 ...
- M5 ...
- M6 ...

## 3) Timeline & Collaboration
Week 1: ... • Week 2: ... • Week 3: ...
Client responsibilities: assets by Day 3, single decision owner, 48h review windows.

## 4) Investment (Options)
| Option | Includes | Investment | Timeline |
|---|---|---:|:---|
| A — Essentials | ... | $X | Y wks |
| B — Plus | ... | $X | Y wks |
| C — Premium | ... | $X | Y wks |
Payments: 50/40/10 (or 40/40/20). Rush: +10–20%. Optional Retainer: $X/mo.

## 5) ROI, Proof & Risks
ROI math with client inputs (conservative) + tiny sensitivity.
2–3 proof cards (metric + timebox + what changed).
Top-3 risks with mitigations.

## 6) Terms (Lite)
Acceptance (48h), Changes (log/quote/schedule), Payments, IP, Confidentiality, Warranty (30d to spec), Liability cap, Availability.

## 7) Sign & Start
Signature block • Payment link • Start date held through {date}

2) Discovery SPADE Note Sheet

Situation — stack, team, deadlines, constraints
Problem — baseline → target; cost of delay
Aim — single success metric by a date
Drivers — sponsor, signers, derailers, why now
Execution — budget, legal/security, procurement steps

3) Options Menu Starters (swap in)

4) Proof Card Template

Client / Vertical: {anonymized if needed}
Outcome: {metric + timebox}
What changed: {3 bullets}
Visual: {one screenshot or chart} (optional)
Quote: “{10–15 words}” (optional)

5) Change Log (CSV headings)

ID, Request, Reason, Scope Impact, Price, Schedule Impact, Status, Owner, Due

6) Email Library (cover → close)

7) Quick QA Before You Send

8) 60-Minute Proposal Sprint (timer)

9) Post-Launch Extensions (sell the sequel)

10) Your Vault Folder Map

/ProposalVault
  /00_Template
  /01_Snippets/Executive_Summaries
  /01_Snippets/Milestones
  /01_Snippets/Assumptions_Risks
  /02_Options
  /03_Proof
  /04_Terms
  /05_Email
  /06_Admin (Change_Logs, Access_Checklists, QA_Matrices)

Leave a Reply

Your email address will not be published. Required fields are marked *

0
    0
    Your Cart
    Your cart is emptyReturn to Shop
    Continue Shopping