Hey friends 👋

You’re twenty minutes into the investor meeting and it’s “going well”.

Slide 14 is your favorite. The pipeline slide. Fifteen logos, three of them enterprise names everyone in the room recognizes, $2.4M in weighted pipeline value printed across the top.

You believe that number. Your whole team does. When the biggest logo entered the CRM, your co-founder screenshotted it for the group chat. You planned the next sales hire against that column.

The investor leans in. “Walk me through the deal in the second row. Who’s your champion, and what have they committed to?”

You start answering and hear it out loud for the first time. A director replied to your cold email six weeks ago. One call. They said it was interesting. They have not responded since.

The investor writes something down. The meeting stays polite for another half hour. The pass email lands Thursday morning.

Let’s dive deep 👇

Subscribe now

The newest show in startup theatre

Pipeline Theatre belongs to the startup theatre family, the collection of ways founders perform progress instead of making it. Vanity metrics perform usage. Procrastivity performs effort. Pipeline theatre performs demand.

The staging is simple. Take every conversation you’ve had, assign each one a stage and a probability, multiply by a deal size, and sum the column. The output is a big number with recognizable names attached. It looks like demand. It weighs nothing.

Stage props are built light on purpose. Easy to carry, easy to strike when the show closes. A pipeline built from interest works the same way, and it strikes itself the moment someone applies real weight: a hard question, a close date, the end of a quarter.

The whole show runs on one substitution: interest standing in for intent. Interest is a pleasant conversation. Intent is a commitment with a price.

An assumption tragedy in three acts

Every tragedy is built the same way. The ending is written into the opening scene, the audience can see it coming, and the protagonist cannot. A theatrical pipeline follows that script. Each act below stages a bigger untested assumption than the last.

Act I: The Stages

CRM stage names imply commitments. Qualified implies someone got qualified. Evaluating implies an evaluation is underway. In pipeline theatre, deals get promoted by activity on your side of the table. You sent the deck, so the deal is engaged. You ran the demo, so the deal is evaluating. The buyer cleared nothing.

The test for any stage is the interest versus intent question: what did the buyer give up or commit? Time beyond a polite thirty minutes. Effort, like exporting data or documenting a workflow. Access to the person who signs. Money, in any form. If the answer is nothing, no sales process has started, whatever the stage column says.

Picture a founder selling compliance software who demos for a quality director at a 2,000-person food manufacturer. The director says it could be big and promises to socialize it internally. The deal moves to Evaluation, 60%. Six weeks of silence follow. That 60% measured the founder’s mood on demo day.

Act II: The Weights

Weighted pipeline multiplies deal size by stage probability, and the probability is supposed to encode evidence of intent: your historical close rate from that stage. You have ten customers. You have no close-rate history worth truly noting. So the number next to each logo is five stacked assumptions: right buyer, urgent problem, live budget, you beat the status quo, they move this quarter. Multiply five untested assumptions together and you land under 10%. The CRM says 25. That 25 is a vibe wearing a percent sign.

Then the spreadsheet compounds it. No single deal claims $2.4M, and no single weight looks unreasonable on its own: a 25 here, a 60 there, each one a small round-up of a real conversation. Sum fifteen small round-ups and they stack into a headline number no one ever decided to write. The total is the one line on the slide that nobody authored and everybody believes.

Act III: The Logos

Your ten closed customers are 40-to-80-person companies. Founder-led motion, three-week cycle, the owner signed. The three impressive names on your slide are enterprises. Different buyer, because now there’s a VP, a procurement team, a security review, and a budget cycle. Different sales cycle, because nine to eighteen months is normal there. Different motion, and you’ve run that motion zero times.

Repeatable sales requires alignment on five things: same profile, same problem, same channel, same motion, same objections. An enterprise logo in your pipeline misses on all five, so it inherits none of your track record. Your close rate for that motion is zero attempts, zero closes. There is no honest percentage to write down.

Closing the medium-sized business proved the medium-sized motion. Evidence refuses to travel between segments without new data. You haven’t run the enterprise motion once, so nothing about it is predictable, which means nothing about it is repeatable, and the slide prices it like it already scales. A logo carries interest at best. Intent has a champion with a name and a cleared ask with willingness to pay.

The math

Take the $2.4M slide and probe every deal with the one question investors ask: what has this buyer committed?

Six deals: cold outreach, no reply. Zero commitments. $0.

Four deals: one call each, ending in some version of circle back next quarter. Interest expressed, no ask ever made. $0.

Three deals: demo complete, they requested a case study. Effort flowed, from you to them. $0.

One deal: they exported six months of production data for a scoping exercise. Effort cleared. It stays, weighted by your real demo-to-close history.

One deal: signed LOI with pricing and a start date. Money committed. It stays.

Re-weighted total: about $140K 🤏 against the $2.4M on the slide. Look at which deals survived. Both are mid-market companies that resemble the ten you’ve closed. The three famous logos that made the slide “impressive” contributed nothing, because none of them ever lifted an ounce. In fact they likely hurt you more than you think. They soaked up outreach hours that belonged to the profile you actually close, and they held your forecast hostage the whole time.

The missing $2.26M was never in the market. The slide was its only address. You forecasted a sales hire and set your raise timing against it anyway.

Who the show is for

The show opens for investors, and sometimes it runs for a meeting or two, because logos earn nods. But investors have sat through more pipeline slides than you’ve had customer calls, and their probing questions are all intent questions. Who’s the champion. What have they committed. When did they say they’d sign. Walk me through your last three closed deals and show me how this one resembles them. One honest answer strikes the set.

The show has a second audience, and this is where the demise gets quick. Run it enough times and you buy a ticket yourself. You forecast hires against the weighted number. You time the raise against it. You tell your co-founder the quarter is covered. Misrepresenting the pipeline costs you a term sheet. Misweighting it costs you the company, because even when the room declines to probe, the quarter probes. The quarter always probes.

Rebuild it as a ledger of intent

A pipeline is a ledger of commitments, and the only weights that belong in it are ones the buyer lifted. Rebuild yours on four rules.

A deal enters when the buyer clears their first ask. They match the profile you’ve validated, they’ve confirmed the problem is urgent, and they’ve given up time, effort, access, or money. Before that, the name lives on a contact list, and contact lists carry no dollar value.

Name your stages after commitments. Time committed: they blocked a 90-minute working session. Effort committed: they exported the data, documented the workflow. Access committed: they put you in the room with the economic buyer. Money committed: paid pilot, deposit, LOI with pricing and dates. A deal moves when a new commitment clears. Activity on your side of the table moves nothing.

Weight from your own history, per motion and per profile. No history for a profile means the deal is an experiment, and experiments carry no dollar value on an investor slide. Track them separately and say so out loud. Naming the enterprise deal as an experiment builds more credibility with investors than costuming it as pipeline ever will.

Then do this today. Open your CRM. Next to every deal, write the last commitment the buyer cleared: time, effort, access, or money. Blank cell, the deal comes out. Logo that looks nothing like your closed customers, out of the total and onto the experiments list. Re-sum what’s left and put that number on the slide. It will be smaller. It will also hold weight in any room, including the one where you talk to yourself.

Until next week,

Cam

Leave a comment

Hey friends 👋

You closed your first eleven customers yourself. Every one was a grind. The awkward pricing conversations. The follow-ups that felt like begging. The demo where you watched the buyer’s eyes drift to their second monitor.

You hate it. So you do what every advisor, podcast, and LinkedIn carousel tells you to do: hire someone great and get back to what you are best at.

Enter the AE with the shiny resume. $140K OTE, logos from two Series B companies, speaks fluently about pipeline discipline.

Ninety days later: zero closed deals. Your warmest leads have gone quiet. And you genuinely cannot tell whether you hired the wrong person or handed them a pitch that never worked in the first place.

That ambiguity is the expensive part. You paid six figures to learn nothing.

Let’s dive deep 👇

Subscribe now

The Founder Arc

Every critical function in your startup travels the same three stages: Founder-Only, then Founder-Led, then Founder-Less. We call this the Founder Arc, and it maps directly onto the progression we teach for every growth engine: predictable, then repeatable, then scalable.

Founder-Only is where you find predictability. Founder-Led is where you prove repeatability. Founder-Less is where you scale what you proved.

The founder in the hook jumped from stage one straight to stage three and skipped the middle entirely. The middle is where the actual handoff happens.

And the arc covers more than sales. Product decisions, support, onboarding: every core function walks the same path, and every one fails the same way when a stage gets skipped.

1. Founder-Only: do the scary thing until it gets predictable

This stage is data collection, and you are the only instrument sensitive enough to run it.

In sales, that means you take every call. You hear the same objection for the fifth time and notice it only shows up at companies under 50 employees. You watch deals close fast when the buyer just lost a key employee to the problem, and stall forever when they found you through a webinar. You learn the exact words customers use to describe their pain, and those words become your outbound.

In product, it means you sit in the discovery calls and make the roadmap calls yourself. You watch a customer limp through their duct-taped workaround on a screen share and learn what must-have actually means. You ship the wrong thing once, feel it, and never again prioritize by loudest voice.

What you are building is pattern recognition you cannot buy back later. The question JDM asks every founder at this stage:

Can you separate what worked from what happened to work?

Your first wins are full of noise. Warm intros. Lucky timing. A buyer who turned out to be your college roommate’s boss. Founder-Only is how you learn which wins were the motion and which were just the weather.

Skip this stage and those learnings evaporate. A hired rep hears a fatal objection, logs the deal as lost to price, and moves on. You would have heard the same objection and recognized a mispositioned value prop.

2. Founder-Led: the step almost everyone skips

Founder-Led is a light delegation. Your first hire works beside you, not instead of you.

Concretely: you run the calls while they shadow. Then they run the calls while you shadow. Every place their motion deviates from yours becomes a coaching note or a playbook edit, because sometimes their deviation is the improvement.

This is where repeatability gets proven, and the definition matters. Repeatable means someone who is not you can execute the motion successfully. You do not know whether your playbook is real until it survives contact with another human. Until then it is a pile of things that worked for the founder, which is a different document.

