Skip to main content
All articles

When to Pivot, When to Persist: A Decision Framework for Founders

The hardest call in a startup is knowing when you've learned enough to change direction. Here's how to make that decision without letting fear or sunk cost rule.

G

Glauber Bannwart

March 6, 2026 · 3 min read

When to Pivot, When to Persist: A Decision Framework for Founders

Every founder reaches this moment: things aren't working the way you expected. Growth is flat, conversion is low, users churn after week two. The question arrives: is this a "keep going" problem or a "change direction" problem?

Getting this wrong in either direction is costly. Here's a framework for making the call.

First: Separate the Signal from the Noise

Not everything that isn't working is a reason to pivot. Some things aren't working because:

  • You haven't found your audience yet (distribution problem, not product problem)
  • The product needs another sprint to be genuinely good
  • You're measuring the wrong thing
  • It's too early to have signal

Before asking "should we pivot," ask: "do we have enough signal to make this call at all?"

The minimum threshold: 100 real users who've tried to use your product for its core use case. If you don't have that, you're pivoting on noise.

The Three Types of Pivots

Not all pivots are equal. Understanding which type you're considering shapes how you evaluate it.

1. Customer segment pivot: Same problem, same solution — different who. If enterprise HR teams don't care but mid-market ops managers love it, that's a customer pivot.

2. Problem pivot: Same customer — different problem to solve for them. If you built a scheduling tool for doctors and they don't care about scheduling but desperately need patient communication, that's a problem pivot.

3. Solution pivot: Same problem, same customer — different how. This is the most common and least disruptive.

A fourth type — "different everything" — is usually just starting over with better information.

The Framework: Four Questions

Ask these four questions before deciding:

1. Is there a version of what we're doing that clearly works? Look at your best users. If even a handful of them genuinely love the product and get obvious value from it, that's a signal the product has something. The job is to find more of those people, not to change the product.

2. Are we solving the right problem for the wrong people, or the wrong problem for the right people? The answer tells you which type of pivot to consider (customer vs. problem).

3. Do we have evidence of what would work better, or are we guessing? Pivoting based on "I have a feeling" is dangerous. Pivoting based on 15 customer interviews that all pointed to the same unmet need is rational.

4. Does the team believe in the pivot? A pivot the team doesn't believe in will fail for different reasons. If the shift requires rebuilding conviction from scratch, factor that into the cost.

The Sunk Cost Trap

The biggest risk is persisting not because of signal but because of how much you've already invested. Sunk costs are real emotionally but irrelevant logically.

Ask yourself: "If I were starting fresh today, with everything I know now, would I build this? For this customer? Solving this problem?"

If the honest answer is no, you have your answer.


FounderSequence helps founders clarify their direction before over-committing. Submit your lean canvas for an honest assessment →