The Build Is the Easy Part to Budget For
A marketing site project gets quoted at $8,000 to $15,000. That number is visible, negotiable, and has a clear end date attached to it. It gets approved, the work gets done, and it shows up as a line item everyone can point to. The build cost is the cost everyone talks about.
The cost nobody talks about — the one that actually determines whether your web operations are sustainable — is everything that comes after. And at ten or more sites running simultaneously, the math becomes uncomfortable very quickly.
What Maintenance Actually Costs Per Site
Maintenance is not a single task. It is a category of ongoing work that includes plugin security updates (which for a WordPress site can arrive multiple times per month and cannot be safely ignored), hosting management, SSL renewals, backup verification, uptime monitoring, and dependency audits. For a reasonably complex WordPress site, this alone represents two to three hours per month at minimum.
Then there is content management. Every live marketing site has a client or stakeholder who wants changes. Copy updates, new service additions, image swaps, campaign landing pages, team member updates. Individually these requests take 20–45 minutes each. Across ten sites they become a constant, low-grade operational drain that is nearly impossible to batch efficiently because the requests arrive asynchronously and each one requires context-switching into a different site's CMS.
Add analytics review — even a basic monthly audit of GA4 data across ten sites — and you are looking at three to five hours per site, per month, conservatively.
The Compounding Effect at Scale
At five sites, three to five hours per site per month means fifteen to twenty-five hours of pure maintenance work. Manageable. A senior team member can absorb it. At fifteen sites, it becomes forty-five to seventy-five hours per month — nearly two full work weeks dedicated to keeping things running rather than building anything new. At that point, the operations have consumed the team, and the only way to grow the portfolio is to hire specifically for maintenance work.
This is not a hypothetical. It is the actual operational reality for most agencies and in-house marketing teams that have accumulated a portfolio of sites without building a corresponding operational infrastructure. The sites were built one at a time, each as a bespoke project, with no shared tooling, no centralized deployment pipeline, no unified team access management. The overhead compounds with each addition.
Team Coordination as a Hidden Cost
Beyond the direct work hours, there is the coordination overhead. Who has access to which site? Who approved that copy change before it went live? Who is responsible for the plugin update that broke the contact form on a client's site last Tuesday? Without a centralized operations platform, these questions get answered through Slack threads, shared password managers, and institutional memory — all of which fail in predictable ways as teams grow or turn over.
The coordination cost is difficult to quantify precisely, but anyone who has managed a portfolio of sites without purpose-built tooling knows it is real and it is significant.