TL;DR: Most companies don't have too few tools. They have too many, held together by people. Zylo's 2026 SaaS Management Index puts the average portfolio at 305 apps and $55.7M a year. Harvard Business Review found workers switch between apps about 1,200 times a day, losing roughly 9% of their working time just getting their bearings again. Consolidation isn't only about cancelling licences. It's about moving the work between tools into one place. Ballet does that: it connects to the systems you keep, replaces the glue and point tools in between with versioned playbooks, and gives you one run history for all of it.
The numbers on SaaS sprawl are well known:
The HBR authors make the key point: switching costs are rarely an accident. They come from how the work is designed. Each new tool solves one problem, and a person (or a fragile automation) ends up carrying data between that tool and the rest.
So sprawl has three layers, and only the first shows up on the invoice:
| Layer | What it looks like | Who pays |
|---|---|---|
| Overlapping point tools | A separate app for lead routing, another for ticket triage, another for reporting, each with its own seats | Finance |
| Glue | Zaps, scripts, cron jobs and spreadsheets that move data between systems, often owned by one person | Ops and engineering |
| Swivel-chair work | People copying from the help desk to the CRM, checking Stripe before replying, pasting numbers into a weekly deck | Everyone, every day |
Cancelling apps attacks the first layer. The bigger win is in the second and third.
You're not going to replace Salesforce, Zendesk or Stripe, and you shouldn't. They hold your customer, ticket and billing data, and your teams know them.
What you can consolidate is everything around them:
That is the layer Ballet is built for. Keep your systems of record. Move the work between them into Ballet.
Ballet ships first-party integrations for the systems most operations teams already run:
| Category | Integrations |
|---|---|
| CRM | Salesforce, HubSpot |
| Support | Zendesk, Intercom, Freshdesk |
| Payments | Stripe |
| Email and calendar | Gmail, Outlook, Google Calendar |
| Files and data | Google Drive, Google Sheets, OneDrive |
| Advertising | Google Ads, Meta Ads, LinkedIn, ChatGPT Ads |
| Messaging | WATI (WhatsApp) |
| Engineering | GitHub, Cursor |
| Knowledge | Brainfish |
For anything not on that list:
Credentials for all of these live in one encrypted, per-workspace secret store and are never shown back to users. See How Ballet protects the credentials you connect.
One place to connect means one place to audit what has access to what, instead of credentials spread across a dozen point tools and personal automation accounts.
A playbook is a saved workflow: ordered steps, each bound to a tool call or code, versioned per workspace. You describe what you want in plain language with Ask Ballet, the AI console, and it builds the playbook. You review the steps, then publish. Until you publish, nothing changes what real runs do.
Because a playbook can read from and write to any connected system, one playbook often replaces both a point tool and the glue around it. For example:
The AI writes the process, and the playbook runs it the same way every time. A known process doesn't need a model to re-decide it at 2am. That is what makes a playbook safe to hand to a team, unlike a chat.
Glue usually lives in a different place for each trigger type: a cron job here, a webhook listener there, a button in another app. A Ballet playbook can start:
Playbooks can also be run from other tools. External AI clients such as Claude Desktop or Cursor can connect to Ballet as an MCP server, and developers can call playbooks through the API. Your process lives in one place, wherever it's started from.
Every execution is a run, with a recorded history of what each step did. When something goes wrong, you look in one place, not in five vendors' logs and a Zapier task history.
Workspace reports turn the results into live panels that recompute for any date range, built around your own business data rather than platform metrics. You can share run output with people outside the workspace. Often that replaces the reporting tool, or the screenshot pasted into Slack.
SaaS-management research generally recommends the same sequence: inventory what you have, look at usage and overlap, then act (BetterCloud, State of SaaSOps 2024). Here is how that maps onto Ballet.
1. Audit the stack and the work around it. List your apps with owner, cost and usage, and also the workflows that cross them. The question to ask is "where does someone copy data from one tool into another?" Those are your candidates.
2. Pick one workflow, not one tool. Choose a frequent, well-understood process that spans two or three systems, such as ticket triage or lead routing. Avoid starting with your most political or most rarely used process.
3. Build it as a playbook. Describe it to Ask Ballet, connect the systems it touches, and review the steps before you publish.
4. Run it alongside the old way. Compare the run history with how the process works today. Track the result you care about: time to first response, leads routed correctly, hours of manual work saved.
5. Retire what it replaced. Cancel the point tool at renewal, delete the zap or script, revoke the old credentials and update the runbook. A consolidation that leaves the old tool running hasn't finished.
6. Repeat. Each playbook you add makes the next one cheaper, because the connections, secrets and patterns are already in place.
| Usually consolidate into Ballet | Usually keep |
|---|---|
| Single-purpose tools that move or enrich data between systems | Systems of record: CRM, help desk, billing, files |
| Zaps, scripts and cron jobs that one person maintains | Tools teams work in all day and actually like |
| Manual copy-and-paste steps across tools | Regulated systems with their own audit requirements |
| Ad hoc reporting rituals | Deep, specialised tools with no overlap |
Consolidation doesn't mean doing everything in one app. It means each piece of work has one home, one owner and one history.
Each guide lists the point tools that team typically pays for, published prices with sources, what a playbook can replace, what's worth keeping, worked examples and how not to overpay at renewal.
| Team | Typical candidates to consolidate | Guide |
|---|---|---|
| GTM (marketing and sales development) | Lead routers, form-to-CRM glue, enrichment workflows, ad-spend reporting | Tool consolidation for GTM teams |
| RevOps | Dedupe tools, routing engines, CRM and billing sync, stale-deal alerts | Tool consolidation for RevOps |
| FinOps | Dunning add-ons, subscription-analytics tools, invoice chasing, seat audits | Tool consolidation for FinOps |
| CS Ops | Triage add-ons, health-score platforms, CSAT tools, engineering escalation | Tool consolidation for CS Ops |
If you'd like help picking the first workflow to consolidate, talk to our team.