From Solo Dev to Agency: How Your CMS Choice Evolves

I had 12 WordPress sites to maintain and every Monday felt like patch day at a company I didn't sign up to run. Security update here, plugin conflict there, one client's Elementor license expired and their forms silently broke over the weekend. I was billing for new features but spending half my time just keeping the lights on.

That's the scaling trap no one talks about when you go from freelancer to running a small agency. The CMS that worked perfectly for your first three clients becomes a full-time ops job at ten.

TL;DR: The right CMS for a solo dev (fast to spin up, familiar ecosystem) is often the wrong CMS for an agency (high per-site cost, fragmented maintenance, hard to standardize). WordPress works until you're managing 8+ active client sites simultaneously. Webflow works until you see the per-site pricing. The real answer at agency scale is a self-hosted open platform where you control the stack — one server, all clients, one update cycle.

Stage 1: The Solo Dev CMS (1–3 Clients)

When you're starting out, the right CMS is the one you can ship with on Friday afternoon. Speed matters more than architecture.

For most freelancers, that means WordPress. You know it, your clients know it, there's a theme for everything, and you can hand it off with a 30-minute screencast. The ecosystem is enormous — 60,000+ plugins, unlimited theme options, thousands of tutorials for every edge case.

At 1–3 clients, the tradeoffs are manageable:

• Maintenance overhead: minor — maybe 2 hours a month per site
• Cost: essentially zero for the platform itself (hosting + domain is the main bill)
• Speed to launch: days, not weeks
• Client handoff: easy — editors know WordPress or can learn it from YouTube

Webflow is also a solid pick here, especially if you're doing marketing sites with a lot of design work. The visual builder is genuinely good, client handoff is clean, and you don't need to think about hosting. It's also where designers who code often feel most comfortable.

Ghost is a third option worth naming — clean, fast, and built for content-focused sites. If a client runs a newsletter or a blog-heavy site, Ghost fits better than WordPress in many cases.

The solo dev CMS decision comes down to: what you're fast with. The tech debt you accumulate at 1–3 clients is low enough that "familiar" beats "optimal."

Stage 2: The Scaling Problem (5–15 Clients)

This is where things get messy, and it usually happens faster than you expect.

You win a few referrals. Your existing clients recommend you to their network. You bring in a part-time developer to help with delivery. Suddenly you have 8 active client sites and the Monday morning routine goes like this:

1. WordPress core update available (3 sites)
2. Plugin update queue: 47 plugins need attention across 7 sites
3. One site's security plugin flagged a brute-force attempt overnight
4. A client emailed: their contact form stopped working after a plugin auto-updated
5. Another client's Yoast license expired; their SEO settings disappeared from the editor

You're not billing for any of this. And it never stops.

The per-site cost problem gets real here. Let's run the actual numbers for a WordPress-heavy agency:

That $900–$2,000/month isn't profit — it's overhead you either eat or pass to clients who then question why their "simple WordPress site" costs so much.

Webflow has an even sharper edge here. At $23/month per Business site, 10 client sites cost $230/month just in Webflow fees before hosting or labor. And you can't self-host — you're locked to Webflow's CDN, their pricing tiers, their editor limitations. If a client wants a feature Webflow doesn't support natively, you're writing custom JavaScript hacks or telling them no.

"The Webflow model works great when you're building sites for clients who never need custom backend logic. The minute they want a member portal or a custom data dashboard, you're stuck." — common pattern in the r/webdev community

What else breaks at this stage:

• Standardization is impossible. Each WordPress install has a different combination of plugins, theme, PHP version, and custom code. There's no "agency standard build" — every site is a snowflake.
• Security surface grows linearly. Each site you add is another target. One compromised plugin can spread. Patchstack's 2024 report counted 7,966 WordPress vulnerabilities — most in plugins, not core.
• Knowledge transfer is painful. When you hire someone, they have to learn 8 slightly different codebases, not one consistent stack.
• Client expectations diverge. The editor experience on Site A (built with Divi) looks nothing like Site B (built with Gutenberg), even though both are "WordPress."

