How to Price Out-of-Scope Work Without a Long Proposal

The client loves the staging site. Then comes the addition — two new templates, a webhook, "probably small."

You know a full proposal will sit in their inbox for a week. You also know if you start without a number, you will eat the work and resent them by Friday.

Out-of-scope pricing does not need a ten-page deck. It needs a repeatable micro-format you can send in twenty minutes.

The mini change order format

For most freelance add-ons, four lines beat four pages:

1. What — one paragraph of deliverable
2. Price — fixed fee or capped hours
3. When — ship date and what it pushes
4. Approve — "Reply yes to start"

Subject line: Add-on — webhook + 2 templates ($X)

Attach nothing if the thread is the record. For bigger adds, append to the statement of work as v1.1.

Price fast with a simple formula

Rough math beats paralysis:

• Estimate focused hours (include test + deploy)
• Multiply by your effective rate, not your aspirational one
• Add 20–30% buffer for client feedback and context switch
• Round to a clean number ($750, not $743)

Run the request through the scope creep calculator if you are unsure — seeing compound hours across clients stops you from discounting "just a webhook" into free work.

Scripts to send the number same day

Standard:

"Looked at this against our SOW — it is out of scope. I can do [deliverable] for $X, delivered by [date]. Reply yes and I will slot it in."

Two options:

"Option A — templates only, $X by Friday. Option B — templates + webhook, $Y by next Wednesday. Which works?"

Trade:

"I can include the webhook if we move the blog migration to phase two. Want me to send both paths?"

Same collaborative tone as change orders without sounding difficult.

Fast quotes still need a clear today.

WorkFocus helps freelance developers see signed milestones and add-ons across clients — so priced work gets done, not buried.

Try WorkFocus free

When to escalate from mini quote to full proposal

Use a fuller freelance proposal when:

• The add-on is bigger than 30–40% of the original fee
• New stakeholders appear with new requirements
• Timeline, stack, or hosting assumptions change
• You need a new phase with its own deposit

The client is not wrong to want detail on large shifts. They are wrong to expect large shifts for a small-add price — and you set that boundary.

Start before approval and you retrain the client

The fastest quote is worthless if you begin without a yes.

Hold the branch. Send the number. Wait for approval. Starting early teaches them that scope is optional — the root problem behind scope creep.

Keep a personal rate card for common add-ons

Maintain a private list:

• Extra revision round — $X
• Additional template page — $Y
• New integration (standard API) — $Z range
• Rush fee (< 48h) — +25%

You will quote faster and more consistently. Clients get predictable economics. You stop reinventing math under pressure.

The bottom line

Price out-of-scope work with a short change order, a simple hour formula, and same-day follow-through. Save full proposals for phases, not pings.

When priced add-ons still compete with everything else on your plate, try WorkFocus free — so freelance developers can see what is in scope today across every client.