Your 'Good Enough' Systems Are Quietly Bleeding Money

A few weeks ago, I sat down with the CEO of a plastics manufacturer in Southern California. Fifty employees. Solid revenue. Growing. I asked about their quoting process.

“It works,” he said. Then he paused. “I mean, it’s a huge pain in the ass. But it works.”

Here’s what “works” looked like: five people processing purchase orders from scattered email inboxes. Custom price sheets for every customer, manually updated whenever resin prices shifted. An engineering team spending hours on calculations that should take minutes. Their quoting target was 40% margin. Their actual realized margin? Twenty-one percent.

Nobody had connected those two numbers. The system “worked.” It just worked badly enough to leak nearly half their target margin into thin air.

This is the most expensive lie in business: “It’s fine for now.”

The Hidden Cost of “We’re Very Antiquated”

I hear some version of this phrase in almost every discovery call. Founders and operators know their systems are held together with duct tape. They’ll even say it out loud, usually with a self-deprecating laugh. “We’re very antiquated.” “It’s so bad.” “I just want to free up a few hours a month.”

That last one gets me every time. A CEO running a manufacturing operation will describe a forecasting process that lives entirely in a personal Excel spreadsheet, updated manually every month, and frame the problem as “a few hours.” Not as a single point of failure. Not as institutional knowledge trapped in one person’s head. Just a minor inconvenience.

Founders are remarkably good at understating systemic problems. I think it’s a survival mechanism. When you’re running a company, you have to triage constantly. The system that mostly works gets pushed to the bottom of the list, below the deal that needs closing and the hire that needs making. The problem is that “mostly works” compounds. Every manual step is a place where errors creep in, where margin evaporates, where your best people spend their time on work that doesn’t need a human brain.

Technori reported earlier this month that one startup burned through $300,000 of their $2 million raise on cloud infrastructure in just three months. Over-engineering. They eventually rebuilt their architecture and cut that bill by 80%. That’s a dramatic example, but the slow bleed is more common and harder to spot. It’s the five people doing data entry that an integration could handle. It’s the spreadsheet that nobody else can maintain. It’s the quoting process that “works” at half the margin you think you’re earning.

Where the Money Actually Goes

When I audit a company’s systems, the leaks usually fall into three categories.

Process leaks. Manual steps that exist because “that’s how we’ve always done it.” Every handoff between a person and a spreadsheet, or between an email and a system, is a place where data gets lost, duplicated, or delayed. I’ve seen companies where five different people touch the same customer order before it reaches production. Not because five steps are needed, but because nobody ever mapped the flow end to end.

Knowledge leaks. Critical business logic that lives in someone’s head instead of in a system. The operations manager who knows the pricing rules. The developer who’s the only one who understands the deployment process. The founder who manually runs a monthly forecast in their personal spreadsheet. This isn’t just inefficient. It’s a business continuity risk. What happens when that person takes a vacation? Or quits? I’ve written before about key person risk, and this is where it starts: in the systems that depend on one brain to function.

Visibility leaks. You can’t improve what you can’t measure. When your data lives in email threads, spreadsheets, and people’s notebooks, you have no real-time picture of your business. That plastics manufacturer had no idea their actual margins were 21% instead of 40% because the data to connect those dots was scattered across half a dozen disconnected systems. They weren’t making bad decisions. They were making decisions with bad information.

The Fix Isn’t Always a Big Rewrite

Here’s where I see founders make the second mistake. They recognize the problem, and then they overcorrect. “Can you build us a full ERP? Soup to nuts, CRM, inventory management, accounting?”

Maybe. Eventually. But probably not right now.

The companies I work with at Jetpack Labs rarely need a ground-up rebuild on day one. They need the right intervention at the right layer. Sometimes that’s an AI-powered quoting engine that cuts a 15-hour process to 15 minutes. Sometimes it’s an integration that connects two systems that were talking to each other through a human clipboard. Sometimes it’s just instrumenting what you already have so you can see the real numbers.

The key is knowing where the biggest leak is and stopping it first.

I think about it like plumbing. If you’ve got a burst pipe in the basement, you don’t start by renovating the bathroom. You stop the flood. Then you assess the rest of the system. Then you make a plan.

Technori’s recommendation is that startups should reserve 15% to 25% of each sprint for addressing technical debt and system improvements. I’d modify that slightly: spend the first sprint just mapping where the water is going. Talk to the people who actually use the systems every day. They know where the problems are. They’ve usually been working around them for years.

What “Fine for Now” Actually Costs

Let me make this concrete. Say you have a five-person team spending an average of two hours a day on manual data processing that could be automated. That’s ten person-hours a day. Fifty a week. At a blended cost of $40 an hour, that’s $2,000 a week, over $100,000 a year, spent on work that a well-designed integration could eliminate.

That’s not the total cost, though. It’s the direct cost. The indirect costs are harder to measure but often larger: errors that require rework, delayed decisions because the data isn’t ready, opportunities missed because your team is busy with busywork instead of building relationships or improving your product.

And then there’s the compounding effect. Every month you don’t fix the leak, the cost continues. Every new customer you add makes the manual process a little more painful. Every price change creates more spreadsheets to update. The system doesn’t just stay “fine.” It gets worse, slowly, in ways that are hard to notice until they’re expensive.

Starting the Conversation

If any of this sounds familiar, here’s what I’d suggest. Pick the one process that your team complains about the most. Not the one that’s theoretically the biggest problem. The one that someone brings up at every team meeting, or the one that keeps a key person working late.

Map it out. Every step. Every handoff. Every place where data moves from one format or system to another. You’ll probably be surprised by how many steps there are and how many of them exist for no good reason.

Then ask: what would this look like if we started from scratch today? Not “what software should we buy,” but “what does the ideal flow look like?” Start with the process, not the tool.

That’s the work I do with founders every week. Not selling software. Not pushing toward the biggest possible project. Just finding where the water is leaking and helping you decide which pipe to fix first.

If you’re sitting on systems that “work” but you suspect they’re costing you more than you realize, I’d be happy to talk through it. Sometimes a thirty-minute conversation is all it takes to spot the leak.