Every fractional COO engagement at OAG produces a three-number diagnostic at the end of week four. SaaS spend vs. utilization. Decision latency. Founder-bottleneck count. Together they're the operational waste audit. They are the single most useful artifact most operators have ever seen of their own business, and the most commonly misread.
This post is how to read each of the three numbers, what they imply, and what to do in the 60–90 days after seeing them.
Number 1: SaaS spend vs. utilization.
The number is a percentage. SaaS spend you actually use, divided by SaaS spend you pay for. Most operators are in the 60–75% range. If you're at 90%, you're either disciplined or you've never audited.
The component categories matter more than the headline number:
- Tools at 0% utilization. Cancel immediately. There is no reason to pay for software nobody opens.
- Tools at <30% utilization. Either downgrade to a cheaper tier or cancel. The 30% threshold is empirical: below it, the tool's value almost never justifies its full price.
- Tools with seat utilization <60%. Audit the seat list. Former employees, contractors who finished their project, accounts that should have been deactivated months ago.
- Tools with feature utilization <30% but seat utilization >80%. The seats are using the tool, but not using most of what you're paying for. Downgrade the tier.
Reading the number wrong: "We're at 71%, that's pretty good." No, 71% means 29% of your SaaS spend is funding nothing. At $2,400/month total, that's $696/month or $8,352/year of pure waste. Ranking yourself "pretty good" is how you stay there.
Number 2: Decision latency.
Decision latency measures how long, on average, a decision takes to route from origin to resolution. We measure it across three categories: routine decisions (pricing exceptions, vendor renewals), strategic decisions (hiring, scope changes), and operational decisions (process choices, vendor selection).
Healthy ranges, in our experience:
| Decision type | Healthy | Yellow | Red |
|---|---|---|---|
| Routine | < 1 day | 1–3 days | > 3 days |
| Operational | < 5 days | 5–14 days | > 14 days |
| Strategic | < 21 days | 21–45 days | > 45 days |
Most companies we audit have routine decisions in the 3–7 day range. That means a sales rep waiting a week to know if they can offer a 5% discount. Multiply by deal volume and the cost compounds fast.
The cause is almost always a routing problem, not a decision-quality problem. The information needed to make the call exists; it's just queued behind a meeting, behind a Slack thread, behind an executive whose calendar is full. The fix is rarely "make decisions faster." The fix is "route decisions correctly."
Number 3: Founder-bottleneck count.
Per week, how many decisions route through the principal that shouldn't? We count by category:
- Decisions with an obvious correct answer. The pricing matrix says X. The expense policy says Y. These shouldn't reach the founder at all.
- Decisions that belong to a function head. The marketing director should pick the marketing tool. The sales VP should approve the sales hire.
- Decisions that don't actually need to be made. "Should we do X?" when X isn't resourced. Deciding by inaction is fine.
Healthy founder-bottleneck count for a $10M–$50M operator is 5–10 per week. Most companies we audit are at 25–60 per week. At that volume the founder is the bottleneck for the entire business, and the team has stopped trying to make any decisions independently because they know it'll get re-litigated anyway.
The number is the most psychologically uncomfortable of the three. Founders react in predictable ways: "but I want to be involved in those decisions." Sometimes that's true; usually it's a habit. Reading the number honestly is harder than fixing it.
What to do in the 60–90 days after seeing the numbers.
Same playbook every time:
SaaS, cancel the 0% tools immediately, downgrade or cancel the <30% tools by month two. Audit seat lists by month one.
Decision latency, pick the worst category (usually routine) and document the decision rules. Write down the pricing matrix, the expense policy, the vendor-selection criteria. Once they're written, the routing problem solves itself, the team doesn't need a meeting to apply a rule.
Founder-bottleneck count, for each routinely bottlenecked decision category, name a function head as the owner. Tell the team explicitly. Stop accepting the questions in your inbox; bounce them to the owner. The first week is uncomfortable. By week four, the count is half.
Reading without us.
You can do all three measurements yourself. The SaaS audit is a credit card statement and a spreadsheet. The decision latency measurement is a week of timestamping. The founder-bottleneck count is a tally sheet on your desk for two weeks.
The hard part isn't measuring. It's reading the numbers honestly and acting on them. Most founders see the numbers, agree with them, and then continue operating exactly the same way. The audit is not the deliverable. The cuts in the next 90 days are.
If the numbers are confronting and you'd rather have an outsider drive the conversation, that's what the engagement is for.
Keep reading.
- Replacing the SaaS Stack with $75/mo of Cloudflare, Most small operators run on $500–$3,000/month of SaaS that compounds with every new hire. …
- What We Cut in the First 90 Days, A typical $10M–$50M operator carries 30–40% operational waste. The first 90 days of an Axi…
- How to Actually Move a Team from Storming to Performing, Most LMM teams stop at Norming and the leadership thinks that is success. It is not. This …
- Lean Six Sigma for the Lower-Middle Market, Without the BS, DMAIC, SIPOC, Black Belts, control charts, kaizen events. At enterprise scale these earn t…
Talk through it.
If any of this is applicable to where you are, book a scoping call. No pitch deck.