The AI CEO Dashboard Kit: An Excel…

1. Key Themes

Theme: Headline growth can mask a retention problem, and retention should be the CEO's first-order metric

Fast MRR growth coexists with shrinking value from existing customers

The sample company looks healthy on top-line growth and efficiency but is quietly leaking value from its installed base.

"Northwind Metrics grows MRR about 6% a month to $2.37M ARR, and its burn multiple sits at an excellent 0.6x. Now look at the third card. 12-month NRR is 90.7%, so last year's customers are worth 9% less today, which is the kind of number a pitch deck leaves out and an investor finds in diligence."

All growth is new-logo growth, which makes the model fragile

The dashboard's takeaway is that expansion isn't contributing, so retention must be fixed before scaling spend.

"Every dollar of growth came from new sales. Burn is at its most efficient yet, but 14.5 months of runway and 1.3x pipeline coverage put retention first." (Exhibit 1)

Retention damage is lumpy and concentrated, not gradual

The NRR chart annotates a single month in which Enterprise churn dragged the metric sharply down.

"Nov 25: 2 Enterprise churns, -$10.4K MRR" and "92.2% in Nov 25" (Exhibit 1)

Theme: Metric definition errors are a hidden source of risk in investor-facing numbers

A denominator mistake can flatter the business and end up in a data room

Small formula choices can misstate the health of the business, with reputational consequences.

"One churn rate divided by month-end customers instead of start-of-month customers makes the business look healthier than it is, and it ends up in a data room with your name on it."

Methodology should be explicit on the dashboard itself

Exhibit 1's footnotes show the conventions that make the metrics comparable and defensible.

"NRR compounds the last 12 monthly NRRs and excludes reactivations; runway = cash / average net burn of the last 3 months."

Theme: Automated data validation as a CEO-grade discipline

Checks that flag bad data before anyone else sees it

The kit pairs the KPIs with an audit layer, tested by planting errors in the sample data.

"It returns the 8 numbers a board asks about, 4 charts and 14 checks that flag bad data before anyone else sees it."

"The 14-check audit tab, which caught all three errors I planted in the sample"

Theme: Founders know revenue cold but not the metrics boards and investors scrutinize

MRR is known; NRR and burn multiple are not

The author argues there is a gap between topline awareness and the sophisticated metrics asked about in board settings.

"Every CEO knows MRR to the dollar. Ask for net revenue retention or burn multiple on a board call, and most of us open a spreadsheet, pull three exports and hope the formulas hold."

Theme: Claude/LLMs as the analysis layer on top of operating data

Prompt libraries for cleaning data and anticipating investor questions

The kit bundles prompts spanning data prep through diligence prep, and extends to live dashboards once data is in a warehouse.

"10 copy-paste Claude prompts, from cleaning a messy Stripe export to the 10 questions an investor will ask about your numbers"

"The Claude Dashboards prompt that rebuilds the same view as a live dashboard once your data sits in a warehouse"

2. Contrarian Perspectives

Efficient burn and fast growth can coexist with a deteriorating business

Conventional wisdom treats a low burn multiple and 6% monthly growth as signs of excellence. The article argues the opposite signal can be hidden underneath.

Burn multiple of 0.6x is called "excellent," net burn is "down 34% since October 2024," and MRR is up 6.2% month over month.
Yet NRR is 90.7%, meaning the installed base shrinks even as new sales mask it.

"Burn is at its most efficient yet, but 14.5 months of runway and 1.3x pipeline coverage put retention first."

Pitch decks omit the metric investors find first

The article implies that selective metric presentation is the norm and that it backfires in diligence.

"...the kind of number a pitch deck leaves out and an investor finds in diligence."

Healthy-looking logo churn can understate revenue risk

Logo churn is a modest 2.0% per month, yet NRR is below 100%, and the biggest hit came from just two Enterprise accounts. This suggests that revenue-weighted retention, not logo count, is the metric to manage.

"Nov 25: 2 Enterprise churns, -$10.4K MRR" alongside "Logo churn 2.0%, 3-month average, per month" (Exhibit 1)

3. Companies Identified

Northwind Metrics (fictional)

Description: Invented B2B SaaS company used as the worked example.
Why mentioned: Illustrates how strong growth and burn efficiency can sit alongside weak retention.
Quote: "Northwind Metrics grows MRR about 6% a month to $2.37M ARR, and its burn multiple sits at an excellent 0.6x." Footnote: "Northwind Metrics is an invented company."

Stripe

Description: Payments platform whose export is the kit's primary data source.
Why mentioned: The model is built to ingest a Stripe CSV (or CRM export) and compute board-level KPIs.
Quote: "You paste a Stripe or CRM export into one Excel file, and it returns the 8 numbers a board asks about"

Claude / Anthropic

Description: AI assistant used to power the kit's prompts and dashboard rebuilds.
Why mentioned: Core tool for data cleaning, investor Q&A prep, and live dashboards.
Quote: "10 copy-paste Claude prompts, from cleaning a messy Stripe export to the 10 questions an investor will ask about your numbers"

Excel / Google Sheets

Description: Spreadsheet platforms hosting the workbook.
Why mentioned: The delivery format of the kit, with cross-compatibility emphasized.
Quote: "an .xlsx with 10 tabs and 4,300+ live formulas that also opens in Google Sheets"

The AI Corner

Description: The newsletter and publisher of the kit.
Why mentioned: Source of the kit and a library of ~200 guides and playbooks.
Quote: "The kit is one of about 200 guides and playbooks in The AI Corner, and a paid subscription opens all of them."

4. People Identified

Ruben Dominguez

Description: Author of the post (credited on The AI Corner).
Why mentioned: Built the dashboard kit and describes the founder pain point firsthand.
Quote: "So I built the kit I wanted for that moment."

5. Operating Insights

Compute KPIs from a single source export, with audit checks built in

Consolidating the numbers from one Stripe/CRM paste, rather than stitching multiple exports, reduces formula drift. Adding automated checks catches errors before they reach investors.

"Ask for net revenue retention or burn multiple on a board call, and most of us open a spreadsheet, pull three exports and hope the formulas hold."

Use a consistent, documented NRR and runway methodology

Define NRR and runway the same way every period and footnote it. Compounding trailing monthly NRRs and excluding reactivations avoids flattering the figure.

"NRR compounds the last 12 monthly NRRs and excludes reactivations; runway = cash / average net burn of the last 3 months."

Pair top-line KPIs with pipeline coverage and payback to decide where to focus

The dashboard juxtaposes runway (14.5 months), CAC payback (13.2 months), and pipeline coverage (1.3x of Q4 target) to prioritize retention over more acquisition spend.

"Open pipeline of $316K against a $250K Q4 new-ARR target." and "CAC payback 13.2 mo, 3-month CAC $17.2K" (Exhibit 1)

6. Overlooked Insights

Test your audit layer by planting errors

The author validated the checks by seeding known mistakes into the sample and confirming detection, a practical method for trusting any financial model's controls.

"The 14-check audit tab, which caught all three errors I planted in the sample"

Weighted pipeline is thin relative to open pipeline in early stages

Early-stage pipeline is heavily discounted when weighted, so headline coverage overstates near-term bookings. Discovery holds $105K open but only $11K weighted, while Negotiation is $40K open and $30K weighted. Pipeline coverage is therefore more fragile than the 1.3x suggests.

"Open pipeline by stage... gray = open, green = weighted" with Discovery "$105K" vs "$11K" and Negotiation "$40K" vs "$30K" (Exhibit 1)