The product version: your first product hire makes prioritization calls inside your framework while you stay in the customer conversations. You review their decisions against your rubric every week. When their calls and yours converge for a full quarter, the function is ready to leave home.

Founders skip this stage for an honest reason: it does not relieve the discomfort. You are still doing the scary thing, now with an audience, and it feels slower than handing over the keys.

We see the move constantly: a founder maxed out on sales plans to exit it entirely before their first hire has closed a single deal. Skipping the middle turns delegation into abandonment. The hire inherits a job with no map, and when they fail, the founder concludes sales does not work for this business.

3. Founder-Less: scale the channel you proved

Founder-Less is where every function should eventually land: sales that closes without you, product that ships without you. The only open question is when you have earned the handoff.

The graduation test is repeatability alignment across five elements: same customer profile, same urgent and severe problem in the same language, same channel to reach them, same motion in the conversation, same objections. Five for five, and someone other than you has run the motion successfully without you in the room.

Pass that test and hiring becomes a math question: add input and output grows at least in proportion, hopefully better. Proportional is the floor, and the playbook is what pushes past it. Rep two ramps on a documented motion instead of rediscovering one, so each unit of input buys more output than the last. You are fueling an engine.

Hire before that test and you are buying parts for an engine that does not exist.

The arc fails in the other direction too. Some founders never leave stage one. The bottleneck founder has a favorite line: nobody understands our customers like I do. That founder is still personally approving every ticket at month 30, and the company ships at the speed of one calendar. Founder-Only is a stage, and camping there caps your company at the size of your week.

The trap: hiring away your discomfort

The tell that you are about to skip a stage: you are delegating a function because it is painful, while telling yourself it is because you are strategic.

Sales feels gross, so you hire a head of sales. Code is intimidating, so the dev shop owns product decisions while you focus on strategy and fundraising. Whatever that means.

You have confused not being naturally good at something with not needing to learn it. Nobody is naturally good at founder sales. The founders who look like naturals did their reps in private.

So we hold a hard line here, and we gave it a number.

The 40-Before-Delegation Rule: do the critical function yourself, successfully, at least 40 times before you hire someone to own it.

In sales, that is 40 complete reps through your motion, first touch to close or clear loss. Wins and losses both count, and the losses carry most of the information. This is where true learning happens.

In product, that is 40 prioritization decisions you made, shipped, and scored against what actually happened.

If you cannot write the job description with specific success metrics and staple a playbook to it, you are too early. Never delegate what you cannot repeat.

The math on skipping the arc

Run the numbers on the founder from the top of this article.

A $140K OTE rep costs roughly $75K for six months, fully loaded. Handing them an unproven motion means running an experiment with two unknown variables at once: does the motion work, and can this person execute it.

When the experiment fails, you cannot attribute the failure. Wrong pitch? Wrong customer profile? Wrong channel? Wrong hire? Any of the four explains zero closed deals, so you eliminated none of them. $75K and two quarters, spent to stay exactly as confused as you started.

The part that hurts more than the cash: an early-stage startup with a tight beachhead might have 60 genuinely qualified prospects in reach right now. A rep learning an unproven motion burns 20 of them. Those leads do not regenerate next quarter. Time comes back. Money sometimes comes back. A torched beachhead does not.

Compare the alternative. Forty founder-run reps cost you zero incremental cash and isolate exactly one variable: the motion. Every lost deal teaches you something true about the pitch, because you know it was delivered the way you intended. That is the cheapest signal available anywhere in your company, and delegating early trades it away for comfort.

Do this before your next hire

Pick the function you most want off your plate. Be honest, it is the one you just thought of.

Count your reps. Complete executions of the full motion, not meetings attended.

Under 40? You have your answer and your calendar for the next eight weeks. Book the next five reps this week, and write one playbook entry after each: what you said, what they pushed back on, what you will change.

At or past 40? Write the playbook before the job description. Customer profile, problem language, channel, motion, objections with answers. All five, in writing. Then make your first hire a Founder-Led hire: run ten reps beside them, and hand over the pen only when their results look like yours.

Until next week,

Cam

Hey friends 👋

The wire hits on a Thursday. $500K pre-seed, eleven months of pitching to close it.

Friday you make the list. A sales hire, because founders can’t do sales forever. A $30K booth at the industry’s biggest conference. A $45K agency rebrand, because the current site screams side project. Four months of engineering for the enterprise features every prospect asked about.

Every line item feels like company building.

Six months later the sales rep has quit. The booth produced 212 badge scans and zero buyers. The brand is gorgeous and conversion didn’t move. The enterprise features sit behind two stalled procurement processes, untouched.

$310K gone. Now ask the only question that matters at your stage: what did you learn with the money?

The sales hire couldn’t sell your product. You suspected as much, since you couldn’t either. Everything else on that list, you could have learned for the price of a nice dinner.

Every bet was oversized for the evidence behind it. That gap has a body count. And in this case, likely your startup.

Let’s dive deep 👇

Subscribe now

Habit #5 in the series: They optimize for learning per dollar spent

Quick recap for anyone joining late:

Habit #1: high conviction founders test what could kill them.

Habit #2: they fall in love with the customer’s problem, not their own solution.

Habit #3: they think like scientists and act like founders.

Habit #4: they prioritize shortening time-to-customer.

Habit #4 put a clock on your learning. This one puts a price tag on it.

High conviction founders optimize for learning per dollar spent.

Every action a startup takes buys two things at once: a shot at progress (evidence) and a learning. Low conviction founders price the first. High conviction founders price both, and they refuse to pay $180K for a lesson on sale for $300.

Your runway is a research budget

Before product-market fit, your business is a stack of unproven beliefs. Customer, problem, willingness to pay, channel. Beliefs all the way down.

Capital at this stage has one job: convert dollars into evidence until enough of those beliefs become facts that spending on growth stops being a gamble.

Which means the honest unit of runway at pre-seed is the number of experiments remaining, not the number of months remaining.

$400K funding $2K experiments is 200 shots at the truth. The same $400K committed to four big swings is 4 shots. Same bank balance. A 50x difference in what you’ll know when it’s gone.

Size the bet to the evidence

Habit #1 gave you the Ladder of Evidence and the line that the lesson never changes, only the price does. Habit #5 turns that into a spending policy, and we wrote the long version of it in Stop betting the house on a maybe.

The short version comes from poker. Amateurs go big on weak hands because excitement or desperation says to. Professionals size every bet to the strength of the hand in front of them. Your hand is your evidence, and a compliment at a demo is a pair of twos.

Traction is a trendline, and your bets should match the slope. A single data point is a clue. A consistent curve is a case. When the story is still unclear, make small bets. When the signals compound, invest more. When the market starts pulling you in, that’s when you sprint.

In dollars, proportional betting looks like an earned ladder. $500 of coffee and cold calls earns the right to spend $5K on a concierge test. Five customers paying full price for the concierge version earns the right to spend $50K on a real build. Paying customers who stick around earn the right to spend $500K acquiring more of them.

Skip a rung and the difference rides on a guess. A $50K build backed by conversation-level evidence is a $45K gamble wearing a $5K experiment’s clothes. Better to underbuild for a no than to overbuild for a maybe.

The moment this discipline matters most is the week after a raise. Money in the bank creates pressure to make moves that match the new number. Investors expect motion. Your co-founder expects hires. Resist all of it. The wire changed your balance. It did not change your evidence. Bet on the slope, not the spike.

Risky theater

Big actions taken on evidence too thin to warrant them have a name: risky theater.

Risky theater is the expensive cousin of procrastivity from Habit #1. Procrastivity hides in cheap busywork. Risky theater hides in bold moves. Both produce motion the market never gets to falsify. Only one of them torches six figures doing it.

Three founders you will recognize:

The conference founder. They drop $30K on a booth and a sponsorship tier before ever running their pitch past ten cold prospects, which costs nothing. The booth stress-tests their logistics, their banner printer, and their small talk. The message walks in untested and walks out untested, now with a $30K receipt.

The early hirer. They bring on a $140K enterprise sales rep to escape founder-led sales before the motion is predictable. Predictability comes first, then repeatability, then scale. A rep handed an unpredictable motion can only multiply the ambiguity, and in month five everyone agrees to call it a bad fit.

The big builder. They turn two unpaid pilots into an eight-month enterprise roadmap. The evidence on hand supports a $3K concierge test. The spend assumes a validated product. The $147K between those two numbers is pure exposure.

Each bet ran 50x to 100x ahead of the evidence behind it. And each returned close to zero falsifiable information per dollar, which is the tell. Theater spends big and learns small.

The math

Put one hypothesis on trial: independent veterinary clinic owners will pay $350 a month for software that automatically rebooks no-shows.

Four experiments can test it, at four price points.

Experiment one: conversations. Twenty calls with clinic owners, each ending in one of the four asks: TEAM (Time, Effort, Access, Money). Will they put down a deposit, intro you to their office manager, commit to a pilot start date? Cost: about $300 and a week.

Experiment two: a payment link. A landing page, $200 in ads, and a checkout that captures a card for a founding-member rate. Cost: about $700.

Experiment three: concierge. You rebook the no-shows manually for five clinics at full price. No product exists. The clinics don’t care. Cost: about $3K, mostly your time.

Experiment four: build first, ask second. Eight months of engineering, then the same question. Cost: $180K or a large part of the cap table.

All four experiments test the same hypothesis and return the same binary: owners pay or they pass. Each step up buys a little more certainty. The price climbs 600x from the first experiment to the last. The certainty of the experiment doesn’t.

Founders default to experiment four, because the product feels safer to stand behind and the launch reads better on LinkedIn. And when the answer comes back no, they’ve burned the better part of a pre-seed round to hear it.

Now allocate the research budget. Two founders, $300K each. Founder A makes two $150K bets. Founder B spends $60K running experiments one through three against their riskiest beliefs, then puts $240K behind whatever survives. If each big bet rests on even one coin-flip assumption, Founder A clears both flips 25% of the time. Founder B bought dozens of chances to be wrong cheaply and saved the big check for a belief that already survived contact with the market.

Same money. Wildly different information and learning gained.

Build the habit this week

Open your budget. Include the spends you’ve already committed to in your head. Those count.

