Price extra work

Give every extra client request a number before it gets a yes.

The hardest part of charging for extra work is not the math. It is making the impact clear early enough that the client sees a normal project decision, not a surprise invoice. EasyScope turns a request into effort, cost, delay, and a clean next step.

Pricing moment

before acceptance

The request is still a decision, not a hidden obligation.

Request pricing

Live project
Client ask
New onboarding email flow
Estimated effort
7 hours
Additional cost
560 EUR
Delivery shift
+1 day

Client ask

New onboarding email flow

Estimated effort

7 hours

Additional cost

560 EUR

Why it matters

Extra work gets underpriced when it stays conversational.

A friendly request can still be real work. You need a lightweight way to translate it into scope, price, and timing.

You answer too quickly

A fast 'sure' feels helpful, but it can commit you to hours you never quoted.

The client sees only the visible task

They may not see QA, revisions, admin, documentation, or knock-on schedule changes.

You invoice too late

Charging after delivery feels like a dispute. Pricing before approval feels like a choice.

The EasyScope way

A simple pricing flow for extra requests

EasyScope makes the commercial impact visible without forcing you into a long negotiation.

01

Capture the request exactly

Write down what changed, which deliverable it affects, and whether it was part of the original scope.

02

Estimate effort and schedule impact

Use your rate, workday settings, project budget, and current workload to show the real impact.

03

Offer a clear decision

Send the client an approval path: accept the extra cost, defer the request, or keep the original scope.

Proof points

Pricing that stays connected to the project

EasyScope helps you avoid a separate spreadsheet, a separate email script, and a separate invoice trail.

Rate-aware calculation

Use the project billing mode, rate, and workday settings.

Budget visibility

Show current and projected budget usage before the client decides.

Approval workflow

Turn priced work into a change order, quote, invoice, or deliverable.

Diplomatic copy

Draft a calm explanation when you need to push back.

No awkward surprises

Pricing without making it weird

Should I charge for every tiny request?

Not always. The point is to know the impact, then choose deliberately whether to include, defer, decline, or charge.

What if the client expects it for free?

Show the effort and timeline impact. The conversation becomes about tradeoffs rather than personality.

Can this work for hourly and fixed-price projects?

Yes. Hourly projects need clarity; fixed-price projects need boundaries. EasyScope supports both billing styles.

Stop turning new requests into invisible labor.

Price the change while it is still a decision and protect the project before delivery pressure takes over.

Price an extra request