# How to Write a Proposal That Gets a Campaign Approved

URL: https://trycompass.co/journal/how-to-write-a-proposal
Type: blog
Locale: en
Published: 2026-11-06
Updated: 2026-11-06

---

> Learn how to write a proposal for a marketing campaign: open with the decision, show the arithmetic, add a stop rule, and cut the sections nobody reads.

Your campaign idea is solid. The budget approval meeting is Thursday. The proposal you send on Wednesday decides whether the idea runs in Q1 or dies in a shared folder. Knowing how to write a proposal comes down to one move: stop describing what you want to do and start showing the decision you need, the numbers that justify it, and the rule that stops the spend if it fails.

This guide covers marketing campaign proposals, the kind a growth lead sends to a CFO, a client, or a head of marketing. It skips the template ritual and focuses on what gets signed.

## Start with the decision, not the background

Most proposals open with "Company overview" and "Our understanding of your needs." The reader skips both. They already know who you are, and they want the ask.

Put the decision on the first page, in three lines:

- 
What you want approved (a budget, a headcount, a test window)

- 
What it returns, in a number the approver already tracks

- 
By when, and what happens if it misses

A concrete opening looks like this: "We request $42,000 over 8 weeks to run a re-engagement route across email and paid social. Target: 600 recovered accounts at a cost per acquisition under $70. If week 3 CPA is above $95, we stop and return the remaining budget."

That paragraph does the job of a six-page executive summary. Everything after it is evidence.

## Pick one problem and size it before you pitch the fix

A proposal that solves five problems convinces no one. Choose the single problem the approver feels most, and size it with a number from their own data, not an industry average.

"Email opens plateau at 18%" is a symptom. "We lose roughly 1,100 trial users a month between day 3 and day 10, and each one cost us $38 to acquire" is a problem with a price tag. The second version tells the approver what doing nothing costs, which is the only comparison that matters in a budget meeting.

Pull the figure from the CRM or the analytics export before you write a word of strategy. If you cannot size the problem, you are not ready to propose.

![Hands arranging cards connected by red string on a corkboard to map a campaign route](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/trycompass/2026-11/67f083-img1.webp)

## Write the route as steps someone could execute

Here is where marketing proposals go soft. "We will leverage multi-channel touchpoints to nurture the audience" is a sentence nobody can run on Monday morning.

Rewrite every strategy line until it names four things: the channel, the audience segment, the trigger, and the owner. Compare:

- 
Vague: "Nurture lapsed customers through email."

- 
Executable: "Day 0: email to customers inactive for 60 days, segment A (past two orders). Day 3: if no open, retarget on paid social. Day 7: if no click, send an SMS offer. Owner: lifecycle manager."

The executable version has a bonus. Any person, or any orchestration tool, can pick it up and run it without a kickoff call. If the brief only makes sense with you standing next to it, the brief is unfinished.

This is also the test for how much detail to include. Write until a competent stranger could launch week one from the page alone, then stop.

## Price the work against an outcome, and show the arithmetic

Budgets get approved when the math is visible. Show three columns: spend, expected result, and the unit cost you are betting on.

- 
**Email and SMS sequence:** $6,000 spend, 220 recovered accounts, $27 each.

- 
**Paid social retargeting:** $24,000 spend, 280 recovered accounts, $86 each.

- 
**Creative and production:** $12,000 spend, supports both channels.

Then state the blended figure: $42,000 for 500 accounts is $84 each. Compare it with the number the approver cares about, such as new-customer CPA of $140. Now the proposal is not asking for money, it is offering a cheaper path to a customer.

Two habits make this section credible. First, give a range, not a point estimate: "450 to 600 accounts." A single number reads as invented. Second, label what is assumption and what is measured. "Open rate of 32%, measured on the March send" earns trust. "Conversion of 4%, assumed from similar campaigns" invites a question you should answer before they ask.

![Desk flat-lay with calculator, sticky notes and notebook for budget planning](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/trycompass/2026-11/ce37f4-img2.webp)

## Add the stop rule that nobody else includes

This is the section that separates a proposal that gets approved from one that gets a "let's circle back."

Approvers fear one thing more than a weak return: an open-ended commitment. Remove that fear by writing your own exit conditions into the document.

A stop rule has three parts:

- 
A checkpoint date (end of week 3, not "periodically")

- 
A threshold on one metric (CPA above $95, or fewer than 150 recovered accounts)

- 
A named action (pause paid spend, reallocate to the email sequence, or close the test)

It feels counterintuitive to hand the reader the conditions under which you lose. In practice it does the opposite. It tells the approver the downside is capped, which turns a "yes, but" into a "yes."

It also forces you to choose your success metric before the data arrives, which protects you from the quiet drift where a failing test gets redefined as a learning.

## Skip the sections everyone copies

Most templates carry sections that exist because other templates have them. Cut these unless the approver asked:

- 
**Company history.** They hired or funded you. They know.

- 
**A glossary of channels.** If you must explain what retargeting is, you are writing to the wrong person.

