A Feeling Is a Story. A List Is Proof.

Vague is the tell. When someone selling you a system can't say what it actually did last month, the honest read is that very little did. Adjectives are free; counts are not.

The word that should make you suspicious

"Streamlined." "Optimized." "Way more efficient." These are the words that arrive when there is nothing underneath to point at. They sound like progress and commit to nothing. Ask one follow-up question and they fall apart.

Try it sometime. Someone tells you their operation got more efficient. You ask: efficient at what, exactly, and how many times last month? Watch what happens. If the work is real, the answer comes fast and specific, because they were already counting it. If it isn't, you get a longer adjective. More words, same fog.

This is not a personality flaw in the people selling to you. It is a structural fact. Vague language is what you reach for when there is no record to draw from. A founder who reconciled every invoice last month doesn't say "our finances are tighter now." They say the number. The vagueness is the data. It is telling you, accurately, that nothing got counted, which usually means nothing got done.

So before you evaluate the claim, evaluate its texture. A claim made of moods is a claim with no paper trail behind it. You are being asked to buy a feeling about the future. The feeling will leave no trace you can check later, which is convenient for everyone except you.

A feeling is a story you tell yourself about the future

Here is the difference that matters. A feeling points forward and asks for trust. A list points backward and asks for nothing. "This will save you so much time" is a story about a month that hasn't happened. "Forty-one no-shows followed up, same day" is a record of a month that did.

Stories are easy to produce. I can write you a beautiful one about your calmer Fridays in about ninety seconds, and it will cost me nothing and obligate me to nothing. A list is expensive in the only way that counts: it can only exist if the work actually occurred. You cannot retroactively manufacture a true count of reconciled invoices. Either the reconciling happened or it didn't.

That asymmetry is your whole defense. When you are tired and busy and someone is good at talking, the feeling does most of the persuading. It bypasses the part of you that checks things. The list re-engages it. It drags the conversation out of the future, where anything is possible, and into last month, where only some things actually occurred.

So when you catch yourself feeling convinced, stop and ask where the conviction is coming from. Is it from something you verified, or from a mood the conversation put you in? If it's the mood, you haven't learned anything yet. You've just been told a good story.

Why your brain treats a count as a receipt

Alex Hormozi says the more specific the claim, the more your brain believes it. He's right, and there's a real mechanism under it.

Your mind runs a quiet fraud check on everything it hears. Part of that check is asking, often below awareness, how hard would this be to fake? Vague things are cheap to fake, so they get discounted. "We're more efficient" could be said by anyone about anything. Specific things are expensive to fake, so they get believed. "The inbox hit zero on Friday at 4:40" is the kind of detail you only produce if it happened, because inventing convincing specifics is more work than just doing the thing.

A round number sits in the middle and usually reads as marketing. "We save you ten hours a week" is suspiciously clean. Nothing real is that tidy. "Eleven and a half hours, but four of those were one ugly reconciliation in March" reads as true precisely because it's lumpy. Reality has texture. Marketing sands it off.

This is why a count functions like a receipt and a promise functions like a pitch. A receipt is evidence of a transaction that already cleared. A pitch is an invitation to one that hasn't. Your brain knows the difference even when you're not consciously tracking it. The trick is to let that instinct do its job instead of letting a confident voice override it.

How to use this before you buy anything

This works on more than software. Use it on agencies, hires, tools, consultants, your own quarterly review.

Before you commit, ask for the boring version: what did this actually count last month? Not what it can do. What it did. A good system, or a good operator, will have an answer ready, because the counting is the work. If the answer is a brochure, you have your answer too.

When you get a list, read it for falsifiability. "Every invoice reconciled" is checkable; you can pull one and look. "Improved financial visibility" is not; there is nothing to pull. Favor the claims that could embarrass someone if they were false. Those are the ones that took real work to be able to say.

Watch for "every" versus "mostly." "Mostly reconciled" is the sound of a system that breaks under load, which is exactly when you'll need it. The gap between every and most is where chargebacks live, where the lead that would have closed goes cold, where the refund you didn't catch in time becomes a dispute.

Then apply it to yourself. At the end of your month, write the list, not the mood. Not "things felt smoother." The actual count of what got done and what slipped. If you can't write it, that's the finding. You weren't measuring, so you don't yet know.

The list can lie too, so here's the harder rule

I owe you a caveat, because a count can be cherry-picked. Someone can show you the forty-one no-shows they followed up and stay very quiet about the two hundred leads that never got a first reply. A list of wins with the losses cropped out is just a prettier story.

So the real rule is one level up: ask for the denominator. Forty-one of how many? Every invoice, out of how many invoices total? A specific number with no base rate is half a receipt. It tells you something happened without telling you whether it was most of what should have. The honest version of a list includes what it missed, because anyone tracking the wins is also tracking the gaps, by definition.

I'll be straight about my own seed list, the one about reconciled invoices and same-day follow-ups and Friday inboxes at zero. Not one of those is a verified statistic I'm asking you to take on faith. They are the shape of a month when work is genuinely logged. The moment a system is actually doing them, each line becomes a number. Until then they're examples, and I'd be breaking my own rule if I dressed them up as data.

That's the standard. Specific, checkable, with its denominator attached, including what it failed to do. Anything short of that is a story wearing a number for a costume.

Run your business on receipts, not moods

Most of what gets sold to a busy founder is a mood. It arrives as optimism about the future and leaves nothing behind you can audit in ninety days. By the time you'd notice it didn't work, the conversation that sold it to you is long over and the money is spent.

The fix is almost rude in its simplicity. Stop buying futures. Start buying records. Ask everything and everyone in your operation to leave a paper trail, and treat the absence of one as the result it usually is. A back office that works produces evidence as a byproduct. The evidence isn't extra. It's the proof that the work is real and not a feeling about the work.

This changes how you run things, not just how you buy them. When your default question becomes "what did we count?" the whole operation quietly tightens, because people manage what gets measured and ignore what doesn't. The adjectives drain out of your status meetings. What's left is shorter, truer, and a lot easier to act on.

A feeling is a story. A list is proof. Build the kind of operation that can hand you the list without anyone staying late to write it. If you want to see what that looks like running underneath a business, that's what we build at MARSA — the part that does the work and leaves the receipt. marsa.ai/business.