A pivot is a change to one core part of your plan: who you sell to, what problem you solve, what you build, how you charge or what you build it with. The Lean Startup calls it a structural course correction. You keep the team and everything you’ve learned, and test a new direction.
This guide covers the signals that say it’s time, a runway check to do first, the five main pivot strategies and what each one keeps from your product, and how to make the call.
One bad month isn’t a signal. A pattern across several of these is.
| Signal | What you see | How to check it |
|---|---|---|
| The problem doesn’t hurt | People in interviews can’t recall the last time it happened and have never tried to fix it | Ten problem interviews in your main customer group |
| Nobody commits | Polite interest, but no pre-orders, pilots or introductions | Solution interviews with a direct ask |
| Users wouldn’t miss it | Few users say they’d be very disappointed without the product | The Sean Ellis question; 40% is the usual bar (First Round Review) |
| Only one part works | One feature or one customer group drives almost all use | Usage by feature and by customer group |
| The numbers don’t close | Winning a customer costs more than the customer brings in | Lifetime profit per customer against the cost to win one |
| A bigger player arrives | A large company ships the same thing with more money and existing customers | Win and loss notes from sales calls |
Two of these do most of the damage. In CB Insights’ March 2026 study of startups that shut down since 2023, 43% of those with a known reason cited poor product-market fit and 19% cited unit economics that didn’t work.
A pivot costs time, and every month of it costs cash. In the same study, 70% of the startups ran out of capital. The report calls that almost always the final cause of death, not the root problem. The median time from the last fundraise to shutting down was 22 months, and nearly a quarter kept going for more than three years after their last raise.
So before you choose a direction, write down three numbers:
If the second number is bigger than the first, cut spending before you pivot, or pick a smaller pivot.
Zume raised $446 million, pivoted from robot-made pizza to sustainable packaging and still didn’t find a viable market, according to the same report. And most businesses don’t last: of the US business establishments that opened in the year to March 2021, 47.2% were still operating in March 2026, according to the US Bureau of Labor Statistics. Test the new direction as hard as you’d test a new idea.
| Pivot | What changes | What you usually keep | Typical trigger |
|---|---|---|---|
| 1. Zoom-in | One feature becomes the whole product | That feature’s code and data, your users who rely on it | Only one part works |
| 2. Customer group | Same product, different buyer | Most of the code; onboarding, pricing and messages change | Another group shows more pain |
| 3. Platform | Mobile to web, app to API, or the reverse | Backend, data and business logic; the front end is rebuilt | Users want it where they work |
| 4. Revenue model | How you charge: subscription, one-time, usage or ads | The product; billing and pricing pages change | The numbers don’t close |
| 5. Technology | What it’s built on | Product knowledge and data; much of the code is rewritten | Costs or quality block growth |
One feature turns out to matter more than the whole product. You make it the product and drop the rest. The reverse, a zoom-out, also happens: your product becomes one feature of something bigger. Work backward from the feature people use most.
The product is right, but you sold it to the wrong people. A tool built for freelancers turns out to matter more to agencies. Run new problem interviews with the new group before you change anything in the code.
You move from a mobile app to the web, from an app to an API, or the other way round. The backend and data usually survive. The screens don’t.
You change how you charge, for example from a one-time price to a subscription, or from free with ads to paid. In apps, the stores have rules for this. On the App Store, existing subscribers must agree to a price rise if it’s more than 50% and more than about US$5 a period (US$50 a year for annual plans), if they’ve already had a rise in the past 12 months, or if they live where consent is always required. You can also keep the old price for existing subscribers, as Apple’s subscription pricing help explains.
You rebuild on a different stack to cut running costs or fix quality problems. It usually means rewriting the most code, so do it only when you can show the current stack is what holds growth back.
Run one meeting with a clear question: pivot or persevere?
Then tell the team in writing: what changes, what stays and what stops. Unclear direction lands hard on developers. In the Stack Overflow Developer Survey 2026, unclear priorities or requirements was the top reason respondents gave for their job getting harder in the past six months, at 16.6% of 18,214 people. A pivot announced in a hallway makes that worse.
Most pivots keep more code than founders expect. The data model, sign-up, payments and admin tools often survive. Before you decide to rebuild, find out what you have. Our code and architecture audit costs a fixed $3,500, takes 5 working days and tells you what to keep, fix or rebuild, with hours for each fix.
A pivot doesn’t have to be a crisis, either. In our Guestroom case, a self-funded founder needed a mobile MVP on a tight budget and deadline. After the first iteration, the product moved into customer development, gathering feedback for the next pivot.
Treat the new direction like a new product and estimate it from scratch.
Our project estimate turns your brief into user stories. You confirm what’s in scope, and every hour in the budget traces back to a story you kept. Uncheck the stories your current product already covers, and the hours come off. We check the hours the model suggests against what our team actually books on finished projects, then multiply by our published rate of $39-55 an hour.
The estimate also suggests customer groups and gives each one a TAM, SAM and SOM with a note on what the number covers. Treat them as hypotheses to test, not verified demand. The unit economics show how many customers pay for the build and in which month it’s paid back, and you can change any starting number. Compare the payback month for your current direction and the new one. See what the new direction costs to build before you commit to it.
A change to one core part of a startup’s plan, such as the customer group, the problem, the product, the revenue model or the technology, made after testing showed the current plan won’t work. You keep what you’ve learned and test the new direction.
When several signals line up: the problem doesn’t hurt enough in interviews, nobody commits after seeing the product, few users would miss it, or the cost of winning a customer is higher than what they bring in. Check your runway before you decide.
Zoom-in (one feature becomes the product), customer group (same product, new buyer), platform (for example mobile to web), revenue model (how you charge) and technology (what you build it on).
Usually not all of it. The data model, sign-up, payments and admin tools often survive. An audit of the code tells you what to keep, fix or rebuild before you spend on it.
Testing a new direction with interviews and a prototype takes a few weeks. A first version of it typically takes us 2-4 weeks. Plan both inside the cash you have left.
Carefully curated content for resourceful Devs, CTOs, and PMs. No spam.