The Founder’s Real Edge? Knowing How Much to Bet

Big ideas are supposed to feel exciting. The decisions behind them are usually messier—and that is where the real work begins.

Imagine you run a boutique hospitality company. Your clients already text the concierge for trainers, massages, hard-to-get dinner reservations and the occasional 6:00 a.m. cold plunge. A wellness membership seems like an obvious next move: recurring revenue, deeper client relationships and a service that fits the brand.

On a pitch deck, it practically launches itself.

Then the operations lead asks who will answer those 6:00 a.m. texts. Finance wants to know how many members it takes to cover a new hire. Someone points out that the New York vendor list is excellent and the Miami list is mostly three people saved under “maybe.” The mood changes.

Good. Now you are finally discussing the business.

Founders are often praised for vision, conviction and speed. They need all three. What rarely gets celebrated is the less glamorous skill underneath them: deciding how much to commit before the evidence catches up. A hunch may be worth pursuing. It is not automatically worth a lease, a full-time team or six months of everyone’s attention.

The aim is not to eliminate uncertainty. That option is unavailable. The aim is to shape the decision so the company learns something useful without letting one attractive idea put the rest of the business in a headlock.

“Is this a good idea?” sounds sensible, but it is too large a question. People end up arguing about the future in general, which is a wonderful way to fill an hour and a poor way to decide anything.

Ask what you are deciding now.

Those are not the same choices. You might be deciding whether to interview 20 clients, take deposits from 15 founding members, run an eight-week pilot or spend $180,000 on a polished launch. Each choice buys a different amount of information, carries a different risk and gives you a different way out.

Once the decision is small enough to see clearly, write down what would have to be true for it to work. For the membership, maybe 70 active members cover the fixed operating cost. Maybe clients will pay for year-round access, not just use the service when they are traveling. Maybe the current team can handle a pilot but not a second city. Maybe the margin survives the kind of requests real clients make, as opposed to the tidy requests imagined in a conference room.

Then separate the evidence from the optimism:

• What you know: measured costs, signed agreements, deposits and behavior you have actually observed.

• What you are assuming: plausible claims that have not met a customer’s credit card yet.

• What could change the answer: the few unknowns that would make you expand, redesign or walk away.

This is basic work, but basic does not mean easy. The U.S. Small Business Administration’s guidance on market research and competitive analysis points founders toward the questions that matter: actual demand, market size, pricing and the alternatives customers already have. A compliment from a loyal client is encouraging. A deposit is evidence. It is important not to confuse the two just because the compliment was delivered over a very nice lunch.

A landing-page test and a ten-year lease should not go through the same decision process. That sounds obvious. Inside a growing company, it often is not.

Jeff Bezos gave this distinction a useful name in Amazon’s 2015 shareholder letter: one-way and two-way doors. A one-way-door decision is difficult or expensive to reverse. A two-way-door decision lets you step back through without doing lasting damage. The first kind deserves patience. The second usually benefits from speed.

The trouble is that “reversible” can be misleading. A service may be easy to shut down on paper and still disappoint clients who planned around it. A new feature can be removed from the product and live forever in screenshots. There is always a cost to the return trip.

So price it. Before you move, decide how much money can be spent, how much staff time can be borrowed from the core business and what promise is being made to customers. Name the person who can stop the test. Put an end date on the calendar. If nobody has the authority to call time, the pilot is not really a pilot; it is a new department with shy branding.

This is close to what University of Virginia Darden professor Saras Sarasvathy calls affordable loss. In her research on expert entrepreneurs, she found that they often start with what they can afford to put at risk, rather than trying to predict the biggest possible return. It is a practical response to an annoying truth: early forecasts tend to look precise long before they deserve to.

Small tests only help when they are honest.

A survey that asks, “Would you be interested in a premium wellness membership?” will collect plenty of polite enthusiasm. It may tell you something about the wording. It will not tell you who will pay $1,200 a month, use the service often enough to stay and recommend it to a friend without being nudged.

For the hospitality company, an honest test might be 25 invited clients, a real but refundable deposit and an eight-week program in one city. Cap the cash exposure at $18,000. Use the current team where possible, but track every hour they spend arranging vendors, moving appointments and smoothing over the gaps between the brochure and real life.

Do not polish the pilot past the point where it can still surprise you. If you build the full app, hire the director and announce a national rollout first, you have not reduced uncertainty. You have just made changing your mind more embarrassing.

