Freelance pricing decision
When Should a Freelancer Reprice a Project?
Reprice a project when new facts make the commercial commitment materially different from the assumptions behind the current fee. Common triggers include added deliverables, compressed timing, more reviewers, extra revision rounds, missing client inputs, expanded rights, greater implementation responsibility, or risk that was not visible when the original price was set.
Repricing is not a penalty for a client changing their mind. It is a correction when the work, timing, responsibility, or risk no longer matches the assumptions used to create the current offer.
Trigger 1
The deliverable grew
A five-page website now includes copywriting, analytics setup, migration, or a launch campaign. A logo package now includes a complete social system. A strategy engagement now includes implementation.
The work may still be attractive, but it is not the same offer. Restate the expanded deliverable, remove items if the budget must remain fixed, or issue a revised price before commitment.
Trigger 2
The schedule became denser
Urgency can require evening work, parallel tasks, faster decisions, held capacity, or moving other clients. Even when total production hours look similar, the schedule can carry a different opportunity cost and delivery risk.
Ask which date is truly fixed and which milestone is required. If urgency remains, price the actual working conditions and make the client’s input deadlines explicit.
Trigger 3
More reviewers or revisions appeared
One approval owner and two consolidated rounds are different from five stakeholders submitting separate feedback until everyone is comfortable. Review coordination is work, and conflicting authority creates rework risk.
Reprice when the review structure exceeds the assumptions behind the original fee. Alternatively, preserve the fee by restoring the original reviewer and revision boundary.
Trigger 4
Dependencies moved to the freelancer
A quote may assume the client supplies final copy, product data, access, or approved assets. When those inputs are missing and the freelancer is asked to research, create, clean, or chase them, responsibility has expanded.
Name the newly owned dependency. Decide whether it becomes a separate deliverable, a client responsibility with a later date, or a reason to decline the current conditions.
Trigger 5
Rights, risk, or implementation responsibility changed
Expanded licensing, source-file transfer, production deployment, regulatory review, performance guarantees, or responsibility for a third-party system can change the commercial exposure even if the visible artifact is similar.
Do not guess at legal consequences. Identify the changed term, obtain appropriate professional advice where needed, and issue a revised offer only when you understand what you are taking on.
- State the changed assumption without blame.
- Offer a revised scope and price or restore the original boundary.
- Confirm timing and approval before commitment.
- Decline when the remaining risk is unacceptable.