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.
