Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

The connection between my business systems has no owner and keeps failing quietly

Short answer

A connection between two systems, such as a shop and an accounting tool, needs an owner in the same way an application does. Without one nobody notices failures, expired access or changes at either end. Name a person, list what flows each way, and set up an alert for failures.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Orders, customers or invoices in one system do not match the other.
  • The link worked once and nobody knows who set it up.
  • Staff re-enter data by hand to fix differences.
  • The connection fails and I only find out from a customer.
  • Nobody knows what happens if one of the systems changes or is replaced.

Why does this happen?

  1. It was built as a one-off

    Someone connected two tools to solve a problem. It was never treated as something that needs care, so it was never assigned.

  2. It sits between two teams

    Each team owns its system, but the link belongs to neither. Problems are always the other side's.

  3. It fails silently

    Many links give no alert when a record is skipped. The errors show up weeks later as wrong totals.

  4. Either end changes

    When one system is updated, renamed or has its access keys expire, the link can stop without any sign on the other side.

  5. The builder left

    The person who made the connection moved on, and the knowledge of how it works went with them.

What can I do about it today?

  1. List what flows between the systemsFor each link, write what moves, in which direction and how often, for example new orders going from the shop to the accounts.
  2. Name a business ownerPick the person who cares most if the data is wrong. They do not need to be technical, but they own the question.
  3. Find where it runs and who can log inCheck which tool or server carries the link and whose account it runs under. Make sure that account is the company's.
  4. Do spot checksOnce a week compare a few records on both sides, for example yesterday's orders, and write down any differences.
  5. Do not edit the link in a hurryChanging its settings without understanding it can duplicate or delete records. Ask first.

When should I bring someone in?

  • Financial or customer records already differ between the two systems.
  • Nobody can find where the link runs.
  • One of the systems is about to be replaced or upgraded.

How do I handle it?

  1. Trace the flowI follow each kind of record from one system to the other and write down the rules that change it on the way.
  2. Find where it can failExpired keys, changed fields, limits and duplicates are checked, and I note what would happen in each case.
  3. Add visible checksA failed or skipped record raises an alert to the named owner instead of disappearing.
  4. Document it on one pageWhat flows, where it runs, who owns it and how to restart it, written so the next person can pick it up.
  5. Reconcile the differencesExisting mismatches are listed and corrected in a controlled way, with a backup first.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Who should own an integration?

One named person who is accountable for the data being right, supported by someone technical who can fix it.

Can the link be monitored without much effort?

Usually yes. A failure alert and a short regular count check on both sides catch most problems.

What if one of the systems is being replaced?

Then the link has to be rebuilt or moved. Listing what flows today makes that planning much easier.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.