1. List every planned spend over $1K for the next 90 days. Price time honestly. A month of engineering is a spend whether or not it shows up in QuickBooks.

2. Next to each line, write the belief that has to be true for that spend to pay off. Then score your evidence for that belief, 0 to 10. No 7s. 7 is where founders hide from themselves.

3. Flag every line where the dollars are big and the score is under 6. That’s your risky theater list, and every founder has one.

4. For each flagged line, write the cheapest experiment that buys the same learning. Use the tenth rule to size it. Run the cheap version first, and let the result size the next bet.

One budget line at a time: spend like a scientist until the evidence lets you spend like a CEO.

Want the worksheet we use with real companies?

Access the Validation Roadmap template → email cam@tractionlab.io

Until next week,

Cam

Hey friends 👋

The pitch is in three weeks, so you do what feels responsible. You tighten the deck.

Version 9 gets a cleaner TAM slide. Version 10 gets a competitive matrix your designer friend polished over the weekend. Version 11 gets pull quotes from your two pilot users, set in beautiful type.

The meeting went fine. Then the investor asks one question: “What have you learned since we talked in April?”

Every improvement since April lives in the deck. The company underneath it is running on the same three data points it had in the spring.

Nine weeks of work. The story got sharper. The evidence never moved.

Let’s dive deep 👇

The clock starts at the hypothesis

This series is about the small, repeated choices that separate founders who build conviction from founders who build artifacts.

This is Habit #4: High conviction founders prioritize shortening time-to-customer.

Time-to-Customer (TTC) is the elapsed time from forming a hypothesis to testing it with the market. The clock starts the moment you say “I believe X.” It stops the moment a real prospect gets the chance to prove you wrong (maybe right…).

Everything you do between those two moments either creates market contact or postpones it. Research postpones it. Deck revisions postpone it. Building postpones it, right up until the build lands in front of someone who can buy.

High conviction founders treat this number (TTC) the way a CFO treats burn. They know their current TTC, they know the target for their stage, and when Monday morning asks what to work on, shortening the clock wins.

It prioritizes challenging assumptions in the market versus endlessly building without customers ever checking your assumptions.

So, worry less about revising the pitch deck. Worry more about acquiring evidence. Conviction is built from evidence, evidence comes from the market, and the market can’t answer a question you haven’t asked yet.

Prioritizing the clock looks different at each stage. Same habit, three versions.

1. Discovery: finding problems worth solving

The hypothesis on trial: a specific segment experiences a specific problem with enough urgency and severity to act on it.

Say you believe operations managers at 50-to-200-person logistics companies lose a day a week to manual load scheduling. The long version of testing this puts three weeks on the clock before first contact. Desk research. A persona document. An interview guide with 22 questions. A list of warm intros you’re still waiting on.

The short version: 15 cold LinkedIn messages Monday. Five 20-minute conversations by Friday. Ask about their week and listen for the problem to show up unprompted.

Two of five describe the pain without you naming it, then pull up the spreadsheet workaround they built at 11pm? Signal. Zero of five? Also signal, and it cost you coffee money instead of a quarter.

The target at discovery is days. Reports describe markets. Conversations expose them.

2. Validation: proving willingness to pay

The hypothesis on trial: this segment will pay a specific price for a specific outcome (or pay at all).

AI has made the delay here seductive. You can stand up a working prototype in a weekend, so the temptation is to build first and let the product earn the ask. Building got faster. The customer’s decision timeline didn’t. Founders now stack more assumptions before first contact than ever, and they stack them at higher speed.

Say you’re building a startup who is focusing on churn prediction for subscription businesses. The long version of testing willingness to pay takes a month. You build the model, then run a free pilot with three companies pulled from your 25-prospect list. The reports go out. One company says it flagged two accounts they were about to lose. The other two shrug.

A month on the clock, and the question that decides the business, will anyone pay, never gets asked. Feasibility gets the whole month. The paying question gets nothing.

The short version is a priced ask in week one. “If we flag the accounts you’re about to lose before they churn, would you commit $500 to a 60-day paid pilot?” Twenty-five phone calls. A few hang-ups, a few maybes, and a handful of people either reaching for a card or telling you exactly why not. Either way the clock stops and you know something.

The target at early validation is one to two weeks. A landing page with a payment link. A deposit. A pilot with terms signed before it starts. Money is the only interview answer that can’t lie to you.

3. Acquisition: building the growth engine

The hypothesis on trial: a specific channel produces customers predictably.

This one matters because repeatability comes after predictability, and scale comes after both. Same profile, same problem, same channel, same motion, same objections. Each of those is its own hypothesis, and each one only resolves on contact.

A compliance training platform selling to home healthcare agencies had 11 paying customers, all from the founder’s network. Their hypothesis: cold outbound to agency administrators is a repeatable channel. Solid hypothesis. Then they spent three weeks preparing to test it. Eight email sequence variants. A new sending domain. CRM pipeline stages. A tracking dashboard. A running debate about whether to target compliance officers or owners.

Three weeks, zero information. Eight sequence variants before the first send is A/B testing your imagination.

Then they hit send and the learning started within days. 400 emails over six weeks. 34 replies. 12 demos. 3 closed customers, fully cold, averaging 18 days from first email to signature. Every number they now know about their motion arrived after contact.

The short version starts sending on day two. Twenty emails, your existing domain, your single best-guess sequence. The market grades your list, your message, and your target title before your dashboard would have shipped. Build the dashboard once there’s data worth dashboarding.

The target is two to four weeks at pre-seed for an outbound test, four to eight at seed for paid acquisition. A growth engine is a machine made of answered questions. Short loops build it while your competitors are still configuring their CRM.

The cost of a long clock

So what do you lose when TTC stretches? Three things, and they compound.

You wager more on every answer. While the clock runs, you keep building on the untested assumption. More features, more content, more pipeline, all stacked on a foundation the market hasn’t inspected. When the verdict finally arrives, it lands on the whole stack at once. Time equals risk. The longer you wait to find out if you’re right, the more you’ve bet that you are.

Your answers get vague. A six-month build-and-launch that flops can’t tell you what failed. Wrong segment? Wrong price? Wrong channel? Wrong message? One big bet returns one ambiguous funeral. Ten small experiments return ten specific answers, each one naming the exact thing to change.

Your runway buys fewer answers. Runway is a budget of answers and learning. Twelve months of cash at a six-week TTC buys you 8 resolved hypotheses before zero. The same twelve months at a one-week TTC buys you 48.

Now remember that your first guess at the customer is usually wrong. So is your first price, your first channel, and your first message. Call it 10 resolved hypotheses to reach a repeatable motion. The one-week founder gets there in under three months with runway to spare. The six-week founder dies two answers short, holding a beautiful deck and no damn idea which assumption did it.

Same idea. Same money. Different clock.

Build the habit this week

Take your riskiest hypothesis and write it as one falsifiable sentence. If you ran the Habit #1 exercise, you already have it.

Now compute your TTC on it, honestly. The date you first believed it versus today. If the market hasn’t touched it yet, your TTC reads “and counting.” That number is your baseline.

List every step standing between you and market contact. Cross out everything that’s preparation. The interview guide. The second landing page draft. Sequence variants five through eight. Preparation feels responsible. Contact produces evidence.

Then run the shortest version that puts the hypothesis in front of a real prospect, inside the target for your stage. Days at discovery. One to two weeks in early validation. Two to four at pre-seed. Four to eight at seed.

Last, write your TTC on the wall next to your runway. Together they decide how many answers you get before the money decides for you.

The deck can hold. Version 11 reads about the same as version 8, and no investor ever wrote a check for typography. Go get an answer this week. Then get the next one faster.

Want the worksheet we use with real companies?

Access the Validation Roadmap template → email cam@tractionlab.io

Until next week,

Cam

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

Hey friends 👋

You’ve been building your product for 14 months.

The product is finally good. Actually good. You’ve rewritten onboarding three times. You’ve shipped every integration users asked for. You’ve polished the dashboard until it sparkles. Your 30 active users give you an NPS of 62.

So why won’t anyone new sign up?

You add another feature. Crickets. You rebuild the onboarding a fourth time. Crickets. You’re convinced the next release is the one that finally makes it click, so you keep building, because building is the thing you know how to do.

Then on a Tuesday night you ask your co-founder the question you’ve been dodging for a year. Do these people actually have the problem we think they have?

Honest answer: No. Not really. Not enough to pay for it. Not enough to switch from whatever they’re doing now. You built a beautiful solution to a problem you fell in love with on day one and never tested what the customer actually wanted and would pay for.

Let’s dive deep 👇

Habit #2 - High Conviction Founder Series

Last week we covered Habit #1: high conviction founders test what could kill them. They hunt the fatal assumption and run at it first.

This week is about what you fall in love with, because that decides what you’re willing to test in the first place.

High conviction founders fall in love with the customer’s problem, not their own solution.

Notice the possessives. The customer’s problem. Your solution. Both words matter, because the trap shows up in two costumes and most founders only recognize one of them.

The obvious version is solution love. You fall for your specific implementation, your tech, your architecture, your brand. You defend the thing you built because it’s yours. What’s not to love.

The sneaky version is problem love that’s really self-love. You fall for your own articulation of the problem. You walk into every customer conversation certain you already know what hurts, and you spend the call leading them to the confirmation instead of listening for what they actually said.

The risk is the same in both costumes: you’re in love with your own idea of the problem and the solution instead of staying curious about theirs.

The customer decides if you succeed or fail. Nobody else gets a vote.

Subscribe now

Your problem statement is a guess too

Here’s the part most founders miss.

Everyone knows the solution is a hypothesis. We say it constantly. The product is a guess at the thing, guesses get revised, fine.

But your problem statement is a guess too. It’s just an earlier guess in the sequence, and a more durable one, because you wrote it before you talked to anyone and it feels like bedrock by the time you’ve built on top of it for a year.

It can either be the foundation of a sturdy startup or the card that brings down the house of cards.

Two things hold still: the customer, and the job they’re trying to get done. Everything else, including your problem statement, is up for revision.

The problem is wherever their current way of doing that job breaks down. You don’t get to decide where that is from your desk. You find it by watching where the job actually fails them, and how badly.

