← All field notes

Price WordPress maintenance from the work you actually cover

The software bill is easy to put into a spreadsheet. The time spent chasing a missing license, explaining a failed form or waiting for client approval is easier to leave out. That is how a maintenance package can look profitable until the team starts delivering it.

Build the scope before choosing the price. This worksheet is an operating-cost exercise, not a claim about market rates or a substitute for advice from your accountant.

Write the service in observable terms

List the recurring work, the reporting schedule and the response commitment. Distinguish monitoring from incident resolution. Say whether content edits, emergency recovery, custom code and security investigation are included, capped or quoted separately.

Specify what the client must provide: active licenses, authorized access, a working staging environment where required and someone who can approve disruptive work. If those conditions are missing, your team may spend more time coordinating than maintaining.

Use the maintenance checklist to define a baseline, then adapt it to the site’s important workflows. A shop with several payment integrations should not inherit a brochure site’s testing allowance by accident.

Estimate delivery from a real sample

Measure a few maintenance sessions and include the surrounding administration. Record preparation, changes, verification, reporting and follow-up. Separate unusual onboarding repairs from recurring work so the first month does not distort every future estimate.

Use a loaded internal labor cost that reflects what an hour costs the business, not just what a contractor charges for a task. Add the software and storage attributable to the service, plus a clearly labeled allowance for expected exceptions.

A new service will involve estimates. Mark them as estimates and review them after you have actual delivery records. A precise-looking number is not more reliable merely because the spreadsheet shows two decimal places.

A small worked example

Suppose a hypothetical package has $30 in expected monthly delivery costs: labor allocated to the service, tooling and an exception allowance. At a $100 selling price, $70 remains before the business’s other overhead and taxes. The contribution margin on that simplified model is 70%, because $70 divided by $100 is 0.70.

That is an arithmetic example, not a recommended price or a standard industry margin. If delivery costs rise to $50, the same price leaves 50%. If you promise unlimited changes, the cost may not have a useful upper bound at all.

For a target contribution margin expressed as a decimal, the worksheet formula is price = expected service cost ÷ (1 − target margin). Be careful to define which costs you included; otherwise two margin figures may describe different things.

Make annual discounts pay for something

Annual payment can improve cash collection and reduce billing administration, but it does not remove twelve months of work. Model the full year’s expected delivery against the discounted revenue. Keep cash collected separate from profit earned.

Check the actual payment processor fees for your account rather than borrowing another agency’s rate. The SBA’s financial-management guidance is a useful reminder to maintain records and distinguish the financial views used to run a business.

Review scope before blaming the price

When a package underperforms, look at the work behind it. Is one client consuming repeated out-of-scope fixes? Are expired licenses creating avoidable delays? Would better onboarding reduce the recurring effort?

Use the client report to make exceptions visible, then discuss a scope change when the pattern is clear. Pick a date to compare the estimate with delivered hours. If you never revisit the assumptions, the worksheet will keep reporting the margin you hoped for rather than the one the service earns.


Have a correction or a workflow we should cover? Tell the IrmaWP team.