> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/getting-started/getting-started-in-slack/prep-your-monthly-business-review-from-slack.md).

# Prep your monthly business review from Slack

Most of a monthly business review is reconstruction: pulling each function's numbers, chasing the ones that are missing and reconciling the ones that don't agree. By the time the deck is ready, there's little time left to think about what it says.

Rhythms gathers updates across your connected tools and prepares the business review, so your team spends less time chasing status and more time deciding what happens next.

{% hint style="success" %}
**The short answer**

In any channel Rhythms is in, or in a DM, post `@Rhythms prep the September MBR`

Rhythms clarifies the scope, drafts from accessible sources, lists missing inputs, and drafts your business review.
{% endhint %}

<p align="center"><a href="https://api.rhythms.ai/slack/add?cta_id=gitbook_how_to_mbr" class="button primary" data-icon="slack">Try for Free in Slack</a></p>

***

## Before you start

* [**Set up Rhythms in Slack**](https://help.rhythms.ai/getting-started/getting-started-in-slack/getting-started-with-rhythms-in-slack.md)
* **Connect the tools where your team works:** The more context Rhythms can read, the less chasing you have to do

***

## Step 1: Ask for the review

#### If you already have a format

Attach a relevant document and ask Rhythms to work off it

**Try it:** `@Rhythms prep the September MBR using last month's format`

> **Also works:** *"draft the MBR from the August review doc" · "build the business review for the leadership meeting on the 14th"*

#### If you're starting fresh

**Try it:** `@Rhythms prep a monthly business review for the leadership team`

Name the month and whether this is a company-wide or team review. Rhythms may ask which review series or prior document to use. For a first MBR, say so and supply a template or the sections you want.

**Try it:** `Company-wide, first MBR. Use headline outcomes, changes, risks and missing inputs, then decisions and owners. Keep unknown numbers and owners explicit.`

***

## Step 2: Provide context, review the draft and fill the gaps

#### Provide context

Connect tools where your teams do their work. Then point Rhythms to the channels, projects, documents and reports that matter for this review.

<details>

<summary>See examples here!</summary>

<table><thead><tr><th width="189.640625">Your function</th><th>Worth connecting</th><th>What it adds to the review</th></tr></thead><tbody><tr><td>Leadership and Operations</td><td>Google Sheets, Google Drive</td><td>Performance against plan and each team's review inputs</td></tr><tr><td>Program management</td><td>Jira, Asana</td><td>Milestones, dependencies and cross-team blockers</td></tr><tr><td>Engineering</td><td>Jira, Linear, Datadog</td><td>Delivery progress, blockers and slipped commitments</td></tr><tr><td>Marketing</td><td>HubSpot, Mixpanel</td><td>Campaign pipeline and conversion</td></tr><tr><td>Product</td><td>Linear, Mixpanel</td><td>Launch progress, adoption and retention</td></tr><tr><td>Sales</td><td>HubSpot, Salesforce</td><td>Pipeline movement, closed deals and renewal risks</td></tr></tbody></table>

</details>

{% hint style="warning" icon="lightbulb-on" %}
**Tip:** Start with the tools your team already relies on. Project, customer and reporting data make your business reviews actionable

[Manage your connectors →](https://help.rhythms.ai/connectivity/manage-connectors-for-your-workspace.md)
{% endhint %}

**Try it:** `@Rhythms draft the September MBR using #team-leads and #launch-readiness, the Launch project in Jira, our September business plan in Google Drive, pipeline in HubSpot and activation and retention in Mixpanel. Compare results with plan, link the sources and flag missing or conflicting inputs.`

Swap in your own channels, project names and document links. Use connected sources Rhythms can access, or attach the relevant files and notes in the thread.

#### Review the draft

Review a concise snapshot in Slack: performance against plan, the main risks and decisions that need attention. Keep the scorecard, supporting detail and full narrative in a Rhythms document.

**Try it:** `@Rhythms save the MBR as a document. Post a summary here with performance against plan, risks and decisions, and link to the full review.`

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FHhFwP51FiAACUgkctYKk%2Fmbr-summary.webp?alt=media" alt="September MBR summary in Slack showing performance against targets, risks, pending decisions and a link to the full review in Rhythms."><figcaption><p>A monthly review snapshot</p></figcaption></figure>

<details>

<summary>See what happens when you click on <mark style="color:blue;">"Read the full September MBR"</mark></summary>

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FB9iesiAdXL3ATgXmlZbJ%2Fseptember-mbr-executive-full-view.webp?alt=media" alt="September MBR executive view in Rhythms, with four metric cards, revenue and activation charts, risks and follow-ups, and a decisions table with owners and dates."><figcaption><p>The September MBR in Rhythms, with metric cards, charts, risks and decisions.</p></figcaption></figure>

</details>

#### Fill the gaps

Open the document link to review the full scorecard and supporting detail. If an input is missing, ask Rhythms to draft a request in the same thread.

**Try it:** `@Rhythms draft a request to Priya and Sam for the missing inputs by Thursday; show it here before sending`

> **Also works:** *"which numbers don't match last month?" · "why is pipeline coverage down?" · "move churn to the top and add a decisions page"*

**Tip: Correct it in the thread.** Specify the incorrect fact and the replacement. If you are working on a saved document, name that document so the edit applies to it.

***

## Step 3: Carry the decisions forward

Turn the review's decisions into clear next steps. Rhythms can draft a recap with owners and dates, flag anything unassigned, and help with the follow-through.

#### Choose the next action

**Try it:** `@Rhythms draft today's MBR decisions with owners and dates, and suggest follow-through you can take off our plates.`

Share the meeting notes or decisions in the thread. Ask Rhythms to keep missing owners explicit and offer quick replies to add the recap to the MBR, draft owner follow-ups, or do both. Review the recap before choosing an action.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FrH2wmCWE3lnBb5Vheia7%2Fmbr-offers-actions.webp?alt=media" alt="MBR decision recap with owners, dates and an unassigned item, followed by three quick replies: Add recap to the MBR doc, Draft owner follow-ups, and Both."><figcaption><p>Review the decisions and choose what Rhythms should handle next.</p></figcaption></figure>

#### Take work off your plate

Let Rhythms take work off your plate. In this example, Rhythms prepares messages for the owners. Nothing is sent until you confirm.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fnog9b4TaizQrWrT9hUFC%2Fmbr-owner-follow-ups.webp?alt=media" alt="After Draft owner follow-ups is selected, Rhythms produces three messages for review and flags the pilot partner access item as unassigned. The messages have not been sent."><figcaption><p>Rhythms prepares the follow-ups and can send them on confirmation</p></figcaption></figure>

<p align="center"><a href="https://api.rhythms.ai/slack/add?cta_id=gitbook_how_to_mbr" class="button primary" data-icon="slack">Try for Free in Slack</a></p>

***

## Make it a habit

**Ask about recurring prep.** Specify when the review happens and when you need the draft. Check which recurring options are available and whether a playbook was created. Do not assume that a saved document has an active refresh schedule.

**Try it:** `@Rhythms prep the MBR every month, a week before the review`

**Check in between reviews.** The business doesn't wait a month to change.

**Try it:** `@Rhythms what's changed since the September MBR?`

***

## Worth knowing

**It follows your format.** Point it at last month's review or a template and it keeps your sections, terms and order.

**It tells you what it couldn't find.** Missing or conflicting numbers are listed, not filled in.

**Sharing your documents.** Once the draft has been saved to the Library, check its link and sharing permissions before distributing it.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/getting-started/getting-started-in-slack/prep-your-monthly-business-review-from-slack.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
