Journal/Pricing
Pricing

One price is a yes/no question

Most of the negotiation that follows exists because the client wants to say yes but the only lever visible to them is the number, so they pull it. "Can you do it for less" is often not a comment about your value. It is the only move you left them.

Pricing-Airquotes - Airquotes - Proposal Platform for Creative Studios

Send a client a single fee and you have asked them a yes/no question. Most of the negotiation that follows exists because the client wants to say yes but the only lever visible to them is the number, so they pull it. "Can you do it for less" is often not a comment about your value. It is the only move you left them.

Send them two or three scoped options and the question changes from "is this worth it" to "which of these fits." That shift does more for close rates than any amount of proposal polish, and it works for a specific reason: the client now compares your options against each other instead of comparing your single number against nothing, or worse, against the cheapest competitor who scoped a fraction of the work.

The options need to be honestly different, though. Three versions of the same scope at three prices reads as exactly what it is. What works is a difference in scope depth, and the test is simple: the client should be able to explain to their business partner why the options cost different amounts without seeing the fees.

For a web design project, that might be design and build of the core site, the site plus a CMS and content migration, or the full engagement including copywriting and a post-launch support period. Each option ends at a different point in the project, which is a difference any client can articulate.

For a brand identity project, it might be a core identity system, identity plus applications, or identity plus applications plus rollout guidelines. The scope grows outward from the same center rather than cutting the center thinner.

Two structural rules keep this from becoming a mess.

First, each option needs its own complete scope, not a shared scope with asterisks. The moment your middle option is defined as "Option A plus these extras minus that thing," the client has to hold a diff in their head, and clients do not sign documents they had to decode. Write each option as if it were the only one in the proposal.

Second, anchor deliberately. The option you actually want to sell goes in the middle, scoped to what the project genuinely needs. The smaller option exists so the client can see what they would give up. The larger option exists so the middle one looks reasonable. Studios that skip the larger option consistently sell their smallest scope, because the smallest scope became the anchor.

The reason more studios do not price this way is that it triples the proposal writing work. Three scopes, three fee breakdowns, three payment schedules, all of which have to stay consistent when the client asks for a change to one of them. This is where the errors live: the payment schedule that still totals the old fee, the phase that was removed from the scope but survived in the timeline. It is real work and worth budgeting time for, because the pricing logic pays for it: stop asking yes/no questions worth five figures.