My playbook from blank page to launch (no fluff)

Every new product I take on follows the same arc: strategy, narrative, experience, proof, launch, learning. The tools change. The sequence does not. Skipping steps feels entrepreneurial. It usually just feels expensive later-especially when the team discovers, three months in, that the homepage still cannot explain what the product does.

This article is the method I use with founders and product teams. It is not a ceremony. It is a way to keep launches from becoming theatre: lots of noise, little learning, and a Slack channel full of screenshots nobody acts on. If you want the shorter version of why I delay pixels, see why I start every project without opening Figma. If you want the “is this even worth building?” filter first, start with how I decide whether a product is worth building.

Why sequence beats hustle

Most early launches fail for a boring reason: the team ships an interface before they agree on the decision they want a stranger to make. Marketing then tries to compensate with volume. Design tries to compensate with polish. Neither fixes an unfinished story.

Good product strategy is not a slide deck. It is a shared answer to five questions: who is this for, what job are they hiring it for, what must they believe, what is the first valuable outcome, and how will we know we are wrong. Y Combinator’s Library returns to versions of these questions constantly because they are the ones that survive contact with customers.

The six-stage launch arc

I keep the arc deliberately plain. Fancy names make teams feel organised while they skip the hard bits.

1. Strategy: ICP, job, outcome, tradeoffs.
2. Narrative: homepage and onboarding story.
3. Experience: screens that reduce belief gaps.
4. Proof: evidence placed where objections live.
5. Launch: one primary CTA and a measurement plan.
6. Learning: weekly decisions based on real behaviour.

Stage 1: strategy before screens

I start with a product strategy framework before designing a single screen. The goal is not consensus theatre. The goal is tradeoffs people can defend.

The five boxes

• Customer: who is in, who is out (be rude about the “out”).
• Job-to-be-done: the progress they want, in their language.
• Current alternatives: including spreadsheets, agencies, and doing nothing.
• Outcome: the first measurable change your product creates.
• Belief gap: what they must believe before they buy or activate.

Real companies do this quietly. Stripe’s early clarity was not “payments infrastructure for developers” as a slogan alone-it was a ruthless ICP and a job (accept payments without becoming a payments company). Notion’s early expansion looked chaotic from the outside; underneath, the job stayed “one workspace where work lives.” Linear’s wedge was not “another issue tracker”-it was speed and taste for teams who already knew the category.

Fictional example: a founder builds “AI meeting notes for everyone.” Everyone is not an ICP. After the five boxes, it becomes “async meeting notes for remote product teams who already use Slack and hate rewatching recordings.” Suddenly the homepage writes itself-and half the roadmap can be deleted without ceremony.

Stage 2: narrative: the story customers can repeat

Narrative is not brand poetry. It is the sequence of sentences that move a stranger from confusion to a next step. Most startups fail here because the product does not have a marketing problem-it has a clarity problem.

I write the homepage before the feature list. The homepage is the pitch under pressure: cold traffic, short attention, no sales call to rescue you. Nielsen Norman Group’s work on how users read on the web is still useful here-people scan for relevance and next actions, not your origin story.

A simple narrative spine

1. Who this is for (so the wrong people leave quickly).
2. The job and the costly status quo.
3. How it works in three steps max.
4. Proof that this works for people like them.
5. One primary action.

Apple’s product pages are instructive even when you are not shipping hardware: one idea per section, proof next to claims, and almost no decorative clutter in the first viewport. Airbnb’s homepage-which I unpack in a dedicated teardown-owns the job immediately: find a place. Startups often bury the job under category language and a carousel of ambitions.

If a smart stranger cannot explain your product after one scroll, your narrative is not ready for paid traffic. It is barely ready for your mum.

Stage 3: experience: screens that reduce belief gaps

Once the story is clear, UI becomes translation. Each screen should either reduce a belief gap or advance a job. If it does neither, it is decoration-however elegant the spacing.

• Homepage answers belief gaps for cold traffic.
• Onboarding delivers the first outcome fast.
• Pricing resolves risk and value comparison.
• Feature pages map to jobs-not internal modules.

Time-to-value is the silent killer of “successful” launches. Teams celebrate signups while activation limps. I design the first session like a product: what must the user complete to feel progress? Figma’s early “open a file and draw” clarity, or Stripe’s “get an API key and charge a card,” are not accidents-they are first-session design.

For web performance and experience quality, I treat web.dev’s Core Web Vitals as hygiene, not a growth hack. Slow pages do not only hurt SEO; they tax trust before your copy gets a fair hearing. Accessibility is the same category of seriousness-WCAG guidance is not optional polish if you claim to build for real customers.

Stage 4: proof: evidence with a job