Watch what people do. How many pay? How often do they book? Which services matter after the novelty wears off? What breaks on a busy Thursday? If the membership itself falls flat but clients keep asking for the corporate retreat package hidden inside it, pay attention. The market is not obligated to like the part you put in the headline.

Founders need optimism. A company would never leave the ground without it. But optimism should not chair every meeting.

Before a meaningful commitment, run a premortem. Psychologist Gary Klein’s premortem method asks the team to imagine that the project has already failed and explain why. People tend to surface concerns more freely when failure is presented as a fact to investigate instead of a possibility they have to defend.

Have everyone write alone for five minutes before the founder or most senior person speaks. Otherwise, the room will quickly discover that it has always shared the boss’s opinion. For the membership, the list might include:

• Members could not book the services they joined for.

• The price covered the visible service but not the coordination behind it.

• Clients liked the concept and then forgot to use it.

• The experience varied so much by city that the brand promise stopped meaning much.

Pick the three failures that feel both plausible and damaging. Give each an early warning sign and an owner. That is enough. A premortem should make the plan sturdier, not leave the team staring into the middle distance.

An idea can sound beautifully simple for months. Put it into a schedule and it starts admitting things.

Who owns the vendor contracts? Which services cannot begin until insurance is confirmed? How long will staff training take? What needs to happen before the second city opens? A plain project plan, the sort your team will actually update, is useful because it puts owners, deadlines, dependencies and spending in the same place. Its job is not to impress anyone. Its job is to reveal work that the idea conveniently left out.

Past projects are especially helpful here. Psychologists Daniel Kahneman and Amos Tversky described the planning fallacy: our stubborn tendency to underestimate how long a future task will take, even when similar work has run late before. If your last three vendor integrations took six weeks, the new one probably does not take three because the team feels energized.

Use the outside view. Look at what comparable work actually required. Add the lawyer, the training, the customer-support scripts and the quiet week after launch when the team fixes everything it did not know to ask about. A good plan may make the idea look harder. That is not a flaw in the plan.

Founders sometimes invite finance in after the interesting decisions have been made. By then, the spreadsheet is expected to confirm the plot.

Bring the numbers in earlier, while they are still allowed to be rude.

Say the membership adds $150,000 in annual fixed costs and produces $180 in monthly contribution margin per active member. The break-even point is about 70 active members. If the contribution margin turns out to be $130, the business needs roughly 97. Neither number tells you what will happen. Both tell you what must happen.

Now you can have a useful argument. How quickly can the company reach 70 paying members? What monthly churn can it tolerate? Does the second hire arrive at 100 members or earlier? What happens to cash if clients pay monthly while vendors require deposits?

For a question like that, a straightforward financial calculator can help you run the loan, margin or cash-flow math without turning the document into a miniature finance department. Try the case you want, the case you can defend and the case that makes everyone sit up a little straighter. The point is not to produce a prettier forecast. It is to find the threshold the company cannot afford to miss.

Decision meetings age badly. Six months later, everyone remembers being more cautious, more supportive and generally more perceptive than the notes suggest. This is normal. It is also why the decision should be recorded while the disagreement is still fresh.

Keep it short:

• What are we approving now?

• What evidence supports it?

• What must be true for it to work?

• How much money, time and trust are we willing to risk?

• What would make us expand, change course or stop?

• When will we review the decision, and who owns that review?

This note protects the team from judging every decision by its ending. A thoughtful bet can lose. A sloppy bet can get lucky. If the company only rewards the outcome, it eventually teaches people to hide uncertainty and take credit for favorable weather.

On the review date, compare what happened with what the team expected. Which assumption failed? Which warning arrived early? What did paying customers reveal that interviews did not? Then decide again. Continue, adjust or stop.

There is a particular kind of courage in launching something. There is another kind in looking at a project you championed and saying, “We learned enough. This version is not the business.”

That sentence is easier to say when the original decision included a spending limit, a review date and clear signals. Without those boundaries, every review becomes personal. People defend the project because they feel they are defending their judgment, their status or the story they told the team.

A founder’s job is not to be the person who knew all along. Nobody did. The job is to keep the company close enough to reality that new information can still change the plan—and to do it before the cash, the calendar and the team’s patience are gone.

Big ideas still matter. They give a company somewhere worth going. But the businesses that last are usually built in the quieter moments afterward: when somebody asks the inconvenient question, puts a boundary around the bet and gives reality a chance to answer.