Lumeo enters the next twelve months with £6.2m in cash and a burn rate rising from £480k to £550k as six enterprise sales hires ramp through Q3. The naive runway of thirteen months sounds adequate against a twelve-month plan — it is not, because nearly all of the buffer rests on a single cash event: a £1.6m annual renewal from the account representing 22% of ARR, due in month five, currently under formal procurement review by a newly appointed VP of Operations with no contractual protection and no identified switching cost in Lumeo's favour. Strip that inflow and the base case does not survive. The honest range runs from £1.8m at exit if everything goes right, to a forced decision point at month eight if the renewal loss and the Series C raise go wrong simultaneously. The central finding across all three scenarios is that the renewal and the raise are not independent risks — they share a common trigger.
A 22% account lost to a competitor mid-diligence is an ARR quality signal that Series C investors will reprice immediately, turning two manageable risks into one compounding crisis. The one assumption that holds the plan together is that the raise proceeds on its original terms regardless of what the renewal does. That assumption is false in the crisis case and fragile in the downside. The actions that change the odds are not operational — they are sequencing decisions: confirm the renewal before diligence opens, secure a bridge facility before either risk fires, and pre-stage the lever set so the response to a trigger is a 30-day execution, not a debate. Lumeo is a vertical SaaS business serving mid-market general contractors and subcontractors in the UK construction sector, currently one year past its Series B raise.
The company is planning through a twelve-month horizon, with the stress test triggered by a board meeting scheduled for the end of next month. The goal is to walk the board through the honest range of outcomes — base, downside, and crisis — alongside the actions that hold across all three, rather than present an optimistic case and absorb the hard questions in the room. The concern is structural: with £6.2m in cash and £480k in monthly burn, the naive runway is roughly thirteen months — almost exactly equal to the planning period. That leaves virtually no buffer for a deal slip, a hiring cost overrun, or a soft quarter. The board meeting is an opportunity to get ahead of that, but only if the stress test is built on honest assumptions rather than the plan-deck version.
The £1.8m exit balance depends almost entirely on the £1.6m renewal arriving in month five. Strip that single cash inflow and the base case does not survive — which means this is not a conservative case. It is the case where the highest-risk assumption happens to go right. The Series C also has to close without slippage, because three months of runway at exit burn leaves no room for a slow raise.
£650k at month twelve is not a safe landing — it is approximately six weeks of runway at the post-lever burn rate. A Series C process that takes longer than expected, or a second revenue miss in H2, would make this a cash-out scenario rather than a tight-but-manageable one. The downside is survivable only if the fundraise is already well advanced when the renewal trigger fires. The board needs to understand that this case is not 'uncomfortable but fine' — it is 'raise or cut deeper, immediately.'
This is the scenario management is currently structured to avoid rather than prepared to navigate. Eight months of runway with a stalled raise and a weakened ARR story leaves no good options — a distressed fundraise, a forced acqui-hire, or a covenant breach if any debt is in the structure. The actions that would make this survivable — pre-qualifying alternative investors, securing a bridge commitment, or identifying a second-tier cost base well below £380k — are not currently on the plan. The board needs to know what the crisis playbook actually is, not just that the scenario exists.
| Scenario | Exit cash | Runway | Key change |
|---|---|---|---|
| Base case | ~£1.8m | Exits at ~£1.8m — roughly 3 months of runway at exit burn | Renewal holds; ARR to £10m; burn to £550k |
| Downside | ~£650k | ~10 months — exits at ~£650k, roughly 1.5 months of runway at exit burn | Renewal lost; four hires paused; marketing cut; levers pull burn to £400–420k |
| Crisis | Forced decision point at month eight — crisis case does not survive to month twelve | ~8 months — hits emergency cash threshold before end of planning period | Renewal loss cascades into the raise; full lever set pulled including G&A |
| Action | Trigger | Owner | Lead time |
|---|---|---|---|
| Treat the 22% account renewal as a live enterprise sale — board-level business case, multi-threaded below the new VP of Operations, champions identified inside the account. The goal is a verbal close by week four, so renewal status is confirmed before Series C diligence opens. This is not a relationship management task; it is a structured sales process with a hard deadline. | Immediate — starts this week regardless of renewal tracking | CEO and VP of Sales | Week four verbal close; month five cash confirmation |
| Secure a conditional bridge facility from existing investors — a committed line that activates automatically if the Series C slips beyond an agreed date or if a single account representing more than 15% of ARR is lost. The facility does not need to be drawn to do its job: its existence removes the scenario where a stalled raise and a renewal loss are simultaneous crises with no liquidity backstop. | Immediate — target conditional commitment within two to four weeks, before Series C process opens | CEO and Board | Two to four weeks to conditional commitment |
| Pre-stage the full cost lever set so that a £150–170k monthly reduction is a 30-day execution decision, not a debate. Document the specific cuts — hire freeze, S&M to minimum, G&A reductions — with named triggers, sign-off authority, and sequencing. The downside lever (£130–140k) and crisis lever (£150–170k) should both be documented separately so the response is calibrated to the scenario, not improvised under pressure. | Activates when renewal is confirmed lost or Series C diligence stalls beyond 30 days | CFO | 30 days from trigger to full effect |
| Accelerate the next tier of enterprise accounts to structurally reduce revenue concentration — explicit pipeline targets designed to bring the largest single account below 15% of ARR by end of 2027. The outcome is 18–24 months away, but the pipeline decisions — which segments to target, which deals to prioritise, which hires to orient toward expansion — have to be made in the next 60 days to hit the 2027 target. | Baseline action — not stress-triggered; pipeline decisions required within 60 days | VP of Sales and VP of Customer Success | 60 days for pipeline decisions; 18–24 months for structural outcome |
Lumeo's runway is not healthy — it is contingent. The thirteen months of naive runway against a twelve-month plan sounds like a buffer; it is not. The base case exits at £1.8m only because a single £1.6m cash inflow arrives in month five from an account under active competitive review with no contractual protection. Remove that inflow and the base case does not survive. The downside exits at £650k — approximately six weeks of runway at post-lever burn — which is survivable only if the Series C is already well advanced when the renewal trigger fires. The crisis case does not reach month twelve at all: it hits an emergency cash threshold at month eight, when a stalled raise and a lost renewal land simultaneously and the remaining lever set cannot compensate for the absent cash. The honest characterisation for the board is this: Lumeo has adequate runway if two high-dependency events both go right on schedule. That is not a healthy position. It is a position that requires immediate action on sequencing, not reassurance about the plan.
What this is. This Cash Runway Stress Test was built through a guided conversation between Demo and Ren.
How it was built. All analysis reflects your own thinking — structured using established frameworks, sharpened, and presented clearly.
This report was produced by Ren, an AI advisor built by Renatus. It is based on information you provided during the conversation and established frameworks. It is intended to support — not replace — your own judgement. All conclusions should be reviewed before acting on them.
Renatus applies the underlying principles of established methods and credits their origin where relevant. Named frameworks, methods, and instruments are the property of their respective owners. Reference to them does not imply endorsement or affiliation.
3 frameworks were used to structure your thinking:
