Skip to content

Articles

Why one tool for everything fails across companies

Updated 5 min read By Operators team

“One tool for everything” fails across companies because each company has its own team, habits, clients and confidentiality rules. The tool that suits one rarely suits all, the migration stalls halfway, and the walls between companies get thinner. A lighter approach works better: let each company keep the tools its people use, and gather only what needs you into a single view on top.

The key points

  • Each company’s team chose its tools for reasons. Overriding them has a cost.
  • Migrations across companies often stall halfway, leaving two systems.
  • Putting several companies in one workspace weakens the separation between them.
  • What you need is one view of what needs you, not one tool for all the work.
  • Leave the work where it lives, and collect the signals.

Why it is tempting

When you run several companies, the tool sprawl is real. Three trackers, two chat tools, four inboxes. Moving everyone onto one system sounds like the obvious fix. One login, one search, one place to look.

For one company, consolidating tools is often right. Across several companies, the picture changes.

Why it fails

Each team chose its tools

An engineering team on one tracker and an agency team on another did not choose by accident. Their tools fit their work, their clients and their habits. Asking them to move costs weeks of their time and some of their goodwill, to solve a problem that is mostly yours.

Clients and partners have their own tools

A fractional COO cannot move a client onto their preferred tracker. A studio cannot make every portfolio company’s customers use the same support desk. Much of the work across companies lives in tools you do not control.

Migrations stall halfway

Moving one company is a project. Moving four is a programme. Somewhere around the second company, a crisis arrives, and the migration pauses. Now you have the old tools and the new tool, and more places to look than before.

Shared workspaces blur the lines

Putting several companies into one workspace with folders or projects per company makes the separation depend on permissions settings. Those get copied, widened for convenience and forgotten. Search crosses companies. A new hire at one company can find another’s plans. For fractional executives, a mixed workspace can breach a client’s confidentiality terms.

One tool rarely fits every stage

A two-person company and a fifty-person company need different things. A tool configured for one is either too heavy or too light for the other.

What you actually need

Look at the problem again. You do not need every company’s work in one tool. You need to know, in one place:

  • What is waiting on you, across every company.
  • What is due today and tomorrow.
  • What got done.
  • What has gone quiet.

That is a much smaller set of information than “all the work”. It can be gathered from many tools without moving any of them.

The lighter approach

Leave the work where it lives

Each company keeps the tools its team uses. Detailed tasks, conversations and documents stay there. You still open them when you need the detail.

Collect the signals into one view

Gather only the signals into one view, grouped by company: requests waiting on you, deadlines, completions. You can do this by hand with a daily list, or with a board that reads each company’s tools. Operators is one example: it reads from each company’s tools, keeps titles, dates, owners and links rather than the content itself, and keeps each company walled off from the others.

Keep the separation at the company level

Each company stays in its own space in its own tools. Your combined view should still show which company every item belongs to, and never file one company’s work under another. A view that asks you where something goes is safer than one that guesses. The Unsorted guide shows how this works in Operators.

Fill gaps without migrating

For tools that your combined view cannot read yet, send their important events in through an automation, rather than moving the tool. The guide to sending work in from other tools shows one way.

Read, do not write

A combined view that only reads from each company’s tools is safer than one that writes back. It cannot break anything in the tools, and the teams keep ownership of their own systems. The article read-only by default explains why.

When consolidation does make sense

There are good reasons to share a tool across companies:

  • Shared functions. A studio’s shared finance or design team works across companies and benefits from one system for that shared work.
  • The same team. Two companies run by the same small team with the same processes.
  • A deliberate merger. When companies are combining anyway.

Even then, keep each company’s own work in its own space within the tool, and check the permissions regularly.

A quick test before you consolidate

Ask three questions:

  1. Do the teams want this, or do I?
  2. Will the companies be as well separated afterwards as before?
  3. Is my real problem the number of tools, or the number of places I have to look?

If the answer to the third is “places to look”, a single view on top will usually solve it faster, and without anyone having to move.

What to do next

Questions people ask

Should all my companies use the same project management tool?
Only if the teams genuinely want it and the companies share people and processes. For separate companies with separate teams, forcing one tool usually costs more than it saves.
Why not put every company in one workspace with separate folders?
Folders are a weak barrier. Permissions get copied, search crosses companies, and people end up seeing work they should not. Separate companies are safer in separate workspaces.
How do I see everything if every company uses different tools?
Gather only what needs you, such as requests, deadlines and what got done, into one view grouped by company, and leave the detailed work in each company's own tools.
When does a shared tool across companies make sense?
When the companies share a team, such as a studio's shared design or finance function, and the shared work genuinely spans them. Keep the companies' own work separate even then.

See every company you run on one screen.

Try the demo first: no sign-up, and every screen works on made-up data. You can't connect your own tools to it.

Join the list