A breakdown only matters if it costs them something real and they’re trying to fix it now. Severe means it’s bleeding time, money, or relationships. Urgent means they’re already looking for a way out, not filing it under someday. A problem that’s severe but not urgent feels like validation in the room and converts to nothing later. You’re hunting for the version that’s both.

So when a founder tells me they’re committed to the problem, my next question is the same every time. Committed to the customer’s problem, the one you found by listening and watched them bleed over? Or committed to the problem statement you wrote in a doc fourteen months ago and have defended ever since?

If their current workaround is already good enough, that’s the news you most need to hear. A founder in love with their own framing is the last person able to hear it

What it sounds like in the room

The whole habit comes down to a single conversation, often less than an hour: you, a customer, and a question. Loving your own version of the problem and loving theirs produce two completely different versions of that hour, and only one of them tells you whether the pain is severe and urgent enough to build on.

In the first version, you walk in certain. You’ve got your problem statement, and you’re there to validate it. So you describe the pain the way you wrote it down, and you watch them nod. “Yeah, that’s annoying.” “Yeah, I could see that being useful.” You leave with a notebook full of yeses and a quiet sense that you were right all along.

But were you?

You weren’t getting validation. You were getting politeness. People agree with founders because agreeing is easier than saying no to someone who’s clearly excited. And even when the problem is real, it may not be severe or urgent enough for them to spend time or money fixing it. “That’s annoying” is not “I’m trying to fix this right now and what I’ve got isn’t working.” The first is a preference. The second is severe and urgent. Across a coffee table they sound nearly the same, and a founder in love with their own framing can’t tell them apart.

In the second version, you walk in curious. You don’t pitch the problem, because pitching it tells them the answer you want. You ask for stories about what they’re actually trying to get done, and how they handle it today, and what happens when that breaks. Then you stop talking. You let them tell you where it hurts, in their words, on their trigger, and you listen for whether they’re already spending time, money, or duct tape trying to make it stop.

What comes back is usually close to what you assumed, but not the same, and the gap is the whole point. The job is real. The place it breaks down is not where you thought. You assumed they struggle at step four; they actually lose the thread at step two, and by the time they reach step four they’ve already given up or routed around it. The pain is sharp, but it sits one step upstream of the thing you built. That gap is only visible if you walked in willing to be wrong. Walk in certain and you’ll talk right over it, every time.

This is why the habit is so hard to keep. The leading question feels like research. The polite nod feels like traction. Confirming your own framing feels like progress. It keeps feeling that way right up until the paid acquisition test comes back empty and you finally ask the question from the top of this email: do these people actually have the problem we think they have?

Customers ask for features, not about problems

The trap doesn’t end once you have customers. It changes shape. Now they hand it to you as a feature request.

They don’t bring you problems. They bring you solutions, usually dressed as a feature request. “Can you add a PDF export?” “Can I change the colors?” “Will you build an integration with X?” Every one is a customer doing your product design for you, and customers are not good product designers, even for their own pain.

Most of these are politeness anyway, the same nod from the discovery call wearing a different outfit. The ones that aren’t are still pointing at a solution, not the job underneath it. Build the literal request and you get a bloated product nobody uses. Dig to the job that triggered it and you find the thing worth building.

Take a common one. Three different users ask for a bulk export button. Easy to just build it. Instead you ask what the export is for. The job turns out to be sending a clean weekly summary to a boss who lives in email and never logs in. Nobody asked for a summary email. That’s the real product. The export button would have shipped and sat there unused.

Your own team does the same thing, shaped like their job. A metric dips and the designer wants a redesign, the engineer wants a feature, the marketer wants a campaign. Each one reaches for their favorite tool before anyone has confirmed why the metric moved. Loving the customer’s problem means refusing to act on any of it until you’ve found the why, and you find the why with an experiment, not a meeting.

Build the habit this week

Start with the job, not your product, and not even your problem statement.

Write one sentence: this specific group is trying to get this specific job done, and here is where their current way of doing it breaks down. Who are they, when does the job come up, what does failing at it cost them, and what do they reach for today to try to solve it.

Notice what’s not in that sentence. Your product. If you can’t describe the job and the breakdown without naming your solution, you don’t have problem commitment yet. You have product attachment wearing founder language.

Now stress-test the part you’re most certain about. Take your problem statement into three customer conversations this week with one rule: you are not allowed to confirm it. You’re only allowed to ask what they’re trying to accomplish and where it breaks today, and then shut up and listen for the urgent, severe version of the pain in their words, not yours. If what you hear doesn’t match your doc, the doc was a guess and the guess was wrong. Good. You just saved yourself the next twelve months.

When a pivot is on the table, split it into two columns. Left: what you actually know about the customer and the job. Right: what’s not working about your current solution. If the left column is thin, you don’t have a pivot, you have a discovery problem you skipped. If the right column is the only thing full, you have an execution issue, not a pivot.

Starting with a solution is like building a key before you know what door it opens. You can keep trying your key on every door in the building, or you can start with a door someone is desperate to get through. Fall in love with the door. Build whatever key opens it.

Grit isn’t digging your heels in. Grit is dragging your ego out of the way and staying curious longer than is comfortable. The market doesn’t care how hard you worked on the wrong thing, or how sure you were. It pays you for landing on a real problem, eventually.

Fall in love with the customer’s problem. Stay flexible about everything else, including your own idea of it.

Until next week,

Cam

Hey friends 👋

You’ve had the idea since January.

February went to research. Market sizing, competitor teardowns, average revenue per customer, every report you could pull without leaving your desk. Boy was that comfortable.

March went to the build. Clickable wireframes. A brand identity. A logo, a color palette, a landing page that would make a design agency jealous.

April finally arrives and you talk to four potential customers. Four. Two of them say the problem is real.

Ninety days of work. Two data points. That’s the entire evidence base for whether this company gets to exist, and a phone call in week one would have bought it for the price of a coffee.

Everything you built in February and March was downstream of an answer you didn’t have.

You built an artifact museum. And nobody’s buying a ticket.

Let’s dive deep 👇

A new series: the habits of high conviction founders

We spend our weeks inside validation roadmaps, screening interviews, and pitch reviews. After enough reps, you start seeing the same separation over and over.

Some founders build with conviction. They walk into an investor conversation with this conviction and transfer it through evidence, because every belief they hold is backed by something they did, measured, and can be defended.

Other founders build artifacts. Decks, prototypes, brands, dashboards. Lots of motion. No idea whether the company should exist... Startup theatre.

The difference comes down to habits. Small, repeated choices about what to work on when nobody is forcing the choice. So we’re starting a series on the habits that make for high conviction founders.

This is Habit #1, and it’s the one all the others depend on:

High conviction founders test what could kill them.

The quadrant where startups die

Your startup is carrying dozens of assumptions right now. Most of them are safe. A few of them are fatal.

Sort every assumption on two axes: how much damage it does if you’re wrong, and how much evidence you have that you’re right.

High impact, high confidence. That’s your foundation. You’ve already proven it. Stop testing it.

Low impact, low confidence. That’s just uncertainty. It won’t make or break you.

Low impact, high confidence. Who cares.

High impact, low confidence. That’s the quadrant where startups die. An assumption that would destroy the business if wrong, supported by little or no evidence. That’s your riskiest assumption, and high conviction founders go straight at it.

Most founders do the opposite. They test what’s easy instead of what’s risky. They A/B test the logo when they don’t know if anyone wants the product. That’s rearranging deck chairs while the ship sinks.

The kill-question changes as you grow, but there’s always exactly one at the front of the line:

• Pre-product: does this customer have this problem with enough urgency and severity to pay for a solution now?

• Post-product, pre-revenue: will people actually pay, or just use it for free?

• Early revenue: can we acquire customers predictably and profitably?

• Scaling: do our unit economics hold at volume?

If you can’t name yours in one sentence, that’s the first problem to fix.

Why you keep testing the wrong quadrant

You already know which assumption could kill your startup. Somewhere in the back of your mind, you’ve known for months.

So why are you refining the pitch deck?

We call this procrastivity. Productive procrastination. All motion, no progress on the thing that matters. You’re working twelve-hour days, and every one of those hours is pointed away from the question that decides everything.

And it makes sense, because the kill-question is the scariest one on the board. Testing it means putting your dream in front of someone who can crush it. That sh** is vulnerable.

The logo can’t reject you. The landing page can’t tell you the problem isn’t urgent. The wireframes will never say no.

So you delay. And every delay is delayed learning, because you can’t learn anything until something gets in front of a customer. The customer decides if you succeed or fail. Nobody else gets a vote.

A team we watched had a customer call booked two weeks out. One prototype built, ready to show. They spent the entire two weeks polishing the UI. Fourteen days of work, zero new information, all to protect themselves from feedback they were about to get anyway.

That’s the habit gap in miniature. Low conviction founders protect the dream from the market. High conviction founders feed the dream to the market and keep what survives. Love the problem, not the solution. The customer will tell you what they need and want.

What it looks like in the wild

The seed-stage builders. Three months into their round, a team had burned $200K. Twelve-hour days. Features shipping constantly. Every decision a gut call, every feature a best guess. The kill-question, will anyone pay... it never got tested. The result was a beautiful product that solved a real problem for exactly nobody willing to pay. They tested feasibility for three months. Feasibility was never going to kill them. It was always desirability.

The pilot collector. A founder selling supply chain software landed a pilot with a mid-sized logistics company. Six months, no success metrics, no purchase terms, no evaluation timeline. He posted the win on LinkedIn and added the logo to his deck. Six months later: “we’ve decided to go in a different direction.” His kill-question was whether an economic buyer would pay. What he tested instead was politeness, and polite companies will string you along forever because it costs them nothing. They “paid” him in feedback, not in cold hard dollars.

The artifact museum. One of the more common founders. Discovery stage, $49 per month product, and the kill-question was as cheap as questions get: do these operators feel this pain badly enough to pay, and with the urgency to pay now? Their customers are small businesses who want to be found. A week of phone calls would have answered it. They spent three months building things to avoid making those calls.

