The Pivot
When customer validation fails, change direction based on what you learned rather than pressing forward on a broken plan
The Pivot is the iterative loop built into the Customer Development model that sends a startup back to an earlier step when validation fails. It is most visible as the additional loop between Customer Validation and Customer Discovery in the Customer Development diagram, but iterative loops exist within every step.
The pivot embodies the philosophy that going backwards is a natural and valuable part of learning and discovery, not a failure. Unlike the traditional Product Development model where going backwards means someone gets fired, the Customer Development model assumes multiple iterations are necessary and plans for them by maintaining a low cash-burn rate.
There are several levels of pivoting. Within Customer Discovery, you can iterate by modifying presentations and trying different markets and users. Within Customer Validation, you can modify the sales roadmap and try selling again. The most significant pivot sends you from Customer Validation all the way back to Customer Discovery, which happens when the problem is not in the sales process but in the product itself.
The decision to pivot requires honest self-assessment. You must ask whether you really met the objectives or are just moving the goal posts to justify moving forward. The trigger for a pivot is clear: if you cannot find enough paying customers or if custom feature requests reveal that the product requirements are fundamentally different from what was assumed, it is time to change direction.
Critically, the pivot should happen while the company still has enough cash to iterate. The Customer Development model recommends budgeting for two to three passes through Customer Discovery and Customer Validation, which requires keeping the burn rate low during these steps.
- Going backwards is a natural and valuable part of learning and discovery, not a failure
- Plan for two to three iterations by maintaining a low cash-burn rate during early steps
- The nature of finding a market and customers guarantees you will get it wrong several times
- Keep cycling through each step until you achieve escape velocity into the next step
- Honest self-assessment is required: are you meeting objectives or just moving the goal posts?
- If enough customers ask for the same custom features, they are telling you what the real product requirements are
- In an infinite amount of cash is useless during early steps because it can only obscure whether you have found a market
- You always want to have enough cash to get the validation phase wrong at least once
- 1. Recognize the SignalsIdentify the evidence that a pivot is needed. Key signals include: customers say the product is interesting but will not buy, the sales process does not work consistently across different customers, customers will not deploy the product even for free, custom feature requests converge on a different product than what you are building, or the business model does not produce profitable economics.Pro tipAsk customers the zero-price deployment question. If they would not deploy and use the product even for free, you have a fundamental product-market fit problem, not a sales problem.WarningDo not rationalize failed sales as needing more time or more salespeople. If the pattern is consistent across multiple accounts, the issue is systemic.
- 2. Diagnose the Root CauseDetermine whether the problem lies in the sales process, the product, or the market hypothesis. If the sales roadmap needs refinement, iterate within Customer Validation. If customers consistently say the product does not solve a painful enough problem, pivot back to Customer Discovery. If custom feature requests reveal different product requirements, those are not custom features, they are the real product specification.Pro tipDistinguish between a sales execution problem and a product or market problem. Sales execution problems can be fixed by iterating the sales roadmap. Product or market problems require going back to Customer Discovery.WarningDo not assume the problem is always in sales. Sometimes the product itself needs to be reconfigured around what customers actually need, which requires a deeper pivot.
- 3. Preserve Cash and ResetBefore pivoting, reduce the burn rate to ensure enough runway for additional iterations. Fire unnecessary staff, shut down premature sales efforts, and reset expectations with the board. Present both the problem and the suggested fix to investors rather than waiting for the board to tell you how to run the company.Pro tipPresent the problem and your plan to fix it to the board yourself. You never want a board to have to tell you how to run your company. When that happens, it is time to update your resume.WarningIn flush times a startup may get two or three iterations. In tough times investors are tighter and make the calculations with a frugal eye. A startup might not get another round of funding.
- 4. Execute the PivotReturn to the appropriate phase based on your diagnosis. If iterating within Customer Validation, modify the sales roadmap and return to Phase 1 of validation. If pivoting to Customer Discovery, use the core technology and come up with another product configuration, then test it with customers. Incorporate the lessons learned from the failed iteration into your updated hypotheses.Pro tipWhen pivoting back to Customer Discovery, take everything you learned. The failed iteration is not wasted if you capture the lessons and apply them to the next configuration of product, customer, and market hypotheses.WarningDo not pivot without updating your hypotheses in writing. If you do not capture what you learned, you risk making the same mistakes in the next iteration.
FastOffice first targeted the home office market with a 1395 dollar device. When individual customers would not pay, the company pivoted to Fortune 1000 corporations with distributed workforces, rebranding the product as HomeDesk. But this strategy suffered from the same fundamental problem: the product was nice to have but did not solve a compelling problem for either market.
When InLook's CEO discovered the entire sales forecast was phantom demand, he did not just fire the VP of Sales and hire a new one. He diagnosed the root cause as a complete absence of a validated sales process. He cut the team from eleven to three, slashed the burn rate, and went into the field himself to build a sales roadmap from scratch.
The concept of the pivot in the Customer Development model grew from Steve Blank's observation that startups invariably get their initial hypotheses wrong but rarely have a structured way to change direction. In the traditional model, going backwards is considered failure, so teams press forward even when their market assumptions are clearly wrong. Blank built the iterative loop into the model as an explicit acknowledgment that failure and course correction are expected parts of the startup journey. The pivot concept later became one of the central tenets of the lean startup movement popularized by Eric Ries.