Mid-year integration audit: the hidden spreadsheet

June is the last reasonable month to tidy pipes before the second half (holidays, retail peaks, Hacienda again). The symptom is always the same: a “temporary” March spreadsheet that is now the system. A Zap nobody pays for. A gateway webhook that sometimes arrives.

An integration audit is not a box-and-arrow slide. It is the list of events: order paid, XML accepted, appointment created, message sent. Each event has an owner. What has no owner dies in November. Custom software is born from that list, not from a UI restyle.

An afternoon inventory

• Where money is confirmed — payments.
• Where supplier invoices are stored — Journal.
• Where the customer conversation lives — Respond.io.

If the map does not fit on one sheet, it is not because you are complex. It is because nobody had drawn it.

Let’s take that afternoon. You leave with a map. The second half is planned on top of it, not on top of the myth.