$65M+ Revenue InfluencedAI Training for TeamsAI TransformationMarketing / Sales / HR / Finance6+ Years Building Growth Systems125+ Projects Delivered$65M+ Revenue InfluencedAI Training for TeamsAI TransformationMarketing / Sales / HR / Finance6+ Years Building Growth Systems125+ Projects Delivered$65M+ Revenue InfluencedAI Training for TeamsAI TransformationMarketing / Sales / HR / Finance6+ Years Building Growth Systems125+ Projects Delivered$65M+ Revenue InfluencedAI Training for TeamsAI TransformationMarketing / Sales / HR / Finance6+ Years Building Growth Systems125+ Projects Delivered$65M+ Revenue InfluencedAI Training for TeamsAI TransformationMarketing / Sales / HR / Finance6+ Years Building Growth Systems125+ Projects Delivered$65M+ Revenue InfluencedAI Training for TeamsAI TransformationMarketing / Sales / HR / Finance6+ Years Building Growth Systems125+ Projects Delivered$65M+ Revenue InfluencedAI Training for TeamsAI TransformationMarketing / Sales / HR / Finance6+ Years Building Growth Systems125+ Projects Delivered$65M+ Revenue InfluencedAI Training for TeamsAI TransformationMarketing / Sales / HR / Finance6+ Years Building Growth Systems125+ Projects Delivered
All 20 AI systems

Open-source playbook · 14 of 20 · For leaders

Weekly Business Review

Monday’s numbers take someone half a day to pull, and nobody explains why they moved.

The systemPulls every key number into one review, flags what changed and drafts the why before the meeting.

// The problem

Half a day to pull the numbers. Nobody to explain them.

Someone exports from four tools, pastes it all into a sheet and sends it round on Monday morning. Then the meeting asks why leads are down, and the answer is “I’ll find out.”

  • Exported from the CRM
  • Downloaded from LinkedIn Ads
  • Copied from billing
  • Pasted from the help desk
MetricThis weekWhy?
2Qualified leads151ask Priya?
3Win rate31%good week?
4Churned revenue$6.2kchecking
5Open support tickets61
Sent round at 10:40 on Monday. The meeting started at 10:00. Sample, fictional company.

// How it works

Every number in one scorecard, and a why for the ones that moved.

On Sunday night it pulls each number from its source and compares it with last week and the target. The numbers that moved most get a drafted reason, with where it came from. Their owner confirms it before Monday.

Weekly business reviewWeek 42 · sample scorecard, fictional company

  • Better than last week
  • Worse than last week
  • Target
  1. New bookingsMaya Chen, Sales

    Last week$88k

    This week$92k

    Target$90k

    +5%

  2. Pipeline createdMaya Chen, Sales

    Last week$395k

    This week$410k

    Target$400k

    +4%

  3. Qualified leadsPriya Raman, Marketing

    Last week198

    This week151

    Target190

    −24%

    Why it moved AI draft

    The LinkedIn “Ops leaders” campaign paused on Tuesday when its monthly budget ran out. It brought 41 of last week’s 198 leads. Every other channel was within its usual range.

    LinkedIn Ads · campaign historyCRM · leads by source

    Confirmed by Priya

  4. Win rateMaya Chen, Sales

    Last week22%

    This week31%

    Target25%

    +9 pts

    Why it moved AI draft

    Smaller deals closed faster after the new two-week pilot offer: 5 of this week’s 7 wins used it. Deals over $50k won at the usual rate.

    CRM · closed deals

    Waiting for Maya: shown as a draft until then

  5. Churned revenue (monthly)Tom Becker, Customer success

    Last week$1.0k

    This week$6.2k

    Targetunder $1.5k

    +$5.2k

    Why it moved AI draft

    Two customers left: Ostra Clinics ($3.9k a month, moved to an in-house tool) and Pellbrook ($2.3k, closed its US office). Both were flagged as at risk in September.

    Billing · cancellationsCRM · account notes

    Edited and confirmed by Tom · added why Pellbrook left

  6. Cash collectedInes Moreau, Finance

    Last week$121k

    This week$118k

    Target$110k

    −2%

  7. Open support ticketsKofi Mensah, Support

    Last week58

    This week61

    Targetunder 60

    +5%

