TattvaDocs
Use casesPerformance marketing

MBR / QBR assembly

Stop assembling the monthly business review by hand. Let Tattva compute the period's figures, add the context only you have, and polish the draft.

Planned

This use case needs definitions that aren't in the Library yet (marketing %, its target and NRoAS). Until your data analyst adds them, Tattva can't answer it as shown here.

The question: "Every month and every quarter we spend days turning numbers into a presentation leadership can follow. Can we start from a draft?"

The monthly and quarterly business reviews (MBR, QBR) take one or two days of analyst time each cycle, and much of it is computing the same figures again. Ask Tattva to compute the period's metrics and draft the narrative around them, add the context it can't see, then polish.

Who asks

  • The performance-marketing lead, before each MBR
  • Function heads across the company
  • Leadership preparing the board QBR

Frequency

  • MBR: monthly, in the first week after month end
  • QBR: quarterly, in the first weeks of the new quarter

What the draft draws on

Tattva can use:

  • Metric values for the period and the one before, computed from your stored definitions, with the comparisons computed in code
  • Goals linked to those metrics on Overview › Goals (see Marketing efficiency)
  • Documents you uploaded, such as last month's review or a planning memo

It can't read tracker runs, Foresight, decisions or earlier answers. Bring those in yourself: open each tracker's History tab, the Decisions page and the relevant conversations in the Sessions drawer, and paste the points you want covered into your question.

How to ask it

  • "Draft an MBR for September: marketing % vs target, NRoAS and repeat share vs August, what's working and what isn't. Context: we paused the prospecting ad sets on the 12th and the creative agency delivered 4 of 10 planned creatives."
  • "Draft a QBR for Q2: a scorecard for our goals' metrics vs Q1, and recommended commitments for Q3. Decisions this quarter: [paste]."
  • "For the board QBR: top five wins, top three risks, and the six-month outlook for each of these four metrics: [list]."

What you'll get back

A structured draft you can paste into your deck:

  1. Headline: one line on the state of the business.
  2. Goal scorecard: for each goal, current value, target, trend, status.
  3. What changed: the biggest movements in your metrics, with the comparison.
  4. Decisions and RCAs: from the context you pasted, tied to the figures.
  5. What's working, what isn't.
  6. Commitments for next period: concrete asks.

Every computed figure can be checked in the Trail, so when a board member asks where a number came from, you can show them. Points you pasted in come from you, not from a query; check them before circulating.

The outline

MBR/QBR for period [start, end]:
├── Compute each goal's metric at start vs end → scorecard
├── Compute the other key metrics vs the previous period
│   └── Flag movements over 15%
├── Add the context you pasted (tracker alerts, decisions, RCAs)
└── Draft the narrative, section by section

How to make it recurring

Reports aren't scheduled, so make this a habit:

  1. On the first working day after month end, ask for the draft in Reasoning.
  2. Click Save as report on the answer. The report opens and appears on the Reports page, shown as slides.
  3. Edit the title with Edit, and mark it Shared so the team can see it.
  4. Use Export: Print to PDF… (then choose "Save as PDF" in your browser's print dialog), Download as Markdown, or Copy Markdown to paste into your slide tool.
  5. Give yourself two or three days to polish before circulating.

What you stop doing

  • Recomputing the month's metrics and their comparisons by hand
  • Writing the first draft of the narrative from a blank page
  • Hunting through old conversations for the chart you remember (use the Sessions drawer instead)
  • Writing the same "Marketing % was X this month" sentence every time

Pitfalls

  • Treating it as final. It's a draft. The storytelling is your job.
  • Skipping the polish for the QBR. The board reads sentences, not tables. Rewrite the headline.
  • Including everything. A QBR that mentions every tracker is unreadable. Cut.
  • Sending it unread. An unedited draft sent out is worse than none.
MBR / QBR assembly — Tattva Docs