Death by a Thousand Systems

I was talking to a mid-sized commercial builder in New York recently, and they were telling me how painful it is just to get reporting on where they stand financially across their jobs. It takes almost an entire day, sometimes longer, to pull together a straight answer on their current cash position. This wasn't a small shop with no software. It was a sophisticated builder with real tools throughout the business.

As we dug in, it turned into a story I hear seven or eight times a week. Five or six systems, each one good at its one job. One for bidding and budgeting. One for scheduling. One for RFIs and submittals. Accounting somewhere else. A pile of spreadsheets holding it all together. Nothing talks to anything else, so somewhere in the middle of it there's a person, or a few people, whose real job has quietly become stitching it together by hand.

This has become the status quo. Every builder I talk to is running some version of it, and the whole industry has quietly accepted it as 'just how construction works.' You need a tool for bidding, a tool for scheduling, a tool for accounting, so you go get them, and you live with the gaps between them. Except those gaps aren't free. They cost hundreds of thousands of dollars a year in wasted salary, errors, and lost margin, hiding in plain sight because everyone's been paying it for so long it stopped looking like a cost. So let's unpack how we all ended up here, what it's actually costing you, and how you get out of it.

Nobody Chose This. We All Ended Up Here Anyway.

Nobody decides to run their company on five or six different systems. It happens one tool at a time. You start with one. Then you add another because you need to send ITBs out faster. You add another because you need somewhere to manage your schedule. Then you bring in accounting software because you're scaling and need somewhere real to track the financials. Every time, it feels like you're gaining efficiency. And every time, the tool did solve a real problem.

The problem is, as you're adding tools, most people don't stop and look at the whole system. So the tools pile up. The manual work of connecting them piles up faster, and all that data entry and re-entry falls on your team. We were doing this at Ernest, and I genuinely believed we were getting more efficient with every tool we added. We weren't. We'd added five or six systems to improve the business and ended up less efficient than when the whole thing lived on Excel, email, and in my head.

That's the part that still gets me. None of the tools failed. The failure was in the space between them, and there was no software for that space. There was just us.

The Gaps Between Your Systems Cost Real Money

It's easy to write this off as annoying but survivable. In reality, it's killing you slowly. No single tool is ever the problem. The whole system is.

This starts with your team being the glue, manually filling in the gaps and holding everything together. The builders I talk to describe the same thing: their team spends five to ten hours a week, per person, just moving data between systems. At the high end that's a full day, a quarter of the week, gone. If you're paying your PMs $100K a year, that's $25K per PM paid for data entry.

Then there are the human errors. Moving data by hand between systems means something eventually goes wrong. A scope gap left open. A budget line misplaced. A CO value billed incorrectly. Every mistake costs money. You catch them on a quiet day when it's cheap to fix. You don't catch them during the chaos of bid day when it's extremely expensive.

Finally, the biggest impact to your business and margin is headcount bloat. You keep hiring, because everyone truly is busy. Another PM, another coordinator, not because you won more work but because the work you already have is drowning the people doing it. You're scaling the glue instead of scaling the business.

That's the trap. With every system you added, you got less efficient, wasted more salary, created more errors, and over-hired to keep up, and it's almost impossible to spot, because it happened slowly and everyone genuinely is busy. Builder after builder we talk to is carrying this exact cost.

We Didn't Want a Better Tool. We Wanted an Operating System.

The answer was never going to be a seventh tool that talked to the other six a little better. We tried versions of that. Better integrations, more automations, another dashboard to see across the others. It's still five or six systems and now you're paying to maintain the wiring between them.

What we actually wanted wasn't another tool. It was an operating system for the whole business. One place that ran the entire job, precon to turnover, budgeting to billing, bidding to project management. Not five tools with better plumbing between them. One system where the data got entered once and then moved on its own.

That's what we built, and it's what became Shackleton. A super submits a daily log and the schedule updates. A sub's quote flows straight from your bid into a draft subcontract, so nobody's copying numbers between tools. An RFI sitting unanswered shows up against the trade schedule it's about to delay. Nobody touches an export button, because there's nothing to export to. When you ask our AI agent where a job stands, it isn't stitching five files together, it's reading the one set of data the whole company already works from.

Once we got onto a single system, everything changed. The hours came back almost immediately. Our team stopped babysitting spreadsheets and got to focus on building again. We did more with the same team, bid more, won more, and made more on every job we ran. Revenue per PM doubled, without adding a single hire to keep up.

So here's the honest test. Walk over to your team right now and ask which of your jobs are behind schedule and under-billed at the same time. In one system that's a thirty-second answer. In five, it's a project, because your schedule and your financials live in different tools that have never spoken. If you get a clean answer on the spot, you don't have this problem and you can ignore me.

If they start clicking through systems to piece it together, that's your answer. It's death by a thousand systems, and it's been quietly costing you for years. You've built a real business in spite of your software. Imagine what you'd do with software that actually worked for you.