Systems Integration: The Cost of Typing the Same Data Twice
Disconnected systems cost hours and errors every month. Learn to price the cost, decide which system owns each data point, and plan systems integration.
Published on 5 min readTopics:systems integrationintegrations and migrationsERP
When your ERP and your online store don't talk to each other, someone on your team types the same order twice. When your CRM and your finance system don't talk, someone copies data from one to the other before every close. Systems integration ends that retyping, but it only works if you decide up front what to connect, which system owns each piece of data, and what happens when a connection fails. This article shows how to calculate the cost and make those choices.
Disconnected systems charge you in hours and in errors
The most visible cost is time. Someone spends part of the day retyping orders, checking stock on two screens, or building a spreadsheet that merges numbers from three systems. Nobody logs this as a cost, because it looks like routine.
The less visible cost is error. Every extra keystroke is a chance to swap a number, forget an item, or leave an order out. The effect shows up far from its source: an invoice with the wrong amount, a product sold with no stock, a report that doesn't match finance's.
Then there's the cost of doubt. When two systems show different numbers for the same data, the meeting starts by arguing about which number is right, instead of deciding what to do with it.
Do the math before asking for any systems integration
List every manual bridge, meaning every time someone carries data from one system to another. For each one, multiply three numbers: how many times a day it happens, how many minutes it takes, and how many working days the month has.
An example, with illustrative numbers: 40 orders a day, 4 minutes to retype each one, 22 working days. That's 160 minutes a day and almost 59 hours a month, more than a full work week of one person spent only on copying. Swap in your own numbers.
Then add what that bridge has already cost in errors: reorders, refunds, hours spent double-checking. With the math done, the order sorts itself out: the most expensive bridge is the first one to connect.
Decide which system owns each piece of data
Integration doesn't mean copying everything everywhere. For each type of data, pick one system that owns it. The others only receive it.
When you integrate an ERP with an e-commerce store, for instance, stock belongs to the ERP and the store only reads it. The customer record is born in the CRM and the ERP only receives it. If both systems can change the same data, sooner or later one undoes the other's change: the customer updates their phone at 10 a.m. in the CRM, the ERP sends the old number back at 11, and the invoice goes out to a phone that no longer exists.
Build a three-column table: the data, the system that owns it, and the systems that receive it. If nobody in the room can fill in a row, that's the first problem to solve, and no tool will solve it for you.
Decide how fast each piece of data needs to arrive
Not all data needs to arrive instantly, and instant costs more. Set a deadline for each one.
Store stock needs near-immediate updates: if it only updates overnight, the last item can be sold twice during the day. Billing sent to finance is usually fine once a day, and is simpler to maintain. The management report can be ready before the day starts.
The deciding question: what is the damage if this data arrives an hour late? If the answer is none, don't pay for real time.
Plan for what happens when the connection fails
Every connection between systems fails at some point: a system goes down, a record arrives with an empty field, an order carries an item that doesn't exist on the other side. What decides whether the integration helps or hurts is what happens at that moment.
Agree on three things before you start. Who gets notified, and through which channel. Where the list of what didn't go through lives. How to resend without duplicating. Without that, the error disappears in silence and you only find out when a customer complains.
Test with real data, including the ugly cases: the customer with an accented name, the order with a discount, the item cancelled halfway. And if you're also switching systems, the connections to your other systems belong in the same inventory. See what to check before a system migration.
Five questions before you hire a systems integration
- Which manual bridges exist today, and what does each one cost per month?
- For each piece of data, which system owns it?
- How much delay can each piece of data tolerate?
- Who is notified when a connection fails, and how is it resent?
- Do both systems already offer this connection out of the box? If they don't, it may be worth considering custom software that does what the off-the-shelf option can't.
If any answer is "I don't know," that's your first task, before any contract is signed.
Bring this list to the conversation. We map your company's manual bridges with you, calculate what each one costs, and decide which to connect first, so your team gets its hours back. Reach us on WhatsApp (+55 92 8129-8199) or by email at contato@ygormendanha.com.
ShareShare on LinkedIn