The hidden cost of swivel-chair work

Every business we've ever audited has some version of this conversation:

"And then Lisa copies the order from the email into the CRM. And then she types it into the scheduling system. And then she updates the spreadsheet for the finance team."

That's swivel-chair work — the pattern where a person is the integration between two systems that should talk to each other. It's the single most common source of silent cost we find in SMBs, and also the most quickly addressable.

Why it's invisible

Swivel-chair work hides because nobody's job description says "re-type data between systems." Lisa's title says "Operations Coordinator" and her job includes a hundred real responsibilities. The re-typing is just one of them — she's fast, she rarely makes mistakes, and she's been doing it for years.

The cost is absorbed into her salary and never surfaces on any line item. But it's still there.

How to find it

Three questions surface most of it in an afternoon:

1. "Walk me through an order/lead/ticket/invoice from arrival to close." Listen for phrases like "and then I put it into" or "and then I update the…" — every one of those is a candidate.

2. "Which systems do you have open right now?" If the answer is five or more, something is getting copied between at least two of them.

3. "What do you do first thing Monday morning?" Reconciliation work hides here — people quietly syncing data across systems to start the week clean.

The math

Here's the math that usually lands with founders:

• One coordinator, 90 minutes a day on swivel-chair work.
• 90 min × 5 days × 50 weeks = 375 hours/year.
• At a $30/hr fully-loaded cost, that's $11,250/year.
• Per person. Across a 10-person operations team, that's six figures annually in labor going into work that creates zero customer value.

That's the raw labor number. It excludes:

• Error cost — every transcription step introduces errors, which introduce downstream cleanup, which introduces more labor.
• Speed cost — swivel-chair steps delay every process they're part of. Response times get measured in hours instead of minutes.
• Morale cost — nobody got into this business to be a human API. Your best people notice, and some of them leave.

What to do about it

Integration doesn't have to mean a six-figure software project. Most swivel-chair work is eliminated by one of three things:

1. A native integration you haven't turned on. Your existing tools probably talk to each other already — the connection was never configured.

2. A lightweight automation platform. Workflow tools can move the data between systems for a small monthly cost, often without a single line of code.

3. A small custom integration. When native and no-code options don't fit, a couple of days of engineering work can eliminate the step permanently.

The right answer depends on volume, system APIs, and data sensitivity. But the decision is tractable in a week, not a year.

Where to start

The swivel-chair workflow worth fixing first isn't the longest one. It's the one that:

1. Runs most often (daily or more).
2. Feeds customer-facing response time (orders, quotes, leads, support tickets).
3. Has the most error-prone current state.

Fix that one. Measure the before and after. Use the win to fund the next one.

Every business has ten hours a week of invisible labor going into swivel-chair work. Finding the right one to eliminate first is an afternoon of investigation and a few weeks of work. The payback period is almost always under a quarter.