Your business has grown. Have your systems?
When you were 15 people and doing $5 million in revenue, you could run the business on Excel, email, and a shared drive. Everyone knew where everything was. The workflow was informal but it worked. You could scale fast with minimal infrastructure.
That was then. Now you're 50–100 people and doing $20 million+. The team has tripled. The projects have gotten more complex. The data volume has exploded. But your systems haven't changed. You're still stitching together the same cobbled tools with manual processes and workarounds.
This isn't a failure. It's actually a growth signal. The question isn't why the systems are straining — it's whether you'll recognise the signs before everything breaks.
Sign 1 — Your best people are the integration layer
There's one person who "just knows" where everything is. They know that the project status is in this spreadsheet, the actuals are in that tool, the client communication happened in email. When something needs to connect, they reconcile it manually. When a question comes up that requires pulling data from three systems, they spend an hour piecing it together. When they're sick, nothing moves. When they leave, you realise how much institutional knowledge walked out the door.
This person isn't being inefficient — they're being heroic. They're holding together systems that were never designed to work together. But you can't scale a business on heroism. You scale it on systems. When your best people are spending their days being glue, they're not doing the work only they can do.
Sign 2 — Month-end takes a week (and nobody trusts the numbers)
Finance closes the books. Operations disputes the figures. The PM says the project was 15% profitable; the accountant says it was 8%. The gap isn't small enough to ignore, but it's big enough to distrust. Nobody's lying. The data just lives in different places and gets reconciled differently by different people.
When month-end takes a week and the output is still disputed, you don't have a data accuracy problem. You have a system architecture problem. The business is running on partial instruments.
Of mid-sized companies say they've outgrown the digital tools they started with
They're operating on systems designed for a fraction of their current size and complexity. They know it. The question is when they'll do something about it.
Sign 3 — You've bought tools, but they don't talk to each other
Your sales team uses HubSpot. Your delivery team uses Asana. Your finance team uses Xero. Project Intake happens in a form. Billing triggers from a spreadsheet. The tools all work beautifully on their own. But the joins are manual. Data gets copied. Spreadsheets get created to bridge the gaps. Each system is a silo.
You've invested in tooling, but not in connectivity. You've added complexity without adding integration.
Of decision-makers say siloed systems actively limit business growth
It's not just an efficiency problem. Nearly half of business leaders say disconnected tools are constraining what the business can actually do — limiting visibility, slowing decisions, and blocking the kind of cross-functional clarity you need to scale.
Sign 4 — Reporting is archaeology, not management
You want to know the real-time margin on your active projects. By the time you get a report, it's from last Friday. Reporting has a lag. Sometimes a big lag. The data is accurate, but it's stale. You're flying on instruments from yesterday, making decisions on outdated information.
In a fast-moving business, that lag is a problem. A margin issue you could have caught early becomes a client relationship problem by the time you see the numbers. A utilisation dip you could have corrected becomes a pipeline miss.
Of business spreadsheets contain at least one error
When reports rely on manual data entry and spreadsheet formulas, errors compound. By the time you're reading a report, you're not sure which numbers are fact and which are formula drift.
Sign 5 — Onboarding takes weeks because the process is in people's heads
A new project manager joins the team. You can't hand them a documented workflow because the workflow doesn't exist on paper — it lives in spreadsheets, email threads, and what people have picked up from watching others. Onboarding becomes "work with this person for a week and pick it up." That week becomes two. The new hire is unproductive while they learn. Your experienced people are pulled away from their own work to teach.
Undocumented processes are a scaling ceiling. You can't grow faster than your ability to teach people the workarounds.
Sign 6 — You're spending money on admin that should be spent on delivery
You have people whose job, in essence, is to manage the gaps between systems. They don't create client value. They don't execute projects. They manage data flow and system friction. In a business of 50–100 people, you might have 2–3 FTEs doing this. That's $200K–$300K a year in payroll that's going to fixing problems that shouldn't exist if the systems were designed properly.
Of senior staff time is spent on admin tasks that systems should handle
That's not a typo. Almost a third of your best people's time is going to system friction, not value creation. Scale that across a team of 50 and you can see why margins compress as you grow.
Sign 7 — Your accountant is asking questions you can't answer quickly
"What's the margin on the Johnson project?" You don't know off the top of your head, so you have to dig. "Can you break down Q1 costs by job?" That takes someone several hours to pull together. "Are we tracking towards our utilisation targets?" You have to check three places and reconcile manually.
When your accountant and your CFO are asking questions that take hours to answer, your systems are telling you something: they're not designed for the business you're actually running. They're designed for the business you used to be.
If you counted 3 or more — what to think about next
Here's what not to do: don't buy anything yet. Don't switch to the new all-in-one platform. Don't hire more admin staff to manage the friction. None of those solve the core problem.
Instead, start by mapping. Follow a single piece of work from creation to completion. A project quote, from the moment it's created in sales through to invoice and payment. Count how many times a human touches that data. Count how many system transitions happen. That's your current state — and it's probably worse than you think.
Once you see it clearly, ask: What if that flow was automatic? What systems would need to talk? What business logic would need to trigger? Where would you save time? Where would you have better visibility? That's your design state.
The gap between those two is where the opportunity lives. Not in buying new tools, but in architecting how work actually flows.
Is this your business?
If you're recognising yourself in multiple signs above, the systems aren't supporting your growth anymore. The first step isn't picking tools — it's understanding how work actually flows, where it's breaking, and what to prioritise.
Take the Self-Assessment