Why GTM concepts fail

Every founder has intuition about their market. Every consultant has a playbook that worked at their last company. Every industry has dogma about how things are supposed to work. All of these fail regularly, and the failure is almost always attributed to bad execution. But the real problem is something deeper: confidence masquerading as knowledge.

The stakes are high. A founder who confuses confident intuition with validated knowledge burns months and capital. A consultant who applies yesterday’s playbook to today’s market creates cascading failures. An investor who preaches universal dogma funds the wrong motions. The cost is not just capital. It is time you will never recover.

Founder intuition: plausible but wrong

Founders are usually the ones closest to their market. They talk to customers, they know the product, they understand the vision. But founder intuition about GTM—how the market will discover you, what will convince them to buy, who the ICP is—is often confidently wrong.

The confabulation problem. After you have acquired a few customers, you naturally think backwards to figure out why they bought. “They bought because they found us in Product Hunt.” “They bought because they already knew about the category.” “They bought because our product was so obviously better.” These stories feel true because you have remembered them so many times. But they are often confabulations. You have picked the salient facts that fit a narrative, not the causal facts that explain the decision.

Consider a SaaS founder who acquired their first five customers through a cold email campaign and concluded: “Cold email is our motion.” They hired two SDRs, scaled the motion, and found that conversion rates collapsed at 100 outbound emails per day. The real reason the first five bought was not cold email. It was that they knew the founder already, had heard about the product in other conversations, or had a triggering event (just hired a new person, budget cycle, outgrew the old tool) that aligned with the email. The founder had picked the salient fact (email sent, customer acquired) and ignored the unmeasured facts (relationship, reputation, trigger event).

A founder’s intuition about “why customers buy” is almost always a post-hoc narrative, not a causal mechanism.

The selection bias problem. You have probably talked to your first 10 customers extensively. You know why they bought. You assume these are representative of your market. But they are not. They are usually the easiest customers to sell to: people who already knew about the problem, people who were actively looking for a solution, people who have the budget and authority to buy quickly. Your market is much larger and much more diverse. The median prospect is nothing like your first 10.

A B2B founder with a product for compliance teams built their motion on their first 10 customers: all Fortune 500 companies, all referred by a VC who knew the CISO, all high-budget, all consensus buyers. The founder concluded: “Our ICP is large enterprises with decentralized IT. We will build a sales-led motion with account-based marketing.” They hired three enterprise AEs, spent $300k on ABM, and closed zero additional deals. The first 10 were not representative; they were champions with relationships and urgency. The typical compliance buyer at a Fortune 500 does not move that fast. The founder had built a motion for the easy 1% (referred relationships) and failed on the hard 99% (cold outreach).

A founder who takes their first 10 customers as representative is building a motion designed to work on the easy 1% and fail on the hard 99%.

The narrative bias problem. Founders tell stories. The story is compelling, coherent, and psychologically satisfying. “We are the only product that does X. Customers desperately need X. Therefore, we will win.” This narrative is seductive because it is simple and clear. But markets do not work on narrative; they work on incentives, switching costs, distribution, and timing. A customer does not buy because your product is unique; they buy because the cost of switching to you is lower than the cost of staying with the status quo, or because the cost of the problem you solve is higher than the price of your solution, or because a peer recommended you.

A dev-tool founder with a build-optimization product believed their narrative: “Developers waste 20% of their time on slow builds. We can save them 10 hours per week. They will beg for our product.” They launched, positioned aggressively around developer efficiency, and found that even when developers loved the product and saw 30% faster builds, they did not upgrade or pay. Why? Because the savings were not worth the switching cost: learning a new tool, migrating pipelines, supporting a new vendor. The product was unique. Developers desperately needed it. But the narrative had ignored distribution control: build tools are chosen by platform teams, not individual developers, and platform teams do not prioritize developer happiness over organizational risk. The founder had built the motion for the narrative, not the market.

A founder’s narrative about why they will win is almost always divorced from how customers actually make decisions.

Consultancy frameworks: context collapse

A successful consultant has a playbook. They applied it at Company A and saw results. They apply the same playbook at Company B and get nothing. Why?

