Your Weekly Business Review Is Rebuilt from Scratch Every Monday

It is Sunday, 9:47 PM. Your COO opens the WBR deck template from last week. 34 slides. Four of the six dashboards feeding those slides changed a metric definition inside the last seven days. Three tabs in the source Google Sheet are broken because the RevOps analyst renamed a column on Friday afternoon. The pipeline coverage slide reads 3.2x on the deck and 2.4x on the live Salesforce dashboard.

She opens Salesforce. The definition of qualified pipeline changed on Thursday when the CRO added a stage-gate. The 3.2x number pulls from a Notion snapshot the analyst pasted on the 30th of last month. The 2.4x number is live. She has 90 minutes before the Monday meeting where six executives read this deck at 8:30 AM.

She opens Slack. She pings the RevOps analyst on his phone. He is at dinner. She pings the FP&A lead, who tells her the burn number on slide 14 is a placeholder because the month-end close has not landed the June actuals. She pings the head of customer success, who confirms the churn slide is missing the two accounts that gave notice on Friday.

Weekly business review is a function. Most Series B and C teams have not staffed it because the first WBR deck at Series A was 12 slides that the COO built in 40 minutes on a Sunday. The deck grew to 34 slides across four business units in eighteen months. The function lives in the gap between the COO who owns the meeting, the RevOps analyst who owns pipeline, the FP&A lead who owns actuals, the CS lead who owns churn, the head of product who owns activation, and the CEO who reads the deck at 8:15 AM. On the org chart it sits under Operations. In practice it sits inside a Google Slides file that gets duplicated every Sunday night.

The 34 slides nobody rebuilds twice

Pull the last four Monday decks and diff them. Count the slides where the metric definition changed and the prior week's number was not restated. Count the slides where the source dashboard is a screenshot instead of an embed. Count the placeholder text that reads TBD or Updating. Most teams past Series A find 8 to 14 slides with a stale definition, 12 to 20 slides sourced from a screenshot, and 3 to 6 slides with a placeholder that survives to the meeting.

Walk one slide. Pipeline coverage. The definition of qualified pipeline moved twice in Q2 as the CRO tightened stage-gates. Neither move landed as a footnote on the slide. The prior four weeks show 3.4x, 3.1x, 3.2x, 3.2x. The live dashboard reads 2.4x. Two of the six executives spend 11 minutes in the meeting arguing about which number is right. The head of sales says the ramp is on track. The CFO says the coverage is thin. Neither statement is wrong against the number they are reading. Both are reading a different number.

The team that should own this knows it is broken. The RevOps analyst spends four hours every Sunday rebuilding four pipeline slides from a Salesforce report he exports by hand. The FP&A lead pushes actuals into the deck at 6 AM Monday after the overnight sync from NetSuite. The CS lead updates the churn slide from a Zendesk export that lags account-level cancellations by 48 hours. Nobody owns the definition file. Nobody owns the audit trail. The COO reads the deck for the first time in the meeting.

Hiring a BizOps lead is the slow answer

The textbook fix is a business operations analyst or a chief of staff. Loaded comp in the US runs $130K to $190K a year. Months one through two go to reading the last quarter of decks, mapping the source dashboards, and shadowing the COO through one full quarter of WBRs. Months three through six are when three of the 34 slides get rebuilt against a canonical definition file, one dashboard gets embedded live, and the Monday meeting starts on time.

The fractional version is faster to start and stops at the same wall. Six to nine thousand a month buys eight to twelve hours a week of senior BizOps time. The first month rebuilds two dashboards and writes the first definition file for four metrics. The other 30 slides stay on the Sunday-night rebuild cadence because the hours run out.

Both versions assume the work is a person rebuilding a deck. The work itself is watching every source system for a metric definition change, restating the prior four weeks whenever a definition moves, pulling every dashboard into the deck as a live number rather than a screenshot, drafting the two-sentence commentary that names the delta against last week and the delta against plan, flagging the placeholder before the deck goes out, and rebuilding the deck as a Monday morning artifact rather than a Sunday night scramble. On 34 slides across six functions that is 30 to 50 hours a week of senior operations work, and no single hire clears that pile on top of running the meeting.

What a fractional AI weekly reporting function does