This is the stage where you start Googling "cms for agencies" at midnight.

Stage 3: The Agency Stack Decision

When you hit the scaling wall, you have three real paths:

Path A: Standardize on WordPress (managed toolkit). Pick one page builder, one plugin set, one hosting provider, and enforce it across every new client. MainWP or ManageWP can give you a central dashboard. This is the path many agencies take because it requires the least change.

The downside: you're still paying per-site on hosting and plugins. You're still on WordPress's security treadmill. You're standardizing a fragmented ecosystem, not replacing it.

Path B: Go full Webflow agency. Webflow has an Agency plan and a team dashboard. Visual design quality is high, client editors love the interface, and handoffs are clean.

The downside: $23/month per site (Business tier) adds up fast. No self-hosting option. No backend customization without hacking. You're fully dependent on Webflow's pricing decisions — and they raised prices in 2022.

Path C: Move to a self-hosted open platform. One server, one codebase, one update cycle. All client sites run on the same stack. You update once, it benefits everyone. Your team learns one system deeply instead of ten variations.

This is what actually scales.

CMS Comparison: WordPress vs Webflow vs Self-Hosted at Agency Scale

Here's what each option actually looks like when you're running 10+ active client sites:

The self-hosted path is the clear winner at scale on cost and maintainability. The tradeoff is the initial setup investment — you need someone who can provision a server, set up SSL, configure a web server, and deploy a PHP/Node/whatever-your-stack application.

For a developer-run agency, that's a morning's work. For a non-technical agency, it's a blocker.

See also: the hidden costs of WordPress breakdown for a deeper dive into what you actually spend, and our self-hosting TCO comparison for the numbers over 5 years.

The Economics at Each Stage

Let's put real numbers on it. These are estimates based on typical agency setups, not worst-case or best-case.

The self-hosted column barely moves as you add clients, because you're adding sites to one server, not spinning up new paid instances. A $20/month VPS (Hetzner CX22, DigitalOcean Basic, Vultr) handles 10–20 modest sites without breaking a sweat. At 50 clients, you might need a bigger server or a second box — still orders of magnitude cheaper than per-site SaaS pricing.

This is exactly what self-hosted CMS for agencies covers in detail: the architecture, the server sizing, and how to structure client deployments.

What Platform Makes Sense at Agency Scale?

The honest answer: any self-hosted open-source CMS you and your team will actually maintain. The technology is less important than the commitment to standardization.

That said, here's how common options compare for agencies:

WordPress (self-hosted, no managed hosting): Brings cost down but keeps the plugin/maintenance complexity. You still have 10 different plugin configurations to manage. Better than managed WordPress, but still fragmented.

Ghost (self-hosted): Great for content-focused sites. Clean API, fast, easy to run on a VPS. The limitation is it's opinionated about content types — it's a blog/publication platform, not a general-purpose CMS. If clients want custom post types or complex content models, you'll hit walls.

Payload CMS / Strapi: Headless-first, Node.js based. Good if your team lives in JavaScript. The self-hosting story is solid; you control everything. Setup requires more technical investment than traditional CMSes. See our best self-hosted CMS platforms guide for the full comparison.

UnfoldCMS (what we built): A Laravel + React CMS built for developer teams who want a clean, modern stack. Built-in content management (posts, pages, custom content types), media library, user roles, SEO tools, and a shadcn/ui admin. You install it on a VPS and run as many client sites as the server handles.

One honest note on multi-tenancy: UnfoldCMS does not have native multi-tenant architecture where one application instance serves multiple client databases. The verified, working approach is to run separate installs for each client on one VPS — each with its own database and application directory, proxied through Nginx. This is more setup work than a single-instance multi-tenant system, but it gives you full isolation between clients. Each install is independently deployable, and one client's problem doesn't affect another. See /cms-for-agencies for the deployment pattern.

What to Migrate First When You Outgrow Your Current CMS

