Prove the Return or Don't Spend the Time

TL;DR: You can raise more money, hire more people, and buy more compute, but you cannot buy back a quarter. Time is the only line item that never refills, which means every investment of money or effort has to earn a demonstrable return — not a vibe, a number. The most common way businesses violate this is buying software nobody asked for: a tool sold to someone senior, justified by a pain no one actually had, opened twice after onboarding, and quietly billed for years. The fix isn’t a procurement policy. It’s one question you ask before you spend anything: what measurable thing gets worse if we don’t do this, and how will we know in 90 days? If you can’t answer, you’re buying bloat.

Time is the only non-renewable line item

Every other resource a business runs on can be topped up. Run low on cash and you raise a round, take a loan, or sell more. Run low on people and you hire. Run low on compute and you put it on a card. The supply is constrained, sometimes painfully, but it exists.

Time is the exception. The quarter you spent migrating to a database you didn’t need is gone. The two engineer-months poured into a process that protected no one don’t come back when you realize the mistake. There is no funding round for last spring. This is the asymmetry that should govern how a business spends, and almost nobody runs their company as if it were true.

I’ve watched smart operators agonize for a week over a $5,000 line item and then wave through a decision that quietly burned a month of the team’s attention — because the month never showed up on an invoice. Money is legible. Time isn’t. So we guard the legible resource and hemorrhage the irreplaceable one.

The entire discipline of running a business well comes down to fixing that backwards. Treat time as the scarcest thing you own, because it is, and force every claim on it — every tool, every initiative, every “we should really” — to justify itself against that scarcity.

“Demonstrable” is the operative word

It is easy to agree that investments should pay off. The agreement is cheap because pay off stays comfortably undefined. The work is in the word demonstrable.

A demonstrable return is one you can point at. A metric that moved. A cost that dropped. A cycle that got measurably shorter. Revenue you can trace back to the thing. The test isn’t “did this feel worth it” — feelings are generous narrators — it’s “can I show you the number, and would you have predicted that number before we started?”

Most spending that goes sideways fails precisely here. It produces the sensation of progress without the substance. A new tool gets adopted, dashboards light up, there’s a Slack channel and a launch and a sense that the team is now Doing The Thing Properly. None of that is a return. Activity is not output. Looking busy is not the same as moving a number, and a surprising amount of what businesses buy is, on honest inspection, the purchase of the feeling of being on top of things.

If you can’t say in advance what number a spend is supposed to move, you have not made a decision. You’ve made a purchase and attached a story to it.

The bloat tax

Here is the pattern, drawn from more companies than I’d like to admit having seen it in.

A platform gets bought — call it forty thousand a year, all-in once you count seats — to solve a problem. Someone senior sat through a very good demo. The vendor’s deck described a pain in language crisp enough that everyone nodded, and the tool was approved on the strength of that nod. It onboarded. There were training sessions. For about six weeks it had the glow of the new system everyone’s supposed to be using.

Then the usage graph did what those graphs do. A spike during onboarding, a slope down through month two, a flat line by month three that never recovers. Eighteen months later it’s still being billed, nobody can quite remember who owns the contract, and the honest answer to “what does this do for us” is a shrug and “it was supposed to help with…” The sentence doesn’t finish because the pain it was bought to kill was never one the company actually had. It was a pain the demo had.

That’s the bloat tax. Not a single dramatic mistake but a slow accretion of tools that each made sense in the room where they were approved and add up to thousands of dollars a month solving nobody’s problem. Seat sprawl. The analytics suite the marketing hire used at their last job. The second project tracker bought because the first one “wasn’t quite right,” now running in parallel with it. Each one defensible alone. Together, a tax on the company that no one voted for and no one can point to a return from.

The mechanism is always the same: the tool was matched to a described problem, not a measured one. Nobody asked, before signing, what specifically would get worse without it — and so there was no way to ever tell whether it helped.

Effort is spend too

Money at least leaves a trail. The more dangerous version of this disease spends time, and time doesn’t invoice.

The migration nobody needed is the canonical case. The current system is fine — boring, a little unfashionable, but fine. Someone makes the case that the new thing is cleaner, more scalable, more correct, and the case is technically true in the way that most architecture arguments are technically true. A quarter disappears into the move. At the end the company is in roughly the same competitive position it started in, having spent its scarcest resource buying tidiness no customer will ever feel.

Or the process ritual: the mandatory review, the extra approval step, the meeting that recurs forever, each instituted to prevent some problem that, examined closely, had happened once and wasn’t actually prevented by the ritual anyway. These have negative return. They consume time every single week and protect against nothing, but they survive because removing them feels reckless and keeping them feels responsible.

This is the same illness as the unused platform, with the diagnostic harder to run because there’s no line item to flag. You have to notice it deliberately. The question that catches a $40k tool — what gets measurably worse without this? — is exactly the question that catches the needless migration and the protective ritual. We just rarely point it at our own effort, because our own effort always feels like work, and work feels like progress.

Why smart teams keep doing this

None of this happens because people are foolish. It happens because every force in the room pushes toward spending and almost none push back.

Sunk cost keeps the dead tool alive: we’re already paying for it, ripping it out would admit the original call was wrong, so it stays. Optics reward motion: a leader who launches a new platform looks decisive, while one who kills three redundant ones and buys nothing looks like they’re not doing much — even though the second created far more value. Fear of the gap drives the purchase: a competitor uses the tool, a peer company has the process, and the absence feels like a risk you can close with a credit card. And “everyone uses it” does enormous unearned work, because matching what’s standard feels safe even when standard is wrong for your stage and size.

Add it up and the default gradient of any organization slopes toward more — more tools, more process, more spend — with nothing on the other side of the scale unless someone deliberately puts it there. The deliberate counterweight is the whole job.

The test

You don’t need a procurement policy or a quarterly audit ritual, both of which risk becoming their own bloat. You need one question, asked out loud, before any meaningful spend of money or hours:

What measurable thing gets worse if we don’t do this — and how will we know in 90 days?

That’s it. Two clauses, and most bad spending dies on the first one. If you can’t name the specific thing that degrades without the tool, the migration, the process, then you’ve found a solution shopping for a problem, and the honest move is to not spend. If you can name it but can’t say how you’d know in 90 days whether it worked, you’ve named a hope, not a return, and you’ve given yourself no way to ever shut it off.

The 90-day clause matters as much as the first. A return you can’t check is a return you’ll never disprove, which is how the unused platform survives to year two. Naming the signal in advance — the number that should move, the date you’ll look — builds the off-switch at the same moment you build the on-switch. You decide before you’re emotionally invested how you’ll know if you were wrong.

It feels almost too simple to be a discipline. That’s the point. It’s not hard to understand; it’s hard to do, because doing it means saying no to plausible, well-demoed, everyone-uses-it spending that every instinct says yes to.

What running a business actually is

Strip away the rest and running a business is this: spending a finite, non-renewable resource on the small set of things that demonstrably pay you back, and refusing — actively, against the room’s gradient — the much larger set of things that merely feel like progress.

The tools that became bloat weren’t bought by careless people. They were bought by competent operators who skipped one question because the demo was good and the spend was approved and saying no would have felt like falling behind. The cost wasn’t only the money, though the money was real. It was the attention the team spent half-using something that solved nothing, and the quarter that bought tidiness instead of advantage — time that doesn’t come back, in the one budget that never refills.

So prove the return, or don’t spend the time. Everything else is a story you tell yourself while the only resource that matters drains away.