The Founder Challenges Checklist: Common Mistakes in Years 1-3
A diagnostic checklist for founders in years 1-3 — 42 checks across product, market, team, revenue, and operations with a scoring framework and recovery playbook.
Whether you're looking for an angel investor, a growth advisor, or just want to connect — I'm always open to great ideas.
Get in TouchAI, startups & growth insights. No spam.
TL;DR: The first three years of building a company are defined less by what you do right and more by how quickly you catch what you are doing wrong. This post is a structured, first-person checklist of the 42 most common mistakes I have made and watched other founders make across product, market, team, sales, and operations. Each module has a scoring system. At the end you get a total score, a priority triage if you checked too many boxes, and a pivot-vs-persist decision framework. Use this as a diagnostic, not a report card.
Most startup mortality data gets presented as a single statistic — "90% of startups fail" — stripped of the timeline that makes that number actionable. When you look at the failure curve over time, a clear pattern emerges. It is not random. It clusters.
| Year | Primary Failure Mode | Underlying Cause |
|---|---|---|
| Year 1 | Premature scaling or running out of runway | Building before validating; no product-market fit signal |
| Year 2 | Team fracture or product drift | Co-founder conflict; scope creep; hiring too fast |
| Year 3 | Revenue plateau or competitive displacement | Failure to find repeatable sales; incumbents respond |
I have been in or adjacent to all three of these failure modes. The Year 1 version nearly killed PitchGround before it found its footing. The Year 2 version showed up in team dynamics I did not manage soon enough. The Year 3 version was a plateau that felt like growth until I looked at the underlying numbers and realized we were running in place.
What I noticed across all of them was that the mistake had usually been made six to twelve months before the consequence became visible. By the time you feel the pain, the root cause is old news. That lag is what makes the first three years so treacherous. You are always reacting to decisions your past self made when they knew less than you do now.
The checklist below is built around that lag. Each item is a mistake that tends to get made silently and discovered loudly.
How to use this checklist: Go through each module honestly. Check the box if the statement is currently true or was true at any point in your first three years. Do not check based on intent — check based on what actually happened. Score each module at the end. Total your score. Then use the triage framework.
Product is where most founders feel most comfortable and, paradoxically, where they make the most consequential mistakes. Technical founders over-build. Non-technical founders under-specify. Both avoid the harder work of finding out whether anyone actually needs what they are building.
I have made eight of these ten mistakes at different points in my career. Some more than once.
[ ] 1. I built the product before doing 20+ customer discovery conversations. Twenty is not a magic number. It is a minimum threshold. Below twenty, you are still in the confirmation bias zone — you find the handful of people who validate your idea and ignore the signal from everyone else. Above twenty, patterns start to emerge that you did not expect and cannot dismiss. If you launched before having twenty substantive, open-ended conversations with potential customers who were not your friends, you built on a hypothesis, not evidence.
[ ] 2. My roadmap is driven by founder intuition rather than a structured feedback loop. Intuition is useful for generating hypotheses. It is not a product management system. If your roadmap is essentially what you and your co-founder think should be built next — without a documented process for collecting, categorizing, and prioritizing user feedback — you are going to build things that feel right and miss things that matter.
[ ] 3. I have added features to compete rather than to solve documented customer problems. This is one of the most expensive mistakes in Year 2. A competitor ships a feature. You feel pressure. You add it to the roadmap. You build it. Your customers barely use it. Meanwhile, the two problems your best customers have been complaining about for six months are still on the backlog. Feature parity is a trap. The only winning move is to solve your customers' problems faster and more completely than anyone else.
[ ] 4. My product has not had a meaningful change in six or more months. Stagnation in an early-stage product is almost always a symptom, not a strategy. Sometimes it means the team is depleted. Sometimes it means there is no clear product direction. Sometimes it means the founder has shifted attention to fundraising or sales and the product has gone quiet. Whatever the cause, if your product has not meaningfully evolved in two quarters, something is wrong.
[ ] 5. I cannot explain our core value proposition in two sentences without using jargon. If you cannot do this, your customers cannot either. And if your customers cannot explain why they use your product to someone else, your word-of-mouth loop is broken before it starts. This is not a marketing problem. It is a product clarity problem that manifests as a marketing problem.
[ ] 6. I have never run a structured usability test with a real user. Watching someone use your product for thirty minutes — without prompting them, without explaining features, without rescuing them when they get confused — is one of the most humbling and productive activities a founder can do. Most founders do it once, if ever. The ones who do it regularly build dramatically better products.
[ ] 7. Our time-to-value is longer than one session. Time-to-value is how long it takes a new user to experience the core benefit of your product for the first time. If that takes more than a single session — or, in consumer products, more than a few minutes — you are losing the majority of users before they ever understand why they should stay. Most activation problems are actually time-to-value problems.
[ ] 8. I have shipped a major feature that zero or near-zero users adopted within 90 days. This is a direct measurement of whether your product development process is working. Every team ships features that underperform occasionally. But if this is a pattern — if you regularly build things that do not get used — your feedback loop is broken somewhere between customer input and shipping.
[ ] 9. We have not deprecated or removed a single feature in the past year. Product debt is as real as technical debt. Features that are rarely used still need to be maintained, documented, and worked around by new features. Founders who cannot delete features are usually afraid of the conversation with the small number of users who depend on them. That fear accumulates into a product that is bloated, slow to navigate, and expensive to maintain.
[ ] 10. I do not know our weekly active user retention rate by cohort. If you are not looking at cohort retention — meaning, of the users who signed up in a given week or month, what percentage are still active 4 weeks later, 8 weeks later, 12 weeks later — you are flying without instruments. Aggregate retention numbers hide the reality. Cohort analysis shows you whether things are getting better or worse over time.
Module 1 score: Count your checks. _____ / 10
Market mistakes are the ones that kill companies quietly. You can have a great product, a talented team, and solid execution — and still fail because you chose the wrong market, mis-timed your entry, or failed to understand who you were actually selling to. Market mistakes feel like product problems or sales problems until you zoom out far enough to see what is really happening.
[ ] 1. I defined my target market as "anyone who could benefit from this." This is the most common market mistake in Year 1 and the one that wastes the most early runway. "Anyone who could benefit" is not a market. It is a category. The discipline of narrowing — picking a specific customer profile, a specific use case, a specific distribution channel — feels like leaving money on the table. It is actually the opposite. The narrower your initial target, the faster you can find product-market fit and the clearer your early messaging becomes.
[ ] 2. I have not written down a specific ICP (Ideal Customer Profile) with at least 5 attributes. Title, company size, industry, pain intensity, and a buying trigger. Those five are the minimum. If your ICP is not written down with that level of specificity, it does not really exist. Decisions about product, pricing, positioning, and hiring all depend on a shared, concrete understanding of who you are building for. Without it, every team member is making up their own version.
[ ] 3. My market sizing was done using top-down TAM math, not bottom-up customer math. "The global CRM market is $80 billion, and if we capture 1% of that..." is not market analysis. It is a fantasy. Bottom-up market sizing asks: how many specific customers exist who match my ICP, what would they plausibly pay, and what is the realistic percentage I could reach in a given time horizon? Those numbers are almost always smaller than the top-down version. They are also almost always closer to reality.
[ ] 4. I have not validated that my target customers have budget authority and willingness to pay. Discovery and interest are not the same as purchase intent. Users will tell you something is interesting. They will join a beta. They will give you feedback. None of that tells you whether they will pay for it, who in their organization controls that budget, what the approval process looks like, or what competing priorities the budget is already committed to. Skipping this validation is why so many companies build things that users love and do not buy.
[ ] 5. I entered a market that is dominated by one or two incumbents without a clear wedge. Competing head-to-head against an entrenched incumbent without a specific, defensible angle of attack is a very slow way to go out of business. The wedge does not have to be technology. It can be a specific vertical they do not serve well, a pricing model they cannot match, a distribution channel they have ignored, or a user experience decision they are too large to make. But you need one. "We are better" is not a wedge.
[ ] 6. I have not spoken to a lost customer or a churned user in the past 90 days. Churned users and lost prospects are your most honest source of market intelligence. They have already made a decision against you — which means they have no incentive to be polite. Most founders avoid these conversations because they are uncomfortable. The founders who do them regularly learn things that no amount of user survey data will surface.
[ ] 7. My category is shrinking or commoditizing and I have not adjusted my positioning. Market conditions change. A category that was growing when you entered may be slowing. A differentiation that was meaningful 18 months ago may have been commoditized by open-source alternatives or well-funded competitors. Positioning is not a one-time exercise. If you have not revisited your core positioning in the past year, you may be fighting for a position that is no longer worth holding.
[ ] 8. I have not identified the top three alternatives my customers consider before choosing us. Your real competition is not always what you think it is. Sometimes it is a spreadsheet. Sometimes it is a process a customer has built internally. Sometimes it is a different category of tool entirely. If you do not know the top three alternatives your best customers evaluated before choosing you — and the top three reasons they chose you over those alternatives — your positioning work is incomplete.
Module 2 score: Count your checks. _____ / 8
Team mistakes have the longest consequence curves of anything on this list. A bad product decision can be reversed in a sprint. A bad market choice can be corrected with a pivot. A bad hire — or a series of bad hires — can take 12 to 18 months to fully resolve, and the damage to culture and momentum can last even longer.
I will be direct about this module: most team mistakes are founder mistakes. The team does what the leadership models. The hiring bar reflects what the founder is willing to tolerate. The culture is the founder's behavior, repeated and amplified.
[ ] 1. I hired for skillset before validating culture fit and execution style. In early-stage companies, how someone works is more important than what they have done. A brilliant engineer who needs lots of structure, long timelines, and clear specifications will underperform in a chaotic 8-person startup, no matter how impressive their resume. A less credentialed person who can operate in ambiguity, take initiative, and communicate clearly when things go sideways will be worth ten times more. Hiring resumes over working styles is a Year 1 mistake that shows up as underperformance, frustration, and eventual churn.
[ ] 2. I have a co-founder and we have never explicitly discussed equity, roles, or exit scenarios. The conversations that feel too early to have are almost always the ones you need to have immediately. Equity splits, decision-making authority, what happens if one co-founder wants to leave, what happens if you get a buyout offer — these need to be written down and agreed upon in the first 90 days. The co-founder relationships that blow up in Year 2 almost always trace back to assumptions that were never made explicit in Year 1. If this item is checked, start with the Cofounder Conflict Resolution 40-question compatibility audit.
[ ] 3. I have kept an underperformer on the team for more than three months after identifying the problem. This is the most common team mistake I see in founders who have strong loyalty instincts. Keeping someone on after you have identified that they are not performing — hoping they will improve, giving them one more chance, not wanting to have a hard conversation — almost always makes things worse. It demoralizes the rest of the team, who can see the underperformance. It delays the backfill. And it usually does not result in the improvement you are hoping for.
[ ] 4. My team has no documented values, operating principles, or decision-making framework. Culture is not a ping-pong table or a Slack emoji reaction. It is the answer to: how do we make decisions when reasonable people disagree? What behavior is rewarded and what behavior is penalized? What do we do when we face a tradeoff between speed and quality? If these questions are answered by whoever is loudest in the room, you do not have a culture — you have a personality contest.
[ ] 5. I have hired from my personal network without doing structured evaluation. Hiring friends, former colleagues, or referrals from trusted sources is efficient. Skipping the evaluation process because you trust the source is not. The same structured bar — work samples, reference checks, scenario-based interviews — should apply to everyone. The referral gets you to the top of the candidate pool. The process determines whether they get an offer.
[ ] 6. I have not had a one-on-one with every direct report in the past two weeks. One-on-ones are not status updates. They are your primary signal for what is actually happening on the team — what is blocking people, what is frustrating them, what they are not telling you in group settings. Founders who skip one-on-ones because they are busy are the same founders who are blindsided by resignations, team conflict, and morale problems that have been building for months.
[ ] 7. I have made a significant hire at the VP or director level before we had product-market fit. Bringing in senior executives before you have found product-market fit is almost always a mistake. Before making any growth hire, run through the 12-signal readiness test to check if the business is ready. VP-level hires are built to scale a motion that is already working. In the pre-PMF phase, what you need is people who can discover and experiment, not people who can optimize and manage. Senior executives who are accustomed to large teams, clear strategy, and defined processes frequently underperform — and become frustrated — in the ambiguity of pre-PMF startups.
[ ] 8. I do not know what my best employee's career goals are for the next two years. Retention of high performers is not primarily a compensation problem. It is an alignment problem. If you do not know where your best people want to be in two years — and cannot show them a credible path to get there inside your company — you will lose them to someone who can. The conversation is simple: ask them directly, listen carefully, and follow up on what you hear.
Module 3 score: Count your checks. _____ / 8
Sales is the function that most technical founders avoid longest and learn the least about until it becomes a crisis. The result is predictable: companies that build genuinely useful products and then cannot figure out how to sell them consistently, scalably, or profitably.
The mistakes in this module are not about closing tactics or negotiation skills. They are about the structural decisions that determine whether your revenue motion is repeatable.
[ ] 1. I do not have a documented sales process with defined stages. If your sales process lives in your head — or varies completely from one deal to the next — you cannot improve it, train someone else on it, or identify where deals are getting stuck. A documented process does not need to be complicated. It needs to define what moves a deal from one stage to the next and what evidence you need to advance it.
[ ] 2. I have not calculated my Customer Acquisition Cost (CAC) and Customer Lifetime Value (LTV) by channel. CAC and LTV are not metrics you calculate once for a pitch deck. They are the core inputs to every growth decision you make. Which channels to invest in. What price point is defensible. Whether you can afford to hire a sales rep. Whether paid acquisition is sustainable. If you are making these decisions without channel-level CAC and LTV data, you are making them on guesses. If you are not sure where to start, the step-by-step CAC calculation guide walks through the methodology with real examples.
[ ] 3. My pricing was set based on gut feel or competitor benchmarking rather than value-based analysis. Pricing is one of the highest-leverage decisions a founder makes and one of the most under-researched. Competitor benchmarking tells you what others charge. It tells you nothing about what your customers would pay, what value they are actually extracting, or what pricing model best aligns with how they experience that value. Most early-stage SaaS companies are priced 20 to 40 percent below where they could be. The SaaS metrics benchmarks for your stage are a useful reference point for calibrating whether your pricing is structurally in range.
[ ] 4. I have not attempted to raise prices in the past 12 months. Pricing is not a set-and-forget decision. As your product matures, as you deliver more value, as your positioning becomes clearer, your prices should reflect that. Founders who are afraid to raise prices — because they fear churn, because they feel guilty, because they do not want the conversation — leave significant revenue on the table and often misread the churn signal when they eventually do raise prices. Most customers are less price-sensitive than you think.
[ ] 5. I do not have a repeatable lead generation system that works without my personal involvement. Founder-led sales is appropriate in Year 1. If you are still the primary lead generation engine in Year 2 or Year 3, you have a dependency problem, not a sales strategy. The goal of early founder-led sales is to figure out what works well enough that you can systematize it, hand it off, and step into a coaching role. If you have not made that transition, your company cannot grow faster than you can personally work.
[ ] 6. My churn rate is above 3% monthly for a B2B SaaS product. Three percent monthly churn compounds to roughly 30% annual churn. That means you need to replace 30% of your revenue every year just to stay flat. At that level, growth is extremely expensive and the underlying problems — whether product, onboarding, customer success, or ICP mismatch — are almost certainly getting worse over time, not better. Churn above that threshold in B2B SaaS is not a sales problem. It is a foundational problem — and understanding the retention vs acquisition tradeoff is critical before deciding which lever to pull first.
[ ] 7. I have not done a detailed win/loss analysis in the past quarter. Win/loss analysis is not asking customers why they chose you. It is systematically documenting the reasons deals close or do not close, across enough deals to see patterns. Which objections come up most often? Which competitors win when? At what deal size does your win rate change? What is different about the deals that move quickly versus the ones that stall? Without this data, your sales process improvement is guesswork.
[ ] 8. I am discounting more than 20% off list price to close deals. Discounting is a short-term tool that creates long-term problems. Customers who got a heavy discount will anchor to that price in renewal conversations. Heavy discounting signals that your list price is not credible. And a pattern of high discounting usually means one of two things: your pricing is too high relative to the value you deliver, or your sales process is not creating enough urgency and value before the pricing conversation. Both are fixable, but not by discounting more.
Module 4 score: Count your checks. _____ / 8
This is the module most founders skip, and it is the one that, left unchecked, makes all the other problems worse. The operational and mental state of the founder is the single variable that affects everything else. A founder who is depleted, unclear, or operating from panic makes worse product decisions, hires worse, sells worse, and leads worse.
I have written a longer piece on Founder Burnout specifically. This module is about the operational habits and mental patterns that create the conditions for burnout and poor decision-making, long before the burnout itself arrives.
[ ] 1. I make most of my significant decisions reactively rather than in scheduled decision-making blocks. Reactive decision-making — responding to whatever the loudest problem is right now — is cognitively expensive and produces worse outcomes than deliberate, scheduled thinking. Founders who are always in reactive mode eventually lose the ability to think strategically because they have conditioned their brains to treat every incoming input as urgent. Scheduling decision time — protecting it, not filling it with calls — is one of the highest-return operational habits I know.
[ ] 2. I have not taken more than three consecutive days off in the past six months. This is not about self-care in the abstract. It is about cognitive function. Chronic overwork degrades decision quality in ways that are nearly impossible to perceive from the inside. You feel like you are thinking clearly. You are not. Three consecutive days is the minimum threshold for actual cognitive recovery. Below that, you are managing fatigue, not recovering from it.
[ ] 3. My operating metrics dashboard does not exist or I do not review it weekly. If you do not have a dashboard — a single view of the 8 to 12 numbers that tell you whether your business is healthy or not — and you do not review it on a weekly basis, you are navigating by feeling. Feelings are useful. They are not a substitute for data. The dashboard does not need to be complex. It needs to exist and be used.
[ ] 4. I have not written down my personal one-year and three-year goals for the company. Strategy without written goals is aspiration. Writing goals down forces clarity, creates accountability, and gives you a reference point for evaluating the decisions that come at you every week. Founders who do not write down where they want to be tend to drift toward whatever the most recent conversation or crisis is pointing them toward.
[ ] 5. I am the primary decision-maker for more than 70% of significant company decisions. This is a leverage problem. If the company cannot make meaningful decisions without you, you have built a company that is entirely dependent on a single point of failure. That founder is also almost always overloaded, under-rested, and gradually losing the ability to think clearly about any one thing. The solution is not more delegation for its own sake — it is building the systems, frameworks, and leadership capacity so that most decisions can be made well without you.
[ ] 6. I have not invested in any personal development — reading, coaching, a peer group — in the past 90 days. The founder's rate of growth needs to exceed the company's rate of growth. If your company is growing faster than you are developing as a leader, operator, and thinker, you will eventually become the bottleneck. This is not theoretical — it is the most common reason growth plateaus in Year 2 and Year 3. The investment does not have to be expensive. It has to be consistent.
[ ] 7. I have not had a frank conversation about company health with my board or a trusted advisor in the past quarter. Founders who are struggling tend to hide it — from their board, from their investors, from their advisors. The instinct is understandable: you do not want to appear weak, you do not want to trigger alarm, you do not want to be replaced. The result is that the people who could actually help you do not know you need help until the situation is much harder to fix. Transparency with your board and advisors is not weakness. It is one of the highest-leverage tools you have.
[ ] 8. I do not have a written definition of what success looks like for the company in 24 months. Without a definition of success, every path looks equally valid. You cannot make good tradeoff decisions — about where to invest, what to cut, which opportunities to pursue — without a clear picture of where you are trying to go. The definition does not have to be perfect. It needs to be written down, shared with your team, and revisited quarterly.
Module 5 score: Count your checks. _____ / 8
Add up your scores from all five modules. Your total is out of 42.
| Total Score | Interpretation | Recommended Action |
|---|---|---|
| 0–6 | Strong operational health | Maintain discipline; revisit in 90 days |
| 7–12 | Manageable risk with clear gaps | Prioritize top 3 checked items; create 30-day action plan |
| 13–20 | Significant structural issues | Use priority triage below; get external perspective immediately |
| 21–30 | Multiple compounding problems | Serious intervention required; consider advisor or coach engagement |
| 31–42 | Critical state | Do not wait; pivot-vs-persist decision framework applies |
A note on honesty: The value of this checklist is entirely a function of how honestly you answered it. The temptation is to answer based on intent ("we plan to do this") rather than current reality ("this is true right now"). Plans do not count. Only current reality counts.
| Module | Your Score | Max | Health Threshold |
|---|---|---|---|
| 1 — Product | _____ | 10 | 0–3 healthy; 4–6 review; 7+ urgent |
| 2 — Market | _____ | 8 | 0–2 healthy; 3–4 review; 5+ urgent |
| 3 — Team | _____ | 8 | 0–2 healthy; 3–4 review; 5+ urgent |
| 4 — Sales/Revenue | _____ | 8 | 0–2 healthy; 3–4 review; 5+ urgent |
| 5 — Mental/Ops | _____ | 8 | 0–2 healthy; 3–4 review; 5+ urgent |
| Total | _____ | 42 |
If any single module scores in the "urgent" range, treat it as a priority regardless of your total score. A company can survive market mistakes if the team is strong. A company with a broken team can survive nothing.
A total score above 5 means you have more active problems than you can reasonably address simultaneously. Trying to fix everything at once is a common founder response that usually results in fixing nothing well. The triage below helps you sequence.
Not all mistakes are created equal. Some are root causes. Some are symptoms. Before you create an action plan, ask: which of the items I checked is the upstream cause of the others?
Common constraint patterns:
For each item you check, you need three things:
Most founders skip step 3. Without a measurable outcome and a deadline, action items live in a planning document forever.
Every checked item that you cannot address in the next 90 days needs to be explicitly deferred — with a date — or delegated to someone with the authority and resources to act on it. Leaving it in a limbo of "important but not urgent" is how things stay broken for 18 months.
The 5+ rule: If you checked 5 or more items in any single module, that module requires dedicated intervention before you invest further resources in the others. A product with 7 checked boxes cannot be fixed by better marketing. A team with 6 checked boxes cannot be fixed by a new sales strategy.
If your total score is above 20 — or if you are scoring in the urgent range on multiple modules — you are facing a decision that goes beyond fixing individual items. You need to evaluate whether your current strategy, product, or market deserves continued investment, or whether a more fundamental reset is required.
This is the hardest decision in startup life. It gets called many things — pivoting, repositioning, resetting, starting over. The language matters less than the quality of the reasoning behind it.
| Signal | Weight Toward Persist | Weight Toward Pivot |
|---|---|---|
| Cohort retention is improving quarter over quarter | Strong | — |
| At least 10% of customers expanded usage without prompting | Strong | — |
| Your best customers have referred others | Moderate | — |
| Churn is above 5% monthly and has not improved in two quarters | — | Strong |
| You have not found a repeatable sales motion after 18+ months | — | Strong |
| Core team is leaving or has left | — | Strong |
| You genuinely do not want to work on this problem anymore | — | Moderate |
| You have changed your core thesis more than three times | — | Moderate |
No single signal is determinative. The matrix is a thinking tool, not an algorithm. What you are looking for is weight — which direction do the strongest signals point?
If the weight is toward pivot, do not pivot randomly. Undirected pivots — "let's try something completely different" — usually waste 6 to 12 months and exhaust the team without surfacing a better opportunity. Directed pivots start with what you already know:
What assets do you have that still have value?
A good pivot preserves as many of these assets as possible while changing the application — the specific problem you are solving, the customer you are solving it for, or the business model you are using to deliver that value.
What does your data tell you about where the pull is? Most companies, even ones that are failing by most measures, have a small number of customers who love them disproportionately. Those customers are your best signal for where to go next. Interview them. Understand what specific problem they are actually solving with your product. Ask them what else they are struggling with. Ask them who else has the same problem. The next direction is almost always adjacent to the customers who stayed, not the ones who left.
If you decide to persist with the current strategy, the decision needs to come with real changes — not just renewed commitment. Deciding to persist while changing nothing is not a strategy. It is optimism.
Before committing to persist, answer:
The last question is the most important. Persist decisions without explicit decision triggers tend to become indefinite — which means you are not persisting based on evidence, you are persisting based on inertia.
"The founders who survive the first three years are not the ones who made fewer mistakes. They are the ones who caught their mistakes faster, acknowledged them honestly, and changed direction before the consequence became irreversible."
This is what I have come to believe after years of watching founders navigate this period — and after making many of these mistakes myself. The checklist above is not a judgment. It is a map. The goal is not to score zero. The goal is to know where you are so you can decide where to go.
How often should I run through this checklist?
Quarterly at minimum. The first three years of a company move fast enough that your score can change significantly in 90 days — in either direction. Running it quarterly gives you a trend line, not just a snapshot. Some founders run it monthly when they are in a high-change period.
I scored above 20 but the business feels fine. Should I be worried?
Possibly. The lag between making a mistake and experiencing the consequence is one of the core themes of this checklist. Feeling fine now does not mean the underlying problems are not accumulating. Look specifically at which boxes you checked and assess whether any of them are in the category of "consequences typically appear 6-12 months after the mistake." If yes, take the score seriously regardless of how things feel today.
What if I do not know the answer to some of the checks?
Not knowing is itself data. If you cannot answer whether your cohort retention is improving, whether your CAC and LTV are healthy by channel, or what your churned users think of you — those are measurement gaps that need to be closed. The inability to answer is functionally equivalent to checking the box.
My co-founder and I scored this differently. Who is right?
You both are, and that disagreement is the most valuable outcome of the exercise. Comparing scores with your co-founder reveals where you have fundamentally different reads on the state of the business. Those gaps in perception are almost always more important than the scores themselves. Do not try to reconcile them immediately — first understand where they come from.
Is a high score in one module more concerning than a distributed score across modules?
Generally yes. A high concentration in one module suggests a systemic failure in that area — your product development process is broken, or your hiring is systematically poor. A distributed score suggests you are fighting on many fronts simultaneously, which is exhausting but often reflects early-stage chaos rather than fundamental dysfunction. The exception is Module 5 (mental/operational) — a high score there amplifies every other problem because it degrades the quality of the decision-making that determines how well you fix everything else.
At what score should I consider bringing in a coach or advisor?
If your total score is above 13, an outside perspective is almost always worth the investment. The reason is not that coaches or advisors have magic answers. It is that founders above that score are usually too close to their own situation to see it clearly. An experienced operator who has no stake in your current strategy can often see the upstream constraint in 30 minutes that you have been unable to see in 18 months. Formalizing that outside perspective through a structured advisory board is often the most capital-efficient way to get it.
Can a company recover from a score of 30 or above?
Yes, but it requires radical honesty about what is broken, a willingness to make changes that feel very uncomfortable, and usually external help — a new co-founder, an experienced operator in a key role, a strong board member who has been through a similar situation. Companies at that score level have compounding problems, which means fixing one thing is not enough. You need to fix the right things in the right sequence, and you need people around you who have done it before.
Is the pivot-vs-persist framework applicable to pre-revenue companies?
Yes, with a modification. Pre-revenue companies should replace the revenue-based signals with engagement-based equivalents. If cohort retention of active users is improving quarter over quarter, if users are expanding their usage voluntarily, and if users are referring others — those are the pre-revenue equivalents of the persist signals. If none of those are true after 18 months, the case for pivoting is strong regardless of revenue.
Udit Goenka is a founder, operator, and investor. He writes about startups, product, and the mechanics of building companies at udit.co.
Angel investor Udit Goenka breaks down 10 recurring failure patterns in AI startups — from demo PMF to compute cost traps — and how to diagnose and avoid each one.
A brutally honest case study of a portfolio company failure — what we missed, what went wrong, and what I changed about my investing process after.
A practitioner's framework for measuring PMF using Sean Ellis scores, retention curves, qualitative signals, and the 5 PMF archetypes — with benchmarks.