Flagged: any number that moved more than twice its usual weekly swing. Numbers come straight from the source; the AI never types one.

// Sunday night → Monday 9 am

Ready before anyone opens a laptop. Checked before anyone walks in.

  1. Sun 9:00 pm

    Pull

    Reads every number straight from the CRM, billing, ad accounts and help desk into the scorecard sheet.

  2. Sun 9:10 pm

    Compare

    This week against last week, the 8-week trend and the target. Flags any number that moved more than twice its usual weekly swing.

  3. Sun 9:15 pm

    Draft the why

    For each flagged number, looks at what changed nearby (a paused campaign, a lost customer, a new offer) and writes a short note with its source.

  4. Mon 7:00 am

    Owners check

    Each owner gets their notes in Slack or Teams: confirm, edit or reject. Nothing is final until they do.

  5. Mon 9:00 am

    The meeting

    The review opens on the flagged numbers. Confirmed notes are marked as confirmed; anything else shows as a draft.

Rules for every “why”

  • Only causes it can point toEvery note names the report, campaign or record it came from.
  • “No clear cause found” is an answerIf nothing explains the move, it says so and asks the owner instead of guessing.
  • Numbers, not peopleIt explains what moved, never who to blame. No ratings, no rankings.
  • The owner has the last wordOwners confirm, edit or reject every note. Their version is the one in the meeting.

// For your tech lead

Can we build it? Here’s what it takes.

The hard part isn’t the AI. It’s agreeing which numbers matter, where each one comes from and who owns it. Once that’s written down, the build takes one to two weeks.

Tools you’ll use

JobUseOr
Where the numbers liveHubSpot reports, billing, ad accounts, help deskSalesforce reports, a data warehouse
The scorecardGoogle Sheets, with SPARKLINE for the trendsExcel sparklines, Looker Studio
Pulling it every Sundayn8n, on a scheduleMake, Zapier, or a short script
Drafting the whyClaudeChatGPT, Gemini
Owner sign-offSlack messages with confirm and edit buttons, sent from n8nTeams, or email

Access it needs

  • Read-only access to the CRM, billing, ad accounts and help desk
  • Edit access to the one scorecard sheet
  • A Slack or Teams app that can message each owner

Three ways to build it

  1. Start simple1–2 days

    Keep your current sheet. Paste in the week’s numbers and run a saved Claude prompt that flags the big moves and lists what to ask each owner.

  2. Production1–2 weeks

    n8n fills the sheet on Sunday night, flags the big moves, has Claude draft each why from campaign, deal and ticket history, and asks owners to confirm.

  3. Custom3–5 weeks

    Moves the numbers into a warehouse, adds a dashboard, and keeps a log of past whys so each new note starts from what explained that number before.

Guardrails

  • Numbers come straight from the source; the AI never types or changes one
  • Every why names its source, or says no clear cause was found
  • Each owner confirms or edits their notes before the meeting
  • Unconfirmed notes are clearly marked as drafts
  • It explains numbers, never blames people

What to measure

  • Hours spent preparing the review, before and after
  • Flagged numbers with a confirmed why by 9 am
  • Notes owners had to rewrite
  • Meeting time on decisions vs. on status

Who builds and runs it

An ops or finance lead who owns the scorecard, plus someone comfortable with n8n and your tools’ reports for one to two weeks. After that, each number’s owner spends a few minutes on Monday morning confirming their notes.

// Want help building it?

We’ll build your Weekly Business Review with your team.

In 30 minutes with our founder, we’ll look at your tools and your week, and work out what your first AI systems should be and how long they’ll take.

Book a Strategy Call
Pallav KaushishFree 30-minute call with our founder · No commitmentPallav Kaushish Co-Founder, AIxGrowth