B2B Scope Changes: Protect Margin Before Extra Work Starts

In this article

Short answer: do not let new customer requests become invisible operational favors. Before work starts, log the request, estimate labor, third-party cost, schedule impact and risk, recalculate margin, and obtain written commercial approval. A change order should be an economic decision—not a surprise invoice or hidden margin loss.

In B2B service and project contracts, margin is rarely destroyed by one dramatic event. It often leaks through an extra report, another integration, a second site, an additional review round, or a compressed deadline. This is different from a price-adjustment clause, which addresses movements in agreed inputs. Change control governs a change in what will actually be delivered.

Establish a baseline before enforcing discipline

You cannot prove that a request is new when the original scope is vague. The baseline should define deliverables, assumptions, exclusions, review rounds, customer dependencies, milestones and acceptance criteria. The World Bank’s 2024 contract-management guidance emphasizes scrutinizing change requests and using a documented process rather than informal commitments.

Name one commercial owner for change orders. The delivery lead estimates operational impact and finance validates cost, but one person must have authority to quote, trade scope, or decline unpaid work. Without that ownership, delivery may promise an enhancement that sales and finance discover only at month-end.

Turn each request into a one-page decision

The record needs seven fields: requested outcome, reason it is outside scope, hours by role, external cost, schedule and risk effect, proposed price, and expected margin. Allow only three outcomes: paid acceptance, a scope swap that removes work of equivalent cost, or a reasoned rejection. “Start now and agree later” is not a valid fourth outcome.

Calculate the price as (direct delivery cost + support and risk allowance) ÷ (1 − target margin rate). When the customer requests acceleration, add the actual cost of parallel work, overtime or supplier expedites instead of an arbitrary percentage. Compare the result with the account’s cost to serve; a contract can look profitable while repeated unbilled changes make the relationship uneconomic.

Hypothetical example: a small request consumes most of the margin

Assumptions: a QAR 240,000 contract has planned cost of QAR 168,000, producing QAR 72,000 gross margin, or 30%. The customer requests an additional integration requiring 140 hours at a fully loaded cost of QAR 260 per hour, plus QAR 8,000 for testing and support. Incremental cost is 140 × 260 + 8,000 = QAR 44,400.

If the company absorbs the request, margin falls to QAR 27,600, only 11.5% of revenue. Passing through cost is not enough to preserve the original margin. At a 30% target, the change price is approximately 44,400 ÷ 0.70 = QAR 63,429. The proposal could be rounded to QAR 63,500 with the revised milestone. If the customer declines, offer a scope trade that removes work with comparable cost.

A practical one-week implementation

1. Review five active contracts and mark unlimited deliverables and ambiguous assumptions.
2. Create a shared change log with ID, owner, status, decision and approval date.
3. Set a rule that out-of-scope work cannot begin without written approval, except for a time-limited emergency path.
4. Estimate with fully loaded role costs, not salaries alone.
5. Review open requests weekly across sales, delivery and finance.

Metrics that show whether the control works

• Value of unbilled out-of-scope work as a percentage of revenue.
• Share of change requests decided before work starts.
• Median cycle time from request to decision.
• Forecast versus realized margin after changes.
• Acceptance and invoice disputes linked to scope.

Do not penalize teams for logging changes, or they will hide them to protect delivery speed. Nor should every clarification become a billable event; ambiguity created by the supplier remains the supplier’s responsibility. The opposite failure is bureaucracy. If approval takes two weeks, informal promises return. Create a fast lane for low-value requests and a clear authority limit for the project manager.

The decision

Start with the three largest active contracts, not new software. Create a baseline, log and decision card, then monitor free work and post-change margin for one month. If loss continues, the problem is not only the original price; it is the decision gate after signature. Use the wider B2B margin-leakage view to connect change control to quotation, delivery and collection.

اقرأ المقال بالعربية

Sources: World Bank Contract Management Practice, June 2024; World Bank Procurement Regulations: contract change management.