Three different scenarios. Same habit failure. The fatal assumption sat untested while the comfortable ones got all the attention.

The cost of waiting

Here’s the math that should change your week.

The cost of testing your kill-question depends on which rung of the Ladder of Evidence you’re standing on:

• Customer conversations cost you time and coffee money.

• A landing page test costs about $200 in ad spend.

• An MVP costs you in the low thousands and up if you’re careful. Way more if you’re not.

• Launching at scale adds a zero or two.

Now layer on the clock. We track a metric called Time-to-Customer: the elapsed time from “I have a hypothesis” to “I tested it with a real customer.” It’s the single most important velocity metric at the early stage, and it has stage-appropriate targets:

• Discovery: days. The experiment is a 20-minute conversation.

• Early validation: 1 to 2 weeks. Landing page plus a payment link.

• Pre-seed: 2 to 4 weeks. An outbound cold sequence.

• Seed: 4 to 8 weeks. A paid acquisition test.

Put the two together and the cost of procrastivity gets visceral. At discovery stage, the target is days and the price is coffee. Stretch the same test to three months and you pay for the answer with a brand identity, a landing page, and a quarter of runway. Stretch it past a full build and the identical answer costs $200K.

The lesson never changes. Only the price does.

One rule keeps you honest: your experiment should cost roughly one tenth of the decision it informs. A $50K build decision deserves a $5K test, not a $50K leap of faith. And when you don’t know the answer, run the cheapest experiment first.

Build the habit this week

At Traction Lab we use a tool called the Validation Roadmap for exactly this. It lays out the nine stages every startup has to prove, in order: Customer, Problem, Willingness to Pay, Channel, Acquisition, Activation, Revenue, Retention, Referral. For each stage you write down what you believe and how much evidence backs it.

You don’t need the worksheet to start. A blank page works. Here’s the exercise:

Write one belief statement for each of those nine stages. “We believe there is a specific, reachable segment of people who...” and so on down the line.

Score your conviction in each from 0 to 10. No 7s. 7 is where founders hide from themselves. Force the call: are you confident or not?

Now circle the stage where two things are true at once: being wrong is fatal, and your score is lowest. That’s your kill-question. There’s exactly one.

Rewrite it as a falsifiable hypothesis. Specific, measurable, falsifiable. “People want our product” is an assumption. “At least 15% of qualified prospects will sign up for a paid pilot within 30 days of seeing our demo” is a hypothesis.

Then design the cheapest experiment that could kill it, and run it inside the Time-to-Customer target for your stage. Discovery stage means days, not weeks. If your plan to test it starts with “first we build,” you’ve already smuggled procrastivity back in.

You’ll be tempted to test something safer first. That temptation is the whole reason this habit is rare, and the whole reason it’s worth building.

Test what could kill you. Everything else can wait.

Want the worksheet we use with real companies?

Access the Validation Roadmap template → email cam@tractionlab.io

Until next week,

Cam

Share Traction Thinking

Hey friends 👋

You’ve got a product. You’ve got a few early customers. You’ve even got some signal that people want what you’re building.

So you do what every founder does next: you hire for “marketing.”

You set up Google Ads. You launch a LinkedIn campaign. You start posting on Twitter. You sign up for three conferences. You hire a freelancer to write blog posts. You’re testing five channels simultaneously because you heard that’s what growth looks like.

Sixty days and $8,000 later, you’ve got a dashboard full of impressions, a handful of lukewarm leads, and no idea which channel actually works. $8,000 invested with absolutely nothing to show for it.

You didn’t have a marketing problem. You had a go-to-market problem. And you spent marketing dollars trying to solve it.

Let’s dive deep 👇

Two different games

The distinction is simple once you see it. And invisible until you do.

Go-to-market operates in a world of unknowns.

You don’t know exactly who your customer is. You don’t know if the problem is urgent enough to drive action. You don’t know what message makes them pay. You don’t know which channel reaches them. You have hypotheses about all of them (well we hope). You have instincts. But you don’t have proof or evidence. The goal of go-to-market is to turn unknowns into knowns through small, cheap experiments. You’re on a path to predictability. You’re not there yet.

Marketing operates in a world of knowns.

You know the customer. You know the problem. You know the message. You know the channel. You’ve proven all four with data. Now your job is to scale what works, optimize spend, and build repeatability. And repeatability is the foundation for scalability. You’re not experimenting. You’re executing.

Think of it as two board games.

Go-to-market is Battleship. The board is hidden. You’re lobbing shots in the dark trying to find where the ships are. Every experiment is a coordinate. Hit or miss, it updates your map. You’re building a picture of reality one data point at a time.

Marketing is the board game of Risk. You can see the whole board. You know where your armies are. You know where the opportunity is. Your job is to allocate resources strategically against a known landscape.

Most early-stage founders are playing Battleship but spending money like they’re playing Risk. They’re allocating resources against a board they can’t see.

The tell

Here’s how you know you’re still in go-to-market mode, still operating in unknowns. Each unknown builds on the one before it.

1. You can’t describe your customer in one sentence with specifics

Not “small business owners.” Not “people who need project management.” Something like “operations managers at 20-50 person logistics companies who are currently tracking shipments in spreadsheets.”

If you can’t get that specific, your customer is still an unknown. Running ads to a fuzzy audience is spending marketing dollars on a go-to-market problem.

2. You haven’t confirmed the problem is urgent and severe enough to drive action

Your customer might exist, but do they care about this problem enough to do something about it? Are they losing money this month because of it? Are they actively looking for a solution right now? Or is it a “yeah, that’s annoying” problem they’ve lived with for years and will continue to live with?

If you can’t point to evidence that the problem is costing them something real, your problem conviction is still an unknown. In other words if you can’t quanitfy the pain you don’t have clear enough evidence to demonstrate what value you are creating.

3. You haven’t tested your value prop against strangers willing to pay.

Your network thinks your pitch is great. Your advisor says the positioning is strong. But have cold prospects responded to it with their wallets?

If your messaging has only been validated by people with social incentive to be nice, your value proposition is still an unknown. Polite enthusiasm from warm contacts tells you nothing about whether a stranger would pay.

4. You don’t know which channel reaches your customer consistently.

If your early customers came from a mix of warm intros, a conference, a cold email, and an inbound lead, you don’t have a clear and consistent channel. You have anecdotes. A channel becomes a known when you can describe it, measure it, and repeat it. Until then, it’s an unknown.

If any of those four are true, you’re in go-to-market. You’re operating in unknowns. Act like it.

Subscribe now

The cost of playing the wrong game

Say you have $5,000 to spend on customer acquisition this month. You spread it across five channels because you want to “test everything.”

That’s $1,000 per channel. Not enough volume on any single one to learn anything real. So you get ambiguous data, draw the wrong conclusions, and either double down on the wrong channel or give up on one that might have worked with more volume.

But the wasted money isn’t even the worst part.

It’s the wasted time. It’s the motivation you burn running five experiments that teach you nothing. And when you get lucky and land a customer through one of those channels, you don’t know why it worked. So you can’t repeat it. You throw more resources around hoping to get lucky again, still without a clear path to predictability.

Go-to-market is about creating predictability. Predictability creates repeatability. Repeatability creates scalability. Scattered spend skips the first step and pretends you’re already at the third.

Put that same $5,000 into one channel. Run enough volume to see a real pattern. Test two different messages, three different audiences, and actually measure what happens. One unknown converted to a known.

One real answer beats five maybes. Every time.

How to play Battleship well

If you’re operating in unknowns, own it. Stop optimizing and start experimenting. Your job right now is to find predictability, not to scale it. Give yourself that permission to find predictability. It will pay off in the long run.

Pick one channel.

The one where you have the highest density of your target customer and the easiest access to them. If you don’t know which that is, start with wherever your first 3-5 customers actually came from. If they came from cold email, go deeper on cold email. Not LinkedIn. Not conferences. Cold email.

Run one experiment at a time.

A real experiment has a hypothesis, a specific thing you’re testing, and a way to know if it worked. “We’re going to send 100 cold emails to operations managers at logistics companies using a pain-based subject line and measure reply rate” is an experiment. “We’re going to try some outreach” is not. One turns an unknown into a known. The other just burns time.

Front-load the signal.

Design your experiment to tell you something fast. If you’re running a free trial, add a credit card requirement upfront so you learn in week one who’s serious instead of waiting 14 days to find out who ghosts you. If you’re doing cold outreach, send enough emails to know if it reached them but not too many emails that you’ve used the whole list and have nobody to go back to.

Update your map.

Every experiment is a coordinate on the Battleship board. Hit or miss, it narrows the search. After each one, ask: what did we learn, and does it change where we aim next? Each answer converts an unknown into a known. That’s how you build toward predictability.

A founder who almost missed this

We sat down with a founder recently who had a product, 33 paying customers, and a 20% free-to-paid conversion rate. Solid numbers.

They came to us with what sounded like a marketing question: “Which of these six channels should I invest in?”

Podcasts, newsletters, LinkedIn, Twitter, cold email, Google Ads. They had a plan for all of them.

We asked one question: “Of your 33 paying customers, what was the means of getting in front of them?”

They paused. Most came from one community they were already embedded in. A group of 2,000 people who each paid $15K to be there. High intent. High density. Easy access.

They were sitting on a gold mine and planning to dig six shallow holes instead.

That community was their one known. Everything else was still unknown. The move was to go deep on the known before spending a dollar on the unknowns.

From predictability to repeatability to scalability

You graduate from go-to-market to marketing when you’ve converted your four critical unknowns into knowns:

Customer. Specific enough to build a list of 50 names.

Problem. Urgent and severe enough that they’re actively seeking a solution.

Value prop. Tested on cold prospects who responded with their wallets.

Channel. A single path you’ve proven converts consistently.

When all four are answered with data, you’ve reached predictability. Now you can start building repeatability. And repeatability is where scalability lives. Scale the channel. Test adjacent ones. Optimize the funnel. Spend marketing dollars on marketing problems.

Until then, you’re playing Battleship. Lob small shots. Let the data update your map. Convert unknowns into knowns, one experiment at a time. And stop spending like the board is visible when you’re still finding the ships.

Until next week,

