Almost every WordPress agency tries to run their own maintenance program at some point. The logic is intuitive: clients ask "what about ongoing support?" after launch, the agency does not want to lose them, so they package up some hours and call it a maintenance plan.
The unit economics rarely work, and most agencies eventually realize this and either kill the program or outsource it. Here is what the math looks like up close.
The pricing trap
Agency maintenance plans typically land at $50-150/month per site. The pricing comes from "what clients will tolerate," not "what it actually costs to deliver well." Calculate the underlying unit cost and the gap is uncomfortable.
For a single site at the standard "small" tier, here is what a real maintenance month looks like:
- Tuesday updates: ~30 min of careful work for plugins, themes, core.
- Backup verification: ~10 min weekly to confirm backups completed and a monthly restore test.
- Monitoring response: variable, but assume 30 min/month of investigating false alarms or short outages.
- Monthly performance check: ~20 min to run PageSpeed and review Core Web Vitals.
- Customer report: ~15 min to compile a one-page summary.
- Email and ticket overhead: ~30 min/month average across the year.
That is roughly 3-4 hours of attention per site per month at the basic tier. At a senior engineer's realistic billable rate of $100-150/hour, the cost to deliver well is $300-600/month. Selling it for $99/month is structurally a loss.
Why agencies do it anyway
The accounting is not "this site's maintenance costs $300/month and we sell for $99, so we lose $201." Agencies treat it as relationship insurance: keeping the client on monthly contact, so when they need a redesign in 18 months, the agency is still front of mind. From that lens, even a money-losing maintenance plan is cheap customer retention.
The problem is operational. Maintenance work is interrupt-driven, off-schedule, and not pleasant. It bleeds into design and development time. The senior engineer who is supposed to be billing on a $40K project ends up firefighting a hacked client site for three days.
What changes when agencies outsource
Two things, mostly:
1. The unit economics flip
Outsourced maintenance at agency-partner discounts puts the per-site cost at $40-130/month depending on tier. The agency continues charging $99-199 to clients. Margin per site lands around $50-100/month — modest but actually positive, and predictable.
2. The agency's talent stops being interrupt-driven
This matters more than the dollars. When senior engineers are not getting paged at 9pm because a client's contact form broke, project delivery improves. New project quality goes up. Senior engineer retention goes up.
What the right partnership looks like
Most agencies that try outsourcing settle on one of two models:
- Pure pass-through. Each client gets billed by the maintenance provider directly; the agency takes a referral cut. Lower margin but zero operational overhead.
- Agency-of-record. The maintenance provider works under the agency's account, all comms run through the agency, the agency bills the client at retail and pays wholesale. Higher margin, but the agency stays in the loop.
The Ainygo agency program is the second model. Each agency keeps a single account with us, all of their managed sites under one umbrella, and bills their clients whatever they want. We never contact end-clients directly. The discount on published rates lands around 30-40% depending on volume.
When agencies should keep maintenance in-house
Two scenarios:
- The agency has a dedicated maintenance team — not engineers loaned from project work, but a separate ops function. This works at scale (20+ maintained sites, 1+ FTE on maintenance), rarely below.
- The agency only manages a handful of long-tenured strategic clients where the relationship economics dominate the unit economics. A dozen sites, all loyal, no growth ambition. Manageable.
For everyone else, the question is not whether to outsource. It is when to admit the math.