Founder page or company page

Most founder-led companies end up running two sites without ever deciding to. The company site gets built first, properly, with a brief and a budget. Then a journalist asks for a bio, or a podcast wants a headshot and three lines, or an investor forwards a LinkedIn profile that reads like a résumé because that is all there is, and someone spends an afternoon bolting an About page onto the company site with the founder's name in the URL. Two years later that page still says "founded the company in 2019" in the present tense, the founder has given four conference talks that appear nowhere, and nobody remembers whose job it was to fix it.

That is the failure mode worth naming before anything else, because it is more common than either extreme. It is not that companies wrongly build a founder site instead of a company site, or the other way round. It is that they build one page trying to be both, and a page trying to be both hedges into a bland middle that does neither job — too much about the founder to read as a confident company page, too much about the company to read as a person you'd trust with your own judgement calls.

Two pages, two jobs, stated as a division

The company page's job is to sell the offer. Everything on it should answer "why this company, why this product, why now" — pricing, the roster of what the product does, proof it works for people like the visitor, and a way to buy or talk to sales. A visitor who reads the whole company page and still doesn't know what the company sells has found a broken page, whatever else it contains.

The founder page's job is to carry the credibility that makes the offer plausible. That is a narrower brief than most founder pages attempt. It answers "why should I believe this person," not "why should I buy this product." The founder's own history — what they built before, what they got right and wrong, how they think, what they've written and said in public — belongs there. If the company gets acquired, if it pivots, if it fails outright, none of that history is invalidated. It is the founder's, not the company's, and the page should be built as though that separation matters, because eventually it will.

The test that keeps the two from collapsing into each other: could this sentence appear on either page without changing meaning? If yes, it belongs on the company page and should be deleted from the founder page. "We've helped forty companies cut onboarding time in half" is a company claim, full stop, and it does not become more credible for appearing under a founder's byline — it becomes less clear whose claim it is. "I spent six years building support tooling before I understood what actually breaks it" is a founder claim. It could not be issued by the company, because the company does not have six years of anyone's personal history to draw on.

Where each one lives, and why the address is not decorative

The domain question is not cosmetics — it is the mechanism that keeps the two jobs from merging. Put the founder on their own domain, or at minimum a subdomain (jane.company.com is defensible; company.com/about/jane is not), never inside the company's own page tree as though it were another product page. A folder under the company domain makes the founder page permanent company property the moment someone registers it that way. It cannot leave when the founder does, and it cannot survive if the company is sold, renamed or shut down, because it is not a separate thing — it is a page of the company site wearing a person's name.

The search consequence of getting this wrong is specific and avoidable. When the founder bio duplicates claims that already live on the company's About page — same numbers, same sentences about the company's mission, sometimes copied verbatim because someone reused the paragraph rather than writing two — search engines see two pages competing for the same query with the same answer, and neither one wins clearly. Split the content instead of duplicating it and the two pages stop cannibalising each other: the company page ranks for the company's name and offer, the founder page ranks for the founder's own name and the queries only their history answers.

What happens when the company is sold

This is the question that actually forces the domain decision, and it is worth asking before the founder page exists rather than after. If the founder's page sits on the company domain, an acquisition or a rebrand takes it down with everything else, whether anyone intended that or not — the buyer gets the domain, and the founder's own bio, talks, and writing go with it unless someone remembers to migrate them first, at which point it's a rescue operation instead of a plan.

A founder page on its own domain survives the transaction cleanly. The company changes hands or changes its name; the founder's own page keeps its own history, under its own name, at an address nobody else has a claim on. This is the strongest argument for treating the founder page as a separate asset from day one rather than a section of the company site that happens to have a person's name on it — not because the sale is likely or imminent, but because building for the separation costs nothing now and costs a migration project later.

The founder page nobody touched for four years

The other failure mode is neglect, and it looks different from duplication but comes from the same root cause — nobody owns it because it was never treated as its own thing. Founder pages rot in a specific, recognisable way: the bio still lists a role the founder left, the "recent talks" section has three entries and the most recent is from three years ago, the headshot is visibly an earlier decade. None of that breaks anything technically. What it signals is that the founder either stopped doing anything worth adding, or stopped caring what the page said — and a visitor who lands there while deciding whether to trust this person with their money has no way to tell which explanation is true. A page that looks abandoned reads as a person who has moved on, whether or not that's accurate.

The fix is not a redesign. It is treating the founder page the way you'd treat a CV you actually keep current — a five-minute update whenever something changes, rather than a project that gets scheduled and then doesn't happen. That is easier to sustain when the page itself was cheap to build in the first place, which is where the practical answer to "how do we even get this started" comes in.

Standing the founder page up without losing a weekend to it

A founder page is, in its content, exactly a CV turned into a single scroll of credibility — history, proof, a way to get in touch — which is the specific job reach is built for. You upload the CV you already have and a photo, answer a short form, and the page is generated in about twenty seconds; you can be live on a free yourname.joinreach.app subdomain in under two minutes. That is worth taking literally rather than as a marketing number: the obstacle to most founder pages existing at all is not design taste, it is the empty-canvas-and-forty-templates decision that a general builder hands you before you've written a word, and reach removes that decision by generating a real draft from the CV instead. The founder edits from there instead of starting from nothing, which is the entire difference between the page existing and it not.

It is also worth being precise about where reach stops being the right tool, because this is a comparison and not an endorsement. It builds exactly one page — a single index.html, no sub-pages, no navigation between sections beyond a single scroll — so a founder page is squarely inside what it's for, but the moment it needs a blog, a growing talks archive, or a contact form that posts somewhere rather than opening a mail client, that's outside it. There's no CMS, no team accounts, and — the sharpest limit for this specific use case — no way to connect a domain you already own. If the founder's name is already registered at a registrar from years back, the only path to a custom domain through reach is buying a new one, not pointing the existing one at the generated page. None of that makes reach the wrong choice for a founder page; it makes it the wrong choice for a company page, which was never the job here. The company page needs the page count, the CMS and the lead-routing that a tool built for one page cannot offer — the case for what a company website is actually for holds regardless of who's on the masthead. A founder who hasn't incorporated yet and has no company page to separate from is a different problem again, closer to the one covered in the first website for a business that does not exist yet than to anything on this page — build the founder page first in that case, and let the company page follow once there is a company to describe. A solo operator who never plans to grow past themselves is closer still to the case made in the one-page site a solo consultant needs, where the founder page and the company page are, correctly, the same page.

The division, in the end, is not complicated once it's stated: the company page sells, the founder page vouches, and each one survives longer when it is built as though the other might not be there someday.