The Twentieth Client Site Problem

Your first ten client sites are a portfolio. Your next ten are a workload. The thing that changes between them is not the sites, it is how many different ways you built them, and that number is a choice.

Nobody plans to have twenty differently built websites. It happens one sensible decision at a time.

Client three needed a booking form, so you added a plugin. Client seven wanted a members area, so you used a different one. Client eleven came with a site somebody else made and you patched it rather than rebuilding. Every one of those calls was correct on the day.

Two years later you are maintaining twenty stacks instead of one, and your support time grows faster than your income.

The curve nobody draws for you

Let us use a pretend shop so the numbers stay simple. Call it Pine Road Web, one person, twenty client sites.

Suppose each site needs an hour of unplanned attention per month when it is built the same way as the others, because a fix made once covers all of them. Now suppose a site built its own way needs three hours, because every change is a fresh investigation.

Sixty hours a month is a second job. Twenty is a normal week with room to sell.

Those are made up numbers to show the shape, not a measurement. The shape is the argument though, and anyone who has run more than a dozen client sites will recognise it immediately.

Why the pain arrives late

This is the part that makes it dangerous. At five sites the difference is ten hours and you absorb it, because you are excited and the work is interesting.

The penalty is invisible exactly when the decisions are being made, and obvious exactly when they are expensive to undo. By the time the curve hurts, fixing it means revisiting sites nobody is paying you to revisit.

So the useful moment to think about this is now, whatever now happens to be, because it will not get cheaper.

What sameness actually requires

Three things, and only the first one is about software.

1. One build you repeat. Same structure, same content shapes, same conventions. Site twenty starts as a copy of the system rather than a blank folder.
2. Checks that run without you. A script that finds broken internal links, empty sections and malformed data across every site you run. You find out from the job, not from the client's nephew.
3. The discipline to refuse a better one off. This is the hard one. A custom solution will sometimes be slightly better for one client and worse for your business, and saying no to it is the actual skill.

That third point is where most shops lose. The software was never the obstacle. The temptation to make this one special was.

The exception worth keeping

None of this means every client gets an identical website. Design, content and strategy should differ wildly, because that is the part the client is paying for.

What stays the same is underneath. Where content lives, how pages route, how structured data is generated, how the site is deployed and checked. The client never sees any of it and it is the whole reason site twenty does not ruin your month.

Think of a good restaurant kitchen. Every dish is different and every station is identical. Nobody reorganises the knives because tonight's special is unusual.

Where to start if you are already at twelve

Do not migrate anything. Moving a working site nobody is unhappy with spends your time and earns you nothing.

Instead, pick the system you want and use it on the next build. Then the one after. Older sites move when they were due a rebuild anyway, which is a conversation the client is already expecting and will usually pay for.

Within a year most of your active work sits on one build, and the twenty stack version of your business quietly stops being your future.

Related reading: how you deliver client sites walks through the six step build, and the multi-site management glossary entry covers the vocabulary. The platform directory is where to compare the options.