You already wrote the hard part. It’s sitting in a Google Doc called “Business Plan v3 FINAL” that you haven’t opened since your last funding conversation — and it contains almost everything your homepage needs. The problem isn’t that you don’t know what to say. It’s that nobody told you how to plan a website from the material you already have.
So most founders skip that step. They hand a designer a logo, a color they “kind of like,” and a vague “make it clean,” then wonder why the result looks nice and converts nothing. The gap isn’t design talent. It’s translation.
Here’s how to close it.
The plan already answers the questions the homepage asks
A business plan and a homepage are trying to say the same three things — they just wear different clothes.
Your plan has a market section. Your homepage calls that “who this is for.” Your plan has a value proposition. Your homepage calls that “the headline.” Your plan has a competitive analysis. Your homepage calls that “why us.”
Same substance, different job. The plan exists to convince you (and maybe an investor) that the business should exist. The homepage exists to convince a stranger, in about five seconds, that they should keep reading. Learning how to plan a website is mostly learning to compress the first document into the second.
Pull these four things out of your plan before you touch a single pixel:
- Who you’re for — the specific person, not “everyone who needs X”
- The problem they feel — in their words, not your industry’s words
- Your one-sentence offer — what you do and who it’s for
- Your proof — why they should believe you can deliver
If you can’t find these in your plan, that’s not a website problem. That’s a clarity problem, and it’s cheaper to solve now than after you’ve paid someone to build around a fog.
Cut the plan down to its load-bearing sentences
Business plans are written to be thorough. Homepages are written to be fast. So the first real task isn’t writing — it’s deleting.
Go through your plan and find the sentence that would survive if you could keep only one. Usually it’s buried on page four, phrased for a banker. Something like: “Our platform reduces onboarding time for mid-market HR teams from three weeks to two days.”
That’s your headline. It’s not clever, and it doesn’t need to be. It names a specific person and a specific before-and-after. Clever is what people reach for when they don’t have a clear claim — a clear claim doesn’t need decoration.
The best homepage headline is almost always a sentence you already wrote for someone else, then said out loud until it stopped sounding like a brochure.
Map the homepage as a conversation, not a layout
Stop thinking in sections — hero, features, testimonials, footer. Think in questions, in the order a skeptical visitor asks them:
- What is this? — your headline earns the next three seconds
- Is it for someone like me? — you name their situation back to them
- Can I trust you? — proof: logos, numbers, a real result
- What happens if I say yes? — you remove the fear of the next step
- What do I do now? — one button, one action, no maze
Answer those five in order and you have a homepage. Skip one and visitors quietly leave at exactly the point you skipped. Most sites die at question three — they announce what they do and never once prove it.
Notice that none of this is about the design system yet. The sequence is the strategy. The visuals are how you make the sequence effortless to move through.
Write it before you design it
Here’s the move almost nobody makes: write the whole homepage as plain text, top to bottom, before anyone opens a design tool. No columns, no images, no fonts. Just the words in order.
If the plain-text version is convincing, the designed version will be too. If the plain-text version is vague, no amount of beautiful typography will save it — you’ll just have handsome vagueness. This is also the single biggest thing that separates a site that converts from a site that merely looks expensive.
This is where good judgment earns its keep, and it’s a big part of what you’re actually paying for when you hire well. A designer who only styles your words is a decorator. One who challenges the words — “this headline is a feature, where’s the outcome?” — is a partner. If you’re weighing who to bring in, the difference between those two people matters more than their portfolio’s polish, which is worth remembering when you’re choosing a web designer.
What to leave out (this is most of the work)
Your business plan has a five-year revenue projection. Your homepage does not care. It has an org chart, a risk section, a detailed feature matrix. None of it belongs on the page a stranger sees first.
Restraint is the skill. A homepage that tries to say everything says nothing. Cut anything that doesn’t help a first-time visitor answer one of the five questions above:
- The full feature list → pick the three that matter, link the rest
- The company backstory → save it for the About page, if at all
- Every use case → lead with the one that’s easiest to say yes to
- Industry jargon → say it the way your customer would text it to a friend
You are not documenting the business. You are opening a door and pointing at one thing. Everything you remove makes that point sharper.
The reframe
Here’s the part that stings a little: the reason most homepages don’t convert has nothing to do with the website. It’s that the thinking was never finished. The homepage just exposes it, in public, at full brightness.
Which is good news. It means the hardest, most valuable work is the part you can do in a text document before a designer ever quotes you — and doing it first is exactly how you turn a “$500 to $50,000” question into a real number. The plan you already wrote is the raw material. Turning it into a page that earns attention is a matter of compression, sequence, and the nerve to cut.
If you’d rather not do that translation alone, that’s the whole first phase of how we work — we sit with the plan you already have and find the homepage hiding inside it before anyone talks about pixels. You did the hard part. The rest is knowing what to keep.
