Client budget below your quote? Change the scope with numbers
A worked $80,000 budget example separates a discount from a scope change, with three options you can explain in a fixed-price negotiation.
Start with the cost the budget can support
Suppose a client has an $80,000 budget. Your current project model gives a P80 cost of $68,000. At a 20% target gross margin, the corresponding quote is $85,000: $68,000 divided by 0.80. These are hypothetical inputs, not industry benchmarks.
The useful question is not “How do I remove $5,000 from the proposal?” It is “What can we deliver with a cost threshold of $64,000?” That threshold is the client's $80,000 price multiplied by 0.80. To keep the same margin target at the same modeled confidence, your revised P80 cost needs to fall by $4,000.
A discount and a scope change do different things
A price cut does not make the work cheaper. At a realized cost of $68,000, accepting $80,000 leaves $12,000 of profit and a 15% gross margin. You can choose that commercial tradeoff, but it does not preserve the original 20% target. The chance of achieving 20% now depends on how often your modeled cost is at most $64,000.
| Offer | Price | P80 cost | Margin at that cost |
|---|---|---|---|
| Original scope | $85,000 | $68,000 | 20% |
| Same scope, lower price | $80,000 | $68,000 | 15% |
| Revised scope, re-estimated | $80,000 | $64,000 | 20% |
Build an actual alternative
Imagine the original work includes a reporting module, data migration, and an integration with a poorly documented system. A useful revision might defer the reporting module and replace part of the integration with a documented manual handoff. Write down the changed deliverables, acceptance criteria, client responsibilities, and remaining uncertainty before editing the estimate.
Duplicate the project in BidVariance so the original remains available. Remove or revise the affected tasks, then revisit their associated risk events and dependencies. Rerun the model. The $64,000 P80 cost in the table is an assumed output of that revised model; it is not obtained by subtracting one task's P80 from the total. Percentiles generally do not add or subtract that way.
A phased offer can also be useful: price a tightly defined discovery phase first, then estimate implementation with what you learn. Be explicit that the later phase is not included in the initial price. Splitting a contract without reducing uncertainty does not itself make the project cheaper or safer.
Check what the client is actually buying
- Delivery: does the narrower scope still solve the client's central problem?
- Schedule: did removing work also remove a dependency, or does the same deadline bottleneck remain?
- Economics: compare modeled loss probability and margin-target probability at the actual offered price.
- Exposure: note what happens if an excluded requirement returns as a change request.
A concise explanation could be: “At $80,000, we can include migration and the core workflow, with reporting as a later phase. The estimate assumes one review round and the documented data format. Additional formats would need a separate estimate.” That describes a reviewable offer instead of disguising a discount as an efficiency gain.
Keep acceptance separate from delivery confidence
The simulation describes outcomes under your cost and duration assumptions. It does not predict whether the client will accept, whether your exclusions are enforceable, or whether the assumptions will hold. A lower modeled risk does not resolve those questions.
Use the bid price calculator to check price arithmetic, then read margin versus markup and contingency without double-counting before revising the full project.