The SaaS Spend Diagnostic

Clarus CFO ships with five insight rules out of the box. Each one runs against the latest spend, contract, subscription, and seat data, and produces a typed insight with a severity, an evidence trail, and a recommendation. The five are:

• orphan_spend: money is leaving your accounts payable system and there is no contract attached to it.
• duplicate_tools: two or more vendors are providing services in the same product category.
• inactive_seats: a subscription has seats licensed but not actively used.
• renewal_risk: a renewal is coming up soon and the subscription represents enough annual spend to need a strategy.
• unknown_vendor: a vendor is in your spend but the normalization engine has not been able to identify it confidently.

Together, these five cover the bulk of what shows up in a typical mid-market SaaS audit. The rest of this article walks each rule, the threshold that triggers it, and what to do when it fires.

The orphan_spend rule fires when a vendor has more than one thousand dollars of trailing twelve-month spend and no contract attached to that vendor in the system. The thousand-dollar threshold filters out the small-dollar one-time charges (a domain renewal, a single-use API key) so the rule focuses on subscriptions and ongoing services that should have a contract behind them.

When the rule fires, the recommendation is to find the contract, link it, and confirm the renewal date and the auto-renew terms. Most orphan spend is not malicious; it is a contract that lives in a Google Drive, an attachment in someone's email, or was never countersigned and archived. The link-then-confirm flow handles the lookup and updates the renewal pipeline in one step.

The inactive_seats rule fires when a subscription has an active-seat percentage below the threshold the tenant configures. The default is 70 percent: if you bought 100 seats and only 70 are seeing logins or measurable activity, the rule fires. Tenants tune this up for tools where adoption is critical (CRM, ticketing) and down for tools where occasional use is expected (compliance training, design tools).

The recommendation is to right-size at the next renewal. The renewal negotiation playbook covers the language; the diagnostic flags the opportunity. Most teams find that a single renewal cycle of seat right-sizing returns more savings than a year of contract negotiation on terms.

The duplicate_tools rule joins your active vendors against the canonical category list and fires when two or more vendors land in the same category. The category list groups synonyms together, so Slack and Microsoft Teams are flagged as a duplicate, and so are Datadog and New Relic, and Asana and Monday.

Most duplicates are not waste; they are tradeoffs. A platform team may standardize on one observability tool while a research team prefers another. The diagnostic does not ask you to consolidate; it asks you to confirm the duplication is intentional and document the tradeoff. The ones that surprise teams are usually duplicate tools that arrived with an acquisition or a team-led purchase that bypassed procurement, and those are the ones worth consolidating.

The renewal_risk rule fires when a subscription's renewal date is less than 60 days away and the annual contract value is high enough to warrant a negotiation. The threshold is tenant-configurable; 25 thousand dollars per year is a common default.

Sixty days is the leverage window. Inside 60 days, the tools you have to walk away (alternatives, pilots, switching cost analysis) shrink sharply. Outside 60 days, you have time to gather data, run a pilot, and signal alternatives credibly. The Renewal Negotiation Playbook covers what to do in the window; the diagnostic surfaces the renewal in time to use it.

Vendor normalization is the process of mapping the noisy strings that land in your AP system (Acme Corp, ACME CORPORATION, Acme Co dba Acme LLC) to a single canonical vendor record. The unknown_vendor rule fires when the confidence_score on a vendor is below 0.5 and the vendor has material trailing spend.

Low confidence is usually one of two things: a real vendor that the normalizer has not seen enough variants of, or a typo in the AP system that should be merged into an existing vendor. Both fixes are one-click. After the fix, the recommendation upgrades to the right insight (often orphan_spend or duplicate_tools) and the diagnostic re-runs.

Every finding becomes a typed recommendation on /cfodashboard/recommendations. Each recommendation carries a rationale (the evidence trail), an estimated savings number, and a confidence label (high, medium, low). The action set is consistent across types: Draft Email, Accept, Dismiss.

We do not auto-execute. The point of the diagnostic is to surface the opportunity and let a finance owner decide. The combination of a consistent rationale, a savings estimate, and a one-click email draft turns most findings into a five-minute decision.