You launched and nobody came: a triage plan for zero users

If you spent months building, launched, and have zero users, I would run commercial triage before touching the product again. Pick a narrow buyer and sell the current version by hand until every conversation teaches you what to cut. An empty dashboard is data. It says the market has made no promise.

What did the launch diagnose?

The launch gave you something useful: a clean negative signal from a cold room. Do not soothe it with a new landing page or another launch-day performance. Your actual question is whether a specific buyer will trade calendar time or budget for the thing already sitting on your server, without a press cycle doing the work for you. Good.

YC keeps telling founders to talk to users, and that advice matters most after a silent launch because silence contains no verbs on its own for your roadmap. Silence needs interrogation. A signup chart can show absence, yet it cannot tell you which buyer felt risk or which workaround already felt safer than your promise.

Freeze the product and reopen the market

Freeze the repo. For a short window, every hour that would have gone into onboarding polish goes into finding the buyer who already has the wound your product claims to close. Keep the current build stable and write down the known gaps. Treat every requested feature as a hypothesis with a company name attached.

Your triage document should fit on a plain sheet: the buyer label, the painful event, the current workaround, the sentence you use in email. If that sheet reads like a category pitch, the discipline in Positioning your B2B product: the working playbook for seed-stage founders belongs in the triage doc because it forces the claim into a buyer's mouth.

Shrink the buyer until the sentence hurts

Zero users usually means the audience was too soft to push back. Narrow hurts. Pick a buyer slice small enough that you can name the tool they open on Monday morning and the metric that gets them challenged by a manager when a project slips. Vague founders hide inside broad markets because broad markets never reject a sentence in public.

For an India-built SaaS company selling across time zones, the temptation is to call the ICP global and hope the website translates context. That wastes days. The sharper reference is Your first ICP: how to pick who to sell to before you have data midstream, because the work is choosing a wedge narrow enough for a founder to reach by name.

Replace launch traffic with conversations

Launch traffic is rented attention, while conversations are owned evidence. You need names. Build a small account sheet from LinkedIn, job posts, community threads, and recent funding pages, then write to people whose work contains the pain you claim to remove. A reply from the wrong person is still cleaner than many anonymous visits.

Paul Graham's essay on doing things that do not scale is useful here because the manual act is the test, before the system earns a budget line inside your company. Manual wins early. For channel sequence, I would put your situation beside Outbound or inbound first? Sequencing your first pipeline channel before spending more energy on passive traffic.

Use the next signals to choose the fork

After this triage, the result usually points to a clear fork. Do not average signals. If the right buyers reply and refuse the demo, your promise is weak, while repeated demo stalls point to a softer wound than your launch copy admitted. A founder should change the claim before changing the code when the conversation breaks before the screen share.

Write the triage rule on paper: no new feature work until a named buyer has repeated the pain back and accepted a step in the product. Hold that line. When evidence arrives, the next move is simple: sharpen the ICP before rewriting the sales sentence, and rebuild only the workflow that blocked use.