Cam

Leave a comment

Hey friends 👋

You’ve done the work by talking to dozens of potential users. You’ve filled up a spreadsheet with enthusiastic quotes: “I’d definitely use this” or “I’d pay for that.” You have translated that onto your pitch deck slide titled “Validation or Traction”. So you built it.

Then the moment you have been waiting for: the BIG launch… And almost no one signs up.

You tried hard. You measured the wrong thing. You asked the right people the right questions and listened carefully, but you made a mistake that puts more startups in the startup cemetery than any other:

You confused interest for intent.

Everyone who said they’d use your product meant it — in the moment. But they were projecting a future version of themselves that they are not likely to realize, at least currently. This version, for example, would finally get organized, finally fix that workflow, finally do the thing they know they should do. But that future self doesn’t exist, and building for a fictional customer is expensive and can cost you your startup.

It’s called the Say-Do Gap. It’s the distance between what people say they’ll do and what they’ll actually do. And for founders, it’s the difference between traction and the trough of sorrows.

Let’s dive deep 👇

The Say-Do Gap is actually a feature.

Decades of behavioral research confirm that people are genuinely bad at predicting their own future actions. We overestimate our future motivation, underestimate friction, and consistently fail to account for the dozen competing priorities that will crowd out any new behavior.

When someone tells you “I’d definitely buy that,” they aren’t lying to you. They are doing something worse which is that they are being sincere about a hypothetical version of themselves. And hypothetical customers don’t pay.

The problem compounds because founders want to believe that every “yes” is validation. Every enthusiastic response gets added to the tally. But you’re not counting customers — or even potential customers. You are instead counting compliments and burning cash on product development with no revenue to show for it.

The progress of systematically acquiring evidence can take the form of the Ladder of Evidence. At the bottom of the ladder or weaker forms of validation. These are signals around the problem being urgent and severe whereas when you move up the ladder we are seeing true intent not just interest.

So how do we address human behavior and distinguish between interest versus intent?

Close the gap with The 4 Asks: Time, Effort, Access, Money

If words aren’t reliable in measuring intent then… what is? Action. Specifically, actions that cost something.

The TEAM framework gives you four currencies to test intent. Each one asks the customer to put something real on the table and move from interest to intent.

T - Time

Will they schedule a follow-up call? Will they commit 60 minutes to a prototype walkthrough next week? Will they show up?

Time is the first gate to see if there is intent. If someone won’t give you 60 minutes of their calendar, they’re not giving you their credit card. This signals the problem is not big enough nor urgent enough for them to be a customer.

E - Effort

Will they fill out a detailed onboarding survey? Will they make the necessary data integrations required to get value from your offering? Will they dig up data from their own systems to help you understand their workflow?

Effort creates friction and this friction filters out the casually curious with those that have true intent.

A- Access

Will they make an introduction to the boss that signs the check? Will they refer you to others like them that have “the problem”?

By asking for access you are testing their willingness to spend social capital. If they aren’t willing to part with social capital are they really going to be willing to spend money.

M - Money

The ultimate filter. Will they put down a deposit? Pre-order? Letter of Intent (LOI) with terms outlining price/quantity? Pay for early access even if the product isn’t finished?

Money doesn’t lie. A $50 commitment from 10 people tells you more than “I’d pay $200” from 100 people.

Each TEAM ask moves you up the Ladder of Evidence. Each one supports you in crossing the conviction chasm of the Say-Do Gap. But don’t stop at Time and call it validation. Work your way up the Ladder of Evidence to Money.

Investors are allergic to “interest.”

Investors see through “we have interest” startup theater. When you tell them “50 people said they’d buy,” they’re already discounting it to zero and asking themselves what they are still doing in the room. When you tell them “12 people put down a $100 deposit before we built anything,” that’s a different conversation.

The intent you gather from the 4 Asks: TEAM become your evidence and are much stronger than quotes of interest (even if you have a large amount of them). They show you understand the difference between enthusiasm and demand. They see that you are a founder building on validation not vibes. They show you’re building for real behavior, not hypothetical preference. They show you’re the kind of founder who doesn’t need to learn expensive lessons twice.

The Say-Do Gap doesn’t get solved once. You apply it to every conversation. Every validation conversation should end with a TEAM ask. Our goal is to measure intent not interest. Every positive signal should be tested with a cost. So ask them to pay in one for forms of Time, Effort, Access, or Money.

At the end of the day, the path to “no” is more valuable than a pile of fake yeses. Every person who won’t give you their time is telling you something useful. Every person who won’t give you their money is clarifying who your customer isn’t. That negative space is a gift. It shows you where not to build, where not to spend, and who not to chase.

A quicker path to no is a faster path to the right yes.

So don’t bet the farm on “interest.” Talk is cheap. Commitment costs something. The gap between them is where your validation lives or dies.

Close the gap. Ask using TEAM. Gather intent versus interest.

Until next week,

Cam

Every Monday in The Pivot, we share one mistake we’re seeing founders make, and the quick redirect that makes all the difference — in just 250 words.

Here’s this week’s:

The antipattern: describing your product, not the job it does.

The demo went well. She said it sounded useful.

But she didn’t buy.

Founders assume wrong timing, wrong price, wrong contact. It’s usually simpler: the pitch describes the feature and skips the job it does for them.

“Inventory tracking” is what your product does. “Protect a buyer relationship I spent 20 years building” is what your customer is paying for. Prospects don’t feel urgency for features — they feel urgency for outcomes.

The fix: start from the outcome and work backward.

Apply the “so that / but why?” chain to your own value prop.

Inventory tracking → so that I know what I can sell → so that I don’t lose a sale → but why does that matter? I protect a relationship I’ve spent 20 years building.

Stop at the layer that hurts. That’s your pitch.

The tool: “so that / but why?” chain

Three questions in sequence: Why do they want that? → So that? → But why does that matter? Start with the feature, end up somewhere emotional. The first question gets you the functional job; the third gets you why they’ll actually pull out a credit card.

Nobody buys a drill bit to make a hole — they want some freaking art on the wall.

Run the chain on your own value prop before your next customer call. Your pitch lives at layer three.

Until next week,

—jdm

PS: The Pivot is a new experiment in short-form, highly actionable content. Hit reply and let us know your thoughts. If you love it, please share it with a friend.

Share

Subscribe now

Every Monday in The Pivot, we share one mistake we’re seeing founders make, and the quick redirect that makes all the difference — in just 250 words.

Here’s this week’s:

The antipattern: running ads before you know who’s buying.

You’ve got the product and the vision; now you need people to know you exist. So you launch a Meta campaign. Maybe $50/day, nothing crazy.

You’re “building awareness.”

Except 84% of the market won’t buy in the early stage, no matter how good your ad is, because they’re not in a triggering moment. You’re spending on the crowd that was never going to convert.

Meanwhile, the 16% who would pay never got a message sharp enough to recognize themselves in it.

The fix: get your first 10 customers manually.

Before you spend a dollar on acquisition, identify a narrow early adopter profile defined by a triggering event. A job title and a demographic won’t due.

“HR professionals” → “HR managers at 50-person companies who just had a toxic culture complaint land on their desk.”

Find them, talk to them, and close them by hand.

Only pour money on a channel once you’ve proven — manually — that the message converts.

The tool: the Early Adopter Pyramid

It’s five tiers: everyone with the problem → people who know they have it → people who are actively looking for a solution → people urgently trying to fix it right now → people who have the resources to adopt a new solution.

That top sliver is your market for the first 12 months.

Here’s the full walkthrough.

Until next week,

—jdm

PS: The Pivot is a new experiment in short-form, highly actionable content. Hit reply and let us know your thoughts. If you love it, please share it with a friend.

Share

Subscribe now

You did the work:

Personas. Jobs-to-be-done. Psychographic profile. A three-paragraph narrative about a day in their life.

You know exactly who your early adopter is, and it’s time to sell!

But… where are they?

• You’ve run ads… no one clicks.

• You’ve cold-called… it’s never the right contact.

• You’ve gone to conferences… they stroll past your booth.

Stop the grind. You need a system for finding customers where they already are — just waiting to give you their money.

It’s called channel hacking.

Let’s dive deep 👇

Let’s start with a less-than-obvious question:

Subscribe now

What the heck’s a channel, anyway?

LinkedIn is not a channel. Neither is TikTok nor Reddit.

They’re platforms. Saying “my customers are on LinkedIn” isn’t much more useful than saying “my customers are on the internet,” because so are 1.2B other professionals.

A channel is much more specific:

• Cold outreach to ops managers at Series A B2B SaaS companies via LinkedIn Sales Navigator

• Organic posts in the #OperationsLeaders hashtag, Monday mornings, with a comment-first reply strategy

• A sponsored slot in the Ops Nation newsletter (12k subscribers, your exact ICP)

• A thread-reply strategy in r/operations targeting active questions about your problem space

• A co-marketing arrangement with a consultant who already serves your customers

This reframe matters because it’s what makes the next step possible: actually getting in front of them.

And let’s talk about how.

Four steps to finding any customer

Channel hacking is a framework we developed at the Traction Lab to find anybody you might want to get in front of, and it’s dead simple.

Step 1 — Ideation

List every channel where your early adopter might plausibly be found.

Every single one.

Don’t filter while you’re generating. This step is quantity before quality. Not “would this work?” Not “is this realistic?” Just: could they be here?

Communities. Subreddits. Newsletters. Conferences. Podcasts. Slack groups. LinkedIn niches. Cold email. Paid social. Organic social. Influencer partnerships. Co-marketing arrangements. Industry events. Trade associations. Job boards. Even Craigslist.

Go wide.

Brainstorming is not the time to be critical — or even realistic.

Target 15–30 channels minimum. Most founders hit five and stop; they’ve covered the obvious ones and are starting to repeat themselves. That’s the groan zone — push past it.

The channels past ten are usually the most interesting, because nobody else thought of them either.

Step 2 — Rank

Now score each channel on two factors:

• Customer density — how many of your target customers are actually there?

• Ease of access — how hard is it to get in front of them? Time, effort, money, etc.

These are prior probabilities. As much as possible, base them on evidence. If you have no evidence, on reasonable inference.

