# An Agency's Maintenance Load Tracks Site Count Not Headcount ## Claim An agency's real maintenance burden scales with the number of sites it manages, not the number of people on staff, so a small team can carry portfolio-scale risk. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds for ongoing-care relationships where an agency hosts, secures, and patches sites for the life of the client relationship, not one-time deliverable builds. - The distortion is sharpest at the extremes: the survey shows 47% of solo/small agencies manage 20+ sites, while a third of the largest (10+ person) agencies manage 20 or fewer. - Breaks where sites ship once and the agency has no ongoing responsibility — then team size, not portfolio size, is what matters again. ## Evidence The CloudLinux/WebPros survey of 210 WordPress agencies found plugin/theme updates as the top security challenge scales with portfolio size (65% overall, rising to 75% at 100+ sites), and that 45% of agencies running 100+ sites still update manually, one site at a time — disproportionately concentrated among agencies with the least staff to absorb that load. Headcount predicts almost nothing about workload; site count predicts almost everything. ## Links - [[AI & the Future of Knowledge Work MOC]] — why cheap building raises the maintenance bill rather than the delivery ceiling - [[3. Resources/Permanent Notes/AI Adoption Concentrates Where It Is Pleasant Not Where the Pain Is]] — because extends: this note names the load that automation isn't reaching; that note explains why automation skips it anyway. - [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]] — because extends: the same invisible-work bias that keeps maintenance unautomated also keeps it staffed at headcounts sized for the visible work. - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — because applies-in: portfolio-scale patching is the operational reality any hosting-security standard has to assume, not team size. ## Tests / falsifiers - Compare incident/breakage rates for agencies grouped by portfolio size, controlling for headcount, against agencies grouped by headcount, controlling for portfolio size — see which grouping actually predicts outcomes. - Track whether an agency's growth in headcount (without a matching drop in site-per-employee ratio) measurably reduces its manual-patching rate. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [WordPress Agencies Aren’t Afraid of AI. They’re Buried in Updates.](3.%20Resources/Readwise/Full%20Document%20Contents/Articles/WordPress%20Agencies%20Aren’t%20Afraid%20of%20AI.%20They’re%20Buried%20in%20Updates..md) — the 47%/one-third headcount-vs-portfolio cross-tab and the 45%-manual-at-100+-sites figure.