Starting up

Ten design partners before a landing page

A landing page tests whether your copy is good. Ten design partners test whether the problem is real. Doing them in the wrong order is how a year gets spent optimising a headline for a product nobody needs.

5 min readStarting up

The standard sequence is landing page, waitlist, prototype, partners. It is standard because the first two steps are cheap and produce a number, and a number feels like validation.

The trouble is what the number measures. Signup rate on a landing page measures whether a stranger found a sentence compelling. That is a real signal about your copy and a very weak signal about whether the problem exists, whether anyone owns it, and whether anyone has budget for it.

What you’ll learn

  • What a waitlist number actually tells you
  • Why ten, and why the tenth matters most
  • How to find partners without an audience
  • The four questions that separate interest from a problem

What the number measures

A high signup rate tells you the promise resonates. That is worth something.

It does not tell you whether the person signing up has the problem badly enough to change what they do. It does not tell you whether they are the person who would buy, or a curious adjacent person, or a competitor. It does not tell you whether the problem has an owner inside the company, which is the single strongest predictor of whether anything will ever be purchased.

Worse, the number is directionally misleading in a specific way. Landing pages select for people who like new things. Early enthusiasm from people who like new things is the most reliable source of false positives in B2B.

Why ten

Ten is not magic. It is the smallest number where three properties show up at once.

The problem shape stabilises. By around the seventh or eighth conversation you stop hearing new categories of pain. When the categories stop arriving, you have the shape.

The variation becomes visible. With three partners, differences look like noise. With ten, you can tell which differences are segment-driven and which are company-specific, and that distinction determines what you build versus what you configure.

The tenth one is a test of your pitch. The first three come from your network and would have talked to you regardless. The tenth requires an actual reason for someone with no relationship to you to spend an hour. If you cannot reach ten, the constraint is not distribution, it is that the problem is not urgent enough to buy an hour of attention.

Important: Partners from your network are not evidence about the market. They are evidence about your network. You need at least half from outside it before the sample means anything.

Finding them without an audience

Most founders assume this requires distribution. It requires specificity.

Be narrow enough to be recognisable. "Operations teams" reaches nobody. "Seed-stage AI infrastructure companies with a services component they are trying to productise" reaches the few dozen people who read that and think it describes them exactly. Narrow is what makes a cold message land.

Lead with the observation, not the product. A message that says "we noticed that companies in your position tend to hit X at around Y, is that true for you" invites a correction. People correct strangers far more readily than they evaluate them.

Ask for the thing you actually want. An hour, on their real workflow, with a specific question you want answered. Vague requests for feedback get vague responses; a specific request is easier to say yes to and much easier to say no to, which saves everyone time.

Use the second-degree path deliberately. The ask that works is not "can you introduce me". It is "who do you know who has this specific problem" — a question with an answer, rather than a favour.

The four questions

Once you are in the room, four questions separate interest from a problem.

When did this last cost you something? A problem with no recent incident is a preference. Ask for the incident, the date, and what it cost.
Who owns it today? If nobody owns it, nobody will buy a solution for it. If the owner is three levels below the budget, you have a longer sale than you think.
What have you already tried? Failed attempts are the strongest possible signal. A team that built an internal tool for this has told you the problem is real and expensive.
What would you have to stop doing? Every adoption displaces something. If the answer is "nothing", the thing you are offering is additive, and additive things do not get prioritised.

The fourth question is the one most founders skip and the one that most often predicts whether a pilot converts.

What partners give you that a page cannot

Three things, in ascending order of value.

Real vocabulary, which becomes your copy later and is much better than the copy you would have written. Real edge cases, which shape the product more than any roadmap exercise. And a definition of success in their words, which becomes acceptance criteria you can actually verify work against.

That last one is why this order matters beyond validation. A product built against ten real definitions of success has checkable criteria from day one. A product built against a headline has taste.

When you do build the landing page — and you should — it will write itself, because ten people will have already told you what the promise is.

How we run this on our side is on design partners; the structured version of the underlying thinking is on starting a business, where the pre-signup survey is eight real strategy questions asked one at a time and nothing you answer is ever asked again. Once you have partners, pricing your first pilot is the next hard conversation.

Starting upUnderstand

Brainis Team

Notes on the company loop — company state, decisions, governed autonomy and verified work — from the people building Brainis and running on it.

Bring Brainis the company you want to build.

Start from an idea. Connect what exists. Either way, leave with the next move — and a system that delivers it.