Then plot every channel on a 2×2 grid.

Each channel will land in one of four quadrants:

• Gold mine — high density, easy access

• Moonshot — high density, hard access

• Quick win — low density, easy access

• Questionable — low density, hard access

Step 3 — Decide

Work the gold mine first.

If you’re lucky enough to have multiple gold mines, pick the one with the highest customers-per-unit-of-effort and start there.

One important note: if you map all your channels and every quadrant looks bad — nothing dense, nothing accessible — that’s not a framework failure.

That’s a signal. And a common one!

Either your research is incomplete, or your customer definition is wrong. Something upstream is broken. Go back and revisit who you’ve identified as your early adopter before you keep going.

Don’t skip past this check! A bad map means you’re solving the wrong problem.

Step 4 — Experiment

Your highest-ranked channel gets a test.

But only a small one.

Do not pour real budget into a channel before you’ve run a single experiment. Do not block three months of calendar time for outreach on a channel you’ve never tried.

Not yet.

What “small” means depends on the channel — one week of outreach, one post, one $50 ad spend, one cold email sequence to 20 people.

The goal isn’t to win on that channel. The goal is to find out whether your ranking was right before you commit.

I’ve written about experimentation at length — what a valid test looks like, how to set one up so the data is actually interpretable, and how to avoid celebrating noise as signal.

Go read those if you haven’t.

Short version: the experiment tells you whether the channel is what you thought it was.

Then double down or move to the next one on the list.

What this looks like in practice

Airbnb was trying to tackle demand-side acquisition.

Getting hosts to list their space — the supply side — was manageable. You could reach homeowners through direct outreach, referral programs, and local community events.

Distributed, but findable.

Short-term renters were much harder. Tens of millions of people who needed a place to stay in a city they didn’t live in. And it’s transient!

How do you find them before they’ve decided where to book?

The key insight: they were already with the competitor.

Craigslist.

Craigslist had the density. Millions of people were actively searching for short-term housing in every major market every day.

High density. Clear as day once you looked.

So they built an API integration that automatically cross-posted Airbnb listings to Craigslist. Renters found the listings, clicked through to Airbnb, and booked. The demand base started building.

And when Airbnb no longer needed the integration, they shut it down.

This is what Step 3 actually means. Craigslist was a gold mine — massive density, relatively easy access.

Most founders who can’t find customers aren’t bad at selling.

They just picked two channels and crossed their fingers.

Channel hacking changes the question. Instead of, “Why can’t I get anyone on the phone?”, ask: “Where is the best place to get in front of customers?” That’s a solvable problem.

Map it. Rank it. Choose one. Test it.

Your customers are somewhere. Go find out where.

Until next week,

—jdm

Share

Subscribe now

Every Monday in The Pivot, we share one mistake we’re seeing founders make, and the quick redirect that makes all the difference.

Subscribe now

Here’s this week’s:

The antipattern: investor feedback as a product directive.

An investor tells you, “Show us stronger retention,” and you treat it as signal.

You spend two months building cohort dashboards, overhauling onboarding, and redesigning the activation flow.

And… she passes again.

Because she wasn’t interested — at least not yet.

This fund only leads at $80K+ MRR, and you just aren’t there yet. Her comment wasn’t a real objection. It was a polite proxy for “you’re not our stage yet.”

You burned two months of runway solving the wrong problem, because you read their “no” as “yes, if”.

The fix: figure out what they’re actually telling you.

Every investor comment lives somewhere in a stack: thesis fit, business model viability, communication clarity, or deck polish.

Most founders hear Layer 3 or 4 feedback (how you said it) when the actual problem is Layer 1 or 2 (what you actually are).

What they said: “I didn’t understand.”

What you heard: “You didn’t explain it well.”

What they meant: “Your business doesn’t make sense.”

The tool: Investor Feedback Pyramid

The Investor Feedback Pyramid maps feedback into those four layers. Before you take action, use it to figure out where investor feedback is actually pointing.

And don’t waste two months’ runway chasing a mirage.

Until next week,

—jdm

PS: The Pivot is a new experiment in short-form, highly actionable content. Hit reply and let us know your thoughts. If you love it, please share it with a friend.

Share

Subscribe now

Every Monday in The Pivot, we share one mistake we’re seeing founders make, and the quick redirect that makes all the difference — in just 250 words.

Subscribe now

Here’s this week’s:

The antipattern: every founder has the same moat.

The investor asks: “What stops [large incumbent] from just building this?”

You say: “We have deep domain expertise and strong customer relationships.”

So does every other vertical SaaS founder in the room. It’s the default answer, and it sounds less like a moat and more like a vibe.

The pitch stalls, you know it’s not landing, but you give the same answer next pitch anyway.

The real question underneath — are you building a startup or a feature? — never gets answered.

The fix: make the moat specific or admit it doesn’t exist yet.

Be detailed.

Write out structurally why the incumbent can’t or won’t build this. Not “expertise” — what does the build actually cost them? What’s their time to market? What’s their incentive to enter?

If your moat is customer relationships: how many, how deep, what’s the switching cost, and why can’t a well-funded competitor replicate that in 18 months?

If you can’t answer those questions, don’t paper over it. Be transparent.

The tool: the 6 differentiators

Your job is to make a credible case, typically based on one or more of the six key differentiators: network, scale, scope, integrations, engagement, and experience.

But remember: this is one of the eight things investors look for. Don’t skip it, and don’t skimp on detail.

Until next week,

—jdm

PS: The Pivot is a new experiment in short-form, highly actionable content. Hit reply and let us know your thoughts. If you love it, please share it with a friend.

Share

Subscribe now

Every Monday in The Pivot, we share one mistake we’re seeing founders make, and the quick redirect that makes all the difference — in just 250 words.

Subscribe now

Here’s this week’s:

The antipattern: reading investor enthusiasm as investment intent.

You crushed the meeting.

Forty-five minutes of sharp questions. “We love the team.” “We’re really excited about this space.” You text your co-founder on the way to the car.

Then comes the email: “We’re going to pass for now — we’d love to stay in touch.”

What the deuce?!

The investor didn’t feign interest. But interesting and fundable are completely different things — and investors have every incentive to keep the door open. Optionality costs them nothing. A hard pass closes a future option.

You walked out measuring the temperature of the room. You should’ve been diagnosing blockers.

The fix: ask the question they’re hoping you won’t.

After any meeting with positive energy, follow up with one direct question: “Based on what you’ve seen, what would need to be true for you to invest?”

Most investors will answer honestly when asked directly. What you hear back tells you whether you’re dealing with a real timing issue, a thesis mismatch dressed up as encouragement, or a stage problem they’re too polite to say out loud.

Soft feedback is data. But only if you decode it.

The tool: Investor Feedback Pyramid

Map the feedback you’re getting — “more traction,” “come back in six months,” “we love the space” — against the Investor Feedback Pyramid to diagnose what’s actually blocking the check.

The Pyramid is part of the Traction Lab toolkit. If you’re ready to science the shit out of your startup, join our Venture School.

Until next week,

—jdm

PS: The Pivot is a new experiment in short-form, highly actionable content. Hit reply and let us know your thoughts. If you love it, please share it with a friend.

Share

Subscribe now

Every Monday in The Pivot, we share one mistake we’re seeing founders make, and the quick redirect that makes all the difference - in just 250 words.

Here’s this week’s:

The antipattern: confusing “I have revenue” with “I have a sales motion.”

$19K MRR from seven customers. Strong retention, no churn. The deck writes itself.

Except four came from a former colleague. Two through an accelerator intro. One from a LinkedIn DM to a friend-of-a-friend. No cold closes. No documented process. And only three warm leads left.

That’s not a sales motion. That’s a personal network with a countdown timer.

But the revenue is real enough to mask the problem. So you raise money for sales reps, hand them a process that doesn’t exist, and watch the pipeline dry up right as runway pressure kicks in… and you fold.

The fix: map every customer to their source before you raise.

Before you scale, ask: how did your customers actually find you?

If every answer involves someone you already knew — stop. You don’t have a sales motion yet. You’ve tested the product, but not the go-to-market strategy. Test a repeatable acquisition hypothesis (specific channel, specific ICP, specific outreach) on the next 5–10 people who don’t know your name.

Only raise to accelerate something you can already do without calling in favors.

The tool: customer acquisition source audit.

Build a simple table — name, source, warm or cold, who made first contact. Takes 20 minutes. And you’ll see what you’ve been avoiding.

If you can’t describe your ICP without naming a personal contact, the Early Adopter Pyramid is a good place to start.

Until next week,

-jdm

PS: The Pivot is a new experiment in short-form, highly actionable content. Hit reply and let us know your thoughts. If you love it, please share it with a friend.

Share

Subscribe now

Every Monday in The Pivot, we share one mistake we’re seeing founders make, and the quick redirect that makes all the difference — in just 250 words.

Here’s this week’s:

The antipattern: sizing your raise around runway, not milestones.

Fundraising is brutal — so the temptation to just do it once and be done makes total sense: lock in three years of runway, and never think about it again.

Founders pitch this as a feature. Investors love the confidence.

Except the math doesn’t work. You:

• Gave away more equity at a lower valuation.

• Committed to a milestone sized for the capital, not your actual evidence.

• Will raise again anyway if reality drifts (and it will).

Except… now you’ve burned runway, missed a milestone, and have less equity.

The fix: raise for the next proof point.

Size your round to one specific, measurable milestone: the exact thing you need to prove before the next raise.

Then model it out — two smaller raises at better valuations vs. one big raise at an earlier-stage one. Run the dilution numbers. The math almost always favors milestone-based raises.

Reframe the next raise as a reward, not a chore.

You hit the proof point; now you come back with leverage.

The tool: dilution modeling

Before you take the big round, build a simple two-path model: Path A (raise big now), Path B (raise lean, hit milestone, raise again). Compare the remaining equity in each exit scenario. Most founders who do this exercise take the smaller check.

It takes 20 minutes with a tool like Pulley.

Until next week,

—jdm

PS: The Pivot is a new experiment in short-form, highly actionable content. Hit reply and let us know your thoughts. If you love it, please share it with a friend.

