Founders ask Collective 54 this 3 times in our records, 1 of them in 2026. The proposals, estimating and client contract answers on this site cover setting scope before the work starts; this page covers what to do once the work is running and the client asks for more.
The engagement management essay in the newer book says the most common problem in a boutique is not demand but economic conversion. The firm turns sold work into delivered work and fails to turn delivered work into the profit it should have produced. It names where the profit leaks: in scope drift that feels small in the moment, in rework rationalized as client service, and in teams that are busy without being economically productive. It says this is why founders feel they are working too hard for what they take home.
The delivery essay adds the cultural cause. In the first era, delivery leaders could not push back on sales or reset client expectations, saying yes was rewarded, and margin erosion was normalized as the price of client satisfaction. As an inference, scope creep is rarely one large request. It is twenty small ones, each too minor to argue about, that together turn a profitable engagement into a loss.
You cannot spot a change if the original scope was vague. The proposals answer on this site describes the four decisions that give scope its edges: the outcome stated so a reasonable person could not disagree it was delivered, the boundary with an out list written down, a customization rule that says what can flex and who authorizes it, and the inputs the client must supply. The client contract answer covers putting the change mechanics into the agreement so they are enforceable. The revenue chapter of the 2020 book records what happens without edges: on his first fixed bids, Greg Alexander says, the team was inexperienced in defining scope, clients took advantage, and the firm lost money.
The engagement management essay is specific about the response. Frame the tradeoff clearly. Offer options: reduce scope, extend the timeline or increase the budget. Price and contract the adjustment for the current engagement. Do it without drama and without apology, and do it early, when the client still trusts the firm. It says this alone can be the difference between delivering profit and creating it.
As an inference, the options matter more than the price. A client who hears only that something will cost more feels billed. A client who hears that they can have the new item by dropping another one, by moving a date, or by adding budget feels in control of a choice. The choice is easier to make in the same week as the request than at the end of the engagement.
The essay says the engagement manager owns the engagement roadmap and its profit and loss, and specifically owns pricing and contracting scope adjustments and change orders for the current engagement. It warns about firms that hand out the title without the authority: if an engagement manager cannot reset scope, reprice work or escalate risk early, governance is theater. It also separates the roles. The engagement manager does not push back on sales directly; that authority sits with the delivery manager. What the engagement manager owns is escalation, surfacing early when commercial commitments collide with delivery reality.
As an inference, in a small firm where one person holds several of these roles, the point still holds. Someone must be named as the person who can say this is outside what we agreed, and here are your options, without first asking the founder.
The essay lists the work AI should carry: tracking burn, forecasting contribution margin and flagging erosion early, modeling scope-change scenarios and their economic impact, detecting timeline risk before the client sees it, keeping decision logs and scope-change records current, and drafting scope-change language and pricing scenarios. It describes many engagement managers as extremely busy and financially blind, discovering margin outcomes after the work was done, and calls that a role design failure rather than a knowledge problem.
The finance essay adds the translation that makes drift visible: every hour carries a fully burdened cost, so an analyst spending 25 hours on a task becomes a 2,500 dollar delivery cost. As an inference, a scope request priced in dollars of delivery cost is much easier to discuss than one described as a bit more work.
The essay keeps one decision firmly with the person: when to protect margin versus relationship, when to absorb friction and when to push back. As an inference, some small requests are worth absorbing on purpose, for a strong relationship or a likely expansion, but they should be recorded as a concession the client is told about, not given silently. A concession the client never hears about builds no goodwill and still costs margin.
The essay also says engagement managers sit inside the client reality and see adjacent problems in real time. It describes noticing the next need while delivering the current work, converting it into a clearly scoped follow-on opportunity and handing it to the account manager. As an inference, the best answer to some scope requests is not a change order but a new statement of work, which protects the current engagement and opens the next one.
The essay closes by telling service designers that most engagement problems are downstream of design problems: when services are underspecified, over-customized or economically unrealistic, the engagement manager is left reconciling what was sold with what can be delivered. As an inference, if the same kind of scope change keeps appearing, the offer or the estimate is wrong. The estimating answer on this site covers feeding actuals back into the next estimate.
Collective 54 publishes no change order template, contingency percentage, threshold for absorbing requests or contract clause. The published positions are profit leaking through scope drift and rework, scope creep as an economic decision, the three options of reducing scope, extending timeline or increasing budget, acting early and without apology, the engagement manager owning engagement economics and change orders, escalation when commitments collide with delivery, AI tracking burn and modeling scope changes, fully burdened cost per hour, and engagement problems as downstream of service design.
If you sell by the hour, as an inference, a scope change is mostly a budget and timeline conversation rather than a margin one, though the client still needs to approve it before the hours are spent.
If the client is on a retainer, define what the retainer covers and treat requests beyond it the same way.
And if the founder is still running delivery, the authority question is about the founder being willing to say no, not about a role.
Treat every out-of-scope request as an economic decision, not a favor, because the engagement management essay says most firms lose margin by treating scope creep as client service. Make the scope clear enough that a change is visible. When one comes, frame the tradeoff and offer three options, reduce scope, extend the timeline or increase the budget, and price and contract it early, without apology. Give one named person the authority to do this, track burn and margin while the work runs so drift shows up early, record any request you choose to absorb as a concession the client hears about, and turn larger requests into follow-on work. If the same change keeps recurring, fix the offer.
The engagement management essay says to frame the tradeoff clearly and offer options: reduce scope, extend the timeline or increase the budget. Do it early, without drama and without apology, while the client still trusts the firm.
The engagement management essay gives the engagement manager ownership of pricing and contracting scope adjustments and change orders for the current engagement, with escalation through the delivery manager when commercial commitments collide with delivery reality.
Collective 54 publishes no threshold. As an inference, absorb a request only on purpose and tell the client it is a concession, because a silent favor builds no goodwill and still costs margin.
The engagement management essay says AI should track burn, forecast contribution margin, flag erosion early, model scope-change scenarios and draft scope-change language, while the person decides when to hold the line.
Sources: Greg Alexander, The AI-Native Boutique Firm (Advantage Books, January 2027), specifically The AI Engagement Manager for economic conversion as the common problem, profit leaking through scope drift and rework, scope creep treated as an economic decision, the three options and acting early without apology, the engagement manager owning the engagement profit and loss and change orders, governance without authority as theater, escalation through the delivery manager, financial blindness as a role design failure, the work AI should carry, the human judgment on margin versus relationship, follow-on opportunities, and engagement problems as downstream of service design; The AI Delivery Manager for delivery leaders unable to push back and margin erosion normalized as the price of client satisfaction; The AI Finance Manager for fully burdened cost per hour and the 25-hour, 2,500 dollar example. Greg Alexander, The Boutique: How to Start, Scale, and Sell a Professional Services Firm (Advantage, 2020), chapter 4 for losing money on early fixed bids through inexperience at defining scope. Related Collective 54 answers on this site: how do I write proposals and scope engagements so I get paid; what terms should we spell out clearly in our client contracts; how do I clearly scope and estimate hours before starting an engagement; how do I define clear deliverables so clients know what they are buying; how do I structure and price retainer agreements. Note on scope: Collective 54 publishes no template, contingency, threshold or clause. Scope creep as many small requests, options mattering more than price, naming one person in a small firm, pricing requests in delivery cost, recording concessions, turning requests into new work, recurring changes as a design signal, and the flips are inferences used here to organize the source material rather than published Collective 54 positions.
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.