Proof is often treated as a footer collage of logos. That is decoration. Useful proof sits next to the claim it supports: security near data concerns, outcomes near pricing, process clarity near “how it works.”

Baymard Institute’s research on ecommerce UX keeps reminding retailers that trust and clarity reduce abandonment. The same logic applies to SaaS demos and waitlists: people abandon when risk feels higher than curiosity.

Types of proof that actually move decisions

• Outcome proof: before/after metrics in customer language.
• Process proof: screenshots or short walkthroughs that demystify.
• Social proof: named roles, companies, and specific results-not vague praise.
• Risk reducers: guarantees, security notes, clear pricing, cancel ease.

Early-stage teams often lack logos. That is fine. Specificity beats prestige. “Used by three remote product teams to cut meeting rewatch time by half” beats “Trusted by innovators worldwide,” which sounds like it was written by a tired brochure.

Stage 5: launch: one CTA and a measurement plan

Launch is where teams panic into optionality: book a demo, start free, watch video, join Discord, download whitepaper. Optionality feels generous. It is usually indecision in a trench coat.

Pick one primary action for the stage you are in. Early: waitlist with a clear promise. Mid: product-led activation. Sales-led: a demo that qualifies. Then instrument the path. Google’s Search Central documentation matters if organic discovery is part of the plan-but even more important is whether you can answer: where do people drop, and what did they understand when they did?

1. Define the primary conversion event.
2. Define the activation event that proves first value.
3. Instrument drop-offs between them.
4. Agree what “good” looks like in week one (ranges, not fantasies).
5. Assign an owner for the weekly review.

Stage 6: learning: weekly decisions, not monthly regrets

A launch without a learning rhythm becomes a museum of dashboards. I prefer a short weekly ritual: what did behaviour teach us, what will we change, what will we ignore. First Round Review is full of operating cadence examples; steal the discipline, not the buzzwords.

• What surprised us in qualitative feedback?
• Where did quantitative drop-off match (or contradict) that feedback?
• What is the smallest change that tests a new belief?
• What are we deliberately not touching this week?

This is also where product-market fit misunderstandings show up. Teams treat a spike as fit, or silence as “need more ads.” Learning loops force honesty: if activation is weak, more traffic is a louder version of the same problem-something I unpack in what founders actually need isn’t more marketing.

A worked example: “Harbor,” a fictional B2B tool

Harbor helps boutique hotels manage guest preferences across systems. The founder wants a big launch: Product Hunt, paid LinkedIn, a redesign, and a new AI feature.

We run the arc. Strategy narrows ICP to independent hotels with 20-80 rooms still using spreadsheets for VIP notes. Narrative becomes: “Stop losing guest preferences between your PMS and your front desk.” Experience focuses on importing a CSV and seeing a guest profile in under ten minutes. Proof uses three hotel interviews with specific outcomes. Launch CTA is a guided onboarding, not a webinar. Learning tracks import → first profile used at check-in.

The AI feature waits. The Product Hunt post waits. The team ships something a night manager can explain to a colleague-which is the real distribution channel in hospitality, whether founders like it or not.

Common ways teams break the arc

Roles and rituals that keep the arc alive

Methods fail when nobody owns them. Assign light roles even in a three-person team: one narrative owner, one instrumentation owner, one weekly-review facilitator (can be the same human with a checklist). Rituals beat heroics.

• Monday: check activation and drop-off; note anomalies.
• Midweek: ship one narrative or path improvement.
• Friday: 45-minute learning review with a written decision.
• Monthly: revisit ICP/job/outcome; update non-goals.

This is how systems compound instead of campaigns thrashing. The launch arc is not a one-off waterfall. It is a loop you re-enter with better questions each time-especially after you confuse product shipping with business building.

How this connects to systems, not campaigns

A good launch arc is the seed of an operating system: positioning, experience, proof, and learning that campaigns can amplify later. That is why I care more about systems than campaigns. Campaigns without this foundation are sparks. Sparks are lovely. They do not heat a house.

If you only have thirty days, the same arc still applies-compressed. I outline that compression in what I would change if you gave me your startup for 30 days.

What to do this week

1. Fill the five strategy boxes with your co-founder or product lead.
2. Rewrite the first viewport until a stranger can say who/job/outcome.
3. Map belief gaps to screens and notice the empty cells.
4. Choose one primary CTA and define activation.
5. Book a 45-minute weekly learning review for the next four Tuesdays.

Launches go wrong when teams confuse motion with progress. The arc above is deliberately unglamorous. That is the point. Strategy, narrative, experience, proof, launch, learning-then repeat with better questions. For complementary framing on commercial reality versus feature shipping, read the difference between building a product and building a business.