How the systems connect: what moves between them, what triggers it, what it is matched on, who owns it and what breaks. One deal followed through the stack, then the map, one row per flow.
Boxes marked ↗ open the page for that part of the model.
How to read this
- The path at the top is one deal from form fill to the scorecard. The color says which system is the system of record at that point: the CRM before the subscription, billing after it, the warehouse for everything reported.
- The map is the contract for each integration. Trigger and cadence decide what can be read in real time and what is a day old; the match key is where duplicates and orphans come from.
- The last column is the monitoring list. Every one of those failures has shown up in a real funnel, and most are cheap to detect with a daily exception report.
- Categories, with the tools usually found in each. The design does not depend on the vendor; it depends on who owns which field.
Diagram source: 25-integrations.drawio 25-integrations.svg