Not all client sites are equal. When you decide to move to a better stack, start smart:

Migrate these first:

1. Your own agency website — zero client approval needed, immediate learning opportunity
2. New clients — start every new engagement on the new stack so your install base naturally shifts
3. Simple brochure sites — low complexity, low risk, easy wins for the new workflow
4. Clients who are already unhappy — a migration is easier to sell when there's existing frustration

Leave these for later (or consider leaving them):

• Sites with deeply customized WooCommerce setups — e-commerce migrations are painful and rarely worth the risk
• Sites running complex membership systems tied to specific plugins
• Clients who have explicitly said they're happy and don't want disruption

The migration conversation with clients: Frame it as an upgrade, not a disruption. "We're standardizing our stack so we can serve you faster and more reliably" lands better than "we need to rebuild your site." Give them a what-to-expect document, a training session on the new editor, and a clear timeline. Most clients don't care about the technology — they care that their site works and that editing is easy.

Also check our avoiding vendor lock-in guide before you start — it covers how to structure data exports and contracts so you're never trapped by a platform choice again.

FAQ

Does WordPress still make sense for agencies in 2026?

Yes, for some agencies. If your clients are predominantly small businesses who need e-commerce (WooCommerce), large plugin ecosystems (LMS, membership, etc.), or editors who already know WordPress, it can still be the right choice. The problems show up at scale — 10+ simultaneous active sites with different plugin configurations creates real maintenance overhead and cost. The question is whether your agency type compounds those problems.

Is Webflow worth the per-site cost for agencies?

Webflow's Agency plan gets cheaper per seat, but the $23/month/site Business plan still adds up at scale. Where Webflow earns it: design-heavy marketing sites where visual quality is the main deliverable and clients genuinely don't need backend customization. Where it doesn't earn it: any project requiring custom logic, non-standard content types, or clients who want to move to a different platform later. The vendor lock-in is real — there's no clean data export path.

Can I run multiple client sites on one VPS with UnfoldCMS?

Yes — with separate installs, not a single multi-tenant application. Each client gets their own directory, database, and .env config on the server. Nginx routes each domain to its install. This gives you full isolation between clients (one client's issue can't affect another) and independent deployment per site. The management overhead is more than a native multi-tenant system, but for 5–15 client sites it's very manageable. We have a step-by-step setup guide at /cms-for-agencies.

When should I actually make the switch away from WordPress?

When you notice you're spending more time on maintenance than on billable work — that's the clearest signal. Secondary signals: you're losing bids because your per-site overhead makes your pricing uncompetitive; your team spends time re-learning different plugin configurations per site; a single plugin conflict broke a client site and you couldn't diagnose it quickly. The switch is painful to plan but usually pays off within 6–12 months of running the new stack across multiple clients.

The Bottom Line

The CMS you start with isn't the one you scale with. That's not a failure — it's just how tools work. A skateboard is the right transport for one person on a smooth sidewalk. It's the wrong transport for moving a team across a city.

WordPress is a fine skateboard. At 12 active client sites, you need a different vehicle.

The agency-scale answer is a self-hosted platform on a VPS you control: one update cycle, one stack for your team to know, infrastructure costs that grow slowly rather than linearly. The upfront investment is real, but the compounding savings and operational clarity are worth it.

If you're at the inflection point right now — somewhere between "this is manageable" and "I can't keep up" — look at your maintenance hours over the last month. If they're not billable and they're growing, you already have your answer.

Explore what agency-scale self-hosting looks like: /cms-for-agencies | See pricing | View all features

Sources

• Patchstack Vulnerability Database, 2024: 7,966 vulnerabilities reported in WordPress ecosystem
• Webflow Business Plan pricing: webflow.com/pricing (verified June 2026)
• WordPress.org: w3techs.com market share data, Q1 2026
• Hetzner CX22 pricing: hetzner.com/cloud (€4.51/mo as of June 2026)
• Community patterns sourced from r/webdev, r/selfhosted, and agency developer discussions on Hacker News