Own Your Name

Why founders need a personal page, not just a company site

Investors, journalists and candidates search the founder before the company. What the company site cannot say on your behalf.

A young entrepreneur gives a presentation on startup strategies indoors with a flip chart.
Photo: RDNE Stock project / Pexels

Part of Personal branding without the cringe

Most founders already have a website. It has their photo on the About page, a paragraph under a job title, maybe a link to their LinkedIn. It feels like the box is checked, and for a while it is a reasonable thing to believe, because nobody has yet gone looking for the founder specifically and come away disappointed. The problem shows up later, and it shows up as a pattern rather than a single bad moment: an investor's associate reads the company site closely and then gives the founder a glance before a first call, a journalist writing a company profile searches the founder's name and finds a conference bio from a previous job, a strong candidate deciding between two offers reads the founder's page last, right before deciding. In each case the company site was fine. It just wasn't answering the question that was actually being asked.

The company site is written in the wrong grammar

A company site, even a good one, is structurally written in the plural. Its job is to explain what the product does, who it's for, and why the company is credible as an organization — funding, customers, team size, roadmap. Every sentence on it is written to serve the business, which means every sentence is filtered through what's good for the business to say. That's the right instinct for a company page and the wrong one for the question an investor, a journalist or a senior candidate is actually holding, which is singular: who is this person, and why are they the one solving this problem.

A company site cannot answer that question well because answering it requires a first-person voice the company page structurally doesn't have. The founder bio on an About page is usually two sentences wedged between the CTO's bio and the head of sales's, matched in length and tone so nobody looks favored. It can't spend three paragraphs on the failed company two jobs ago that taught the founder the exact thing this one is built to fix, because that paragraph would read strangely sitting next to four other team bios written in the same clipped, symmetrical register. The format itself suppresses the specific answer, not the founder's willingness to give it.

The three readers who go looking for the person first

This isn't hypothetical curiosity. Three kinds of readers specifically search the founder before, or instead of, the company, and each is looking for something the company site cannot supply.

An investor evaluating an early-stage company is, in large part, evaluating whether this founder is the right person to be betting on this particular problem, because at the earliest stages the product is unfinished and the market is unproven, and the founder's judgment is most of what's actually being priced. A pitch deck states the problem. It does not explain why this founder, of all the people who could try to solve it, has spent years accumulating the specific frustration or expertise that makes them credible on it. That explanation, if it exists anywhere, has to live on a page that speaks in the first person.

A journalist writing about the company is writing about a person whether the piece is framed that way or not — readers remember founders, not cap tables. A journalist who can't find a coherent account of who this person is and why they built this thing will either invent a simplified version themselves or lean entirely on the press release, and neither outcome serves the founder as well as a page that already states it correctly.

A senior candidate deciding whether to join a ten-person company is making a bet on the founder specifically, because at that size the founder's judgment is most of the working environment. They will search the founder's name before they accept, and what they find either closes the gap between "interesting company" and "I trust this person to run it" or widens it.

What prior work is actually for

The useful content on a founder's page is rarely the origin story in the abstract sense — "I always wanted to build something" is not information. What actually does work is specific: the companies or roles that came before this one, stated plainly enough that a reader can see the throughline, and an honest account of why this particular problem, not a generic passion statement about it. A founder who spent six years inside logistics software before starting a logistics company has a credible answer to "why this" that a generic founder page glosses over in a sentence. That specificity is exactly the thing a company About page has no room for, because the company page is arguing for the product and the founder page is arguing for the person, and those are different arguments even when they support the same conclusion.

This is close to what we mean when we say a reputation, not a performed brand, is what actually holds up over time — the difference is covered at more length in personal brand versus reputation. A founder's page is not a marketing asset dressed up as a biography. It works because it's true and specific, not because it's persuasive. Consultants and freelancers face a narrower version of the same problem — one person, one page, no company site to hide behind at all — and the build for that case is covered separately in the personal website consultants actually need; a founder's page differs mainly in having a company site sitting next to it that has to stay out of the way.

The page that survives the company

There's a second, colder reason to build this separately, and it's one founders tend to discover only after they need it. Companies get acquired, wind down, pivot into something that shares a name but not a mission, or simply go quiet. When any of that happens, the company site changes or disappears with it — an acquirer redirects the domain, or a founder lets the hosting lapse on a business that no longer exists. A founder's own page, on a domain the founder owns and controls independently of the company, survives every one of those events, because it was never the company's asset to begin with. It is the one piece of the founder's professional record that isn't hostage to how the business turns out, and for a founder whose next role — the next company, the board seat, the operating job — depends on a legible account of what they actually did, that page matters more after an exit or a shutdown than it did while the company was thriving, precisely because it's the thing still standing.

Getting to a draft, honestly

The reason most founders never build this second page isn't disagreement with the argument above. It's that a founder building a company has no time left over for a second site, and the version of "personal site" they picture is a second product-shaped project — pick a template, write copy from nothing, decide on a design system — competing for hours they don't have. That objection is fair, and it's the actual reason the good idea sits undone for years.

The part of that objection that's no longer entirely true is the time cost. reach turns a CV into exactly this kind of page: upload a résumé and a photo, answer a short form, pick a look, and the page is generated in about twenty seconds — you can be live at a free yourname.joinreach.app subdomain in under two minutes. That speed matters here specifically because a founder's actual obstacle was never taste, it was the blank canvas and the hours it takes to fill one; removing that step is what makes a page this small worth actually finishing rather than staying a task on a list for another year.

It also stops exactly where it should. This is one page, not a second company site: no shop, no CMS, no contact form, no set of sub-pages for a services tree or a blog. The contact section is a mail link and profile links, nothing that posts a form submission anywhere. That narrowness is the right shape for what a founder's own page is supposed to do — say who this person is, what they've done, and why this problem — and the wrong shape for anything the company itself needs to run, which is a separate, larger build with its own tools and its own team. Keeping the two projects apart is not a limitation to work around; it's what keeps the founder's page honest about what it's for.

None of this replaces the general case for having one page rather than an ongoing content practice, which we've made in full in personal branding without the cringe. What's specific to founders is the timing: this is one of the few professional situations where the wrong sentence, absent for lack of an afternoon spent, gets read by exactly the three people whose read of it matters most.

Questions people ask

Should a founder's personal site link to the company, or the other way round?
Both, but the founder's page should be the one that explains the person, and the company site should stay focused on the product. Cross-link them once each; do not try to merge the two jobs into one site.
What happens to a founder's personal page if the company shuts down?
Nothing, if the two were built separately. A personal domain and a company domain are different assets, so a wind-down or acquisition of the business does not touch the founder's own page or its history.
Is a personal website worth it for a founder who already has a LinkedIn profile?
LinkedIn is a directory entry with a fixed layout everyone shares. A founder's own page can lead with the one project or the one line of reasoning that actually explains the current company, in an order LinkedIn will not let you choose.
How is a founder's personal page different from the company's About or Team page?
The About page is written in the plural, for the product, and disappears if the company does. A personal page is written by and about one person, stays online independent of the business, and can say things — prior failures, the specific reason for this problem — that a company page has no voice to say.

Own Your Name — We write about the web people build for themselves rather than rent from a platform.

This article names specific products. How we handle recommendations.