Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Try for Free in Slack


Before you start

  • 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.

See examples here!
Your function
Worth connecting
What it adds to the review

Leadership and Operations

Google Sheets, Google Drive

Performance against plan and each team's review inputs

Program management

Jira, Asana

Milestones, dependencies and cross-team blockers

Engineering

Jira, Linear, Datadog

Delivery progress, blockers and slipped commitments

Marketing

HubSpot, Mixpanel

Campaign pipeline and conversion

Product

Linear, Mixpanel

Launch progress, adoption and retention

Sales

HubSpot, Salesforce

Pipeline movement, closed deals and renewal risks

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.

September MBR summary in Slack showing performance against targets, risks, pending decisions and a link to the full review in Rhythms.
A monthly review snapshot
See what happens when you click on "Read the full September MBR"
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.
The September MBR in Rhythms, with metric cards, charts, risks and decisions.

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.

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.
Review the decisions and choose what Rhythms should handle next.

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.

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.
Rhythms prepares the follow-ups and can send them on confirmation

Try for Free in Slack


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.


Last updated

Was this helpful?