5 Integration Red Flags That Are Costing You Money Right Now

Key takeaways

• If five people on your team spend 30 minutes a day checking another system, that’s over $22,000 a year in salary spent on lookups, before counting the errors and delays those lookups cause

• Integration problems rarely announce themselves. They hide in the reconciliation spreadsheet, and in phrases like “let me check the other system”

• Each red flag on its own looks like a minor inconvenience. Together they’re one problem: a workflow that only works because people carry data between systems

• Fixing the root cause (the disconnect between your systems) is usually cheaper than paying for the symptoms, but not always. A workaround that runs a few times a week can be cheaper to keep

Most integration problems don’t look like integration problems. They look like a busy team doing its best with a complicated process.

Nobody calls a meeting to announce “our systems aren’t connected properly.” What you hear instead is “I’ll just check that in the warehouse system,” or “the numbers should match by Friday.”

The tricky part is how fast these problems start to feel normal. Copy data between platforms for two years and it stops feeling like a problem. It starts feeling like the job.

The hidden cost is still there, though. It’s spread across dozens of small inefficiencies, each one too small to bother fixing, and somebody is still paying for all of them.

The five red flags below are one problem showing up in five places: a workflow that runs across several systems, with people carrying the work over the gaps. We call that human middleware.

If you recognize more than one, it’s worth finding out what they’re costing you. Not every one is worth fixing, and we’ll get to which. And if one makes you wince, don’t take it personally. Nobody designs a business this way. It piles up.

Red flag 1: “Let me check the other system”

Your sales team is on a call with a customer and needs to confirm stock. They minimize the CRM, open the warehouse management system, search for the SKU, and read the number back.

This happens several times a day, across several people. Nobody thinks twice about it, because it’s always worked this way.

The cost of context switching between apps is higher than it looks. If five people on your team spend 30 minutes a day checking a second system, that’s 12.5 hours a week of paid time spent on lookups. At $35 an hour, it comes to over $22,000 a year.

That’s back-of-the-envelope math, on purpose. Swap in your own headcount and your own rate and see where you land.

McKinsey’s research puts the wider picture higher still: knowledge workers spend nearly 20% of their working time hunting for internal information.¹

And every lookup is a small window for error. The stock figure might be stale by the time they find it. The person reading it out might misread a field.

We worked with a wholesaler whose sales team had to leave their order management platform to check warehouse stock by hand before confirming anything to a customer. Log into a second portal, look the number up, come back, finish the order.

Orders still went out. Customers still got served. But the cost in time and accuracy was real, and it added up every day.

Once the systems were connected and stock levels flowed across on their own, the sales team stopped working as translators between two databases and went back to selling.

Red flag 2: Someone’s job is mostly copying data between platforms

You have someone on the team, maybe in operations, maybe in finance, whose day revolves around a spreadsheet. Export from one system, tidy the columns, import into the next. Repeat until lunch.

They might be copying order details from your ecommerce platform into your fulfillment system, or retyping field reports into a central database. They’re good at it, and fast. But they’re doing work a properly connected system would handle in seconds.

Past the obvious salary cost, the errors add up in ways that are harder to see. One study put the error rate for manual data entry at roughly 1%, even under ideal conditions.² Process 2,000 records a month and that’s 20 mistakes. If each one takes 30 minutes to find and fix at $35 an hour, you’re spending over $4,000 a year on rework from a single process.

Each mistake makes more work downstream, too: a customer complaint, a return, a credit note, and somebody’s afternoon spent working out what went wrong.

And because the person doing the transfer is usually the only one who really understands it, you’ve got a single point of failure. When they’re on holiday or off sick, the process just stops.

One of our clients had administrators manually re-entering data from emailed field reports into their central system. The technician had already typed it all up once, in a Word template on site. Then someone in the office read it and typed it again.

Time-consuming, and completely avoidable. The information existed. It just wasn’t flowing where it needed to go. Once reports came in through an app wired into their system, the retyping stopped.

Red flag 3: Monthly reconciliation because the numbers never match

At the end of every month, someone in finance or operations spends days, sometimes a full week, reconciling figures between systems.

The orders in your ecommerce platform don’t match the orders in your accounting software. The warehouse’s stock counts disagree with the website. Revenue in the CRM is a different number from the one your payment processor reports.

Everyone knows the numbers won’t match, so reconciliation has become a scheduled ritual. Lock the door, open four tabs, and spend three days finding out why Shopify says 312 orders and Xero only has 308.

(The four orders do turn up eventually. Usually in the tab you checked first.)

Start with the labor. If one person spends three days a month reconciling, that’s roughly $10,000 a year in salary alone.

The bigger damage happens between reconciliations. For a whole month the business runs on numbers that might be wrong, and decisions about purchasing, hiring, marketing spend and cash flow get made on data everyone already knows is shaky. The purchasing mistakes and late invoices from the other 27 days cost more than the reconciliation itself.