Share

Subscribe now

Learn more →

Hey friends 👋

Every Monday in The Pivot, we share one anti-pattern we’re seeing from founders in the Traction Lab ecosystem, and the quick redirect that makes all the difference—in just 250 words.

Here’s this week’s:

The antipattern: Pitching to VCs pre-traction.

Founders constantly get rejected by VCs who “want to see more traction”, when the real problem is that they shouldn’t be pitching their pre-traction, pre-revenue startup to VC firms in the first place.

It’s like trying to sell a Pinto to someone shopping for a Ferrari.

VCs at the seed and Series A stages just aren’t interested in your stage of company—they’re looking for different metrics, different milestones, different scale, and a lot more evidence.

So you waste months getting “advice” misaligned with where you actually are, then burn credibility by coming back too early.

The fix: Pitch to the right investors.

In other words: match your fundraising outreach to your actual stage.

If you’re pre-revenue and need $50K for experimentation, VCs are not your customer. Target angels who write smaller checks. They’re not looking for high-conviction go-to-market motion. They’re looking for high-conviction founders.

But VCs want retention curves, payback periods, and growth rates you don’t have yet. The advice they give you (“you sound underfunded,” “come back with more traction”) is fundamentally misaligned to where you actually are.

Don’t burn time on the wrong investors.

The tool: The Investment Readiness Scorecard

Set expectations with yourself by mapping your current state of evidence across the 8 Ts of Fundability to our Investment Readiness Scorecard (click to embiggen):

Until next week,

—jdm

PS: The Pivot is a new experiment in short-form, highly actionable content. Hit reply and let us know your thoughts. If you love it, please share it with a friend.

Share

Subscribe now

You’ve been building for nine months. Late nights. Sacrifice.

Launch day finally arrives. Celebratory emojis drop in Slack.

And then… crickets.

No signups. No interest. Just confused silence from your team and polite “congrats!” from friends (who definitely didn’t click through).

You sit there staring at your analytics dashboard—the one you spent three days perfecting—watching the flatline as somber music plays in the background.

And all because you assumed… literally everything.

✅ The customer exists.
✅ They have this problem.
✅ They’re on this channel.
✅ This messaging will resonate.
✅ They’ll sign up.
✅ They’ll pay.
✅ They’ll stay.
✅ They’ll refer.

You built a house of cards and built a foundation on assumptions you never tested.

Let’s dive deep 👇

Subscribe now

Let’s take a moment to talk about Occam’s Razor.

Most people think it means the simplest explanation is correct. But it actually means the explanation with the fewest assumptions is where you start.

Let’s say your car won’t start.

You could assume you have a dead battery. That assumes only that batteries die with normal wear.

But maybe it’s an evil demon. You only need to assume demons exist, they’re malicious, this one targeted you specifically, it followed you to your car, it knows how ignition systems work, it has the power to prevent electrical flow, it chose this exact moment to strike… and I’ll stop there.

The dead battery isn’t “simpler” because demons are complicated. It’s better because it requires fewer unproven premises. Each assumption is a place where your reasoning could be wrong.

This isn’t about complexity. It’s about the burden of proof.

Why does this matter for startups?

You’re betting your life on future events you can’t prove.

Every assumption you stack up is another point at which your entire strategy can break. And unlike evil demons, startup assumptions aren’t as obviously ridiculous.

Usually 😏

But reasonable assumptions seem… well, reasonable.

And that’s what makes them dangerous.

The assumption stack

Every startup model is a towering stack of unvalidated assumptions disguised as a strategy.

When you casually say “we’ll get customers”, here’s what I hear:

1. Customer identification: Small business owners need this.

2. Problem severity: This problem is urgent enough to pay for.

3. Channel access: They’re all on Instagram.

4. Attention capture: Our ads will make them stop scrolling.

5. Message resonance: This value proposition will resonate.

6. Action threshold: They’ll click through to our landing page.

7. Solution validation: Our product solves their problem.

8. Onboarding success: They’ll figure out how to use it.

9. Payment willingness: They’ll convert to paid.

10. Retention: They’ll keep paying month after month.

11. Referral: They’ll tell their friends.

That’s 11 major assumptions. 🤯

And each has sub-assumptions underneath.

Let’s math this a little… if each assumption has an 80% chance of being correct (which is wildly optimistic), your odds of all of them being right simultaneously are only 8.6% ‼️

This is why “build first, sell later” is Russian roulette with 10 chambers loaded.

Worse still? They stack.

Each of those assumptions forms a dependency chain.

You can’t have retention before you have payment. You can’t have payment before you have activation. You can’t have activation before you have acquisition. You can’t have acquisition before you validate the problem exists.

So if you’re wrong about an early assumption, you’re wrong about all of them.

But this is good news!

Just work backward.

Start with your full vision: the complete product, the growth engine humming, customers paying and staying, referrals—all of it.

Now work backward, removing one assumption at a time, until you arrive at a point where you’re not making assumptions anymore. Then test the next thing.

Here’s how it works:

Full Product → Wizard of Oz

Remove the assumption that you need software to deliver value.

If you can’t make it work manually, software won’t save you. Automation doesn’t fix a broken value proposition—it just scales it faster.

Example: Before building automation, do the work yourself. If you’re building scheduling software, use Google Calendar and your own time. If you can’t deliver the outcome when you’re doing everything by hand, writing code won’t magically create value.

Wizard of Oz → Concierge

Remove the assumption that it has to feel like software.

If they won’t pay for a solution custom-tailored to their exact needs, they definitely won’t pay for self-service SaaS.

Example: DocSend started with Dropbox plus Google Analytics. Manually tracked who opened what. Sent individual emails with analytics. Charged money. Once people paid for that clunky manual version, they knew the software version would sell.

Concierge → Fake Door Test

Remove the assumptions that you need to deliver the actual solution at all.

Will they commit to buying it? Landing page, pricing, and a “Start Trial” button that goes to a waitlist. You just validated willingness to pay without building anything.

The button click is the commitment. The waitlist is where you actually talk to them.

If they come, you will build it.

Fake Door → Landing Page Only

Remove the assumption that you need signup functionality.

Does the value proposition even resonate? Run ads. Measure click-through. Measure time on the page. Read the scroll depth. Check the heatmaps.

Validate messaging with zero code.

If nobody clicks the ad, your targeting or hook is wrong. If they click but bounce in three seconds, your value prop doesn’t land. If they read the whole page but don’t click the fake button, your offer isn’t compelling.

Each failure teaches you something. Each lesson costs $200 in ad spend instead of six months of engineering time.

Landing Page → Customer Conversations

Remove the assumption that you know how to articulate the value.

Do they even have this problem? The only real starting point.

If you can’t get 10 people to say, “Yes, I have that problem, and it costs me real money,” then everything else is premature.

Not “that’s interesting.” Not “I could see that being useful.”

Actual pain. Quantifiable cost. The current terrible solution they hate.

Each step backward makes failure cheaper.

Building the full product first means testing all assumptions simultaneously, maximizing risk.

Working backward means testing one assumption at a time to minimize risk.

Share

Don’t start with easy assumptions.

Most founders test the easy assumptions and avoid the make-or-break ones.

The assumption that kills most startups is that someone will pay you money to solve this problem.

Not “Can we build it?” (feasibility assumption—usually yes)

Not “Can we get funded?” (pitch assumption—not even interesting)

The only assumption that matters is whether a customer actually pays for this.

This is why the reverse sequence is so powerful. It forces you to confront that assumption before you’ve invested nine months and $100K.

A return to Occam’s Razor.

Your startup isn’t a house of cards because your idea is bad.

It’s a house of cards because you stacked 11 assumptions on top of each other and called it a plan.

The fix isn’t to have better assumptions. It’s to stop making so many at once.

Occam’s Razor for startups:

• Map every assumption in your go-to-market

• Identify the dependency sequence

• Work backward until you hit one assumption

• Test that assumption as cheaply as possible

• Only add the next assumption once the previous is validated

This feels slower. It’s actually faster—because you don’t waste nine months building something nobody wants.

Slow is smooth, and smooth is fast.

The hardest part of this methodology is that it forces you to confront reality before you’re emotionally ready.

That’s the point.

Most founders would rather build for six months in comfortable ignorance than talk to 10 customers in uncomfortable truth.

Don’t be that guy.

Until next week,

—jdm

Share

Subscribe now

Every Monday in The Pivot, we share one anti-pattern we’re seeing from founders in the Traction Lab ecosystem, and the quick redirect that makes all the difference—in just 250 words.

Subscribe now

Here’s this week’s:

The anti-pattern: hiring your way out of discomfort.

Instead of building conviction through direct experience, you hire an employee to the dirty work.

We’re seeing founders say “sales isn’t my strength” and immediately hire a head of sales, or “I’m not technical” so they bring on engineers to handle all product decisions while they “focus on strategy and fundraising”…whatever that means.

The pattern is the same every time: something feels scary or outside their comfort zone, they delegate it to someone else before they’ve done it themselves enough times to know what “good” looks like, and it burns up like the Hindenburg.

They’ve confused “not naturally good at” with “shouldn’t learn.”

The fix: founder-only → founder-led → founder-less.

Do the scary thing yourself until you have a repeatable, documented process—then and only then can you delegate it.

Close your first 20-40 sales yourself. Build your first MVP or sit next to your developer for every decision. Handle customer support until you can write the playbook.

You’re not hiring a salesperson to take sales off your plate—you’re hiring them to scale a motion you’ve already proven works.

If you can’t describe exactly what success looks like and how to get there, you’re not ready to delegate it.

Start doing everything yourselves (founder only), and then move to light delegation (founder-led), and then to full delegation (founder-less).

The Tool: the 40-Before-Delegation rule.

Don’t hire someone to own a critical function (sales, product, customer success) until you’ve personally executed it successfully at least 40 times and can document the exact process.

If you can’t write the job description with specific success metrics and a playbook, you’re too early.

Never delegate what you can’t repeat.

Until next week,

—jdm

PS: The Pivot is a new experiment in short-form, highly actionable content. Hit reply and let us know your thoughts. If you love it, please share it with a friend.

Share