The Swivel Chair Tax

You know the move even if you've never heard the name for it: pull up System A on one monitor, copy the number, swivel the chair, paste it into System B. Somebody in your business is doing this right now, probably several times a day, probably for a system you assumed was "integrated" because both tools have the word "API" on their pricing page.

It works. That's exactly the problem — it works well enough that nobody escalates it.

Nobody puts "swivel chair" on the org chart

This kind of manual bridging never shows up as a line item. It shows up as:

• "Oh, Denise handles that, she's just really fast at it."
• A recurring 4pm Slack message asking if the numbers reconciled today.
• A spreadsheet named master_v3_FINAL_actual.xlsx that one person understands.
• A new hire who takes three weeks to learn "the process" that turns out to be a person, not a process.

Every one of those is a real cost. None of them shows up on an invoice, so they never get compared against the cost of just building the integration.

What it actually costs

• Denise's time, which is the visible part and usually the smallest part.
• The error rate, because humans copying numbers between systems make mistakes at a fairly predictable rate, and nobody's tracking how often "the numbers don't match" traces back to a typo in a paste.
• The bus factor, because when Denise is out sick, the reconciliation doesn't happen, and nobody finds out until a customer complains.
• The ceiling on growth, because manual bridging scales linearly with headcount. Double your order volume and you need to double Denise, and Denise doesn't scale that way.

Why it persists anyway

Because the manual version has zero upfront cost and the integration has an invoice attached to it. That comparison feels obvious, right up until you actually add up what the manual version has cost over the two years nobody looked at it.

The integration isn't the expensive option. It's the one that has a price tag, which is a different thing.

If someone in your business is the unofficial API between two systems, that's usually the highest-leverage integration you can build — not because it's technically hard, but because you're paying for it every day whether you notice or not.