How to Run a 90-Day Pivot Sprint: A Step-by-Step Guide for UK SMEs

Most pivots don't fail because the idea was wrong. They fail because the business took eleven months to find out. A 90-day sprint compresses that loop into a quarter: fixed weeks, one written hypothesis, weekly milestones, and three or four moments where you stop and decide whether to carry on. It fits UK SMEs because it fits the rhythm you already run on — quarterly VAT returns, quarterly management accounts, quarterly cash planning. Here's how to run one without dropping the day job.

What a 90-day pivot sprint is (and what it isn't)

A pivot sprint is a thirteen-week project with a single hypothesis, a named owner, a spending cap and one metric that tells you whether it's working. It is not a rebrand, a website rebuild or a full relaunch. Those come later, and only if the evidence earns them.

Before week one, write these down. If you can't, you aren't ready to start.

• A one-sentence hypothesis you can say out loud without hedging
• One named owner who can make decisions without calling a meeting
• One primary metric, plus the threshold that counts as success and the one that counts as failure
• A budget you can afford to lose entirely
• A frozen list: everything that stays exactly as it is for 90 days

The frozen list is the one people skip. Say you run a training company moving from open public courses to in-house programmes for employers. Your existing course calendar stays untouched for the quarter. Your website stays up. You change one thing and you measure it, rather than changing eight things and learning nothing.

Weeks 1–2: scope it down to one testable sentence

Use a template: If we [change], then [specific customer group] will [do something observable], and we'll know because [metric] reaches [threshold].

For example: "If we sell to trade customers instead of homeowners, twelve independent builders will place a repeat order within six weeks, and we'll know because trade accounts with two or more orders reach twelve."

Make the segment uncomfortably narrow

"SMEs in the Midlands" is not a segment. "Independent builders' merchants with two to five branches" is. Narrowing isn't a permanent commitment; it's how you get a clean signal in thirteen weeks rather than a muddy one in thirty.

Choose one metric and pre-commit to the kill threshold

Pick something observable: orders, deposits, booked meetings, renewal rate. Not "brand awareness" and not "engagement". Write both the success line and the failure line now, while you're still being honest with yourself.

Gate 1, end of week 2: is the problem real, specific and narrow enough that a stranger could repeat your hypothesis back to you in one sentence? If not, rescope. Don't build.

Weeks 3–4: validate with evidence that costs something

Talk to ten to fifteen people in the target segment. Not to pitch — to understand what they currently do about the problem you think they have. Then ask for something that costs them: a deposit, a signed pilot agreement, a purchase order, a paid trial, a booked date in the diary with money attached.

Compliments are not validation. "That sounds interesting, let me know when it's ready" is a polite no. A £250 deposit is a yes, even if the person is cautious about it.

Cheap ways to test real demand: pre-sell a pilot to five customers at a real price, offer existing clients first refusal on the new service, or run a single landing page with a genuine price and a working payment link. One channel, one offer, one price. Resist the urge to test three variants at once.

Gate 2, end of week 4: have a handful of people in the target segment given you money, a signature or a firm date? If not, change the offer or the segment — not the deadline.

Weeks 5–8: build the smallest version a customer will pay for

Deliver it by hand if that's what it takes. A monthly advisory retainer can start as you, a spreadsheet and a 45-minute call. A new product line can start as a manual fulfilment process. The point of these four weeks is to learn whether the thing works when a real customer is watching, not to build something that scales.

If the pivot changes your legal structure, tax position, insurance or client contracts, take proper advice from an accountant or solicitor before you commit to anything.

Weekly milestones

Every Friday, twenty minutes, three questions. Write the answers in one running document.

1. What moved the metric this week?
2. What did we learn that we didn't know last Friday?
3. What is the single most important thing to do next week?

Gate 3, end of week 8: can you deliver this at small scale without breaking your existing operation? If serving five customers already feels painful, fifty will be a disaster.

Weeks 9–12: sell to strangers, then decide

Until now, most of your buyers have probably been warm — existing clients, contacts, people who took your call because they know you. Weeks 9 to 11 are for cold outreach: people who owe you nothing. That's the honest test of whether the pivot has legs.

Keep it to one channel and one price. Track how many conversations turn into commitments, and note the reasons people say no. Those reasons are often more useful than the sales you make.

Decision week

Book half a day in week 12 and choose one of four outcomes.

• Scale: the metric hit and delivery held. Build the plan for the next quarter.
• Adjust: real demand, wrong shape. Change one variable and run another 90 days.
• Park: promising, but the timing or cash isn't there. Record what you learned and the trigger for revisiting it.
• Stop: the metric missed and nothing new appeared. Close it cleanly and explain the reasoning to your team.

Write a one-page post-mortem while it's fresh: what you assumed, what actually happened, what you'd do differently. That page is the real asset the sprint produces, whatever the result.

Where 90-day pivots go wrong

• Scope creep. A second hypothesis sneaks in during week six and the metric stops meaning anything.
• Vanity metrics. Newsletter sign-ups, social follows and meeting counts flatter you without predicting revenue.
• Skipping the gate. The gate date arrives, the numbers aren't there, and nobody wants to say so. Hold the date anyway.
• No decision-maker in the room. If the owner has to escalate every choice, the sprint slows to the pace of your slowest meeting cycle.
• Running it as a secret project. Your team will notice the time and money going somewhere. Tell them what you're testing and why.
• No cash buffer. A pivot usually costs more and earns later than planned. Decide the ceiling before you start and stop at it.

Your first Monday

You don't need a strategy deck to begin. You need four things by Friday.

1. Write the hypothesis in one sentence and read it to someone outside the business.
2. Name the owner and the decision-maker.
3. Set the metric, the success threshold and the kill threshold.
4. Diary the four gate dates and the weekly Friday review — repeating, all thirteen weeks.

Then start week one. The sprint's real value isn't the pivot itself; it's that you'll know by the end of the quarter whether to go all in, change tack or walk away, and you'll have the notes to prove it either way.

Photo: sakibmia24 / Pixabay