most founders describe next month in vivid detail and 18 months in marketing copy. ask them what month 40 looks like — what arr, what headcount, what leader runs eng, what round at what valuation — and the room goes quiet.
the silence is the diagnosis. month 40 is when the next-next round closes, when the org has either crossed $20m arr or it hasn't, when the eng leader you hire today turns out right or turns out to be the expensive mistake that took fourteen months to surface. the founder has no picture of it — only a spreadsheet that ends at month 24 because that's where runway runs out and the math gets uncomfortable.
a 40-month plan is not a forecast. it is a constraint set — the document that lets you decide which hire matters this quarter by anchoring it to a company that exists three and a half years from now. founders who build one make different decisions at month 4. founders who don't make decisions that look fine at month 4 and look catastrophic at month 22.
what the exercise actually is
every series a check buys roughly 24 months of runway. series b buys another 18-24. month 40 sits inside that next runway window — old enough that the company has matured, young enough that today's decisions still echo. it's the longest planning horizon where the founder's choices still control the outcome.
the exercise is to write down, in one document, what month 40 looks like. arr, gross margin, headcount by function, the next round and its target valuation, the customer profile, the geography, the product surface. it should fit on two pages. anything longer is a forecast pretending to be a plan.
then you work backwards. if month 40 has 80 people, month 24 has roughly 40, month 12 has 20, and the next hire is one of those 20. is the hire you're about to make in the path to that org? if you don't know what month 40 looks like, you can't answer the question. you'll hire whoever was available, with the credentials that looked right, for the role you needed last month — and end up with a series a vp of eng who needed to be a hands-on staff engineer for another six quarters.
without a picture of month 40, the vp-of-eng question is unanswerable. it isn't a vp-of-eng problem — it's a planning problem dressed as a hiring problem. once the founder writes down "month 40 — $18m arr, 25 engineers across three pods, the platform layer is the moat," the next move is obvious. you don't hire a vp of eng for a 25-engineer org when you have 4 engineers — you hire a hands-on lead who'll run that team to month 18 and either grow into the role or hand it off.
why founders refuse to build it
the resistance is consistent across stages and the shape of it always falls into a few patterns.
it feels presumptuous. writing down "month 40 — $25m arr" feels like predicting a future you haven't earned. the reframe most operators land on — the plan is a constraint set, not a prediction. you're not promising you'll hit $25m. you're saying "if we hit $25m, the company that gets there looks like this — make today's decisions in that direction."
it surfaces decisions the founder isn't ready to make. writing down month 40 forces you to name whether you're horizontal platform or vertical app, enterprise or mid-market, whether the next leader is a heads-down builder or an outward operator. founders postpone these because each closes off optionality. the cost — every quarterly hire gets made in the absence of the decision, and the org accretes a shape that fights the eventual answer.
it requires the cfo conversation the founder has been avoiding. the plan implies a series b valuation, series b dilution, and a current cap table conversation. founders who haven't modeled their personal dilution out to series c don't want to write down the milestone that triggers the math. so they don't write any of it.
the 40-month plan is not optimistic or pessimistic — it is the document that turns every interim hire into a question about whether that hire moves the company toward the picture or away from it.
the milestones that matter
a useful plan names the calendar moments when something has to be true. they are the points where the next decision branches.
month 12 — first enterprise ae or pmf retreat. if month 40 has $18m arr at a heavy enterprise mix, you need an ae closing $400k deals by month 12. if month 40 is product-led, month 12 is when you commit to never hiring one.
month 18 — series b conversation starts. the partners leading your b will have tracked you for two to three quarters before that meeting. the plan tells you which firms to seat at month 12, which board updates land at month 14, which metrics need to be steady at month 16.
month 24 — the series b clears or it doesn't. if it doesn't, month 40 is a different company. the plan should include the org that lives on extension capital — what gets cut, what survives, what you're still building.
how zift handles this
zift computes the milestone math from your live burn, arr, and runway every fifteen minutes. set the month-40 picture once, and the monday briefing tells you whether last week's decisions moved you toward it or away from it, and which line item moved the trajectory.
if you're a finance lead at a series a team running the same exercise across multiple entities or product lines, zift handles that too.
the plan you refuse to write is the one your competitors are using to recruit your future eng leader.