A pricing proposal is where most creative agencies quietly lose work they should have won. The brief was strong, the chemistry was good, and then the document landed and something fell apart. Usually, it wasn't the price. It was how the price was presented.
West Melbourne Studios treats every pricing proposal as a piece of persuasion. It's not a spreadsheet sent to fill a procurement checkbox. It's the document that carries your entire value case at the moment the client is deciding whether you're worth it.
What a pricing proposal actually does
A pricing proposal does three things simultaneously. It communicates scope, it justifies cost, and it builds confidence. Most agencies only do the first one. They list deliverables, attach a total, and wait. That approach puts the entire burden of value assessment on the client, who almost always resolves uncertainty by asking for a discount.
The structure of the document shapes how the number lands. A fee that appears on page two, after you've walked the client through your process, your team's credentials, and a clear articulation of what they'll receive, reads very differently from the same number sitting alone at the top of an email.
Before writing a single line of your next proposal, check that you've already thought through how to price your video production services. The proposal is downstream of that decision. If you haven't resolved your pricing logic, no presentation trick will save the document.
Lead with the client's problem, not your services
The first section of a pricing proposal should describe the client's situation back to them. Not a summary of the brief, but a demonstration that you understood what was underneath it. What's the commercial pressure driving this project? What does success actually look like for them?
This section does two things. It proves you listened. And it anchors the entire proposal in outcomes rather than outputs. A client reading their own problem articulated clearly by a supplier is already in a different frame of mind than a client staring at a line item for "concept development."
Keep it short. Three short paragraphs is enough. The goal isn't to write a consultancy report. It's to confirm that you're solving the right thing.
Scope clearly, but don't itemise everything
This is the section most agencies get backwards. They either describe scope so vaguely it could mean anything, or they itemise every task to four decimal places and inadvertently invite the client to negotiate each line.
The right approach sits between those two. Describe what you'll deliver in plain terms: the number of deliverables, the formats, the revision rounds, and the timeline. Be specific about what's included. Be equally specific about what isn't.
Don't list every hour spent in pre-production or every internal review meeting. Those are your process, not the client's purchase. What the client is buying is the outcome. Describe that.
If you're working from a scope of work template, much of this thinking is already done. The proposal draws from it rather than duplicating it.
Present the investment, not just the price
The word "investment" gets overused and has become a mild cliché. But the underlying idea is correct. A price is a cost the client bears. An investment is a cost tied to a return. Your proposal should be written so that by the time the client reaches the fee, they've already understood what they're getting back.
Present the fee as a total, with a breakdown only if the project has genuinely distinct phases or optional components. A single total is clean and confident. A breakdown invites comparison shopping on sub-items.
If you offer tiered options, keep it to two or three. Research on decision fatigue is consistent: more than three options reduces the likelihood of any decision being made. Frame the tiers by outcome, not by the number of deliverables. "Brand launch package" reads better than "Package B: 3 videos + 2 rounds of revisions."
Address risk before the client raises it
Every client reading a proposal is quietly calculating their exposure. What happens if the project runs over? What if the creative direction doesn't land? What if they need to pause the engagement?
A strong pricing proposal answers these questions before they're asked. Include a short section on how changes to scope are handled. Name the revision process. Reference your payment schedule and what triggers each invoice. A brief note on how you handle project pauses or cancellations removes the feeling of risk that sits under any significant commitment.
If you don't yet have a formal policy for any of these, this is the moment to write one. Your cancellation policy and your payment terms belong in the supporting documentation that ships with the proposal, not buried in fine print the client won't find until they need it.
The expiry date matters more than you think
Every pricing proposal should carry an expiry date. Fourteen days is standard. Thirty is too long. Without one, proposals linger. Clients forward them internally, revisit them three months later, and expect the same price after your availability has changed entirely.
An expiry date also creates a mild, legitimate urgency. It's not a fake countdown. It reflects the reality that your capacity is finite and your costs change. State it plainly: "This proposal is valid until [date]."
Follow-up is part of the proposal
A pricing proposal isn't finished when it's sent. Plan the follow-up at the same time you write the document. Who gets it, when do you check in, and what's the next step if they say yes?
Most agencies send a proposal and wait, treating the client's silence as a verdict. It usually isn't. It's confusion, competing priorities, or an internal approval process the client didn't mention. A single follow-up email three to four days after sending, asking one specific question about the proposal rather than asking "any thoughts?", keeps the conversation active without applying pressure.
The proposal is the beginning of the commercial relationship, not the end of the pitch. Write it that way.