How to Write an Agency Proposal From a Voice Memo

How to write an agency proposal from a voice memo

The best scope notes happen in the car park after a call. You remember what the client actually cared about — the rebrand timeline, the stakeholder who hates pop-ups, the budget range they mentioned offhand.

By the time you open a blank doc the next morning, half of that context is gone.

A voice memo fixes that. Not as a gimmick. As a capture tool before you edit anything a client will see.

Why voice works for agency proposals

Typing forces linear writing. Speaking mirrors how you explain projects to your team: messy, contextual, full of "and also…"

You are not publishing the memo. You are harvesting it for:

• Deliverables the client named explicitly
• Risks they are worried about
• Budget signals you should reflect in tiers
• Open questions you need to confirm before sending

That last bucket is underrated. A short "things to confirm" section builds trust. Clients prefer "we want to verify X with you" over silent assumptions.

A simple workflow (no live streaming required)

This is a batch process — record, process, review, send. Not a live AI copilot listening to your Zoom.

1. Record or upload right after the call (2–10 minutes is plenty) 2. Transcribe — let software handle the typing 3. Extract structure — scope blocks, tier ideas, timeline hints 4. Edit in the open — read the transcript; fix names, numbers, and tone 5. Add a confirmation section — bullets the client should verify 6. Publish the proposal link when you are proud of it

Step four is non-negotiable. AI will mishear a budget. It will confidently invent a deliverable. You are the editor, not the audience.

What to say in the memo (prompt yourself)

If you stare at the record button, use this outline:

> "Client name and project type… > What they said success looks like… > Constraints — budget, date, team… > What I think the three tiers could be… > What I still need to ask them…"

You will sound boring. That is fine. Boring memos make clear proposals.

Turning rambling into tiers

Clients do not want one price. They want options that help them decide.

From your memo, look for natural breakpoints:

• Smaller scope — must-haves only
• Recommended — what you would pick if you were them
• Stretch — nice-to-haves with clear added value

Name tiers in the client's language ("Launch", "Growth", "Full rebrand") not internal codenames ("Tier B").

Each tier needs three lines a busy approver understands: outcome, timeline, price.

Common mistakes

Sending the transcript. Never. It is raw material.

Skipping confirmation. If the memo says "maybe Shopify," the proposal should ask "Confirm platform: Shopify vs Webflow?"

One giant tier list. More than three options and decision fatigue wins.

Waiting until Friday. Memo within an hour; draft the same day while empathy is high.

Tools vs discipline

You can do this with Voice Memos on your phone and a doc. Software just removes copy-paste.

ProposalKit transcribes uploads, drafts sections, and gives you a review screen before anything goes live — including a dedicated spot for "things to confirm."

If you already use another proposal tool, steal the workflow anyway: memo → edit → tiers → link.

Try it on your next call

On your next discovery call, record a five-minute memo in the lobby. Before dinner, you should have a draft scope and three tier names — even if numbers are still TBD.

That is the bar. Not perfect prose. Clear choices your client can act on.

Start a free trial · See voice briefs