Why I write the landing page before the product
One page of honest writing is the cheapest prototype. If I can't describe the product convincingly, I'm not ready to build it.
By Nzubechukwu Cyprian · Pharmacy student at UNN, full-stack developer
Before I write code for a new product, I write its landing page. Not the final version — a draft, in plain language, aimed at a specific person. It's the cheapest prototype I know, and it has killed more bad ideas than any technical spike ever could.
What the page forces
A named audience. "For everyone" means for no one. The draft begins with a person: what they do, what hurts, what they tried.
A stated promise. What changes for the user after they use this? If the sentence is vague, the product is vague. The page is where vagueness becomes visible — on paper, where it's free.
An honest price. Writing "₦X per month" next to the promise exposes value arithmetic instantly. If my own draft feels overpriced to me, imagine the stranger.
The two outcomes
If the page convinces me, I have copy ready and a spec sharper than any document. If it doesn't convince me — and several drafts haven't — I just saved weeks of building the wrong thing well.
Words before work. It feels backwards until the first time a landing page draft talks you out of a bad build. Then it feels like insurance.
Keep reading
- Product building
Shipping is a skill, and I practised it badly for years
Finishing things is not a personality trait — it's a practice with techniques. The ones that turned my graveyard of half-projects into shipped products.
- Product building
Nobody told me product decisions are reversible or not
The single question that unblocked my decision paralysis: is this door one-way or two-way? Everything else is noise.
- Product building
The pricing page taught me more about users than the analytics did
Data told me what people clicked. The pricing page told me what they believed. Convincing beats tracking.