Plain-English workflow creation
Describe a workflow outcome in plain English, such as lead routing, attribution, or a renewal play, and Ballet turns it into an implemented workflow.
Ballet
Ballet turns plain-English revenue workflows into reviewable code and running automations for RevOps, Support Ops, and product-led growth teams.
Overview
Ballet is a workflow-automation platform for teams that need to connect multiple systems across their revenue stack. The site frames it as a way to get around engineering queues: you describe the outcome in plain English, and Ballet builds the workflow, runs it, and keeps it working.
The product is aimed at workflows where standard connector libraries or visual automation tools may fall short, especially when proprietary systems, internal APIs, or larger multi-step graphs are involved. Its examples include lead capture into a CRM, account surge detection, and order changes that need to flow through billing systems as well as customer-facing tools.
Core capabilities
Reviewable code output
Ballet writes deterministic workflow code that engineers can read, approve, and replay, instead of relying on an opaque automation graph.
Direct integration with proprietary systems
The product is designed to connect to internal systems and proprietary APIs when off-the-shelf connector libraries are not enough.
Deterministic runs with selective reasoning
Ballet can run workflows with a mix of deterministic steps and agentic reasoning, using flexibility only where judgment is useful.
Auditable workflow execution
The site says workflows are transparent, version-controlled, and replayable, which supports review and change tracking over time.
Build and operate workflows
Ballet is presented as a platform that both builds and runs workflows, then keeps them working as systems change.
Practical use cases
Lead capture and routing
Capture inbound leads, enrich and dedupe them, score them against product usage, and route them without waiting for overnight batch jobs or data engineering requests.
Account surge detection
Detect meaningful changes in product telemetry, enrich the signal, and send a next-best action to the right rep so outreach is based on current events rather than stale CRM fields.
Order change propagation
Let operations teams or account executives amend pricing, terms, or SKUs and propagate those changes through internal billing systems, not only the CRM.
Backlog workflow implementation
Use Ballet to model a backlog workflow during a live working session, then have the team review the generated code before it is approved and run.
Brainfish-triggered execution
Trigger workflows from Brainfish when a knowledge-layer event needs execution across connected systems, while still being able to run Ballet standalone.
Pros and Cons
Pros
- Can turn a workflow described in plain English into reviewable code.
- Designed for multi-system revenue workflows that need internal or proprietary integrations.
- Supports deterministic execution where accuracy matters, with flexibility only where useful.
- Workflows are visible, version-controlled, and replayable, which supports review and approval.
- Examples cover practical revenue operations tasks such as lead routing, account surge detection, and order changes.
Cons
- Pricing is not published on the site pages provided, and the pricing page returns a 404.
- The site presents Ballet as early access for design partners, so availability appears limited.
- Some capabilities and integrations are described through examples rather than a full documented feature list.
FAQ
What is Ballet?
Ballet is a workflow-automation platform. The site says you describe a multi-system outcome in plain English, and Ballet builds it as reviewable, version-controlled code.
How is Ballet different from Zapier or n8n?
The site positions Ballet as an alternative to tools like Zapier or n8n when a workflow needs to connect proprietary systems or handle a larger graph. It emphasizes code-based workflows that are inspectable rather than a brittle visual graph.
Is the output deterministic?
Ballet says the generated workflow code is deterministic where accuracy matters, with agentic reasoning used only on steps that benefit from flexibility. The workflow can be read, approved, and replayed by engineers.
Who is early access for?
The site says Ballet is in early access for design partners with real multi-system workflows stuck behind an engineering queue, including RevOps, Support Ops, and product-led growth teams.
How does security and compliance work?
Ballet says generated code is visible and version-controlled, with approval gates and replayable runs. It also states that it is part of Brainfish and covered by Brainfish’s SOC2 Type II compliance, with details in Brainfish’s Trust Center.
Quick Facts
- Category
- Workflow automation
- Primary users
- RevOps, Support Ops, and product-led growth teams
- Product model
- Builds and runs workflows from plain-English prompts
- Source domain
- ballet.dev
- Availability
- Early access / design partners
- Company
- Built by the team behind Brainfish
Ballet Alternatives
Awish
Awish is an AI no-code automation platform that turns natural-language requests into workflows across connected apps—no manual setup.
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repos and verifies changes with compilers, debuggers, sanitizers, and tests.
MeetStream
MeetStream is a meeting bot API for Zoom, Google Meet, Microsoft Teams, and Webex. Record, stream, and analyze meetings with usage-based pricing and $5 free credit.
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads in Firecracker micro-VMs with private networking and SDK, CLI, or MCP control.
Codex Plugins
Codex Plugins bundle reusable skills, app integrations, and MCP servers into workflows you can install in the Codex app or use from Codex CLI.
Struere
Struere turns spreadsheet data into structured operational software with dashboards, alerts, and automations for teams replacing manual spreadsheet workflows.