High Conviction Founder Series: They think like scientists, act like founders

Build hypotheses, run experiments, iterate with intent. The scientific method is the shortest path to product-market fit.

Hey friends 👋

You’ve done everything the “smart” founders told you to do.

You read the books. You learned your lesson from the last company, the one where you built for a year on a hunch and shipped to silence. Never again. This time you validate first.

So you talk to customers. A lot of them. Forty-three conversations and counting. You’ve got a database of quotes, a color-coded affinity map, and a deck titled “What We Learned.” Every call, someone tells you the problem is real. “Yeah, that’s a headache.” “Yeah, I’d take a look at that.”

Six months in, your co-founder asks how validation is going. Great, you say. Everyone has the problem.

Then they ask the question that stops you cold. Okay. How many of them have agreed to pay for anything?

None. Not one. You never asked. You ran forty-three conversations that could not possibly have failed, called it science, and learned nothing that costs anyone a dollar.

You’ve been thinking like a scientist. You forgot to act like a founder.

Let’s dive deep 👇

Habit #3 - High Conviction Founder Series

Habit #1 was about what to test: the assumption that kills you if you’re wrong. Habit #2 was about what to fall in love with: the customer’s problem, not your own idea of it. Both tell you where to point. Neither tells you how to run the thing.

That’s Habit #3.

High conviction founders think like scientists and act like founders.

Hold both words, because almost everyone drops one of them. Drop the scientist and you get the founder who builds on faith, ships to crickets, and calls a gut feeling a strategy. We covered that one in Habit #1. Drop the founder and you get the version above: endless discovery, a research museum, validated learning that validates nothing, because no experiment was ever allowed to come back no.

The scientist gives you the method. Form a belief or hypothesis you could be wrong about, design a test that could prove it wrong, read the result honestly, update. The founder gives you the nerve and the speed to run it this week, with something real on the line. Neither half works alone. A scientist who won’t ship never finds out. A founder who won’t test finds out too late.

Build a hypothesis you could be wrong

A hypothesis is a belief you can be proven wrong about. If it can’t fail, it isn’t one.

“Pharmacists want better inventory tools” can’t fail. Of course they want that, the way everyone wants everything that sounds free and helpful. It collects nods forever and teaches you nothing. A hope wearing a lab coat is still just a hope.

Here’s one where you could be wrong: “At least 30% of independent pharmacy owners who take a demo will book a paid $200-a-month pilot within two weeks.” Specific about who, measurable against a threshold, narrowed to one moving part, falsifiable. Run it and you get a clean number, and the number can come back ugly. That’s the point. A hypothesis you can’t fail is a security blanket. A hypothesis you can lose is an instrument.

Thinking like a scientist means you write the version that can prove you wrong, and then you want the answer more than you want to be right. Same posture as Habit #2, aimed at yourself this time. You are not in the room to defend your belief. You are there to find out if it’s true.

Run the experiment that can lead to a no

This is where the founder half earns its keep.

Most “scientific” founders run experiments rigged to pass. More interviews. Leading questions. A landing page they show only to friends. Each one comes back warm, and none of it costs the customer anything, which is exactly why none of it tells you anything. Interest is free. People hand it out to be kind.

An experiment is only worth running if it can come back no. That means putting something in front of the customer that asks them to spend a currency they protect: Time, Effort, Access, or Money. A booked pilot. A signed LOI. A card on a pre-order page. An intro to the person who controls the budget. We call these the four asks: TEAM, and they are the line between discovery and validation. Discovery tells you the problem exists and to a degree severity and urgency. Validation tells you someone will pay for it. Those forty-three interviews live entirely on the discovery side of that line.

So the pharmacy founder’s real experiment is a $200-a-month pre-order page in front of fifty owners who took a demo, and a count of how many put a card down. The interview could never fail. The pre-order page can. Acting like a founder means you build the test that can break your heart, and then you go court the no on purpose, because a no this week is the cheapest thing you will ever buy.

Iterate with intent

A loop that spins is not the same as a loop that aims.

When the pre-order page comes back, only three of the fifty owners put a card down. You needed fifteen. The founder reflex is to go build something. Add a feature. Redesign onboarding. That’s motion, and motion feels like progress, and we already have a name for motion that dodges the real question: procrastivity. Procrastivity is hiding behind activity when you are actually procrastinating. Procrastination is unprocessed fear, and the fear you are dodging is exactly where you need to be experimenting.

Intent means the next loop points at the one belief the last result called into question, and nothing else. Three doesn’t tell you to build. It tells you to ask which belief broke. Did the owners who sat through a demo not feel the problem sharply enough to pay, so you pivot the audience? Was $200 the wrong number? Was a pre-order the wrong shape of ask for a first yes? Each is a different experiment, and you only get to run the one the evidence points at. Notice cold email isn’t on that list. You held the channel constant by testing only owners who had already taken a demo, so whether cold email reaches pharmacy owners is a separate experiment with its own number, not this one.

At Traction Lab we use a tool for exactly this: the Validation Roadmap. Nine beliefs every startup has to prove, in order, from Customer to Problem to Willingness to Pay on down, each scored for how much evidence backs it. Read more here. It is a living map, not a checklist. A result downstream can knock over something you thought you had settled upstream, and when it does, you go back and aim there. High conviction founders don’t run more experiments than everyone else. They run experiments pointed at the one question that is load-bearing right now. Every loop buys a real answer. None of them are busywork.

The math: science is the fast path

The reason being scientific can be called careful, or slow, or academic, is the great lie of early-stage building. Run the numbers.

Founder A thinks like a scientist and acts like a founder. One cheap experiment a week, each one pointed at a real question, each one able to fail. Over a year, fifty loops. Fifty wrong directions eliminated or right ones confirmed.

Founder B is all founder. Builds for a quarter, then shows the market what he made. Four loops a year. Four shots. A lot of cash and time burned.

Founder C is all scientist. Interviews forever, never ships a test that can fail. Loops that produce a real answer: zero. Played it safe in the “lab”.

Product-market fit is a search. You don’t know where it sits, so you find it by eliminating the places it isn’t, one cheap test at a time, until the only thing left standing is the thing that works. Founder A searches that space twelve times faster than the builder and infinitely faster than the researcher. The velocity metric we track for this, the time from “I have a hypothesis” to “I tested it on a real customer,” isn’t a nicety. It’s the whole game. We call this “Time to Customer”.

So the scientific method only looks like the careful path. Every cheap experiment that eliminates a wrong direction is a quarter of building you didn’t burn. That’s the whole trick, and it’s why the method is the shortest path to fit instead of the long way around.

Build the habit this week

Pick the one belief that’s load-bearing right now and least supported by evidence. The kill-question from Habit #1.

Write it as a hypothesis you could get wrong. Specific about who, a number for the threshold, a deadline. If you can’t imagine it coming back no, you haven’t written a hypothesis yet. Rewrite it until you can.

Now design the cheapest experiment that could prove it wrong, and put one of the four asks: the TEAM framework inside it. Not a call where they tell you it’s a great idea. A test where they have to spend Time, Effort, Access, or Money, or walk away. And then run it this week. Days, not quarters. If your plan to test it starts with “first we build,” you’ve smuggled the dodge back in.

When the result lands, do the founder thing and act on it. Pivot, persevere, or double down, then aim the next loop at whatever the evidence just exposed. Don’t go quiet and build. Don’t go gather more quotes. Move.

Think like a scientist so you find out the truth. Act like a founder so you find out this week.

Until next week,

Cam