When systems aren’t synchronized, discrepancies compound daily. One missed order becomes a stock discrepancy, which becomes a purchasing error, which becomes a fulfillment delay, which becomes a customer on the phone asking where their order is.

By the time the monthly reconciliation catches it, the damage is done and the trail’s gone cold. Reconciliation fixes the numbers. It doesn’t fix whatever broke them.

Red flag 4: Customers get wrong information because systems are out of sync

A customer orders a product your website says is in stock. The warehouse sold the last one this morning.

A client calls to check on an order, and your support team quotes a different delivery date from the one in the logistics system. Your marketplace listings show one price and your own website shows another, because the last update never made it to every channel.

Customer-facing data errors are the most expensive kind, because they cost you trust. Marketplaces keep score too. Amazon expects sellers to cancel under 2.5% of their seller-fulfilled orders in any seven days, and can deactivate them when they don’t.³ An oversold order usually ends as exactly that kind of cancellation.

The direct cost is easy to count. If an oversold order costs $40 in refund processing and you oversell ten times a month, that’s $4,800 a year. But the customer who doesn’t come back was worth far more than $40.

Every pricing mismatch chips away at a reputation you spent years building. Your customers have alternatives, and they’ll use them.

A 3PL came to us about to lose a major client. The client needed to sell through Mirakl-powered marketplaces, and no off-the-shelf integration connected Mirakl to the 3PL’s warehouse system. If the 3PL couldn’t make it work, the client would move to a provider who could.

So we built the sync. Every time stock moves in the warehouse, the change flows through to every marketplace it affects, with a configurable buffer held back so a late update can’t sell something that isn’t there.

The client stayed. The overselling never started.

Red flag 5: You have built workarounds on top of workarounds

You know this one.

The Zapier automation that updates a Google Sheet, which someone checks every morning to decide whether to update the other system by hand. The email rule that catches order confirmations and forwards them to a shared inbox, where someone copies the details into the fulfillment queue. The workaround that was fine at 20 orders a day and now creaks at 200.

Each layer was a reasonable answer to a specific problem. Stacked up, they form a fragile patchwork that nobody fully understands and everybody’s scared to touch.

Workaround debt is the integration version of technical debt, and it compounds the same way. Each new workaround is one more thing that can break, and it makes the eventual fix more expensive.

The more immediate problem is that workaround-driven processes fail in ways that are hard to spot. A Zap fails at 2am, and the order sits in the task history until someone notices and replays it. A webhook times out, and the retry never fires, because there is no retry. Or an order comes in with a field the automation wasn’t built for, and it drops the record without telling anyone.

These aren’t edge cases. They’re Tuesday.

And they tend to surface at the worst possible moment, like Black Friday or the week a big new client goes live, when volume spikes past what the patchwork was built for and nobody has time to debug a Google Sheet. If any of this sounds familiar, we wrote about the specific signs you’ve outgrown low-code automation.

One ecommerce client’s Royal Mail compensation claims ran entirely on a workaround. Xero can’t search inside PDF attachments, so every lost parcel meant opening purchase orders one at a time and reading them, looking for what each item had cost. Some were scanned photocopies. At twenty minutes a claim and sixteen claims a week, that came to roughly 240 hours a year.

It takes about two minutes now. The hours came back, and a whole kind of work that should never have been manual went away with them.

Where all five end up

Live with all five long enough and you get something that isn’t on any checklist, because it doesn’t look like a problem. It looks like good management.

You open a report, and before you act on it, you check whether the numbers are right. You cross-reference the sales figure against the CRM and open the warehouse system to verify the stock count. Then you ask someone in finance whether the revenue number includes last week’s batch of refunds.

You do this so routinely that it’s stopped feeling like extra work. It’s just “being thorough.”

That’s a symptom dressed up as diligence.

When a team treats its own reporting as unreliable by default, every decision takes longer than it should. Purchasing waits until someone “confirms the stock levels.” Hiring slips a quarter because the revenue numbers “need to be validated first.”

Five minutes of sanity-checking sounds harmless. Multiply it across every decision in the company and you get weeks of delayed action, compounding quietly.

If your team’s default posture toward its own data is skepticism, don’t blame the team. They learned it from the data.

What to do about it: a quick integration audit

If you recognized your business in more than one of those, you’re not stuck. The cost of disconnected systems feels permanent because it’s been around so long. It isn’t, and fixing it usually costs far less than living with it.

Start small. Pick one process your team runs every day and follow it from start to finish. Watch where someone switches tabs, opens a spreadsheet, retypes something that already lives in another system, or says “hang on, let me check.” Count the handoffs.

Even 30 minutes watching your order-to-fulfillment flow will turn up things nobody’s questioned in years.

Then widen the lens. Walk through your other core processes (quote to invoice, customer inquiry to resolution) and note every point where someone copies data or waits on another platform. You’ll probably find more handoffs than you expected. Each one is a candidate for automation.

