When a twelve-page website is premature

Ask a founder why the site has twelve pages and the honest answer, most of the time, is that the agency's sitemap template has twelve pages. Home, About, Services (with three or four sub-pages, one per thing the company might someday do), Case Studies, Blog, Careers, Contact. Nobody sat down and decided the company needed twelve pages. Somebody filled in a structure that was designed for a company five years further along, and the client, having no site to compare it against, assumed that was simply what a website is.

The honest counter-argument deserves to be said first, because it is a real one: a bigger site does communicate ambition, and a services page for something you don't sell yet can occasionally close a deal by making the company look further along than it is. That effect is real and it is also small, situational, and nowhere near large enough to justify what a twelve-page site actually costs once it exists — which is not the cost of building it, but the cost of the eleven pages nobody has a reason to go back and touch.

The cost is not the build, it's the standing debt

A page is not a one-time expense. It is a recurring one, quietly, whether or not anyone notices. Prices move and the pricing page doesn't. A hire leaves and the team page still shows them. A service gets quietly dropped and its page keeps ranking for searches that now lead to a dead end. None of these are dramatic failures — nobody gets fired over a stale team photo — which is exactly why they accumulate. There is no ticket for "the About page is eighteen months out of date." It just sits there, technically live, actually false.

A company with three customers does not have three distinct service lines with their own buyers, their own objections, and their own reasons to rank separately in search. It has one thing it does, sold to whoever will buy it, and a website built as though the market had already been segmented is a forecast dressed up as an asset. Forecasts are supposed to be tested and revised. A published page resists revision in a way a spreadsheet cell does not — someone has to notice it's wrong, remember who has CMS access, and actually go back in, and at a three-person company that someone is usually the founder, who has other things to do that week.

Thin pages don't just sit there, they actively hurt the pages next to them

The instinct that more pages means more chances to rank is not unreasonable, and it used to be closer to true. But a nine-page site made of three genuinely useful pages and six that exist because the sitemap called for them does not simply fail to benefit from the six — it tends to rank worse on the three than a four-page site made of nothing but the four would have. Search engines read a site's pages as a set, and pages that are thin, generic, or obviously templated the same way as three competitors' equivalent pages read as evidence about the whole domain, not as isolated data points. A "Web Design Services" page with four sentences of boilerplate sitting next to your one genuinely detailed case study doesn't coexist peacefully with it. It's context the case study now has to be read against.

This is the part that gets missed in the ambition argument. The twelve-page site isn't neutral-to-slightly-positive. Once several of those pages are thin because nobody had anything specific to write yet, the whole site can rank worse for the two or three searches that actually matter than a smaller, complete site would have. Fewer, finished pages beat more, half-finished ones — not as a stylistic preference, but as an observable search outcome.

The one-page company site is not a compromise, it's the right size for a specific claim

Set the ambition question aside and ask what a company with one offer and a handful of early customers actually needs a visitor to leave believing. Roughly: this is a real company, this is what it does, this is who's behind it, here's how to get in touch. That claim fits on one scroll. It does not need a Services section with sub-pages for services that don't exist yet, and it does not need a blog that will get three posts before someone notices nobody's writing the fourth.

This is close to the argument we made about what a company website is actually for: a site does one of a small number of real jobs, and for a young company selling one thing to people who are mostly finding it through a referral or a conversation rather than a search funnel, the job is almost always the smallest of those — state the offer, look real, provide a way to reach you. A twelve-page site built to also win organic search traffic the company isn't yet positioned to win is doing a job nobody asked for, at the direct expense of doing the actual job well. Whether that first page should carry a founder's name or the company's is its own decision, one we've gone through separately in founder page or company page — but either way, the page count question resolves the same way early on: not zero, not twelve, one.

reach is one honest route to the small version

If the goal is one page that states the offer and gets out of the way, reach is worth naming as one way to get there fast, because the mechanism is different from a blank-canvas builder in a way that matters here. You give it a CV — for a young company this is usually the founder's — and a short form, and it composes a complete page rather than handing you an empty template to fill by hand. The layout is assembled from a large set of vetted section and hero variants, and every line of copy is written fresh from the specifics you gave it, not dropped in as boilerplate. The output is generated in about twenty seconds, and you can be live on a free yourname.joinreach.app subdomain in under two minutes.

That speed is the actual argument, and it's worth being specific about why it matters at this stage: the twelve-page site usually exists not because anyone wanted twelve pages but because the alternative — sitting down with a blank template and deciding what to write — is exactly the kind of task that gets deferred until an agency proposal fills the vacuum with a sitemap. Removing the blank canvas removes the reason the scope crept in the first place.

The limitations are real and worth stating plainly rather than glossing over. reach makes exactly one page — one index.html, no sub-pages, no site navigation. There's no CMS, so there's nothing to grow into later without starting over. There's no shop and no contact form; the contact section is a mail link and profile links, not something that posts anywhere. There's no built-in analytics, so you won't get a number out of it without adding your own. And the moment the company needs a second page, this isn't a tool you extend — it's a tool you migrate away from, because a second page isn't a feature reach adds, it's a different kind of site entirely.

The trigger to expand is narrower than it feels

The temptation to build the bigger site early usually comes from a feeling rather than from evidence — a sense that the company has "grown up" enough to deserve more pages, or that a competitor's twelve pages must mean something. Neither is a trigger. The actual trigger is specific: a second service that has shown up more than once, with its own buyer and its own distinct search demand, not a hypothetical future offering listed to look more complete.

A landscaping company that started doing lawn maintenance and has now had four separate customers ask, unprompted, about tree removal has a second service with its own buyer. A consultancy that occasionally does a favor for an existing client in an adjacent area does not — that's one service with an occasional exception, and building a page for the exception before it repeats is exactly the forecasting error this whole argument is against. The test is repetition, not capability. Could isn't the trigger. Has, twice, is.

When that trigger arrives, this is a migration rather than an extension, and it's worth knowing in advance what actually survives it. Keep the copy that was written specifically about the company — the sentences describing what makes the approach different are rarely wasted, whatever platform they end up on. Keep whatever proof accumulated in the meantime: a testimonial, a completed project, a number. Throw away the structure. A one-page site was never a smaller version of a multi-page site with the extra pages missing; it was a different object built for a different claim, and the multi-page site that replaces it should be planned the way the piece on how many pages a small company website actually needs lays out — starting from what the company now does, not from what the old one-pager happened to already say.