Every few months a prospect asks if we’ll split the engagement: build now, maintenance maybe later, with someone else or in-house. The answer is no. Not because we’re trying to lock anyone in — the contract is month-to-month — but because selling a WordPress build without maintenance attached is, in 2026, malpractice. The question keeps coming up, so here’s why.
The 50/50 model, briefly
Roughly half our revenue from any given client comes from the initial build; the other half from monthly maintenance over 12 to 24 months. A typical engagement might be $9,000 for a 6-page B2B site plus $450/month for maintenance, hosting, security, and content updates. Over 18 months that’s $9,000 + $8,100 — almost exactly 50/50. The split isn’t a pricing trick; it maps to where the actual work happens.
Why selling a build alone is malpractice
A WordPress site in 2026 is not a static document. It’s a running piece of software with five independent moving parts that need to stay in sync:
- Core WordPress — roughly one minor release every 8 weeks, one major release every 4 months
- The theme — typically 6 to 10 updates per year, some of which are breaking
- Plugins — a typical site runs 15 to 30 plugins, collectively pushing 50 to 80 updates per year
- PHP version on the host — major upgrade roughly once a year, breaking
- Browser standards and Core Web Vitals thresholds — Google moves the goalposts twice a year on average
That’s 75 to 100 update events per year, any of which can break the site silently. Selling a $9,000 build with no maintenance is selling a Tesla with no service plan. The site works great for three months, then drifts, then breaks, and the owner blames the builder.
What “maintenance” actually pays for
This is where the conversation usually gets stuck. “Maintenance” sounds like a vague monthly charge for nothing. It isn’t. Here’s what’s actually inside it:
- Pre-update snapshot, staged test, production rollout — repeated weekly across plugins and core
- Vulnerability response — when a critical CVE drops in a plugin we use, we patch within 24 hours, not whenever the client notices
- Performance regression monitoring — weekly Lighthouse scans; if PageSpeed drops below 90 we investigate before Google does
- Backup verification — actually restoring one to staging quarterly to prove it works
- Uptime monitoring + first response — if the site goes down at 2am Saturday, we know before the client’s first prospect does
- Minor content edits — 1 to 3 hours per month included
- SEO drift checks — title tags, schema, and sitemaps stay clean as the site evolves
$450/month covers roughly 6 to 9 hours of senior work. The owner is buying a guarantee the asset stays an asset and doesn’t quietly turn into a liability.
The “broken handoff” problem
The most expensive sites we ever inherit are the ones built by an agency in 2022, handed off to “someone the client’s nephew knows,” and left to drift until 2024. We’ve seen $14,000 builds where the recovery audit costs more than the original engagement — three plugins abandoned, staging no longer matches production, nobody knows the admin password, SSL expired six months ago.
Splitting build from maintenance invites this outcome by design. The builder has no skin in the post-launch game. The maintainer didn’t build it and doesn’t know why decisions were made. The owner sits in the middle paying both parties to argue about whose responsibility the broken thing is.
The objection I hear most often
“My nephew can handle maintenance for less.” Sometimes true. If they’re a working WordPress developer with their own staging environment, version-controlled backups, and a vulnerability monitoring subscription, great — we’ll do a clean handoff. But the honest version of “for less” is usually “for free and not actually getting done.” Six months later the site is two versions behind, three plugins are EOL, and the contact form stopped emailing. Nobody noticed because nobody was looking.
How AJD handles this
We quote build + maintenance together, always. Month-to-month, no contract, cancellable anytime. If a client wants to take over after 6 months or hand it to someone competent, we do a clean handoff — staging environment, backup history, written runbook. We just won’t sell the build alone, because we know what the site looks like in month 9 when nobody’s watching. Whether you work with us or not, ask your current vendor: “what’s your update cadence, and when did you last restore a backup to staging to verify it works?” If they can’t answer in one sentence, you’re already in the broken handoff.
Want a quote that covers the actual cost of keeping the site working? Book Free Discovery Call →
