By role · 4 tools
The web stack for a founder
A founder picks for independence first. The site has to go up this week, be editable by you at midnight without asking anyone, and still be worth handing to the first marketer you hire. That rules out most of what a larger web team would choose, and rules in a few things they would not.
What is a Founder actually accountable for?
You are writing the copy, choosing the design and pressing publish, probably between two other jobs. Two questions decide every tool: can I change the headline myself on a Sunday, and can the person I hire next take this over without rebuilding it. When you do hand it over, hand over the publishing before the writing - the words are the part only you can do at this stage.
What should a Founder build the site on?
Four picks, each with the trade it makes. None of them is the right answer for every company, and a shortlist where everything is excellent is an advert.
You design and publish in the same place, and the result looks like a designer made it without one being involved.
Watch outIt is hosted only, so the site lives on their platform. Moving off later means rebuilding rather than exporting.
The visual editor goes further than the alternatives, so the site can grow into a real marketing site rather than being outgrown in a year. It is also the one a marketing hire is most likely to already know.
Watch outThere is more to learn than the marketing suggests. Expect a few weeks before building a page stops being a fight, and that is time not spent on the product.
AI does the first pass, which matters most when the blocker is a blank page rather than the tooling.
Watch outIt is new. Fewer people have hit the edges, so there is less written down when you get stuck.
Worth adding the moment the site has a blog or changelog, because the words stop living inside the design and can be reused elsewhere.
Watch outPremature for a five-page site. Adding it before you need it buys you a second system to maintain and nothing else.
What can a Founder hand to an assistant?
Each of these is one file you paste once, and then the job runs the same way every time.
Page briefTurn a rough page idea into a brief you can hand to a builder, or to Claude: who it is for, what sections it needs, and what each one has to say.QA passPut a page through the same checks every time: how it holds up at seven screen widths, what the markup says, whether anyone on a keyboard can get through it, and whether the words are right.Which tools should a Founder connect to their assistant?
Connecting these means asking a question about the real site instead of copying screenshots into a chat window.
Questions people in this role ask
Taken from what people actually ask about this, not written to fill the page.
Should I build the site myself or hire someone?
Build it yourself first. Not because it will be better, but because the message changes weekly at this stage, and paying somebody per revision makes you change it less often than you should. Hire when the message has settled and the site has become a job rather than an afternoon.
Framer or Webflow for a first company site?
Framer if you want it live this week and it is mostly a marketing site. Webflow if you expect a blog, several templates and other people editing. A common path is Framer first and a rebuild once the product and the message settle, and that rebuild is a fair price for being live early.
Will my first marketing hire be able to take this over?
More likely on Webflow, which has the larger pool of people who already know it. Framer specialists are harder to find. Ask that before you pick, because the point of a handover is that the new person works without you, and a platform nobody you hire has used puts you straight back in the loop.
What should I hand over first?
The publishing, not the writing. At this stage you are the only person who can say what the company is, and that part is worth keeping. Building pages, keeping the blog moving and running tests all hand over more easily, and they are the parts eating your week.
Do I need a CMS on day one?
No. Until there is a blog, a changelog or a second person editing, a CMS is a second system with nothing in it. The signal to add one is the same words being retyped somewhere else. Picking a builder that can add a CMS later is the part that matters on day one.
Not your job?
Every tool named here has a full entry in the stack, with the verdict and what it costs you.