- 
**Five-year vision.** A campaign proposal covers a quarter, maybe two. Beyond that you are guessing, and the reader knows it.

- 
**Appendices of raw screenshots.** Link to the dashboard. Attach a screenshot only when it proves a claim in the body.

What belongs instead: one page on risks. Name the two things most likely to go wrong (a deliverability dip, a creative that underperforms) and say what you will do about each. Approvers read that page twice.

Length follows from this. A strong campaign proposal runs two to five pages. If yours reaches twelve, the decision is buried.

## Match the format to how the approver reads

The same content lands differently depending on the reader.

A CFO reads the first page and the budget table, then decides whether to read anything else. Build for that.

A client reads for reassurance. Give them the timeline and a named contact for each deliverable.

A head of marketing reads for risk to their own plan. Show how your route fits what already runs, and which channels you are not touching.

Pick the format accordingly. A short document with a pricing block suits an external client who needs to sign. A slide deck suits a live review where you will be interrupted. Tools like PandaDoc handle the signature and tracking side, so you can see when the proposal was opened and which page the reader stopped on, which is useful feedback before the follow-up call.

![Team reviewing a printed proposal around a meeting table](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/trycompass/2026-11/804c08-img3.webp)

## Answer the three objections before they are raised

Every approver arrives with the same short list of doubts, and a proposal that addresses them in writing saves a meeting.

**"Why now?"** Tie the timing to something dated: a seasonal peak, a contract renewal window, a competitor launch. If nothing forces the date, the approver will defer, and deferral is a quiet no.

**"Why you, and why this channel mix?"** Show the one piece of evidence that favors your route over the obvious alternative. A past send with a measured result beats any claim about expertise. If the evidence is thin, say so and shrink the test: a 3-week pilot at $9,000 is easier to approve than an 8-week commitment at $42,000.

**"What do I need to do?"** List the approver's own tasks: sign off on creative by day 4, grant access to the CRM export by day 2. People approve faster when they can see how small their part is.

## Write the timeline as checkpoints, not phases

"Phase 1: Discovery. Phase 2: Execution. Phase 3: Optimization." tells the reader nothing about when they will see anything.

Give dated checkpoints tied to something visible:

- 
Day 1: audience segments and tracking confirmed, linked to the stop rule baseline

- 
Day 7: first sends live, first open and click data shared

- 
Day 21: checkpoint review against the stop rule

- 
Day 56: final report with recovered accounts and CPA by channel

Each date has an artifact the approver can look at. That is how a proposal earns the right to a second one.

## Review it like a skeptical approver would

Before sending, read the document with three questions in mind and mark any page that fails:

- 
Can I find the ask in ten seconds?

- 
Is every number traceable to a source or labeled as an assumption?

- 
Do I know what happens if this does not work?

If the answer to the third is no, the document is not ready, however polished it looks. Then cut one more section. Proposals rarely get rejected for being short.

A visual pass helps too. A clean layout from a tool like Canva makes the budget table easier to scan, but design does not rescue a weak argument. Fix the logic first, then format.

## Where orchestration changes the proposal

If your campaigns run through an orchestration tool, the proposal gets easier to write, because the route you describe is the route the tool executes. The brief, the triggers, and the stop rule become the instructions, not a description of intent. That is the idea behind how Compass handles a campaign: the document you approve and the work that runs are the same object.

The reverse is also true. If your proposal cannot be turned into steps a system could run, it will not survive contact with a real week either.

## What to send on Wednesday

Send two pages. Page one: the ask, the number, the stop rule. Page two: the route, the arithmetic, and the two risks. Attach nothing else unless they request it.

Then follow up with one question instead of "any thoughts?": "Is the week 3 threshold of $95 the right line for you, or would you set it differently?" It moves the conversation from whether to approve to how to approve, which is the only conversation you want.

## FAQ

### How do you write a proposal for a marketing campaign?

Open with the ask: budget, expected result and date. Size one problem using the approver's own data, describe the route as executable steps, show the arithmetic behind the budget, and add a stop rule with a checkpoint date and threshold.

### How long should a proposal be?

Two to five pages for a campaign proposal. The first page holds the decision, the number and the stop rule. If it runs to twelve pages, the ask is probably buried.

### What should go in the executive summary of a proposal?

Three lines: what you want approved, the return in a metric the approver already tracks, and the deadline with the exit condition. Everything after the summary is evidence.

### What is a stop rule in a proposal?

A pre-agreed exit condition: a checkpoint date, a threshold on one metric such as cost per acquisition, and a named action like pausing paid spend. It caps the downside and makes approval easier.

### Should a proposal include pricing?

Yes, with the math visible. Show spend, expected result and unit cost per line, give a range rather than a single estimate, and label which figures are measured and which are assumed.

### What tools help send and track a proposal?

Document tools such as PandaDoc add e-signature and open tracking, while design tools such as Canva or Gamma help with layout. Fix the argument first, then format it.