Service design and productization

How do I write proposals and scope engagements so I get paid?

Most proposals fail before they are written, because they are sent to a buyer who has not yet said out loud what changed, what the problem is, or that they could defend the decision internally, and a document cannot supply agreement the conversation never reached. The published standard is that orientation precedes solution and that alignment must be verbal, so the first rule of a proposal that gets paid is not to write it until the buyer has done both. The second is that a proposal is a scope decision dressed as a document: state the outcome rather than the activity, draw the boundary and write the out list, set the customization rule before you need it, and name what the client must supply. The third is that getting paid is a fee-terms decision made at scoping, not a collections problem later. Price the deliverable from the task-level cost, version the price so the client chooses, collect in advance where you can, and treat the first engagement as sold only when the client is operationally committed to a start.

Founders ask Collective 54 this 6 times in our records, 3 of them in 2026. The phrase so I get paid is the honest part: the question is about scope creep and collections wearing the clothes of a writing question.

Do not write it yet

The material on new client acquisition is explicit that most firms have sales stages describing what the seller has done rather than what the buyer has decided, and that deals advance because proposals were sent. A proposal sent at the wrong moment is the most common example. The Opportunity Standard governs the sale from the buyer side through seven principles, and three of them decide whether a proposal is premature: no trigger, no opportunity, so the buyer must have articulated what changed and created urgency; orientation must precede solution, so a shared understanding of the problem must exist before solutions are discussed or proposed; and alignment must be verbal, stated by the buyer in their own words rather than assumed. A fourth, that the buyer must be able to justify the decision internally, decides whether the proposal will survive the meeting you are not in.

The 2020 book describes the competitor a proposal most often loses to, and it is not another firm. About 40 percent of the time the competitor is do nothing, the project that quietly went away because the client had other priorities, and about 30 percent of the time it is internal resources, because there was no deadline. The published defenses are to put a hard dollar on the cost of inaction and to establish a compelling event with a deadline. A proposal that does not contain both is competing against nothing, which is the competitor that usually wins.

So the first draft of a proposal is a conversation in which the buyer states the trigger, agrees on the problem, repeats the cost of doing nothing, and names the date by which it has to be solved. Write those four things down in the words the buyer used. That is the opening of the document.

The four scope decisions the document carries

The answer on defining clear deliverables covers this ground in depth, and it applies directly, because a proposal is where those decisions become a promise. The published service design material asks for four things. State the outcome rather than the activity, with the test that a reasonable person could not disagree about whether you delivered it. Draw the scope boundary explicitly and write the out list, because the exclusions you are reluctant to put in writing are exactly the ones the client is already assuming are included. Set the customization rule before you need it: what flexes, who authorizes it and what it costs, because ad hoc variation granted deal by deal is how margin disappears without explanation. And name what the client must supply, because engagements fail on client inputs more often than firms admit and an unstated dependency becomes your fault by default.

The founder account in the 2020 book of moving from hourly billing to fixed bids is the cautionary version: the firm lost its shirt the first few times because it was inexperienced at defining scope and clients took advantage, and only as scope discipline improved did fixed bids become the most profitable work it did. Fixed bids pay for a deliverable rather than time, and a boutique that produces the deliverable efficiently keeps the difference. That is the whole economic case for scoping precisely.

Price from the task-level cost

A price that is not built from cost to serve is a guess, and the published costing method is specific: take hours to task level rather than project level, use fully loaded cost rather than salary, add the AI and tooling line most firms omit, allocate overhead consistently, and use the number before signature rather than after. The answer on the true cost of delivering a service works through the method. For a proposal, the practical consequence is that the task-level breakdown of the last three similar engagements is the scoping document, and the price is set against it with the margin benchmarks in view, 75 percent gross margin and 40 percent EBITDA, which leave roughly 35 points of revenue for everything that is not delivery.