Context collapse. The consultant is transferring a tactic or strategy from one company to another without realizing that the context has completely changed. The consultant saw the tactic (e.g., repositioning) and the result (higher sales) and inferred a causal mechanism (repositioning causes higher sales). But the causal mechanism was contextual.

A GTM consultant helped an enterprise data company reposition from “performance” (their strength) to “cost savings” (their market’s priority), and sales increased 40%. They repeated the same repositioning strategy at another data company six months later. Nothing. Why the difference? At the first company, the sales team was weak and had been pitching features instead of outcomes. The repositioning was a sales-enablement fix disguised as a positioning fix. At the second company, the sales team was excellent; the real problem was that they were targeting finance directors instead of ops directors. The finance directors cared about cost but could not move budgets. The ops directors cared about performance but had money to spend. The motion was broken, not the positioning. The consultant saw repositioning → sales increase and inferred causation, ignoring the completely different root cause at the second company.

The expert bias problem. A consultant succeeded with playbook X at three companies, so they believe in playbook X. They apply it to a fourth company, and it fails. Rather than questioning the playbook, they assume the company is executing it poorly. They push harder, require more discipline, ask for more budget. The playbook still fails because the playbook was never going to work in that context.

A sales-efficiency consultant had helped three companies implement an aggressive outbound motion with tight cadence, consistent follow-up, and strict pipeline discipline. All three saw 40% improvements in deal velocity. At a fourth company, the consultant applied the same motion and results were flat. The company had hired better salespeople, implemented better CRM discipline, and tightened the cadence. The consultant blamed execution, recommended more rigor, and asked for another six months. Nothing changed. The real issue: the fourth company’s ICP was early-stage startups with chaos-driven decision-making. Tight cadence and rigid follow-up felt invasive to founders who made decisions ad-hoc. A different motion (relationship-based, long gaps between touches, founder-to-founder sales) would have worked. But the consultant had learned to see tight cadence as the lever and could not imagine a motion without it.

The overfitting problem. A consultant’s playbook is built by observing success and assuming those successes were caused by the playbook, not by other factors. They run a paid search campaign at one company and growth accelerates 100%. They conclude: “Paid search is the lever.” But that company also just launched a major feature, got coverage in a trade publication, and hired a brilliant head of sales. The paid search might have contributed 10% of the growth.

A demand-gen consultant saw a SMB software company’s sales increase 50% after launching a paid search campaign targeted at a new use case. They concluded: “Paid search to new use cases is the playbook.” They applied it to a second company in a different market. The second company spent $200k on paid search and got flat results. The real difference: the first company had just launched a feature that solved the new use case and created natural product urgency. The paid search worked because demand already existed. At the second company, no new feature had shipped, so paid search was just pushing demand that did not exist. The consultant had seen paid search → growth and inferred causation without noticing the product launch.

Startup dogma: categorical and brittle

The startup industry has dogma. It is usually stated as universal truth.

• “Product-led growth always beats sales-led growth.”
• “Land-and-expand is the highest-LTV model.”
• “Viral products win because distribution is free.”
• “Community is the only defensible moat.”
• “Freemium is the way to acquire users.”

These statements are sometimes true. They are true in some contexts. They are not true in all contexts. But they are often applied as if they are universal laws.

The true-in-context problem. Product-led growth beats sales-led growth in markets where the buyer is individual and the problem is self-evident and the implementation is simple. It fails in markets where the buyer is a committee and the implementation is complex and the outcome is hard to see in a trial. A founder who believes “product-led always wins” will avoid sales-led even when it is the only motion that works.

Slack succeeded with product-led growth because individual engineers could download, install, and evangelize Slack to their team, creating bottom-up adoption that outpaced IT gatekeepers. DataDog, a near-identical company selling to the same persona at the same time, succeeded with sales-led motion because IT operations teams (the actual buyer) do not discover monitoring tools through product trials. They evaluate through RFPs and compliance review. Both companies picked the motion that matched their buyer. One happened to have bottom-up influence; the other had top-down control. A founder who believed “product-led always wins” would have forced DataDog into a product-led motion and failed.

