From spreadsheet chaos to a board pack in an hour

A board pack has two jobs: show the numbers, and explain them. Most teams spend 90% of their time on the first job — exporting, pasting, re-colouring, checking — and squeeze the second into the night before. That is backwards. The explanation is the only part a board cannot get elsewhere.

After reviewing a few dozen (fictionalised) board decks across SaaS, marketplaces and services businesses, the same twelve charts appear again and again. Order matters: lead with the headline, then explain it.

1. 1ARR bridge — opening, new, expansion, contraction, churn, closing.
2. 2Revenue vs plan — monthly actuals against budget and last reforecast.
3. 3Gross margin — trend with the main cost drivers called out.
4. 4Burn and runway — net burn by month, months of runway at current and planned burn.
5. 5Net revenue retention — trailing twelve months, by cohort if you have it.
6. 6Gross logo churn — count and ARR, with top reasons.
7. 7Pipeline coverage — next-quarter pipeline ÷ target, by stage.
8. 8Win rate and cycle length — by segment.
9. 9CAC payback — blended and by channel.
10. 10Headcount — actual vs plan, by function.
11. 11Cash — balance, collections and DSO.
12. 12KPI scorecard — the five metrics you committed to at the start of the year, red/amber/green.

The budget almost always lives in a spreadsheet, and that is fine. Connect the sheet, model it as a plan table with one row per month and metric, and join it to actuals on those two keys. The ARR bridge is the only chart that needs real modelling:

1234567891011121314151617with m as (
    select
        customer_id,
        month,
        arr,
        lag(arr, 1, 0) over (partition by customer_id order by month) as prev_arr
    from revenue.customer_arr_monthly
)
select
    month,
    sum(case when prev_arr = 0 and arr > 0 then arr end)              as new_arr,
    sum(case when prev_arr > 0 and arr > prev_arr then arr - prev_arr end) as expansion,
    sum(case when arr > 0 and arr < prev_arr then arr - prev_arr end) as contraction,
    sum(case when prev_arr > 0 and arr = 0 then -prev_arr end)       as churn
from m
group by month
order by month;

With the charts updating themselves, the hour you save goes into commentary. Good board commentary is short and follows a pattern: what happened, why, and what we are doing about it. Three sentences per chart is plenty.

Kimo can draft the first version: for each chart it lists the largest movements and their main drivers, which you then rewrite in your own voice. Treat it as a research assistant, not an author.

• Freeze the period — lock the definitions version and the data cut-off, so numbers do not shift during review.
• One link, not a PDF — reviewers comment directly on charts; the CEO sees the same thing as the CFO.
• Export at the end — generate the PDF for the board portal only when the commentary is final.

The template is available in every Kimo Business Intelligence workspace. Explore a populated version in the dashboards section of the live demo, or read how a Nordic fintech cut its monthly close to two days with the same building blocks.