A three-year goal is a division problem before it is a strategy. Most of them fail the arithmetic, not the ambition. “Triple the business by 2029” divided by 36 months is a number you either can or cannot produce with the people, hours, and equipment you have, and almost nobody does that division before writing the goal down.
Doing it first changes what you write. It also changes the horizon you should be planning against, because three years is longer than it sounds.
What the survival curve says about a three-year plan
The Bureau of Labor Statistics tracks every cohort of new private-sector establishments from the year they open. Of those that opened in the year ending March 1994, 60.6 percent were still operating three years later, and 49.6 percent reached five years. (bls.gov) BLS notes that survival curves follow a similar path regardless of birth year. (bls.gov)
The more useful number in that table is not the headline. It is the year-by-year rate. Of that same cohort, 79.6 percent survived year one, but of the businesses that made it through year one, 85.6 percent made year two, then 89.0 percent, then 89.6 percent, then 91.4 percent. (bls.gov) The risk is heavily front-loaded. Each year you survive, your odds of surviving the next one improve.
That has a direct planning consequence. A three-year goal is not three equal years of risk. It is one hard year followed by two that are progressively less likely to kill you, which means the plan needs to be built around getting through the near term intact, not around the elegance of the year-three number.
Write the goal as capacity, not revenue
Here is the part I would push hardest, and it is an argument rather than a finding. Most three-year goals are written as revenue. Revenue is a poor goal because you do not control it directly. It is the output of demand, pricing power, and competition, and you can do everything right and still miss it because a larger competitor opened nearby.
Capacity is different. Capacity is what you actually build: how many jobs you can complete in a week, how many clients one person can hold without service slipping, how many units come off the bench per shift, at what margin. You control it. And revenue is downstream of it, which means a capacity goal usually produces the revenue goal as a side effect while staying inside things you can decide.
So convert. If the three-year target is 900,000 dollars a year at a 4,000 dollar average job, that is 225 jobs a year, or just under 19 a month, or between four and five every week without fail. Now ask the only question that matters: what is the most jobs the business has ever completed in a single week, and what broke first when it did? That answer, not the revenue figure, is the actual plan. If the record is three a week and the third one meant working Saturday, the three-year goal is not a sales problem. It is a hiring, scheduling, or equipment problem wearing a sales problem’s clothes.
The 90-day number that tells you whether it is alive
A three-year goal you cannot check for three years is a wish. The check is a leading indicator: the smallest number that moves before revenue does and that you can read inside 90 days.
For a capacity goal it is usually one of three things. Throughput per week, measured the same way every week. Time from enquiry to delivered work, which tells you whether the constraint is demand or the schedule. Or margin per job, which tells you whether extra volume is worth having at all. Pick one, write down today’s figure before you start, and set a date 90 days out to look again. If it has not moved, the plan is wrong and it is better to know in the first quarter than in the third year. Deciding which of the three actually matters is easier once you have settled a priority rule for what counts as important.
If the arithmetic says the capacity has to grow before the revenue can, a 90-day expansion plan that audits real throughput first is the next step rather than a bigger sales target.
Where the number lives
This does not need software, and a spreadsheet genuinely is enough for the arithmetic. What it needs is one place where the target, the weekly figure, and the 90-day check date sit together and can be seen by whoever else is meant to care. Prices verified on the vendors’ own pages today.
Notion’s free plan is $0 per member per month and covers databases with custom properties, which is enough to hold the target and a weekly log. Plus is $10 per member per month if you need several people writing to it, and Business is $20 per member per month. (notion.com/pricing)
If you already pay for a productivity suite, use it rather than adding another subscription. Google Workspace Business Starter is $7 per user per month on an annual commitment and Standard is $14, and Sheets plus a recurring calendar entry for the 90-day check covers this entirely. (workspace.google.com/pricing)
The prompt that produced the original version of this article, on establishing clear long-term goals, is built to run that conversation with a team and assign owners to each objective; the wider library at BusinessPrompter.com covers the adjacent planning decisions.
What the capacity number does not decide
Capacity planning has an obvious ugly version, where the answer to every constraint is that the current team should absorb more. That version does not survive three years, because the throughput record you are measuring against was almost certainly set on a week nobody wants to repeat. The honest use of a capacity goal is the opposite: it is the argument for the hire, the second van, or the scheduling change, made with a number instead of a feeling, well before the strain shows up in customer complaints. A capacity ceiling is the case for building the team, not for testing how far it stretches.
It also will not tell you whether the goal is worth wanting. The arithmetic can tell you that 225 jobs a year requires a fourth technician; it cannot tell you whether running a four-technician business is the life you want. That question stays with you, and it is worth answering before you spend three years executing against a number you inherited from a competitor.
Do the division first
Before the planning session, not during it: take whatever annual number you are aiming at by year three, divide it by your average job or order size, then divide that by 52, and write the weekly figure next to the best week the business has ever had. Two numbers on one line. Most of the strategy argument you were going to have resolves itself the moment those two numbers are sitting beside each other, and the ones that do not resolve are the real conversation.
Frequently Asked Questions
Why plan three years out when half of businesses do not last five?
Because the risk is front-loaded rather than evenly spread. In the BLS cohort that opened in the year ending March 1994, 79.6 percent survived the first year, but 85.6 percent of those survivors made year two and 91.4 percent of the remaining ones made year five. (bls.gov) A plan built to get through the near term intact is what earns the later years.
Should the three-year goal be a revenue number or something else?
Prefer capacity. Revenue is an output you do not directly control, while capacity is what you build: jobs completed per week, clients one person can hold, units per shift, and the margin on each. Set the capacity target and the revenue usually follows from it while staying inside decisions you can actually make.
How do I know within 90 days whether the plan is working?
Pick one leading indicator that moves before revenue does: throughput per week, time from enquiry to delivered work, or margin per job. Record today’s figure before you start, set a date 90 days out, and look again. No movement means the plan is wrong, which is far cheaper to learn in the first quarter than in the third year.
Do I need to buy software to track this?
No. A spreadsheet covers the arithmetic, and if you already pay for Google Workspace at $7 per user per month for Starter or $14 for Standard, Sheets plus a recurring calendar reminder is sufficient. (workspace.google.com/pricing) Notion’s free plan at $0 per member per month also holds the target and a weekly log if you prefer a database. (notion.com/pricing)