The survivorship bias problem. We see the product-led companies that won (Slack, Figma, Notion). We do not see the product-led companies that failed because they were selling to a market that does not buy product-led. We assume product-led worked because it is how the winners succeeded, not realizing that the winners succeeded partly because they picked markets where product-led could work.

Miro (collaborative whiteboarding) and Lucidchart (diagramming) both built product-led motions targeting designers and architects. Miro succeeded; Lucidchart struggled in its early years and eventually moved to sales-led. The difference was not product quality or motion execution. It was the buyer. Designers discovering Miro organically and pulling it into their teams created momentum. Enterprises buying Lucidchart for IT diagram standardization had no organic momentum. They needed a sales process. The same motion failed or succeeded based on whether the market had a pull dynamic. A founder looking at Miro’s success and copying the motion would have missed this.

The moral loading problem. In startup culture, some motions are coded as “good” (product-led, land-and-expand, community-driven) and others as “bad” (sales-led, traditional enterprise sales, vendor relationships). So founders avoid the “bad” motions even when they are the right motions for the market.

An enterprise security founder spent 18 months building a product-led motion: free tier, self-serve onboarding, freemium conversion model. The product was excellent. Conversion was 1%. The founder believed the motion was right and the execution was weak. They redesigned the product, optimized the aha moment, and saw conversion improve to 1.5%. Still broken. After 18 months and $500k, they hired their first sales rep out of desperation. Within three months, the rep had closed five six-figure deals. The motion was not broken; the motion was wrong for the market. Enterprise security requires compliance review, integration planning, and vendor assessment. No free trial teaches that. But the founder had avoided sales-led motion because startup dogma says sales-led is old-school and enterprise is boring. The market knew it needed sales-led. The founder did not listen.

The epistemology of GTM

What these three failures have in common is confidence that is not grounded in evidence.

A founder’s intuition feels like knowledge but is often narrative. A consultant’s playbook feels like a law but is often a happy accident. Startup dogma feels like truth but is often categorical thinking applied to a contextual world.

The real skill is epistemic humility: the recognition that your model of how a market works is probably wrong or incomplete.

You do not know if product-led will work in your market until you try it and measure it. You do not know if your ICP is right until you talk to 50 prospects and see if the ones who fit your ICP definition are more likely to buy. You do not know if a six-month sales cycle is inevitable until you have tried to shorten it. You are operating on a hypothesis about how a market works, and hypotheses require testing.

Diagnostic: when to trust intuition vs when to test

Some decisions do require trusting intuition, and testing everything is paralysis. The diagnostic is about classifying which is which.

Trust intuition on taste and speed decisions. Pick a product color palette. Write copy. Structure a landing page. These are fine-tuning decisions in a space where your judgment is reasonably good. Speed matters more than certainty.

Test causal claims about the market. You think your ICP is “mid-market SaaS founders.” You think they will discover you “through peer recommendations.” You think they will pay “because you are 30% cheaper than the incumbent.” These are causal claims about how the market works. Test them before building a motion around them.

The distinction: identity vs causal claims. “Our product does X” is an identity claim. You can know this from building the product. “Customers want X” is a causal claim about preference. You must test it. “Customers will discover us through X” is a causal claim about distribution. You must test it. “Customers will buy because of X” is a causal claim about decision-making. You must test it.

A founder who confuses identity claims (I know what my product does) with causal claims (I know why customers will buy it) will build the wrong motion with confidence.

Rule: Test before scaling. If you have acquired fewer than 20 customers, you do not yet have evidence that your motion works. You have proof of concept with a biased sample. Do not scale. Gather evidence.

Rule: Disagree, then measure. If you and your team disagree on a GTM hypothesis (motion, ICP, positioning, pricing), state both views and measure which one is closer to correct. Do not argue. Do not defer to seniority. Measure.

Rule: Separate confidence from evidence. Confidence feels good. It is not evidence. An investor who is confident about product-led growth is not providing evidence. A founder who is confident about their ICP is not providing evidence. Evidence is: 10 cold outbound attempts, 5 responded, 2 became customers. That is evidence. “I think our ICP is X” is not.

