How to Price a Scope Change Without Guessing
When a client says "can you add one more feature?", freelancers either lowball themselves or overprice and lose the gig. There's a formula that handles both.
If you want a second pair of eyes on your scope-change price, I can review it for $10 and tell you whether the number is too low, too vague, or ready to send. Just send me your scope doc or pricing page and I'll reply within 24 hours with specific improvements: paypal.me/cheapuno
$10 Quick Review — Is Your Pricing Page Actually Working?
I've reviewed 12 freelance pricing pages. 7 had no direct way to hire the person.
That means if someone reads your article and thinks "this could help me price my next project" — they leave without a way to work with you.
What you get:
- I review your pricing page or scope document
- Identify 2-3 specific improvements
- Give you exact wording that converts readers to clients
Delivery: 24 hours. $10 via PayPal: paypal.me/cheapuno
The Scope Change Pricing Formula
Change Price = (Extra Hours × Hourly Rate × Risk Multiplier) + Delay Cost
Step 1: Count the Extra Hours
Be honest. How many extra hours will this add? Don't sandbag, but don't pad either. Write down the real number.
Ask yourself:
- How many screens/files does this touch?
- Do I need to update tests?
- How long is integration testing?
Step 2: Apply the Risk Multiplier
| Risk Level | Multiplier | When to Use |
|---|---|---|
| Low | 1.0× | New feature, no integration |
| Medium | 1.3× | Modifies existing logic or database |
| High | 1.6× | Changes API, auth, or payment flow |
Why it matters: A standalone feature you can build in 4 hours might take 8 hours if it touches your existing data layer. The multiplier accounts for that.
Step 3: Add the Delay Cost
Projects with scope changes often slip. When you add features mid-project, everything else gets pushed back. You deserve compensation for that delay.
Delay Cost = Days Added × Daily Rate
Where Daily Rate = Your hourly rate × 8 hours
Worked Example: The Full Breakdown
You quoted $2,000 for a 2-week project. Client wants to add a user export feature. Here's how the number gets calculated:
Step 1 — Extra Hours:
- Building the export feature: 6 hours
- Updating existing tests: 1 hour
- Integration testing: 1 hour
- Total extra hours: 8
Step 2 — Risk Multiplier:
- Feature touches the existing data layer
- Moderate integration risk
- Multiplier: 1.3×
Step 3 — Delay Cost:
- This change adds 2 days to the timeline
- Your daily rate: $75/hr × 8 = $600/day
- Delay cost: $1,200
The Math:
Change Price = (8 × $75 × 1.3) + (2 × $600)
= $780 + $1,200
= $1,980
The Message You Send:
"Adding user export requires 8 extra hours of work. With the integration risk and 2-day schedule impact, that's an additional $1,980. Want me to proceed?"
They either say yes, negotiate, or drop it. Either way, you're not guessing — you have the math to back it up.
Your Turn: Price This Scope Change
| Field | Your Number |
|---|---|
| Extra Hours | _____ |
| Your Hourly Rate | $_____ |
| Risk Multiplier (1.0 / 1.3 / 1.6) | _____ |
| Days Added | _____ |
| Daily Rate (= hourly × 8) | $_____ |
| Change Price | $_____ |
The Exact Wording to Send Your Client
After calculating:
"Adding [feature name] requires [X] extra hours. With the integration risk and schedule impact, that's an additional $[price] and [N] days. Want me to proceed?"
FAQ
Q: What if the client pushes back on the price?
A: Reply with the math. "Here's how I calculated it: [X hours] × [rate] × [multiplier] plus [delay days] × [daily rate]. Happy to walk through each line." Most clients who push back haven't seen the breakdown — showing your work often ends the negotiation.
Q: Should I just give free advice to get the client to commit?
A: No. Free advice is what got you into this situation. Instead, offer a $10 quick review: "I can look at your full scope and tell you exactly what to charge. $10, 24 hours." This converts free consult seekers into paying clients without giving away your expertise.
Q: My client already agreed to a fixed price. How do I handle scope changes?
A: Go back to the contract. If there's a scope change clause, use it. If not, the exact wording helps: "My original quote covered [original scope]. This new feature falls outside that scope, so here's the additional cost." Frame it as protecting both of you, not as a money grab.
Q: What if the scope change is tiny — just a few hours?
A: Small scope changes still have hidden costs: context switching, re-testing, and re-explaining. Use a minimum multiplier of 1.1× even for "easy" additions. Better to quote slightly high and negotiate down than to lowball yourself again.
Q: How do I know if my original hourly rate is correct for scope changes?
A: Your original rate was probably calculated for the original project scope. Scope changes often warrant a higher effective rate because: (1) you're working on unfamiliar code someone else wrote, (2) the timeline pressure is higher mid-project, (3) communication overhead increases. Consider using 1.2× your normal rate as a scope-change premium.
Q: The client says "we'll handle this next phase" — how do I respond?
A: Get it in writing before the current phase ends. Reply: "Just to confirm — [feature name] is being moved to Phase 2, right? I'll include it in the next scope document." This prevents "I thought that was included" disputes later.
Already Have Articles But No Client Inquiries?
Most freelancers have great content — but no path from "read article" to "hire you."
What I review:
- Your main article or pricing page
- Call-to-action placement
- Offer clarity and conversion language
$10 quick review — 24-hour delivery: paypal.me/cheapuno
Or if you want a full scope assessment: For $25, I do a deep-dive review of your complete pricing structure, including scope-change policies, contract language, and negotiation scripts you can use immediately. paypal.me/cheapuno
Top comments (0)