Founder readiness examples: lessons and useful context

There are no companies in this article and no founders with names. Made-up case studies are worse than useless for this subject, because the details get invented to fit the lesson and then the lesson looks proven.

What follows are situations. They are recognizable rather than illustrative: if you are in one, you will know within a sentence. Each has a reading and a next move.

What to take away

• Each situation below has an obvious reading and a correct one, and they are usually different.
• The missing item is the same in all ten: a result that would have counted as a no.
• Every next move here costs a conversation or an afternoon, not a build.

Everyone says it is a great idea and nobody has asked when they can have it

Enthusiasm is running high and there are no requests. Nobody has asked about a date, a price, or whether they could see it.

The reading. Interest and demand are different states, and the gap between them is exactly this: demand generates questions with consequences attached. Praise without a follow-up question is a social response, not a commercial one.

The move. Make it slightly expensive to be enthusiastic. Ask for half an hour, an introduction, or the file they described. Watch who does it.

You have a waiting list and have never asked anyone for money

The list has grown steadily. It feels like the strongest evidence you have.

The reading. A list measures how many people found the promise worth an email address. That is a real signal about your message and almost none about willingness to pay. It also decays; a name added six months ago is not a person waiting.

The move. Take a slice of the list and ask them to pay or to place a refundable deposit. Do it now rather than at launch, because the answer changes what you launch. What a deposit can and cannot establish is set out in offer testing.

You have already built it and you are now looking for validation

The work is done. What you want is confirmation.

The reading. Validation cannot un-spend the build. But it can still do two useful things: tell you who this is for, which is often not who you assumed, and stop you spending the next six months the same way.

The move. Stop asking whether the thing is good. Ask which slice of people get a result from it, and be prepared for that slice to be much narrower than intended. Narrowing is the usable outcome available to you here, and customer interviews is the instrument for it.

One customer loves it and you cannot find a second

The first one uses it constantly and says warm things. Everyone else is polite and does nothing.

The reading. Two possibilities and they need opposite responses. Either that customer is unusual, in which case you have a consultancy client rather than a market. Or they are the first of a type you have not learned to describe yet.

The move. Write down everything specific about their situation: what triggered them, what they were doing before, what makes their circumstances unlike their peers'. Then go looking for that exact profile deliberately. If you can find three more and they behave the same, it is a segment. If you cannot describe the profile at all, it was an individual.

You can describe the product in one sentence but not the buyer

The pitch is sharp. The answer to "who is this for" runs to a paragraph and includes the word "anyone".

The reading. You cannot test an offer without a who, and you cannot buy traffic, write copy, or pick a channel without one either. The vagueness is not a communication problem, it is an unfinished decision.

The move. Describe the customer in terms that leave a trace in the world: a job title people write on their profiles, a piece of software they must already run, a license they hold, an event they attend. If none applies, you have not found the group yet. Market validation covers how to get there, and the SBA's outline of market research and competitive analysis is a plain statement of the same requirement: describe the group before you size it.

The people who feel the problem have no money, and the people with money do not feel it

Users are enthusiastic and cannot buy. Budget holders can buy and are indifferent.

The reading. This is a structural problem, not a persuasion problem. It will not be fixed by a better demonstration to the enthusiastic group.

The move. Find out what the budget holder is measured on, and whether your outcome touches it. If it does, the offer must be rewritten in their terms, which usually means a different promise and a different price. If it genuinely does not, the honest options are a different buyer or a different product.

The test worked and you cannot repeat the channel

Something converted well. It came from a personal introduction, a post that did unusually well, or a community where you happen to have standing.

The reading. You have evidence about the offer and no evidence about distribution. These are separate results and it is easy to bank both when you only earned one.

The move. Try to reproduce the same conversion through a channel you could buy or build. Until that works, treat acquisition as the open risk and plan around it, rather than assuming the good week generalises. Choosing a route deliberately rather than accepting whichever one produced the good week is the whole of the SBA's marketing and sales guidance, and it is the part of a plan founders skip.

You keep finding one more thing to build before talking to anyone

There is always a reason it is not ready to show. Each reason is individually sound.

The reading. Building is comfortable and controllable; asking is neither. The pattern usually shows up as a sequence of small technical goals, none of which anyone outside has requested.

The move. Notice whether any customer asked for the current task. If none did, book the conversation this week with the thing as it is. The version you are ashamed of will still produce a usable answer.

Two of you disagree about who the customer is

Both descriptions get used in different conversations. Nobody has called it a disagreement, because each version sounds reasonable.

The reading. This is the most expensive unresolved question a small team can carry, because it splits every downstream decision quietly. Feature arguments that never resolve are frequently this argument in disguise.

The move. Write both descriptions down side by side and agree which one the next test is for. Not which is right. Which one is being tested first. That is a smaller decision and it is answerable.

You plan to quit your job once it is validated, and validated is undefined

The plan has a milestone with no definition. Depending on the month, it means revenue, or a number of customers, or a feeling.

The reading. An undefined threshold moves. It will either recede forever, which is the common case, or collapse suddenly on a good week when you least want to be making decisions on impulse.

The move. Write the condition as a sentence someone else could check: what has to be true, by when, and how it is measured. Then decide what happens if the date arrives and it is not met, and tell someone what you decided. The pillar on founder readiness treats that arrangement as the whole of what readiness means.

What these have in common

In every one of them, the missing item is the same: a result that would count as a no. The enthusiastic room, the growing list, the unrepeatable channel, the undefined milestone. Each situation can continue indefinitely without ever producing a discouraging fact.

If you recognize yourself in more than one, that is the pattern to fix first, and it costs nothing to start. Name what would make you stop, then go and find out whether it is true.

Common questions

Why are there no named companies here?

Because an invented case study has its details chosen to fit the lesson, and the lesson then looks proven. These are situations rather than stories, and you either recognize one or you do not.

Can I be in several of these at once?

Usually, and the enthusiastic room plus the undefined milestone is the most common pair. Deal with the milestone first: once a result can count as a no, the other situations become readable.

What if none of them describes me?

Then write your own in the same shape: what is happening, the two readings available, and the cheapest observation that separates them. The shape is the useful part, not the list.

Is a waiting list worth anything at all?

It is worth something about your message and nothing about willingness to pay, and it decays. Treat it as an audience to ask rather than as evidence you already have.

How do I tell an unusual first customer from the first of a type?

Write down everything specific about their situation, then go and look for that exact profile on purpose. If you can find three more who behave the same way, it is a segment. If you cannot describe the profile at all, it was a person.