Stop losing money on scope changes. Here's the 3-step framework I use.
Last month a client asked to add "just one more feature" to a fixed-price project. I said yes. I lost $800.
The problem wasn't agreeing to the change — it was not having a number ready when they asked.
This is for you if...
- You're mid-negotiation with a client on a scope change
- You have a quote drafted but want a second opinion before sending
- You want to sound professional, not desperate, when asking for more money
$5 / $10 Scope Change Review
Two ways to get a second pair of eyes on your scope change:
$5 Scope Message Review
Send me your drafted reply or quote message. I'll tell you if it sounds professional, where the weak points are, and suggest cleaner wording. 24-hour delivery.
$10 Full Quote Evaluation
Send me your project scope + proposed change. I'll evaluate the price logic, client-facing wording, and give you a concrete revised number. 24-hour delivery.
How it works (both tiers):
- Send payment via: https://paypal.me/cheapuno
- Paste your scope change details or drafted message
- I'll send the review within 24 hours
- If I can't give useful feedback, I'll refund it — no hard feelings
Real Case Study: The $800 I Lost (And How to Avoid It)
This actually happened. Details changed to protect the project.
The Setup:
- Fixed-price quote: $1,500 (I estimated 20 hours, $75/h)
- Client: small e-commerce startup
- Deliverable: custom checkout integration
The Change Request:
Three weeks in, the client asked: "Can you also add a gift-wrapping option? It should only take an hour."
What I Did (Wrong):
I said yes. I figured one hour, no big deal.
The Reality:
- Gift-wrapping required: API changes + UI flow + testing + edge cases
- Actual time: 6 hours
- My "one hour" cost me: $450 (6 × $75)
The Pitch I Should Have Made:
"Love that we can add gift-wrapping! This touches the checkout API and requires about 6 hours of additional work. Here's the add-on: $450, which includes the feature + full testing. Want me to go ahead?"
Result with the right pitch: Client accepted. I made $450 instead of losing $450.
Key insight: Clients don't think "one hour" like developers do. Your "quick fix" is always longer than they expect. Have a number ready before they ask.
The 3-Step Scope Change Pricing Method
Step 1: Estimate the additional hours realistically
Multiply by 1.5x for your real hourly equivalent (not your "base rate").
Step 2: Add a scope change fee (15-25%)
This covers the coordination cost of re-opening finished work.
Step 3: Present it as a simple add-on price
Base: $X + Scope Addition: $Y = Total: $Z
Most clients accept this without negotiation if you frame it as a separate line item, not a surprise.
Scope Change Pitch Template (Copy & Paste)
Use this template when a client asks for a scope change:
Hi [Name],
Happy to look at adding [feature]. Let me review the scope impact.
[Feature] touches [areas it affects] and requires approximately [hours × 1.5] hours of additional work.
Here are two options:
Option A — Full implementation: $[calculated price]
Option B — Defer to Phase 2: $[lower price or original scope]
Let me know how you'd like to proceed.
[Your name]
When to use Option B: If the client pushes back hard, offer to defer the feature to a Phase 2 at the original rate. This gives them an "out" without you working for free.
Bad Wording vs Good Wording
| Situation | Bad Wording | Good Wording |
|---|---|---|
| Client: "Can you just add this one thing?" | "Okay, I guess I can add $200." | "This extends the scope by roughly 8 hours. Here's the add-on: $800 — I'll send a simple amendment." |
| Client: "This should only take 30 minutes" | "Um... okay." | "Actual time is closer to 3 hours. The adjustment is $225." |
| Presenting the extra cost | "So... it's going to cost more." | "Original quote: $1,500. New scope addition: $350. Total: $1,850. Here's the breakdown." |
The good examples share a structure: number first, then framing, then explanation. Remove the apology, add a clear next step.
Decision Checklist (Before You Send)
Before hitting send on any scope change communication:
- [ ] Have I calculated the real hours (not just guessed)?
- [ ] Did I apply the 1.5x multiplier?
- [ ] Did I add the 15-25% scope change fee?
- [ ] Is the price framed as a separate line item?
- [ ] Did I give the client two options (full vs. defer)?
- [ ] Is the wording neutral, not apologetic?
- [ ] Did I include a clear next step?
Example Calculation
Example calculation, not a universal pricing rule.
- Base quote: $1,500 (estimated 20 hours at $75/h)
- New feature estimated: 8 hours
- Apply 1.5x multiplier: 8 × 1.5 = 12 hours
- Adjusted rate: 12 × $75/h = $900
- Add 20% scope change fee: $900 × 1.2 = $1,080
- Add-on price: $1,080
Without the framework, you absorb the cost. With it, you charge fairly and keep the relationship healthy.
FAQ
Q: Client insists they won't pay more. What do I do?
A: Cut scope to fit the original price, or walk away. Going silent or accepting losses trains clients to push harder. Name the price and let them choose.
Q: How do I bring up extra cost without sounding greedy?
A: Frame it as a business decision. "I want to make sure this is done properly — the additional scope requires an adjustment of $X. Here's the breakdown." The word "adjustment" sounds less confrontational than "price increase."
Q: I already said yes. Can I fix this?
A: Send a follow-up: "After reviewing the scope more carefully, the extension requires $Y. Here's the updated quote." Most clients expect some negotiation — they won't be surprised.
Q: What if the client says "it should be included in the original price"?
A: "I appreciate that perspective. The original scope was scoped specifically for [deliverable]. This is an additional feature that wasn't in the original agreement. Here's the adjustment for the new scope." If they persist, offer Option B (defer to Phase 2).
Q: Should I ever do scope changes for free?
A: Only if: (1) you genuinely underestimated, AND (2) it's under 30 minutes of work AND (3) the client has been great to work with. Otherwise, charge. Free work trains clients to ask for more free work.
Q: How do I offer a downgrade path without seeming petty?
A: "I want to make this work within your budget. We can either (A) reduce the scope to fit the original price, or (B) defer this to Phase 2 at the standard rate. Which works better for you?" This frames the downgrade as a service, not a refusal.
Continue Your Pricing Journey
If this framework resonates: → The Freelance Scope Estimation Framework — the complete BR × SM × RB formula with real examples
If you want a calculator that applies the formula: → A 30-Second Pricing Decision Tree for Freelance Devs — 5 questions, get your price range instantly
If you want a second opinion on your next quote: → I offer $10 quick reviews — send your brief to paypal.me/cheapuno
If this helped you price your next scope change, send $5 or $10: https://paypal.me/cheapuno
Top comments (0)