Then present the price the way the 2020 book recommends: versioned, so that the client chooses among bronze, silver and gold and in doing so tells you what they value, and structured so that you charge most for the features the client cares about most. The book records that versioning makes clients decide faster. The pricing material adds the governance warning: custom packages that proliferate deal by deal are how pricing architecture drifts, so the versions should be standard and the customization rule should say what happens outside them.

The terms that decide whether you get paid

Getting paid is decided at scoping, not at collections. The 2020 book treats fee quality as a property buyers price, and two of its tests apply to every proposal: whether you collect the fee in advance of performing the work, and whether the average contract is longer than twelve months. Boutiques paid in advance have high fee quality and rarely need cash infusions; boutiques with aging receivables have poor fee quality. The cash answer on this site makes the same point, that cash is decided in the fee terms you set before it reaches the bank.

Three practices follow, and they are inferences from that material. Ask for payment in advance as the default and treat any departure as a concession with a reason. Where the engagement is long, tie payment milestones to buyer commitments rather than to your activity, so that the client is paying for progress they agreed to rather than for hours they cannot see. And write the customization rule into the commercial terms so that a scope change carries a price change automatically instead of a negotiation.

The last of the seven principles applies here too: activation protects revenue, and selling is not complete until the buyer is operationally committed and positioned for a successful start. A signed proposal with no named client owner, no start date and no inputs scheduled is a receivable waiting to age.

The proposal as a signal

The 2020 book lists a top-quality proposal as the second of five steps for beating market leaders, because the document signals that the firm delivers exceptional work, ahead of speed, a price roughly 25 percent below the leaders without discounting so far as to signal cheap, and an enjoyable experience. Against other boutiques, the published differentiator is to guarantee the work, which most boutiques are too risk-averse to do. A guarantee only survives a scope that was written precisely, which is one more reason the scoping discipline comes first.

After signature

The document does not protect the margin; the operating system does. The delivery material assigns scope creep detection, cost-to-complete forecasting and engagement health monitoring to the continuous layer that AI now runs, and the pricing material assigns delivery-to-pricing alignment checks to the same layer. A proposal written correctly gives those systems something to enforce. Without them, the out list is a paragraph nobody reads after the kickoff.

What we do not prescribe

Collective 54 publishes no proposal template, no statement of work language, no deposit percentage and no payment schedule. The published positions are the buyer-side principles that decide when a proposal is ready, the four scope decisions, the costing method, price versioning, and the fee-quality tests.

When this answer flips

If nearly all of your work is repeat business with clients who already know the scope, the proposal is a confirmation rather than a sale, and the discipline that matters is the customization rule, because repeat clients are the ones who ask for a little more.

If you are responding to a formal request for proposal, the buyer has set the trigger and the timeline and often the format, and the leverage is in the out list and the client-inputs section, which is where most such engagements go wrong.

And if you cannot yet scope a fixed bid with confidence, propose a paid diagnostic first, priced and paid in advance, whose deliverable is the scope, because the published account of fixed bids is that inexperience at scope is expensive and a short first engagement is how it is learned.

The short answer

Do not write the proposal until the buyer has stated the trigger, agreed on the problem, repeated the cost of doing nothing and named a deadline in their own words, because a document cannot supply agreement the conversation did not reach and the competitor you usually lose to is do nothing. Then treat the proposal as four scope decisions: the outcome stated so nobody could disagree it was delivered, the boundary with the out list written, the customization rule with its price, and the inputs the client must supply. Price it from the task-level cost of the last similar engagements with the margin benchmarks in view, present it versioned so the client chooses what they value, and set the terms that decide payment at scoping: collect in advance by default, tie milestones to buyer commitments rather than your activity, and make scope changes carry price changes automatically. Treat it as sold only when the client is operationally committed to a start. Collective 54 publishes no template, deposit percentage or payment schedule.

Related questions

Questions founders ask next

When should I send a proposal to a prospect?

