NEXT|GEN
Data and Analytics2Build On This

Monthly Business Report

What This Guide Covers

  • How to turn the numbers you're already tracking into a clear monthly summary you can actually learn from
  • How to use Claude to write the narrative, connecting numbers to what they actually mean for your business
  • How to build a repeatable monthly process that takes minutes, not hours

This guide works best once you've built out other guides in this category, since it pulls together data from weekly attendance, membership exports, churn analysis, and the profitability calculator.

Why This Matters

Numbers on their own don't tell you much without context. This guide's job is synthesis, turning scattered numbers from a few different sources into one clear picture.

Case Study

Tempo Studio

Tempo Studio had been tracking weekly attendance and running occasional churn checks for a couple of months, but never stepped back to look at the bigger monthly picture.

Result: The monthly summary surfaced a slow but steady decline in one specific class format.

Step-by-Step Guide

  1. 1

    Gather your sources for the month

  2. 2

    Bring it all to Claude for a first draft

    AI Prompt
    Here's my business data for [month]:
    
    Weekly attendance trends: [summarize or paste]
    Churn or retention notes: [summarize or paste]
    Class profitability notes: [summarize or paste, if available]
    
    Write a short monthly business report, covering what happened this 
    month, what changed compared to prior months, and 2 to 3 things 
    worth paying attention to next month. Keep it to about a page.
  3. 3

    Push back on anything that feels generic

  4. 4

    Add your own context Claude wouldn't know

    AI Prompt
    Add this context to the report: [anything relevant that isn't in 
    the numbers, e.g. a coach change, a facility issue, a local event].
  5. 5

    Save each month's report somewhere you'll actually revisit

  6. 6

    Make it a fixed monthly ritual

Frequently Asked Questions

What if I haven't built the other Data and Analytics guides yet?

This guide still works with whatever numbers you do have.

How long should the report actually be?

About a page is usually the right length.

Should I share this report with my coaching team?

A simplified version can be a useful way to keep a team aligned.

What if a month was unusual, like affected by a facility closure or a coach transition?

Note that context directly when generating the report.