How to answer: What does the next 12 months look like?
Your board wants to know what the next 12 months look like. Here’s how to answer with a plan, a clear view of cash and an honest look at risk.

Every board wants to know what the year ahead holds and whether the business will be okay. It sounds like a forecasting question, but it is really a question about cash, hiring and risk. A single revenue line won’t answer it. Here’s how we’d answer it, using the example from this month’s The Build.
The question
Put simply, the board wants to know what the next twelve months look like and whether the company will stay healthy along the way. The answer needs a plan, a clear view of cash, and an honest look at what could go wrong.
The business context
The example company is Meridian Software Ltd, a B2B SaaS scale-up reporting to its board. It closed December 2025 with total revenue of $222,000 and cash on hand of $370,576. The board has agreed a plan that grows revenue 12%, and it has set a $300,000 cash floor. Two software developer hires are also on the table.
On paper, the plan looks sound. But a board will reasonably ask what happens if the largest customer leaves or sales slow down. That is where the forecast earns its keep.
The report
Board report - Meridian Software Ltd (Demo)
How we’d answer it
Build the model before you build the slides. Once the range is in place, the board conversation gets much simpler.
1. Start from the budget the board has agreed. Link revenue and expenses to the approved budget rather than rebuilding them from scratch. In this example, revenue grows 12%, and expenses are aligned to the same budget with a note on the salary assumption. Add a note to each assumption. Those notes flow into the assumptions report, which gives you an audit trail of what changed, who changed it and when.
2. Match the timing to how cash arrives. Revenue on the P&L doesn’t land in the bank on the same day. Here, about 70% is collected up front and the remaining 30% arrives in month one. That timing profile moves the balance sheet and the cash line, which is exactly where the board’s real question sits.
3. Put the cash floor where the board can see it. Set the $300,000 floor for cash on hand on the Quick Metrics bar.Any value below it turns red, so the pressure point is visible without reading a table.
4. Model the hires as separate events. Build each developer hire as a microforecast with a July start date. Each one is self-contained and layers onto the base forecast, so you can decide whether to include it and when, without rebuilding the model. Duplicate the first hire for the second and rename it.
5. Build the range with scenarios. The upside adds 8% on top of the 12% base, which takes growth to about 20%, and pulls the hires forward to April. The downside assumes the Henderson account leaves, worth about $30,000 a month, and collections slip so that 30% arrives up front and 70% in month one. The hires stay in July, and then the team tests moving them to September.
6. Show the range, then show what has to be true. In the base case, cash stays above the floor all year, with its lowest point in January at $365,836. In the downside, cash drops below the floor in January and February, recovers in March, then falls below again from September and ends the year at $179,431. The board’s real discussion is about the risks that could tip the balance, here the Henderson account and the timing of hires.
7. Let AI draft the narrative, then check it. Add business context in your company settings and report context for the period. Select the scenarios to add to a trend chart and trended income statement then run Commentary Writer. Read the draft, ask it to regenerate if it misses something, and audit any number it pulls in. Each figure can be traced back to its formula and source.
8. Make a recommendation the board can act on. The recommendation here is to proceed with the base plan and hold the two developer hires until June, then revisit in July once midyear close rates confirm the pipeline. That gives the board a clear decision, a trigger to watch and a date to return to.
The takeaway
“What does the next 12 months look like” is really three questions. Is the base plan on track? Which risks could push cash under the floor? And how should hiring move as the year unfolds? When the base case, the scenarios and the cash view sit side by side, a forecast turns into a decision the board can make.
Want to build this yourself? Start a free trial of Fathom and add a company to follow along with the same steps.
Watch this episode of The Build in full!







