How to price a creative project proposal

The wrong first question

"What should I charge for this?" is the question most pricing guides try to answer. The answer is almost always wrong.

Not because the number it gives is wrong, but because the question is wrong. "What should I charge?" anchors the math on you: your hours, your rate, your floor. The client doesn't care about your floor; they care whether your number is smaller or larger than the alternative sitting on their desk.

The right first question is: what is this work worth to the client?

Blair Enns's clearest framing on this is to abandon the idea that set deliverables have set prices. The same brand identity is worth one number for a coffee cart and a different one for a Series B SaaS company two months from rebrand. The deliverable is the same, but the pricing question is not.

This isn't fancy value-based pricing theory; you don't need a discounted cash flow model. You're just naming what is already true: the client is comparing your number to something. Make sure you know what that something is.

The cleanest articulation of "the something" comes from Jonathan Stark. The client's alternatives are not only "a different agency's quote." They include the cost of delayed ROI from not shipping yet, the internal staff time consumed by the project drag, the competitor who is going to launch first, and the customers churning out of the current bad experience while everyone deliberates. "Is this too expensive?" usually has nothing to do with you and everything to do with whether the client has clearly seen the cost of waiting.

If you do nothing else from this post, do this: in your next discovery call, ask "what does it cost you if this doesn't ship until Q3?" Then listen to the answer before you write a number on a page.

The three pricing models that actually matter

Fixed-fee: the default for project work

If the scope is bounded and the deliverables are agreed, the price should be fixed: the client knows what they're spending, you know what you're shipping, and nobody is re-litigating timesheets at the end of every month.

The deeper reason is risk transfer. Stark's framing is that clients hate risk: when you bill hourly on a fixed-scope project, every hour you spend is a question mark on their budget, and every overrun is their problem. When you fix the price, the question marks become yours, and the client pays a premium for the certainty.

Fixed-fee also fixes a structural problem with hourly: hourly punishes efficiency. The agency that automated a chunk of its QA pipeline, or has done this kind of build twelve times before, finishes faster and bills less, so hourly turns expertise into a discount. Raising the rate helps a little, but only up to whatever ceiling the client has in mind for someone in your role, while fixed-fee doesn't have that ceiling at all.

The ANA's compensation report describes fixed and output-based fees as a recognized model precisely because they remove labor-time haggling from the relationship: procurement doesn't get to argue your timesheet, because you shipped and they pay the invoice.

Hourly: for ongoing work only

Hourly billing isn't dead, just specialized: it's the right model when the scope genuinely can't be defined up front because it's continuous, like a retained role, an embedded engineer, an "ad-hoc as it comes up" arrangement, or a team-augment month. In those cases hourly tracks reality and both sides know what's happening.

For a defined project with a deliverable, hourly is mostly self-injury. It pushes you into milestone friction with the client (every estimate becomes a fight), and it punishes the senior practitioner who works fast.

Ron Baker put it sharper in his AMI interview: the billable hour is a lousy customer experience. The client is paying for an outcome and getting an itemized log of your minutes, which isn't what they wanted.

Value-based: overrated for project work specifically

Here's the contested take. Pure value-based pricing, where the price is set as some function of the client's outcome ("we capture 5% of the revenue uplift"), is recommended in books. The data says otherwise.

Promethean Research's 2025 Digital Agency Industry Report has the cleanest number on this. Pure value-based pricing is used by 2% of agencies. The other 98% are running fixed-fee, hourly, retainer, or some blend, and that isn't because 98% of agency owners haven't read the books; it's because pure value-based pricing is hard to apply at the typical project scale.

The math doesn't work cleanly. Outcome attribution is fuzzy: was the new homepage responsible for the 14% lift in conversion, or was it the paid campaign that ran alongside it? Measurement windows are weird: do you settle the price when the redesign ships, or six months later when the SEO has compounded? Negotiation cost is high: every value-based deal is a custom contract with custom math. And the client's likely objection is fair: "Why should you get 5%? You designed a website." That's not a stupid question.

Brennan Dunn has the nuanced version that's actually defensible. His point: client upside should justify the price, not mechanically determine the budget. Knowing the new site is worth real pipeline doesn't mean you charge a literal slice of it. It means that when the client flinches at your number, you have an answer that isn't about your hours.

Use the value conversation to frame the price. Don't use it to set the price as a literal share of outcome. Save the literal version for retainers and long consulting engagements where the math has time to land and the relationship can absorb the negotiation cost.

Presenting the price on the page

Once you've decided what to charge, you have to put it on the page. The conventions here are widely held among the proposal-software vendors that aggregate sent-proposal data, although the empirical evidence behind those conventions is thinner than the confidence with which they're stated. They're still worth following.

What you call the section

Proposify recommends labeling the section "Investment" or "Your Investment" rather than "Pricing," "Fees," or "Cost." The reasoning is that "fees" emphasizes what the buyer is losing, while "investment" emphasizes what they're getting. There is no clean A/B in the public record proving "Investment" outperforms "Pricing" on close rate, so treat it as a widely-held convention, not as evidence-based fact.

If "Investment" feels too on-the-nose for the client you're writing to, use the word that fits how you talk to them. The label matters less than what's underneath it.

Where attention goes

Industry analysis of roughly 1.3 million proposal sessions found the pricing slide was the most-clicked surface in the document: 87% of engaged sessions included a click on it. Pricing is where attention concentrates.

That's a different claim from "buyers spend the most time on pricing," and they don't: they spend more time on terms and conditions and on the cover, which take real reading. But they check pricing more than anything else, so treat the pricing page as if it's the most-circulated artifact in the proposal.

How many options to show

Show two or three options. Blair Enns has the strongest practitioner argument in his Logo Geek interview: a single price is a binary take-it-or-leave-it, while two or three options shift the conversation from "yes or no" to "which one," and the decision changes shape. It's no longer whether to work with you, it's how much to spend.

The empirical case for three specifically is thinner than people imply. Older Proposify analysis found that winning proposals had fewer total fees than the average proposal, which is adjacent to "don't over-itemize within an option," not "three options beats two." Present options, don't over-itemize within each one, and don't claim three magically converts better than two.

A practical rule: the lowest option should be a real, deliverable thing you'd be glad to ship, not a strawman the client is supposed to reject. If the cheap option exists only to make the middle option look reasonable, the client can feel that, and it cheapens the whole document.

Itemize vs. lump-sum: the discovery-call decision

When you write the price, do you list every component (discovery, design, build, QA, each with a number next to it) or write one number with a short paragraph?

There is no universal right answer, but there's a discovery-call answer.

Itemize when it builds trust

For first-time agency buyers, itemized pricing is reassurance. They don't know what they don't know. A breakdown signals "here's what we're doing, here's what each piece costs, you are not being conned." For procurement-heavy clients (enterprise, regulated industries, anyone with a CFO who has to bless the spend), the breakdown is usually how the spend gets approved.

In design-build community discussion, prospective clients describe sticker shock from large lump-sum quotes that arrive without explanation. The number isn't usually the real issue. Buyers aren't unwilling to spend; they're unwilling to spend on a number that arrives without context.

Lump-sum when it builds confidence

For repeat clients who already trust you, breaking the price into pieces just gives them somewhere to push back. They don't want the receipt; they want the work. A single confident number says "this is what it costs."

For design-led founders who care about outcomes more than breakdowns, itemization can actively undermine the work. You're trying to sell a brand identity, and they get a spreadsheet that lists a separate fee for "second round of revisions," which isn't what they're buying. The spreadsheet shrinks the project, moving the conversation from "is this the right brand?" to "are these line items priced fairly?"

The three discovery questions

You don't have to guess between itemize and lump-sum. Ask, and the client will tell you.

If you're still unsure after all three, default to a hybrid: a single lump-sum total paired with an "included in this engagement" list. The total can sit above the list as a headline number, or below it as a running total at the bottom of the line items, depending on whether you want the number to lead or to land at the end. Either way, you get the confidence of one number with the transparency of a breakdown. Older Proposify data lines up with the "don't over-itemize" half of this: winning proposals listed fewer separate price line items than the average proposal.

The mistake is doing the discovery call and then ignoring what you learned because you have a default template that says "we always itemize." The pricing presentation is one of the few moves in the proposal that should change client to client.

When the gut says "this is too much"

You write the proposal, you put the number on the page, and something feels off. The reflex is to cut: round it down to a "softer" figure, drop 10% to "be reasonable," add a line at the bottom about flexible payment terms.

That reflex is almost always wrong, because the number is rarely the problem.

Here's the diagnostic. When the price feels too high, the issue is usually not that the proposal is too expensive but that it's too thin to support the number: short on context, missing the why, missing what the client gets at the end of the engagement that they don't have today, missing the cost of not doing it. If the only thing on the page is scope and price, the price has to do all the work alone, and any price will feel too high because there is nothing on the page justifying it.

Fix the proposal in this order before you touch the number:

If you've done all three and the price still feels wrong, the scope probably is, so change the scope, not the rate.

The negotiation rule comes from Brennan Dunn: never negotiate your rate. Negotiate scope. If the client comes back with "can you make this work for less?" the answer is not "sure, 10% off." The answer is "what would you take out?"

Maria Piscopo's framing in Communication Arts lands on the same point from the creative-services side: never agree to less money without some change. Less money should mean less scope, longer timeline, fewer revisions, narrower deliverables, less of something. Otherwise you are teaching the client that your price is a starting bid, and they will treat it that way on the next engagement and the one after that.

The client who hears "what would you take out?" and answers "nothing, I just want a discount" is showing you, before the contract is even signed, exactly what every later negotiation in this engagement will look like.

All of the above assumes the client is still in the conversation. If you've sent the proposal and they've gone quiet, that's a different problem with its own rhythm, covered in the companion post on how to follow up on a proposal without being pushy.

A short coda

There's no template for pricing a creative project, and the agencies that try to use one usually arrive at numbers that are either too low to live on or too high to defend. The actual work is figuring out what this client is buying, what it costs them not to buy it, and what shape of price they need to see on the page. Those calls get easier with practice and good discovery.