← Playbooks

RevOps · CS Ops · Business Systems

Ask for the weekly report in plain English. Ballet builds it and runs it on schedule.

The weekly report that spans Salesforce, Zendesk and Stripe usually waits on a BI queue or a fragile spreadsheet.

5 min read

Running ops automations at

  • Mixpanel
  • HireVue
  • Pave
  • Buffer
  • SnapLogic
  • Huntress

With Ballet you describe the report in plain English. It builds the query across the systems you connect, stores a durable version as reviewable code, and runs it on the schedule you choose.

You can also re-run it from Claude or Cursor over MCP when someone asks for an update mid-week.

What this playbook does

You describe the weekly report once. Ballet builds the cross-system pull, the joins and the delivery step as reviewable code, then runs it on a schedule.

What you hand Ballet

Every Monday at 8am, pull open pipeline by owner from Salesforce, open P1 tickets from Zendesk, failed payments from Stripe, join them by account, and post a summary to #revops-weekly with links back to the source records.

When definitions change, you edit the playbook and publish again. The next run uses the new version; previous runs stay replayable.

How to use it

  • Open Weekly Reports in Ballet and connect the systems the report needs.
  • Describe the metrics, joins and delivery destination in plain English.
  • Simulate against last week's data and review the output.
  • Set the schedule and publish.
  • Optionally connect an MCP client so someone can ask for a refresh in chat.

The systems in this play

Ballet generates the integrations this workflow needs

You name the systems and what the workflow needs from each. Ballet builds the connections as part of the workflow, on demand.

CRM

  • Salesforce
  • HubSpot

Pipeline, accounts and owners

Support

  • Zendesk
  • Intercom

Open tickets, CSAT and volume

Billing

  • Stripe

MRR, failed payments and invoices

Don't see yours? Ballet builds the integration as part of the workflow. Bring us your workflow →

What workflow would you hand to Ballet?

Bring us a workflow your team hasn't been able to automate. We'll build it in Ballet and show you what it looks like running across your systems.

FAQs

Weekly Reports, answered

The questions teams ask before they hand this workflow over.

Is this a BI tool?

No. It builds a governed workflow that answers a recurring cross-system question and delivers it where the team already works.

Can I change the report later?

Yes. Edit the playbook, review the diff, and publish. The next scheduled run uses the new version.

Can Claude re-run it?

Yes, once the Ballet MCP connector is connected. Ask for this week's report and Claude can start the playbook.

Who is this for?

RevOps, CS Ops and business systems teams that ship recurring reports without waiting on a BI project.