Picture a six-person consulting firm at its January planning session. Someone writes $1.2M this year on the whiteboard. Everyone agrees it is achievable. By April, revenue looks almost exactly like last April, and nobody can point to a single week where the plan changed what anyone did on a Tuesday.
Nothing went wrong. That is the strange part. No crisis, no bad hire, no lost client. The goal simply never converted into behavior.
This is the gap almost every execution problem lives in. Goals are outcomes. Work is inputs. A goal tells you what the scoreboard should read. It says nothing about which plays to run, who runs them, or what you stop doing to make room. Writing a bigger number on the board changes the scoreboard’s ambition and none of the plays.
Ninety days is the useful unit for closing that gap. Long enough that repeated effort compounds into a visible result. Short enough that you cannot hide inside it. A twelve-month plan lets you defer the hard part until October. A one-month plan is too short for anything that involves other people making decisions. Thirteen weeks sits in the honest middle.
Start by turning the goal into arithmetic
Before you plan anything, force the goal through a calculation. Not a forecast. A simple chain of numbers that must be true for the goal to happen.
Take a B2B services firm targeting $400,000 in new revenue this quarter. Average engagement is $8,000. That means 50 new clients. Their close rate on qualified sales conversations is 25%, so they need 200 qualified conversations in 13 weeks. They currently run about 40 a month, or roughly 120 a quarter.
The goal is not “grow revenue.” The goal is “go from 40 qualified conversations a month to 67.” That is a sentence a team can act on. “Grow revenue” is not.
Do this and one of two things happens. Either you find a plausible path, or you discover in week one that the goal cannot be reached through the route you assumed. The second outcome is worth more than the first. Finding out in January that your math requires a 70% jump in lead volume gives you time to change the equation. Finding out in December gives you a post-mortem.
When the arithmetic breaks, you have four terms to work with, and most teams only ever reach for one.
- Volume. More conversations. The default choice, and usually the most expensive one.
- Conversion. Same conversations, better outcomes. Often the cheapest lever, and often ignored because it is less visible than “launch a campaign.” If you already get traffic and inquiries but few clients, the constraint is here, not upstream. More traffic rarely solves a conversion problem.
- Price or deal size. Raising average engagement value from $8,000 to $11,000 cuts the required client count from 50 to 36. That is a smaller execution burden than a 70% increase in lead flow.
- Existing customers. The term nobody puts in the equation. Renewals, expansions, and referrals almost always convert at multiples of cold demand.
Run the arithmetic across all four before you pick. The path that requires the least new capability usually wins, even when it feels less exciting.
Find the one constraint, not the five improvements
Quarterly planning sessions produce lists. A typical list from a small team: refresh the website, start a newsletter, hire a salesperson, run paid ads, build a referral program, fix onboarding. Six good ideas. Zero of them will be finished well.
Here is the test I would apply to any item on that list.
The substitution test: swap the item for a different reasonable activity. If the plan still feels roughly as sensible, that item was activity, not a lever. Real levers cannot be substituted. If a firm’s problem is that 80% of its inquiries are unqualified, then “improve lead quality” cannot be swapped for “refresh the website” without the plan collapsing. That is how you know it is the constraint.
There is a structural reason to pick only one. Constraints move. Fix the lead quality problem and the next bottleneck appears somewhere else, often in a place you did not predict, like proposal turnaround time or capacity to deliver. Work you did in advance on constraint number three may turn out to be work on a problem that no longer exists. Solving bottlenecks in sequence is not slower than solving them in parallel. It is faster, because you waste less.
The uncomfortable version of this rule: a 90-day plan with five priorities has no priorities. It is a wish list with dates attached.
Diagnosing the actual constraint takes more honesty than most planning sessions allow. Teams tend to name the constraint they know how to fix. A marketing-heavy team will diagnose a marketing problem. A sales-heavy team will diagnose a pipeline problem. Look at where things stall, not where you are comfortable working. If prospects consistently go quiet after seeing the price, the issue is the offer, not the traffic. Many teams spend a quarter buying more attention when the offer itself is the thing failing.
Build the plan out of reps, not projects
A plan made of projects finishes once. A plan made of repetitions compounds and leaves behind a working system.
Compare two versions of the same intent:
- Project version: “Overhaul our email marketing.”
- Rep version: “Send one case-study email every Tuesday for 12 weeks, to the same segmented list, with the same call to action.”
The second is measurable weekly, delegable, and hard to fake. It also produces evidence. After twelve sends you know which case studies pull, which subject lines work, and whether email deserves more budget. The overhaul produces a launch and then silence.
This is where I would apply what I think of as the Monday Morning Test. Hand the plan to whoever is responsible for it and ask what they will do first thing Monday. If they have to interpret, translate, or think hard, it is not a plan. It is a direction. Directions are fine in strategy documents. They are useless in execution documents.
One more constraint on the build. No setup phase longer than three weeks. If your quarter requires six weeks of building before anything runs, you have written a project plan, not an execution plan, and you will spend half the quarter with nothing to measure. Ship something rough by week three and improve it while it runs.
Take the capacity haircut
Thirteen weeks is a calendar fact. It is not your capacity.
Subtract public holidays. Subtract the week two people are at a conference. Subtract the week a major client escalates and swallows everyone’s attention. Subtract illness, a resignation, an equipment failure, a compliance deadline. In a small business, the realistic figure for genuinely productive weeks on new work in a quarter is closer to eight or nine.
Plan at roughly 70% of the calendar. Not because you are lazy, but because plans built at 100% capacity fail in week four and then get abandoned entirely, which costs far more than a modest plan delivered fully.
Then do the part almost nobody does. Write the stop list.
In a twelve-person company, everyone already has a full-time job. Capacity is conserved. Every new commitment displaces an existing one, and if you do not decide what gets displaced, the plan silently displaces whatever is least urgent, which is usually the plan itself. A stop list looks like: pause the podcast for the quarter, drop the two smallest retainer clients, move the monthly all-hands to quarterly, stop responding to inbound RFPs under $5,000. Specific removals, named out loud, with the same seriousness as the additions.
If you cannot name a single thing you will stop, you have not planned. You have hoped.
Pick one weekly number and one name
Every 90-day plan needs a single input metric that moves weekly and sits inside your control.
Revenue is not that metric. Revenue is the scoreboard, and in most businesses it lags the work by weeks or months. Track something upstream: qualified conversations booked, proposals sent, discovery calls completed, activations in the first seven days. Something you could count on a Friday afternoon and know whether the week was real.
The definition of “qualified” matters enormously here. A team that counts every form fill as a lead will hit its number and miss its goal, then conclude that the plan failed when in fact the metric lied. Define the input tightly enough that hitting it should mechanically produce the outcome.
Then attach one name. Not a department, not a committee, not “marketing and sales together.” One person who is accountable for the number even when the work is shared. Two owners is the reliable way to produce zero owners.
The weekly review should take thirty minutes and answer three questions: what was the number, what caused it, and what changes this week. Same time, same day, every week. The discipline of the cadence matters more than the sophistication of the dashboard. A plan reviewed once at day 90 is not a plan. It is a bet.
The day 45 cross-check
Halfway through, you need to know whether to persist or change. Most teams handle this badly. They either abandon a working plan too early because results feel slow, or they keep grinding a broken theory because “we committed to the quarter.”
There is a clean way to tell the difference. Put your input metric and your outcome metric side by side and read the combination.
- Input hit, outcome missed. Your execution worked and your theory is wrong. You booked 67 conversations a month and closed almost nothing. Do not push harder. Change the lever. The problem is downstream, likely in the offer, the pricing, or the fit of the people you are attracting.
- Input missed, outcome missed. An execution problem, not a strategy problem. Keep the theory. Fix capacity, ownership, or scope. Usually the honest cause is that the stop list was never written.
- Input missed, outcome hit. Something else produced the result. Find out what it was before you take credit. Your metric may be measuring the wrong thing entirely.
- Both hit. Increase the dose. This is rarer than teams expect, and when it happens the instinct should be to add resources to the thing that works rather than starting something new.
That first row is the one worth memorizing. Teams routinely respond to “we hit our activity target and revenue didn’t move” by doubling the activity target. It is the most expensive mistake in quarterly planning, and it is entirely avoidable if you read the two columns together instead of separately.
What the whole thing looks like assembled
Back to the services firm targeting $400,000.
The arithmetic says 200 qualified conversations. Their current rate makes that implausible, so they change the equation: raise average engagement from $8,000 to $11,000 by bundling implementation support, which drops the requirement to 36 clients and 145 conversations. Still a stretch, but reachable.
Diagnosis of the constraint: they get plenty of inbound interest, but 60% of first calls end with “we’ll think about it.” That is not a volume problem. That is a qualification and offer problem. Substitution test confirms it. Swapping in “run more ads” makes the plan worse, not neutral.
The lever: tighten the front end so unqualified people self-select out, and rebuild the first call around a specific, priced outcome instead of a general capability pitch. This is offer construction work, not marketing work.
Reps: rewrite the intake questions in week one. Rewrite the call structure in week two. From week three, every single first call runs the new structure, recorded, with a one-line note on where it stalled. Twelve weeks of that produces a real dataset.
Input metric: number of first calls that end with a scheduled next step and a stated budget. Target: 60%, up from 40%.
Stop list: no more free strategy audits for prospects under $10,000. The founder stops attending discovery calls for small accounts. The quarterly webinar is postponed.
Owner: the head of client services. One name.
That is a 90-day plan. It fits on one page, it names what stops, it can be checked every Friday, and on day 45 it will tell you whether the theory or the execution is at fault.
The failure patterns worth watching for
A few things reliably kill otherwise sound plans.
The plan that depends on hiring. Recruiting, onboarding, and ramping a new person consumes most of a quarter. If your plan assumes someone joins in week three and contributes by week five, the plan has a fantasy embedded in it. Build quarters around the people you already have.
The plan that requires a new tool. Tool migrations always take longer than the estimate and rarely change outcomes on their own. Be suspicious of any quarter whose critical path runs through a software implementation.
The plan nobody can recite. Ask three people on Wednesday of week six what the quarter’s priority is. If you get three different answers, the plan exists in a document and nowhere else.
The plan that measures the wrong upstream number. Related to the qualification problem above. Teams optimize what they count. If you count the wrong thing, you will get very good at producing it. This is how businesses end up with impressive traffic charts and flat revenue, or with acquisition costs that quietly climb while volume looks healthy.
Skipping the diagnosis. If you are not sure where the drop-off happens, spend the first two weeks finding out rather than guessing. A structured look at where people leave the process, whether that is a conversion audit or a review of thirty recorded sales calls, is not a delay. It is what prevents you from spending eleven weeks improving something that was never the problem.
A last thought on ambition
There is a common belief that small plans produce small results, so you should stretch. In my view that gets it backwards for teams under about fifty people. Small teams do not fail from insufficient ambition. They fail from too many simultaneous commitments, none of which get enough attention to work.
The most ambitious thing a small company can do in a quarter is pick one constraint, put real weight behind it, and refuse to be distracted for thirteen weeks. That is rarer, and harder, than writing a big number on a whiteboard.
Four quarters of that, each one built on what the last quarter proved, will outperform four years of annual goals nobody converted into Monday morning behavior. The compounding does not come from the size of the goal. It comes from finishing.
