Cost of Fragmented Work

There's a productivity problem most teams don't recognise. It's not that anyone is slow. It's not that anyone is lazy. It's not that anyone is bad at their job.

It's that nobody knows what anyone else is doing.

I've watched this kill ops teams in three different companies. The pattern is always the same: each function builds its own tools, its own processes, its own data. Sales lives in HubSpot. Support lives in Zendesk. Product lives in Linear. Engineering lives in GitHub. Finance lives in spreadsheets.

Each of those tools is great. The fragmentation is what breaks people.

What it actually costs

The visible cost is duplication: the same customer data entered into four systems, the same status updated in three places, the same question asked in two channels because nobody knew it was already answered.

But that's the small cost.

The bigger cost is invisible: every cross-functional decision gets made with partial information. The CSM doesn't see the support tickets. The salesperson doesn't see the product usage. The engineer doesn't see why the feature was requested in the first place.

So everyone makes locally-optimal decisions that add up to globally-bad outcomes.

A specific example

Last month I talked to a Series B SaaS company. Their CSM team was confused why customers kept churning despite having "healthy" usage scores.

Their usage data was in their product analytics tool. Their support tickets were in Zendesk. Their NPS scores were in a separate survey tool. Their renewal conversations were in HubSpot.

Each tool said the customer was fine. Together, the picture was: customers were using the product less every week for three months, opening more support tickets each week, scoring lower in NPS, and dodging renewal conversations.

The CSM team didn't see this because no single tool showed all four signals.

The fix isn't a new tool

The instinct is to find a tool that combines everything. There are dozens of "customer 360" platforms that promise this. They mostly fail because they require you to abandon the tools your teams actually use.

The fix is connectivity. Let the teams keep their tools. Build the connective tissue between them — the workflows that pull signals from one system into another, the routing logic that escalates patterns, the dashboards that combine views.

This is the work most companies skip because it's not a project. It's an ongoing investment. You build a workflow today, another next week, another the week after. Over time you build a nervous system for the company.

Why we built Nimbus

Honestly: because we kept hitting this wall at every company we worked at.

The fragmentation problem doesn't get solved by buying a bigger tool. It gets solved by connecting the tools you have, in patterns that match how your team actually works.

That's what we're trying to build.

— Owen Brooks