Six Subscriptions and the Best Answer You Have Is ‘Probably’
Hollie wasn’t accusing me of anything.
She was just looking at the credit card statement the way you do when a number doesn’t quite make sense — not alarmed, just curious. She pointed at a line item and asked the question flat, no edge to it:
“What does that one actually do for us?”
I knew what it did. I could pull up the dashboard right then and explain the features. I could tell her exactly what problem it was supposed to solve when I signed up for it.
What I couldn’t do — and this is the part that sat wrong — was point to something specific it produced last month. A deal that moved. A client that stayed. An hour I got back. Anything with a number attached.
What came out of my mouth was some version of “it’s part of the system.”
Which is just a more confident way of saying: probably.
—
‘Probably’ Is Not a System
Paying for tools you can’t defend isn’t a budgeting problem. It’s not a discipline problem either.
It’s a measurement problem — and measurement is an ops problem.
The tools aren’t necessarily bad. The problem is that nobody built a way to know if they’re working. So the default answer becomes probably — probably helping, probably worth it, probably doing something useful in the background.
Probably is what happens when you bought a tool before you built a loop to measure it.
—
You Didn’t Buy Six Subscriptions. You Solved Six Fires.
Here’s what actually happened, and it’s worth saying out loud because it’s not carelessness.
One tool for lead follow-up because leads were slipping through. One for scheduling because back-and-forth email was eating an hour you didn’t have. One for proposals because the old process looked unprofessional and cost you a client you were pretty sure you should have closed. One for content. One for the inbox. One for the thing a contractor friend swore would save his evenings — and maybe it saved his. You’re not sure about yours.
By the time you’re at six, every purchase made complete sense at the time. Each one solved a real problem. Each one felt like a decision, not a default.
What never happened: a measurement layer. A way to know if the fire stayed out.
Solving a fire is not the same as building a system. And a collection of fire extinguishers is not infrastructure.
—
The Real Cost Isn’t the Subscription Fee
Six mid-tier SaaS subscriptions might run $300–500 a month. That’s real money. But it’s not the actual damage.
The real cost is running a business with no clear read on what’s working.
Because if you can’t measure the tools, you probably can’t fully measure the pipeline either. You’re making decisions on feel — which worked fine when the business was smaller. Feel doesn’t scale. It also doesn’t transfer.
Here’s what the confidence gap actually looks like in practice:
- When something breaks, you don’t know where to look
- When something works, you can’t replicate it on purpose
- When a client asks why your follow-up is sharp, you say “just how we do things” — which is true, and also means you can’t protect it
A contractor with a CRM, an AI email tool, a quoting app, a job tracker, a voicemail text-back service, and follow-up software can be busier than ever and still have his pipeline living in his head and on his phone. More tabs. More checks. More time spent verifying what the tools produced.
That’s not a tool problem. That’s a measurement problem.
The tool spend is a symptom. The untracked ops is the actual risk.
—
What Measurement Actually Looks Like
Not a spreadsheet audit. Not a dashboard. One question, asked honestly about every tool in the stack:
“Last month, can I point to something specific this tool produced — a deal moved, an hour recovered, a client retained — or am I paying on faith?”
That’s it. That’s the whole diagnostic.
Here’s what to do with the answer:
- Yes, and I can name it — keep it, document the answer, check it again in 60 days
- No, but I know what “working” would look like — give it a 30-day test with one specific thing to look for
- No, and I can’t even define what working would look like — that’s the one
This isn’t about cutting the stack down to nothing. It’s about knowing what you’re running and why. There’s a difference between a tool that saves two hours of proposal time and one that just feels more professional. Both cost money. Only one earns it.
“Feels faster” is not ROI. “We use it a lot” is not proof. The question is what changed because of it — and if the answer is genuinely “I’m not sure,” that’s the measurement gap telling on itself.
—
One Thing You Can Try This Week
Open whatever tool you’ve been paying for longest and ask the question from above: “Last month, can I point to something specific this produced?” Write the answer down — even if it’s two sentences. If you can name it, you’ve just created the start of a measurement habit. If you can’t, you’ve got your first real ops decision of the quarter. Either way, takes about ten minutes.
—
Hollie Asked a Better Question Than Most Business Coaches Do
She wasn’t asking if it was expensive. She was asking what does it do for us — which is an ops question wearing domestic clothes. A tool worth keeping should be able to answer that in one sentence, without hesitation.
If your stack can’t answer Hollie’s question, it’s not a stack. It’s a monthly subscription to the feeling that you’re handling it.
You might be. But probably isn’t the answer you want to be running your ops on.
—
If you’re not sure what’s actually pulling weight in your setup, that’s usually where a conversation with FlowStateOps starts — not with a software recommendation, just an honest look at what you’re running and whether it’s doing what you think it is. flowstate-ops.com
—