Turn your cross-system processes into reliable workflows through chat. Ballet builds the agents, writes the logic and integrations, and runs the work at scale.
When a deal closes, write the handover from the call and send it to the owner.When a customer asks about a refund, check the order and draft a reply.After each event, match attendees to the CRM, enrich them and route the good ones.Every night, find duplicate accounts, merge the safe ones and flag the rest.
Get started with some examples
Deal closes 1.6s 
Read the call 2.4s 
Send to the owner 1.3s Run complete in 7.4s
Read the ticket 1.2s 
Check the order 1.9s Post the answer 1.4s Run complete in 7.0s
Attendee list 1.8s 
Enrich each one 2.6s Route to an owner 2.2s Run complete in 8.1s
Find duplicates 2.7s Flag the rest 1.2s Run complete in 8.0s
Complex knowledge work is never finished in one system. It runs through the CRM, the billing service, a database and a person — which is why it has stayed manual. Ballet is the first tool that automates it reliably.
The integration gets written as part of the build. That covers the CRM everyone has and the service your team wrote in 2019 that has no docs.
See the platform
Refund Request Resolution Connectors 
Salesforce
Zendesk
StripeBallet's AI coding agent can handle the kind of logic, integrations, and multi-system processes that usually need custom engineering — while you build it all through conversation.
See the platform Refund Request Resolution Code 1
2
3
4
5
6
7const deals = await sf.query(
`SELECT Id, Amount FROM Opportunity`
);
for (const d of deals) {
if (d.Amount > 50000) await gate(d);
}The model reads the ticket. Code moves the money. Run the same input twice and you get the same output, which is the part Finance asks about first.
Security & governance Refund Request Resolution Play Open a run from six months ago and step through it with the data it actually saw.
Security & governance Refund Request Resolution Runs ec56e7e3 Schedule b1f0a92c Slack · Jess F 7d24c118 Claude 41a9e07f Chrome panel Describe the outcome and Ballet builds the steps, writes the integrations, and hands your engineers something they can read.
Every playbook, every run, every model — in one place.
US$2,603.62
24,048 runs 3,648 tool calls
PlaybookMemberModelTool
AI Gateway
Which models your builders can use.
anthropic/claude-opus-5 500K 
openai/gpt-5.1-codex-max 400K 
google/gemini-omni-flash 1M 292 models · 5 providers enabled
Security & governance Visit the Trust Center
Your team builds its playbooks in one place, reviewed and versioned together. Everyone else runs them from wherever they already work.
Platform Where a workflow gets written, reviewed, and watched once it's live. 
Chrome extension A side panel next to your CRM or helpdesk. Ask for something, or type / and pick a playbook. 
Claude connector Connect Ballet in Claude and ask it to run a playbook, read what happened, or build a new one. 
Slack agent Mention Ballet on a message, or send it a DM. The result posts back in the thread. Today A list lands after every event and someone spends two days matching it to the CRM, filling gaps, and deciding who follows up.
Event and webinar lists become routed, enriched leads before the follow-up goes cold.
Marketing playbook Play Attendee list Trigger 
Match and enrich Route to an owner Done Today Closed Won fires and the handover depends on whether the rep had time to write one, and how much of the call they remembered.
Closed Won turns into a complete handoff instead of a note someone writes later.
Sales playbook Play Deal closes Trigger 
Read the calls 
Post to the owner Done Today Duplicates and missing owners pile up until someone books a cleanup project, and by the time it ships the data has drifted again.
Duplicates, missing fields and stale owners get fixed continuously, not in a quarterly project.
RevOps playbook Play Find the conflicts Today An agent reads the ticket, searches the docs, checks the account, and writes the same reply they wrote last week.
Common tickets arrive as a draft reply an agent reviews rather than writes.
Support playbook Play Ticket arrives Trigger 
Search the docs Today Invoices age quietly until someone runs the report, and the chase goes out without the account context that would settle it.
Overdue invoices get chased the day they age, with the context the customer needs.
Finance playbook Play 
Invoice ages Trigger Pull the history  | AI agents   | Traditional workflows    | |
|---|---|---|---|
| Speed to build | Minutes, plain English | Fast to start | Weeks, by hand |
| Connects to internal systems | Reaches your proprietary systems | Limited | Not without weeks of ENG effort |
| Consistency | Same output every time | Different & unpredictable | Consistent but rigid |
| Reasoning | Flexible and considered | Deep reasoning | Inflexible, can't adapt |
| Auditable | Yes, transparent code | Minimal reporting | Minimal reporting |
| Cost | Predictable | Expensive | Climbs with volume |
Ballet is a workflow-automation platform from the team behind Brainfish. Describe a multi-system outcome in plain English and Ballet builds it as reviewable, version-controlled code — deterministic where accuracy matters, agentic where judgment helps.
Connector libraries cap out when your stack is proprietary or the graph gets huge. Ballet writes the integration against any API the moment you need it, and the workflow runs as inspectable code instead of a brittle visual graph.
Yes where it matters. Ballet writes deterministic workflow code your engineers can read, approve, and replay. Agentic reasoning is used only on steps that benefit from flexibility — not on the steps that must never drift.
Generated code is visible and version-controlled, with approval gates and replayable runs. Ballet is part of Brainfish and covered by Brainfish’s SOC2 Type II compliance. Details live in the Trust Center at https://trust.brainfi.sh/.
Brainfish is the knowledge layer; Ballet is the execution layer. Customers can trigger Ballet workflows from Brainfish, and Ballet also runs standalone against your existing stack.
We’ll model it on your real systems in a 30-minute session. No SOW, no scope creep.