When a mid-market executive asks me what a "90-day product engagement" actually consists of, I usually get one of two reactions to my answer.
The skeptical reaction: "There's no way you can ship a real product in 90 days with one person."
The hopeful reaction: "Okay, but what does that actually mean week to week? What do I get?"
This essay is for the second reaction. I'm going to lay out the actual anatomy of the program. What it contains. What it produces. What you, the operating executive, are actually paying for.
If you walk away from this essay still skeptical, that's fine. Skepticism is appropriate at your level. But you'll at least be skeptical about the right things, instead of skeptical about a vague concept.
The three phases
The program is organized into three phases. Each phase ends with a decision gate. Each phase produces specific artifacts you can show to your board.
Phase 1: Lock the bet. Days 1 to 21. Three weeks.
Phase 2: Test the bet. Days 22 to 42. Three weeks.
Phase 3: Build for paying customers. Days 43 to 90. Roughly seven weeks.
If that timeline sounds aggressive, it should. The whole point of the program is that the new economics make this timeline possible where it wasn't possible three years ago. If we used 2022 timelines, we'd still be writing the spec at Day 90.
Let me walk you through each phase with the specific deliverables, so you can see what the output actually looks like.
Phase 1: Lock the bet (Days 1 to 21)
The single biggest mistake mid-market companies make with new digital products is starting to build before the bet is properly locked. They write a spec from internal assumptions, hand it to a dev shop, and then discover at Day 200 that the spec was wrong because they hadn't actually talked to enough customers about the problem.
Phase 1 prevents that. The whole phase is about locking the bet before any production code gets written.
Deliverables for Phase 1:
The customer pain document. Two pages. Written in the customers' actual words after the operator has done four to six discovery conversations. The board-ready version of "here is the problem we're solving."
The smallest-viable-version spec. Two pages. Not a full product roadmap. The minimum thing that, if it existed and worked, would generate real customer evidence about whether the bet is worth scaling.
The kill criteria. One page. The specific evidence that, if you don't see it by Day 90, means the bet is not worth pursuing. This document is the most important artifact of Phase 1, and almost nobody else produces one.
A working version one of the product. Not a prototype. Not a click-through. A real, ugly, functional thing that two friendly customers can actually use.
Decision gate at end of Phase 1: You either approve the bet to enter customer testing, or you redirect. Redirecting at Day 21 is small. Redirecting at Day 280 is a year of your life.
Phase 2: Test the bet (Days 22 to 42)
This is where most "innovation initiatives" fail, because the people running them don't know how to extract real signal from early customers. They hear nice things, mistake nice things for buying signals, and proceed.
Phase 2 forces a different discipline.
The operator gets the version-one product into the hands of two to four friendly customers from your existing network. Not surveys. Not focus groups. Real usage. Real workflow. Real money where possible.
The operator's job during this phase is not to sell. It is to watch. To take notes. To document what breaks, what works, what surprises everyone, and most importantly, what customers ask about pricing.
Deliverables for Phase 2:
The friction log. Specific list of every place version one broke down. What confused customers. What was missing. What unexpectedly worked.
The willingness-to-pay signal. The single most important artifact of the engagement. Real evidence about whether customers asked about pricing, asked when it would be available, asked if their team could use it. Or whether they thanked you politely and didn't follow up.
A pivot recommendation, if applicable. Sometimes Phase 2 reveals that the customer wants a related but different product. The operator's job is to flag this clearly, not to keep building toward the original spec out of inertia.
Decision gate at end of Phase 2: This is the big one. You make one of three calls. Keep building toward the original spec. Pivot to the version the market actually wants. Or kill the bet because the willingness-to-pay signal isn't there.
This gate is the one the old playbook didn't have. This is why the new playbook produces dramatically better outcomes for dramatically less money.
Phase 3: Build for paying customers (Days 43 to 90)
If you make it past Gate 2 with a "keep building" or "pivot" decision, Phase 3 is where the operator turns version one into a product that real paying customers can actually use.
This is where the brand gets built. Where the error handling gets serious. Where the onboarding gets thought through. Where pricing gets implemented. Where support documentation gets written.
It is also where the first paying customers get onboarded, in the last two weeks of the engagement.
Deliverables for Phase 3:
A complete, branded, working product. Real users. Real payment processing. Real support docs.
First paying customers. Could be three, could be ten. The number matters less than the fact that they are paying real money for a real thing.
The engagement readout. A board-ready document. What was built. What was learned. What customers paid. What the unit economics look like. What scaling would require. What the operator recommends.
This document is what you take to your board. It is not a deck. It is a real readout backed by real customer behavior.
Your role across the three phases
This is the question I get asked most often, so let me be specific.
Across the entire 90 days, your direct time commitment is roughly one to two hours per week on average, more during decision gates and less during build periods. Across 13 weeks, somewhere between 15 and 25 total hours of executive time.
Your stakeholder time, meaning the involvement of other people inside your company, is even smaller. The whole point of using a single outside operator is that nobody on your existing team needs to spin up a new workstream. The operator handles strategy, build, customer testing, brand, and launch. Your team's role is to provide intros to friendly customers (Phase 2) and to ratify the gates.
This is what makes the program actually possible to greenlight at the board level. Your existing business is not affected. Your A-players are not pulled. Your headcount does not change. The bet is genuinely additive instead of disruptive.
What this whole thing costs
Most engagements at this scale price between $40,000 and $80,000 total, depending on the technical complexity of the bet. That's everything. Strategy. Build. Brand. Launch. Customer onboarding. The board readout. Inclusive.
For comparison: that's less than what mid-market companies typically spend on a single trade show booth. Less than what the average innovation consulting engagement costs for the strategy deck alone. Less than three months of a Chief Digital Officer's loaded comp.
It is, by an order of magnitude, the cheapest version of "test a real digital bet" that has ever existed in mid-market business. That is not me selling you. That is just the new economics.
The thing I want you to walk away with
The 90-day product playbook works because it forces the right decisions at the right time. Lock the bet before building. Test the bet before scaling. Build for paying customers before declaring victory.
Each phase produces real artifacts. Each phase ends with a real decision gate. Each gate gives you a real off-ramp if the evidence isn't there.
That structure is what makes this fundamentally different from the consulting deck, the dev shop build, the CDO experiment, and every other thing you've already tried.
If you've got a bet that has been sitting in a drawer because you didn't know what shipping it actually looked like, now you do.
Same offer, different lens: the day-by-day calendar · versus what you've already tried.
If you want to talk about whether your specific bet maps to the three phases cleanly, book a call. Thirty minutes. No deck. We talk about your idea and the calendar honestly. Program overview: 90-Day Growth Plan.