How epistemic humility changes behavior

Founders with epistemic humility ask different questions:

• “What does the evidence tell us about who buys?” instead of “I think the ICP is this.”
• “Does this tactic work in our market?” instead of “Stripe/Notion/Figma did this, so it should work.”
• “What do we need to test?” instead of “I am confident about this.”
• “Where might we be wrong?” instead of “This is how the market works.”

Epistemic humility does not mean paralysis. You still have to make decisions and move forward. But you hold the decisions lightly. You gather evidence. You update your model when the evidence contradicts it. You remember that confidence and correctness are different things.

A founder who says “I think product-led will work, but I might be wrong, so let’s test it” is practicing epistemic humility. A founder who says “Product-led is the way; we are just executing poorly” is not. The first will eventually find product-market fit. The second might run out of money still convinced they are right but executing poorly.

Named rules: reusable heuristics for GTM thinking

Rule: The Confabulation Audit. Before betting on a narrative about why customers bought, interview the last five customers and ask: “Walk me through your decision. Who was involved? What was the triggering event? What other options did you consider?” If all five tell the same story, you might have a true pattern. If all five tell different stories, you have confabulation. Your narrative is not the market’s pattern.

Rule: The Median Customer Test. You know your top 10 customers well. Now find 20 prospects in your ICP who have not bought. Interview them. Ask: “Does this product solve a problem for you? How much would you need to change to use it?” If the median prospect answers differently than your top 10, your ICP is selection-biased. Adjust.

Rule: The Context Collapse Check. When adopting a playbook from another company, identify three environmental factors that were different: the sales team maturity, the market timing, the product readiness. Then ask: do we have the same conditions? If not, the playbook will not transfer.

Rule: The Dogma Decomposition. When you hear absolute statements (“product-led always wins,” “land-and-expand is the highest-LTV”), decompose them into contexts. In what markets does this hold? In what markets does it fail? If you cannot name a context where it fails, you are hearing dogma, not insight.

Rule: The Evidence Hierarchy. Rank your confidence in GTM claims: (1) You have run 100 experiments and 80 showed the pattern; (2) You have observed 20 cases and 15 showed the pattern; (3) You have observed 3 cases and all showed the pattern; (4) You talked to 1 person and they agreed; (5) You have a theory about why it should be true. Never act at level 5. Never scale at level 1-3 without level 2+ evidence.

The cost of confidence

The cost of misplaced confidence in GTM is high: time, money, and opportunity cost. You spend months executing a motion that will not work because you were confident about something you should have tested. You hire a sales team when you should have built a product-led motion. You position your product toward an ICP that does not actually exist. You build a land-and-expand motion when your actual customers want a land-once-and-deliver motion.

A early-stage founder with $1M in funding burned $400k in six months pursuing an ICP and motion based on conviction and three successful conversations. They did not measure whether the motion worked on the median prospect. When cash ran low, they finally talked to 30 prospects and realized the ICP was wrong. The sales-led motion they had built did not fit. By the time they knew, they had six months of runway left. A competitor who had tested before scaling found the right motion in month 3 and had a 12-month head start with a funded team.

The companies that survive GTM are not the ones with the best intuition or the best consulting or the most startup dogma. They are the ones who held their hypotheses lightly, tested them honestly, and updated quickly when the evidence contradicted them.

This is the first and most important lesson of GTM: your initial model of your market is probably wrong. The question is whether you will discover it is wrong before you run out of resources.

What comes next: from humility to understanding

Epistemic humility gets you to curiosity. It gets you to ask questions instead of assert answers. But curiosity is not enough to build a GTM. You still need to understand the market you are selling to.

The next level is moving from the epistemology of GTM (how you know) to the structure of GTM (what you need to know). You need to see the market itself: who buys, what drives their decisions, where power concentrates, and where the structural openings are. You need to understand the actual jobs customers are trying to accomplish and where your product fits into their workflow.

That is where the next cluster begins.