Then quantify the cost. Time the manual steps, and count the errors that need rework. For the customer-facing mistakes, estimate what they cost you in revenue. You don’t need forensic accuracy. A rough number is enough to justify doing something, and to decide which integration to fix first. If you want more structure, we published a five-step framework for calculating automation ROI with real numbers you can adapt.

Prioritize by pain. Not every disconnected system needs to be connected tomorrow. Start with the ones that touch money, stock or customers, because that’s where errors cost the most and where automation pays back fastest.

A reality check: not every workaround is worth fixing right now.

If the process runs a handful of times a week and the manual cost is under a couple of thousand dollars a year, the integration will cost more than it saves. If the workflow itself is still changing (new tools, or a new business model), automating it locks in a process that might need to be different next quarter. And if the workaround is temporary on purpose, a bridge for three to six months while you validate a new approach, that’s a sensible call.

The test is whether the workaround has outlived its justification. If it’s been “temporary” for two years, it’s furniture now.

And get the right help. Integration is a specialty. It shouldn’t be a side project for your busiest developer. The gap between an integration that works on day one and one that still works on day three hundred is mostly unglamorous: proper error handling, and somebody watching for the day an API changes. If you’re not sure where to start, we wrote about why small businesses benefit from a dedicated integration partner rather than trying to piece it together in-house.

Frequently asked questions: integration red flags

How do I know if my integrations are actually costing me money?

Track the time your team spends switching between systems, copying data, reconciling figures and fixing errors caused by out-of-sync information. Multiply those hours by a loaded hourly rate ($35 is a fair default for most small-business roles). It's usually bigger than anyone guessed, because nobody has added it up in one place before. Even a conservative count often lands in the thousands of dollars a month.

We only have a few systems. Can integration problems really be that expensive?

Yes. The number of systems matters less than the volume of data moving between them, and what happens when that data is wrong. Two disconnected systems handling hundreds of transactions a day can do more damage than ten with light usage. The cost follows the activity rather than the number of logos.

Can Zapier or Make fix these problems?

For low-volume, low-stakes workflows, yes. They hit a ceiling fast when the integration touches money or customers, though. The usual failure modes: retries that only cover some errors, failed tasks waiting for someone to replay them by hand, limited data transformation, and monitoring that only catches the loud failures. If your workaround is already a Zap feeding a spreadsheet feeding a manual check, you've outgrown what those tools do well. We wrote a full breakdown of where low-code automation stops working.

How long does it take to fix a broken integration?

It depends on the systems involved and how tangled the existing workarounds are. A focused integration between two systems might take a few weeks. A bigger project with a data migration or a legacy system in the mix takes longer. Before anyone commits to a timeline, Discovery scopes that one job and turns it into a fixed-price technical specification, so the timeline is written down before the work starts.

What if we have already tried to fix our integrations and it did not work?

That's more common than you'd think, and it's rarely the business's fault. Plenty of people have been burned by a developer who built something that worked at first and fell apart when an API changed or the volume grew. The difference is usually in the approach. Error handling and monitoring, with someone still maintaining it after launch, are what separate the integrations that last from the ones that stop working after six months.

Should we fix all our integration problems at once?

No. Prioritize by impact. Start with the integration behind your highest-value process, usually wherever a mistake costs money or a customer. Fix that one and measure the result, then let the savings (and the lessons) fund the next. One at a time is slower on paper and much safer in practice than a big-bang rebuild.

How do we prevent integration problems from coming back after they are fixed?

Monitoring and maintenance. APIs change underneath you, and so does your own business. A properly built integration has alerting and health checks, so problems get caught before they reach your operations. That's why an ongoing partnership works better than a one-time build. Someone has to be watching.

References

¹ McKinsey Global Institute – “The Social Economy: Unlocking Value and Productivity Through Social Technologies” (2012). Found that knowledge workers spend nearly 20% of their time searching for internal information. The figure has been corroborated by subsequent research including Asana’s Anatomy of Work Index (2023) and Coveo’s Workplace Relevance Report (2023, survey of 4,000 employees), both of which found equal or higher figures. Available at: https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy

² Barchard, K.A. & Pace, L.A. – Preventing Human Error: The Impact of Data Entry Methods on Data Accuracy and Statistical Results. Computers in Human Behavior, 2011. Available at: https://doi.org/10.1016/j.chb.2011.02.004

³ Amazon Seller Central – Cancellation Rate (CR) policy for seller-fulfilled orders: sellers should keep seller-cancelled orders under 2.5% of total orders over a 7-day period, and a higher rate may result in deactivation. Policy text as posted by Amazon staff in the Seller Forums; the full help page requires a Seller Central login. Accessed September 2026. Available at: https://sellercentral.amazon.com/seller-forums/discussions/t/fa2d8307-5daa-406c-a219-816d7da260b0