Not until the buyer has articulated a trigger, agreed on the problem in their own words and can justify the decision internally. The published standard is that orientation precedes solution and alignment must be verbal, and that deals advance on buyer evidence rather than because a proposal was sent. A proposal sent earlier competes with do nothing, which the 2020 book says wins about 40 percent of the time because the client has other priorities.

How do I stop scope creep in a fixed-fee engagement?

Write the scope as four decisions before you sign: the outcome stated so a reasonable person could not disagree it was delivered, the explicit boundary with an out list, a customization rule that says what flexes, who authorizes it and what it costs, and the inputs the client must supply. Then let the continuous layer that AI now runs detect scope creep and check delivery effort against the pricing assumption, because the document alone does not protect the margin.

Should a boutique firm ask for payment up front?

Yes, as the default. The 2020 book treats collecting the fee in advance as a test of fee quality: boutiques paid in advance rarely need cash infusions and are attractive to buyers, while boutiques with aging receivables have poor fee quality. Where an engagement is long, tie milestones to buyer commitments rather than to your activity, and treat any departure from advance payment as a concession with a stated reason.

What makes a proposal win against a larger competitor?

The 2020 book gives five steps for beating market leaders: establish credibility, deliver a top-quality proposal that signals exceptional work, show you can complete the work much faster, price roughly 25 percent below them without discounting so far that you signal cheap, and offer a more enjoyable experience. Against other boutiques the differentiator is to guarantee the work, which most are too risk-averse to do, and a guarantee only survives a scope that was written precisely.

Sources: Greg Alexander, The AI-Native Boutique Firm (Advantage Books, January 2027), specifically The AI Account Executive for the finding that most firms have sales stages describing seller activity rather than buyer decisions and that deals advance because proposals were sent, and for the seven principles of the Opportunity Standard, including no trigger no opportunity, orientation before solution, verbal alignment, the buyer justifying the decision internally, and activation protecting revenue; The AI Service Design Manager, by way of the clear deliverables answer on this site, for defining the offer in outcomes rather than activities, explicit scope boundaries, rules for customization rather than ad hoc variation, and the role the client must play; The AI Pricing Manager for packaging discipline, the proliferation of custom packages as pricing drift, and delivery-to-pricing alignment checks; The AI Delivery Manager for scope creep detection, cost-to-complete forecasting and engagement health monitoring as continuous work AI runs. Greg Alexander, The Boutique: How to Start, Scale, and Sell a Professional Services Firm (Advantage, 2020), chapter 3 for the five competitors, the finding that do nothing wins about 40 percent of the time and internal resources about 30 percent, the cost of inaction and the compelling event as the defenses, the guarantee as the differentiator against other boutiques, and the five steps for beating market leaders including a top-quality proposal and pricing about 25 percent below them; chapter 4 for fixed bids paying for a deliverable rather than time and the founder account of losing money on early fixed bids through inexperience at scope; chapter 15 for price versioning that makes clients decide faster and charging most for the features clients value most; chapter 16 for the task-level engagement breakdown; chapter 30 for the 75 percent gross margin and 40 percent EBITDA benchmarks; chapter 32 for fee quality, including collecting in advance, aging receivables and contracts longer than twelve months. Related Collective 54 answers on this site: how do I define clear deliverables so clients know what they are buying; how do I calculate the true cost of delivering a service; how do I make sure I always have enough cash on hand. Note on scope: the instruction to open the proposal with the four things the buyer said, the three fee-term practices of advance payment by default, milestones tied to buyer commitments and automatic price changes on scope changes, and the paid diagnostic as a first engagement are inferences used here to organize the source material rather than published Collective 54 positions. Collective 54 publishes no proposal template, statement of work language, deposit percentage or payment schedule.

Bring your firm's version of this question.

Collective 54 is the private community for founders and executives of boutique professional services firms between $5M and $50M in revenue. Members work these answers against their own numbers.

More answers in the Answer Library.