Ballet is a new workflow automation platform from the team behind Brainfish. Describe a multi-system outcome in plain English and Ballet writes it as inspectable, version-controlled code your engineers can read, approve, and replay.
The problem it targets
Growth and ops ideas that require connecting two or more internal systems typically stall in an engineering queue. Tools like Zapier or n8n cap out when your stack is proprietary or the automation graph gets complex. Ballet’s claim is that it writes the integration against any API on demand, rather than relying on a fixed connector library.
How it works
You describe the outcome you want. Ballet builds a workflow in code. The execution is deterministic on steps where accuracy matters, and uses agentic reasoning only on steps that benefit from flexibility. The output is auditable code with approval gates and replayable runs, not a brittle visual graph.
Use cases on the landing page
- Lead capture to CRM: Enrich, dedupe, and score inbound leads against your product usage data before routing, with no overnight batch job.
- Account surge detection: Spot changes in product telemetry, enrich them, and push a next-best-action to the right rep via Slack, pulling from systems like Clay, ZoomInfo, and Salesforce.
- Order amendments without an ENG ticket: Let ops or AEs change pricing, terms, or SKUs and propagate the change through internal billing, not just the CRM, across Salesforce CPQ, Stripe, and Freshdesk.
Security and early access
Ballet is covered by Brainfish’s SOC2 Type II compliance. The trust center is at trust.brainfi.sh. Early access is aimed at RevOps, Support Ops, and product-led growth teams with a real multi-system workflow sitting in the backlog. The onboarding offer is a 30-minute working session to model one workflow on your actual systems, no statement of work required.
Ballet runs standalone or can be triggered from Brainfish, which the team describes as the knowledge layer to Ballet’s execution layer. Sign up here.
