Why Does It Take Eight Systems to Answer One Customer Question?

Because the tools were never connected, so your people became the connection. Each login is small, nobody counts them, and the total is a tax your team pays every day.

This is the second pattern in Friction, Found, our series on the friction we see most often inside growing companies.

What is the login tax?

The login tax is the time your team spends going out to systems to collect answers that could have come to them. A customer asks where an order stands. To answer, someone opens the order system, then a supplier portal, then a carrier site, then the inbox, then the spreadsheet that holds the notes none of the systems have room for.

Picture an office where that tour runs eight to ten logins long, several times a day, for more than one person. Nobody would design it that way. It built up one portal at a time, and each one was added for a good reason.

How can you tell if your team is paying it?

Watch what is open on their screens, then listen for a few phrases. Four signs tend to show up together:

• The same row of tabs stays open all day and gets rebuilt every morning.
• Status questions get answered with "let me check and get back to you."
• One person knows which portal is right when two of them disagree.
• Nobody can say how many status checks happen in a day, because counting them is nobody's job.

That last one is why the tax survives. A cost with no owner never makes it onto anyone's list.

What does the login tax cost?

It costs attention more than minutes. Each check takes a moment. The switching is the expensive part: the person stops what they were doing, goes hunting, and has to find their place again when they come back.

It also sets the pace of your customer service. If an answer takes six logins, the customer waits for it, and your most capable people spend the day as couriers between systems.

And the tax grows quietly. Every new vendor portal and every new tool adds a stop to the tour. Nobody approves the increase, because nobody sees it.

Why does this happen even after buying good software?

Because each tool was bought to solve its own problem, and connecting them was nobody's project. The order system does orders well. The carrier portal does tracking well. The gap between them gets filled by a person with two browser tabs.

When tools do not talk, people become the integration. It works, which is why it lasts. We wrote about the same trap from the reporting side in the status-update tax.

What is the first move?

Count the checks for one week. That is the whole first step.

1. Ask the people who answer status questions to keep a tally: which system they opened, and what they were looking for.
2. At the end of the week, group the tally by question instead of by system. "Where is the order" and "has it shipped" are usually near the top.
3. For the top question, ask one thing: could this answer come to us, instead of us going to get it?

Most of the time it can. A status change can trigger a message. A daily summary can land in one place. The check that took six logins becomes a notice nobody had to go find.

Does fixing it mean buying a new platform?

No. If the rule is no new platform and no new spend, the conversation gets more focused, not shorter. The tools you already pay for can usually be connected through an automation layer that sits between them. The team keeps the screens they know, and there is nothing new to learn.

The question to ask is narrow: what do we already own that could send this status to us? We covered how to make that call in automation platform, or just fix the handoff.

What about portals that belong to vendors you cannot change?

Leave them alone and change how often someone has to visit. Many vendors already send status emails that nobody routes anywhere useful. Start with the systems you own, since those are the ones you can connect. The vendor portals usually shrink to a small number of checks that are worth keeping by hand.

Who should own this?

Someone has to, and it is rarely in a job description. IT owns whether the systems are up. Each department owns its own tool. The trips between them belong to no one, which is how they multiplied. We wrote about that gap in who owns the seam between your operations and your software.

Naming one person to own the count, even for a month, is usually enough to get the first connection made.

How do you know it is working?

The row of tabs gets shorter, and "let me check" gets rarer. Customers get an answer on the first call. The people who used to carry status between systems get that attention back for work that needs judgment.

Count again after each change. If the tally for that question drops, move to the next one.

Where should you start if you see this in your own company?

Run the one-week tally. It costs nothing, and it turns a vague frustration into a short list.

If you want a second set of eyes on that list, bring it to a Friction Audit. Give us 45 minutes and we will go through where your team is going out to collect answers, and which of those could come to them using what you already pay for. The Leverage Map that comes out of it is yours to keep.