The CFO sent over a SaaS audit before our second meeting. 47 line items across the company credit card, none of them individually large, almost all of them under $500 per month. The total was $11,000 per month, which surprised no one, because every CFO knows the SaaS bill is bigger than they admit out loud.
What surprised them was what we found inside it.
Eleven of the line items were paying for tools the team had stopped logging into 14 months ago. Nine more were paying for "the integration we never finished," meaning a tool the firm bought to bridge two other tools, never wired up, and kept paying for. Eight were paying for features that already existed inside tools the firm was paying for separately.
The 11 dormant tools came to $2,857 per month in base subscription, plus $1,200 per month in seat add-ons that had not been pruned when staff turned over. $4,057 per month, $48,684 per year, going to nothing.
That number is not a horror story. It is normal. Every SMB we audit has a version of it.
The Stack
Here is what those 11 line items actually were, anonymized lightly. None of these are bad products. The firm just bought them in a different mood than they ended up using them in.
- $890/mo, mid-market CRM at 12 seats. Used by two people for opportunity tracking. The other 10 seats had not been touched in over a year.
- $340/mo, email marketing platform. Sent four newsletters in the last 18 months. The list was inside the CRM.
- $199/mo, dedicated landing-page builder. Built three pages, all of which were live. None had been edited in 11 months.
- $96/mo, premium calendar tool. Calendar features inside the M365 suite the firm already paid for handled the same use cases.
- $165/mo, e-signature tool, separate license. The firm had a second e-signature license bundled inside their practice management platform that nobody had connected.
- $240/mo, dedicated file-sharing tool. SharePoint and OneDrive, also inside the M365 license, were not in use.
- $120/mo, separate AI assistant subscription. Underused. The firm had Copilot inside M365 already.
- $89/mo, survey and feedback tool. Used twice in the last year.
- $199/mo, analytics platform. Connected to nothing. Dashboards never built.
- $420/mo, project management SaaS. Three users active. The rest of the team used email.
- $59/mo, social scheduling tool. Marketing person who set it up had left nine months earlier.
Total: $2,817 base subscription, plus the $1,200 in stale seat add-ons across the active products, for a real-world burn of about $4,200 per month on dormant or near-dormant capacity.
The Audit
We do not start with the SaaS bill. We start with the workflow. The SaaS bill is a symptom.
Inside two days, we mapped the actual work the team did each week. Client intake. Matter setup. Document collection. Status updates. Billing. Reporting. We sorted each step by which tool it touched and how often. The pattern was loud. Most of the work happened inside three places: M365 (email, calendar, Teams, OneDrive), the practice management platform, and QuickBooks. Everything else was a tool somebody had once been excited about and nobody had pruned.
SaaS sprawl is not a budget problem. It is an attention problem. Each individual subscription is too small to fight about, so nobody fights about any of them, and the bill grows by accretion. The audit is the part nobody has time for, which is exactly why we run it first.
What We Built
One custom employee dashboard, branded to the firm, hosted in the firm's own Cloudflare account, with role-based access and Cloudflare Zero Trust on every login.
The dashboard absorbed the work that had been spread across seven of the eleven dormant tools and four of the active tools. The team got: a unified inbox for client communication that pulled live from M365 and the practice management platform; an intake workflow that created the matter, generated the engagement letter, sent the e-signature request through the practice management platform's bundled license, and dropped the signed copy into SharePoint; a project board that was not a separate tool but a view onto the matter records the firm was already keeping; an analytics view that read live from QuickBooks and the practice management platform; and a knowledge layer that ran on Anthropic Claude for matter triage and on Perplexity for research.
The dashboard did not replace M365 or the practice management platform or QuickBooks. Those are doing real work. It replaced the eleven tools nobody was using and absorbed the cross-tool friction.
The Migration
Eight weeks, end to end. The phasing was straightforward.
Weeks one and two were the audit and the Proof of Concept. We mapped every workflow, identified the seven tools to retire immediately and the four to retire after migration, and built a working prototype of the highest-friction workflow (intake) so the team could see what was coming.
Weeks three and four were the connectors. Live read-write into M365. Live read-write into the practice management platform via its REST API. Live read into QuickBooks Online. Stripe and the existing payment processor for billing events. Cloudflare Zero Trust for identity, federated to the firm's Microsoft Entra ID for SSO.
Weeks five and six were the role-based UI. The intake coordinator's dashboard looked nothing like the partner's dashboard. The bookkeeper's view focused on AP and AR. Each role saw only what they needed and the data they were authorized to touch. Audit logging on every action.
Weeks seven and eight were pilot, training, and cut-over. We turned off the seven obviously-dormant tools first. The other four were retired after the team confirmed the dashboard was handling the workflow.
The Math at 12 Months
SaaS savings: $4,200 per month, $50,400 per year, on tools they were no longer paying for.
Time savings: harder to quantify precisely, but the team measured roughly 6 hours per week per professional in tool-switching and re-keying. Across 8 staff at a $90 blended rate, that runs to about $108,000 per year in recovered capacity, on top of the SaaS savings.
Build cost: a Heed Operations Platform engagement, billed monthly. Inside one fiscal year, the firm was net positive on cash and net positive on time. The detailed pricing is on the Operations Platform page.
The same architectural pattern is documented in detail in the law firm employee dashboard case study.
The Lessons
Three of them, in plain language, for any SMB looking at a similar audit.
The biggest line item is rarely the problem. The CRM at $890 per month is doing some work, even if it is overpaying for that work. The 11 small subscriptions doing nothing are the bigger spillage. Audit the small ones first.
The integration tool you bought is usually the thing to kill. If you have a tool whose only job is to bridge two other tools, you are paying for the symptom of a workflow problem. The custom dashboard is the cure.
Stop trying to standardize on one big SaaS suite. The "buy everything from one vendor" approach made sense in 2015. In 2026, the right architecture is keep the systems of record (M365, your practice or job management platform, QuickBooks) and build a thin custom layer that sits on top.
The firm in this story did one more thing worth mentioning. They put the $50,400 in SaaS savings into an annual contribution to a reserve fund and stopped renewing anything they had not used in 90 days. The audit became the discipline. That is the unsexy part nobody writes about.