Hand the Salesforce, NetSuite, Stripe, Zendesk, Amplitude, and HRIS exports, the current WBR template, the definition file for every metric, the SaaS subscription list, the CRM stage-gate history, and the meeting recording archive to a fractional AI agent that runs on a weekly cadence with daily source-system watches. The agent does the work a business operations analyst, an FP&A analyst, and a chief of staff would do together. The cadence is daily on definition changes, weekly on the deck itself, per-slide on the commentary, and quarterly on the KPI tree rebuild.

Every metric definition captured the day it changes. The stage-gate move on Thursday lands as a footnote on the pipeline slide by Friday morning. The prior four weeks restate against the new definition on the same commit. The 11-minute meeting argument over which number is right stops happening.

Every slide sourced from a live embed, not a Sunday screenshot. Pipeline coverage pulls from Salesforce at meeting-open, churn pulls from the CS system at 7 AM Monday, burn pulls from NetSuite after the overnight sync. Screenshots stay in the archive folder. Same shape as the pricing page function on the sales side, run on the reporting side.

Two-sentence commentary drafted per slide. Delta against last week, delta against plan, and the one specific driver named. The pipeline slide reads coverage at 2.4x, down from 3.1x last week, driven by the two enterprise deals slipping from Q3 to Q4. The COO edits or ships. She does not write from scratch at 10 PM.

Placeholders killed before the deck goes out. Any slide reading TBD or Updating at 6 PM Sunday triggers a routed request to the owner with the specific missing input and a two-minute template to fill. The 34-slide scramble collapses to a Monday morning review of four routed asks.

The KPI tree rebuilt quarterly against the plan. Every metric on the deck ties back to a plan number and a definition owner. The 34 slides collapse to the 18 that drive a decision. The other 16 move to a monthly appendix and the Monday meeting runs in 45 minutes instead of 75.

The unit economics of a Sunday-night deck

A Series B company at $17M ARR running a 34-slide WBR is burning three specific things. The COO, the RevOps analyst, the FP&A lead, and the CS lead spend a combined 22 to 34 hours every week on deck assembly against a fully loaded hour of $170 to $260. That is $16K to $37K a month of senior operations time on work a live-embed pipeline covers. Six to nine hours a week come back inside the first sprint.

The meeting itself is the second line. Six executives, 75 minutes, roughly $130 to $210 an hour loaded per attendee. That is $1,000 to $1,600 of executive time every Monday. When 11 of those minutes go to arguing definitions, the meeting loses $150 to $240 a week to a footnote that should have shipped on Friday.

The decision lag is the third line. A pipeline number that reads 3.2x on Monday and 2.4x in reality drives a hiring plan the CFO builds on the wrong denominator. On a company shipping $470K in monthly new ARR against a $1.1M monthly burn, two weeks of hiring lag on the correct coverage number is $80K to $140K of spend that should have paused. The BizOps hire runs $140K to $190K loaded with a three to five month ramp before the deck stabilizes.

A 14-day sprint to stand up the agent runs in the low to mid five figures. Ongoing cost lands closer to one contractor than a BizOps hire. Live embeds land on eight slides in week one. The definition file ships in week two. The Monday commentary drafts at 6 AM before the sprint closes.

What changes after the sprint

Picture the same Sunday, 9:47 PM moment, thirty days after the sprint ships. The COO does not open the deck. The deck built itself at 6 PM against live embeds. The pipeline slide reads 2.4x with a two-sentence commentary naming the two slipped deals. The churn slide reflects the Friday cancellations. The burn slide pulls June actuals from the close pack that landed on the 8th.

By 8:15 AM Monday the CEO reads a deck with zero placeholders, one footnote on the stage-gate move, and 18 slides instead of 34. The meeting starts on time. The pipeline discussion runs four minutes on the delta and the two named deals, not eleven minutes on the definition. The CFO signs off on the paused hiring plan by 9:20 AM. The COO gets her Sunday back.

If your WBR currently lives on a Google Slides file the RevOps analyst rebuilds every Sunday from four dashboards and three broken tabs, the version where the deck ships itself at 6 PM Sunday with live embeds and two-sentence commentary per slide is fourteen days away. Weekly business review is a function. You can hire against it, you can retain a fractional BizOps operator for it, or you can scope a sprint and have it running this month. The work is the same. The math is not.