The room has a proposal. Drop the entry price. Change the segment. Rebuild for a different buyer. Somebody has a deck, and the arguments are all plausible, which is the problem. Plausible is what every option looks like from inside the trough.
A pivot is an experiment. An experiment without a required input and a predetermined reading is not an experiment, it is just another move you will not know how to interpret. This page is about making the pivot on your whiteboard falsifiable before you spend a quarter on it.
Not ten pivot types. These are the things founders actually say out loud, and the order matters more than any of them individually.
The one that has to go first. Every other question assumes the answer to this one is yes, and most teams have never tested it.
The only two demand bets there are. A different person doing the same job, or the same person with a different job. Everything else on the whiteboard assumes demand is already settled.
Pricing, channel, and packaging can be changed on Monday. Segment and need require going out and finding out. The taxonomy is neutral about which dial to turn. The incentives are not.
Liking is not hiring. Interest without action means the forces toward change have not overcome the forces holding position, and the question is which one is binding.
The question nobody asks, and the reason quarters disappear. Turn a dial without the required input and the win is unattributable and the loss is unexplainable. The only honest conclusion left is try something else.
People in real pain already did something about it. A spreadsheet with eleven tabs. A contractor every Thursday. Two tools duct-taped together. Budget on a line item that half solves it. That evidence exists before any search behaviour starts, which makes it the only signal available this early.
Someone who describes the problem eloquently but has never paid a cost against it is describing an inconvenience. Cost counts broadly: money, hours, headcount, an ugly workaround, a route they now avoid, or a consequence they have quietly absorbed. At this stage, no cost paid means no evidence of demand.
At the demand level, every pivot goes through one of these two. They need different evidence and they are not interchangeable, which is why teams that walk through both at once learn nothing from either.
Same job, different person doing it. The work being done has not changed; who does it has. That sounds small and it is not, because the forces, the hiring criteria, and the language all change when the executor changes.
Note that the executor is often not the buyer. A tool bought by a VP and used by an analyst has two people in the room and one of them is doing the job.
Same person, different progress being sought. You keep the audience and change what you are helping them accomplish, usually because the original job turned out to rank low against everything else on their list.
The failure mode here is specific: the new job ranks higher but nothing was ever hired against it. That is an inconvenience with better language.
Changing both at once is not a third door. It is walking through both, and it destroys your ability to learn which assumption was wrong. If the new thing works you cannot say whether it was the audience or the job, and if it fails you have eliminated nothing. Two doors, one at a time.
Which is why turning a pricing or channel dial before the executor is settled produces a reading you cannot interpret. Two more from the standard list are segment bets wearing product clothes: building a platform adds a second executor, and moving up or down market moves you to a different one at a different price point. Both usually get run as architecture decisions with no new customer evidence at all.
All ten pivot types and the specific evidence each one needs →
Pricing is the attractive variable. It can be changed on Monday, it needs no new evidence, and it feels like decisive action. That is exactly what makes it good at hiding a demand problem for another quarter.
Trials, no conversion. The room wants a pricing pivot: lower entry tier, usage-based billing, ship in three weeks.
Changing what you charge is a bet on anxiety and avoidance at the moment of hiring, plus how the customer expects to pay for progress. Nobody has that evidence, so they go get it. Twelve conversations with people who evaluated and did not buy.
What comes back is not about price. All twelve already had a workaround running, and not one could name a moment. No slipped deadline, no failed audit, nothing that made the status quo intolerable. They took the trial because the demo was good.
That is not an anxiety finding, it is a missing push. The dial was never pricing. It was segment. The pricing pivot ships on time, moves nothing, and costs a quarter.
The lesson is not that pricing pivots are wrong. It is that before you change an easy-to-change variable, establish that the variable is actually constraining the decision. Otherwise you have run a clean experiment on something that was never in the way, and the flat result tells you nothing you can use.
There is a sting in the pairing. The dials that are cheapest to turn run on the evidence that is most expensive to collect, because it comes from people who never became records in your CRM. That is most of the explanation for why those dials get turned blind.
You have data. Win/loss reviews, health scores, a quarterly messaging workshop, a pipeline report. The data is not lying, exactly. It is answering a question adjacent to the one you asked.
| What you have | Stands in for | Ask instead |
|---|---|---|
| Usage | Intent | What happened that caused you to act when you did? |
| Deciders | The market | Who has this struggle and hasn't started shopping? |
| Internal consensus | Customer vocabulary | How did they describe this before they knew our category existed? |
In every case the substitute is easier to collect, arrives in a dashboard, and quietly answers a different question than the one being asked. The third column is the version you have to go outside your own data to answer.
The middle row is the one that decides a pivot. Win/loss studies buyers who crossed the decision threshold. The people who would tell you whether the struggle is real never crossed it, so they never became records in your CRM as anything. They are not scarce. They are unaddressed.
Which also bears on question 04. Pull is the lever you control: the demo, the onboarding, the positioning, the integrations. Push is manufactured by the customer's situation and not by your roadmap, which makes it the one input you cannot create. Habit and anxiety can be worked on, with migration tooling, reversible trials, compatibility, hands-on onboarding, but they do not shrink automatically just because the product got better. So there is a threshold. If the struggle is not larger than the friction of changing, no amount of product, pricing, or channel work crosses it.
What changed in their situation that made staying with the old way harder than changing?
This gets at push without asking anyone about pain, urgency, or willingness to pay, all of which produce polite and useless answers. You are looking for the same three fingerprints as the struggle test above, heard from the customer rather than assumed in a meeting.
What would we have to hear, or observe, to know the struggle is strong enough to cause a switch?
Answer this before you go looking, not after. If the team cannot say in advance what would count as evidence, the interviews will confirm whatever the room already believed, and so will the pivot.
The first question finds the trigger. The second defines the reading before you run the test.
Fair, and it is half true. Four of the six interview types need people already inside your product or people who left it, and pre-fit you have neither. What you do have is three: core jobs, switching, and no-decision. Switching does not require anyone to have switched to you. It reconstructs a switch someone already made, to an incumbent or to a spreadsheet or to a contractor, which is the trade you need to understand whether or not you were ever an option.
Those three happen to reach exactly the population that settles question 01. People with the struggle are not shopping, are not searching your category, and will not pass a screener written in your vocabulary. The trough feels evidence-poor, and that feeling is an artifact of where teams look rather than what exists.
One limit worth stating plainly. Evidence from people who have not started looking sizes struggle and nothing else. Someone who is not yet in a decision cannot tell you their hiring criteria or what trade-offs they would make, because those do not exist until a decision is underway. That evidence supports the two demand bets and no others.
Name the reading before you run the test. That order is the whole method, and it takes about ten minutes in a room before anyone opens the roadmap. It is also the only thing separating a course correction you can audit from a move you will spend the next quarter arguing about.
Start from the symptom and work back to the instrument, the population, and how you reach them.
Go deeperTen pivot types, ten different pieces of customer evidence, and why eight of them assume the two nobody gathered.
Choose the modalitySynthetic, AI-moderated, and 1:1 expert interviews, and what each one can and cannot settle.