Maintenance plan: how to price small edits without friction
Small edits are cheap in execution but expensive in interruptions. This framework helps agencies package routine updates clearly, protect margin, and give clients faster outcomes.
The real cost of “small edits” is interruption, not effort
A two-minute request usually creates a ten-minute context switch: locate the page, validate on mobile, run cache checks, and answer follow-up requests. Multiply that across clients and your production calendar gets fragmented.
Most pricing friction starts here: clients expect instant changes, agencies need protected focus blocks. A good maintenance plan aligns both realities.
Use your own assumptions
Estimate the monthly capacity behind small edits
This planning estimate prices the handling chain, not only the visible copy change.
Monthly handling time6 hours
Illustrative internal capacity cost0
Planning note: this excludes account management, rush premiums, structural work, and the value of uninterrupted production time. Replace every default with your own operating data.
See the Editly workflowDefine “small edits” in writing before launch
If you do not define scope, scope will expand by default. Keep your definition operational and easy to reference.
Contract-ready small-edit scope
- Copy-only updates: headings, paragraphs, button labels, short legal lines.
- No layout edits: no structure, spacing, or style-system changes.
- No net-new pages unless explicitly included.
- Bounded volume per month (credits or time).
This model protects the relationship because both sides can predict delivery.
Three pricing models that work
| Model | Best fit | Primary control |
|---|---|---|
| Credits | Solo practice or low request volume | Number and size of requests. |
| Time bucket | Growing studio with varied edits | Monthly handling capacity. |
| Tiers | Agency portfolio and repeatable delivery | Scope, response time, and review depth. |
1) Credit model
Best when requests vary but stay easy to classify. Define examples: one CTA change might be one credit; coordinated copy across five pages might be five. Avoid a complex tariff that takes longer to explain than the work.
2) Time bucket model
Best when trust is established and the work is unpredictable. Include a minimum billing unit, what happens to unused time, and a clear top-up rule.
3) Tiered maintenance model
Best when response time carries real value. Differentiate tiers by service outcome—response window, review depth, number of sites—not by an arbitrary feature pile.
The workflow shift that improves margins
The strongest maintenance plans remove low-value manual actions from your team. Give clients a safe path for routine copy edits in wp-admin, while your team keeps control of design and structural decisions.
For implementation references, use Builder stays intact, Audit log, and White label when client-facing governance is needed.
Then align the scope decision with Free vs Pro comparison.
Suggested client-facing pitch
“You can update routine copy directly in wp-admin whenever you need to. We remain responsible for layout quality and structural consistency. When a change needs design or validation work, it moves into your maintenance allowance and we confirm the timing before we start.”
Next step
Measure one month of real interruptions before setting the package. Then define the self-service boundary, your minimum viable response window, and the work that always requires a separate quote.