Your three-year entrepreneur roadmap

Three years is a planning horizon, not a promise that the market will cooperate. The roadmap advances through proof: capability, access, payment, repetition, transferability, and stewardship.

Write the destination as a capability and a life. “I can find, sell, deliver, and govern valuable work without risking the people or assets I must protect” tells you what to practise. A valuation, birthday, title, or revenue slogan does not.

The path below is ordered but not timed. A salaried builder with family obligations may move through it in small protected blocks. A full-time founder with runway may test faster. A regulated, capital-heavy, or physical business may need professional work and financing before a low-capital service would. Stay at a stage until its gate is met; return when later evidence exposes a weak foundation.

Stage one · Establish the right to experiment

Protect the household floor, health, employment duties, reputation, and legal boundaries. Resolve conflicts involving outside work, employer intellectual property, confidential information, or regulated activity before building.

Gate: the experiment has a written loss limit, honest capacity, separate records and money where required, a stop condition, and no dependence on essential family security.

Without this gate, urgency becomes the strategy. You will accept poor customers, bad capital, unsafe promises, or hidden work because the experiment cannot tolerate delay.

Stage two · Make capability visible

Develop one commercially useful capability and the communication needed to sell and deliver it. Build proof that a sceptical buyer can inspect: a demonstration, measured improvement, work sample, reference, analysis, or clearly bounded case. State what you personally did and what remains unproven.

Gate: someone outside your immediate circle can understand the result, reproduce or verify the evidence where appropriate, and name the problem your capability addresses.

Learning without an artifact remains private potential. An artifact without depth fails under questioning. Build both.

Stage three · Earn access to a painful problem

Choose a narrow customer and workflow you can observe. Separate user pain from buyer priority. Learn the current workaround, consequence of inaction, decision process, budget logic, security or compliance constraints, and reason previous attempts failed.

Gate: independent evidence shows a recurring problem, a reachable decision-maker, a consequence worth addressing, and a reason your next test could teach something decisive.

Do not advance because people called the idea interesting. Interest is politeness until it changes behaviour, grants access, commits time, or funds a test.

Stage four · Complete an honest paid proof

Sell a bounded outcome with written scope, acceptance evidence, price, timing, responsibilities, and payment terms. Deliver it. Collect. Record the actual labour, variable cost, rework, delay, customer result, and promise you nearly broke.

Gate: value was delivered and accepted, money was collected lawfully, the economics are understood, and the customer evidence supports either another sale or a clear change in thesis.

The first transaction teaches selling, scoping, delivery, invoicing, collection, and trust at once. Its amount matters less than whether the exchange is real and honestly measured.

Stage five · Prove repetition

Narrow toward a customer type, problem, offer, acquisition path, and delivery method that can repeat. Compare customers rather than blending them. Track contribution, cash conversion, quality, time to value, retention or repeat use, concentration, and founder-dependent effort.

Gate: the result repeats under conditions you can state; weak economics are not hidden by founder labour, delayed costs, or one exceptional customer; and the thirteen-week cash view can finance the next cycle.

If the gate fails, narrow, reprice, redesign, or return to discovery. Growth cannot repair a unit that loses cash or trust.

Stage six · Transfer the work into a system

Eliminate unnecessary variation. Define the standard path, acceptance criteria, controls, escalation, documentation, and role outcomes. Automate or delegate only after understanding the work. Test whether another capable person can deliver without silent founder rescue. Gate: quality and customer value survive a real hand-off; the founder’s repeated production time declines; exceptions are visible and priced; and no critical process lives only in one person’s memory or account.

Productisation is earned here. Software, subscriptions, hiring, and process layers belong only where they improve recurring customer value or operating economics.

Stage seven · Build the institution and protect ownership

Strengthen the connected engines: customer value, distribution, delivery, people, financial control, governance, risk, compliance, and capital allocation. Give leaders outcomes and authority with evidence gates. Protect the cap table, contracts, data, cash, and the home front.

Gate: the company can detect and address ordinary problems without daily rescue; decisions and accounts can withstand review; growth remains financeable; and founder absence does not make customers unsafe.

This is the three-year outcome worth pursuing: not a guaranteed company size, but evidence of a real enterprise and a stronger operator. If the evidence says a specialised practice, productised service, or valuable professional career is the better destination, take the finding seriously. The roadmap serves the life; the life does not owe the roadmap a startup.

Run the gate review

Before advancing, write:

• • current stage and the decision being requested;
• • facts, assumptions, and forecasts kept separate;
• • evidence for and against the gate;
• • capacity, cash, people, and family cost of the next stage;
• • the bad-but-plausible case and non-recoverable assets exposed;
• • the next smallest commitment, owner, date, and acceptance test;
• • the condition that triggers pause, redesign, or closure.

Review the reasoning after the outcome. A lucky result from a weak process is a warning. A sound test with a negative result may have saved years.

para · ASC pp. 42–44, 132–134 · LG pp. 50, 67–69, 110–114 · GE ch. 42. Stage-gate, proof-of-work, and review mechanisms phrased; fixed ages, prices, activity quotas, and revenue milestones have been removed.