When a waitlist is the right first build

There is a particular conversation that happens, often, on a Tuesday discovery call. A founder describes the product they want to build. The product is good. The user is clear. The core loop is obvious. We're about to scope a sprint. And then we ask the question: who, specifically, will use this on day one?

Sometimes the answer is fifty people, named, with phone numbers. Sometimes the answer is "I think there's a real audience." Both answers can be right. They're answers to different questions.

The founder with fifty named people should be booking a 7-day MVP sprint. The founder with a strong intuition and no list yet should usually do something else first — and that something is what our new $2,999 Landing Page & Waitlist tier is built around. Three days. One sharp page. One working waitlist. A real number on the spreadsheet by the end of next week.

What the landing page actually ships

The shape is small on purpose. In three days, the engagement delivers:

A designed marketing page on a custom domain the founder owns, written and built around the founder's actual positioning — not a template.
A waitlist signup with double opt-in (so the list is actually deliverable, not full of typos and bots).
A welcome email sent through Resend the moment someone signs up, on a sender the founder controls.
A privacy page and cookie banner, written for the jurisdictions you'll get traffic from, so the page is publishable from day one.
Analytics and conversion tracking, wired up so "how many landed, how many signed up" is a number you can read on a dashboard.
A repo handover and a short docs pack at the end. The page is the founder's; we don't operate anything for them after launch.

That's it. Not an MVP. Not a roadmap page. A single, well-built, conversion-aware surface and the email plumbing behind it. The point of the engagement is not the page — it's the spreadsheet of email addresses it produces.

When this is the right answer

The landing-page-first move makes sense in three specific situations.

You're not yet sure who wants it. If the audience is still a hypothesis, building the product won't validate the hypothesis. Building the page and running traffic to it will. A landing page with paid traffic, an honest message, and a working signup tells you more in two weeks than a finished MVP shipped to nobody tells you in six.

You need a number before you can start. Some founders need a signal to commit — to themselves, to a co-founder, to an investor — that the idea is real before they spend on a build. A real waitlist number is that signal. It's also the cheapest way to get it.

The MVP needs an audience to test against. If your product is a marketplace, a community tool, or anything else that's empty without people in it, you need people lined up before launch day. A waitlist that's been growing for a month before the MVP ships is the difference between a soft launch that learns something and a launch that's two people in a room.

When to skip it and go straight to MVP

The landing page is not always the right move. Skip it if:

You already have a list. Customers, paid users, a community, a Substack with a thousand readers. You don't need to validate demand again on a new surface.
The product is a transaction. A marketplace where the value is in the transaction, a tool that earns its keep by being usable — these need the build, not the promise of a build.
You have a window. Investor demo in three weeks. Conference talk in a month. A launch date that doesn't move. A landing page is the wrong sprint to start when the build has to be done by then anyway.

For everyone else — and this is most early-stage founders — the landing-page-first sequence saves a build that turns out not to be wanted, or buys real signal before a build that does.

The three days, broken down

The engagement is short enough that the day-by-day matters.

Day one — message and shape. Two hours with the founder on positioning: the one sentence, the three reasons, the proof, the call to action. Then we draft the page — sections, copy, visual hierarchy — and put it in front of the founder before close of day.

Day two — build and wire-up. The page goes live on a staging URL with the waitlist form, the welcome email, analytics, the privacy page, the cookie banner. By end of day two the founder is clicking through the real thing on a real subdomain.

Day three — polish, launch, handover. A mobile pass, a keyboard pass, a copy pass with the founder, then we cut DNS over to the custom domain, hand over the repo, write the short ops doc, and the page is live.

The thing we don't try to do in the three days: nothing else. No blog. No about page. No pricing matrix. The landing page is one page. The product is the waitlist signup. Scope drift here costs the same in days as it does on the MVP sprint; the strict scope is what makes the timeline real.

What it costs you and what it doesn't

The cost is the $2,999 and three days of founder attention. It doesn't get credited toward a future MVP sprint — discovery does, this doesn't — because the deliverable is a real live page in your name, not a planning artefact for a later build.

The thing it costs you that's worth naming: it delays your "I'm building" feeling by a couple of weeks. A landing page is not as satisfying as a backend. That's fair. The trade is, you get to start the build with a list of people waiting to use it, and the build itself becomes a much shorter conversation about what the first version needs to prove.

What we'd tell a friend

If you have the audience and the conviction, book the MVP sprint. If you have the conviction and no audience yet, do the landing page first. If you have neither yet, do the discovery sprint and we'll figure out which of the two is the right next move.

The three engagements stack: discovery shapes the spec, the landing page builds the list, the MVP sprint ships the product. Most founders don't need all three. The right one to start with is the one that answers the question you're actually still asking.