Are extra fees reasonable for mid-project feature additions?
The clear answer: if additions exceed the written scope at signing, charging extra is fair; conversely, billing again for already-covered items is not. The sole criterion is the documented scope, not subjective arguments.
In practice, mid-project additions causing disputes are common in custom builds. Cases often arise where clients expect quick additions while developers see extra work, due to undefined deliverables at contract time.
This article explains fee origins, how to distinguish fair versus unfair charges, pre-signing scope definition, and change workflows. For early-stage readers, consult a website setup guide first.
Why extra fees arise: distinguishing changes from original scope
Custom sites are coded line-by-line to needs, so new requirements equal new hours and costs—an objective fact.
Two types exist: genuine changes are post-signing requests for undiscussed features, like adding a cart to a brochure site, which is billable; false extras involve splitting already-agreed items for repeat payment, which is unfair.
The difference hinges on written scope coverage. Gray areas emerge from incomplete specs, such as whether contact forms include notifications or spam protection.
Fair versus unfair extras: comparison table
The table below aids judgment on whether charges are justified.
| Dimension | Fair extra | Unfair extra |
|---|---|---|
| Origin | Post-contract new request | Already listed but re-charged |
| Scope basis | Not covered in writing | Arbitrary contract interpretation |
| Pricing clarity | Itemized hours | Single total without details |
| Cause | Client-driven change | Developer oversight billed to client |
| Timing | Quote and agree before work | Inform after completion |
| Amount | Market-comparable | Excessive and punitive |
Fair extras cover new work; unfair ones repeat charges. Multiple red flags warrant negotiation.
Some clients treat custom work as unlimited service, causing scope creep that burdens developers. Fair pricing supports project health.
Common gray areas and dispute prevention
Most conflicts arise from mismatched expectations in undefined areas. Frequent examples include form extensions, responsive design depth, revision definitions, CMS capabilities, and content provision duties. Document these explicitly before signing.
Six essential scope items before signing
Ninety percent of prevention occurs pre-contract. Required items cover total pages, feature lists, revision caps, exclusions, asset sources, and change processes.
| Item | Why it matters | Example |
|---|---|---|
| Total pages | Prevents page-count disputes | 1 home + 5 templates = 12 pages |
| Feature list | Itemized to avoid omissions | Login, form with notifications |
| Revision count | Caps prevent endless edits | 2 design rounds, then hourly |
| Exclusions | Closes gray zones | No payment gateway, no copywriting |
| Asset provider | Clarifies responsibilities | Text and photos by client |
| Change process | Pre-agrees handling | Written order then quote |
Explicit exclusions are especially effective at eliminating ambiguity.
Four-step change process for mid-project requests
Follow written request, impact quote, mutual approval, and record retention for all changes to minimize friction.
| Step | Action | Reason |
|---|---|---|
| Written request | Email or form detailing needs | Creates traceable record |
| Impact quote | Assess hours, cost, timeline | Know trade-offs before starting |
| Mutual approval | Written sign-off first | Agree on money before work |
| Retain records | Attach to contract | Supports acceptance and maintenance |
This converts risky post-work billing into safe pre-work agreement.
Conclusion: clear specs and processes protect everyone
Fee disputes stem from poor communication. Focus on written scope at signing, detailed pre-contract specs, and standardized change steps. Choosing partners willing to clarify scope reduces future costs.
