03 / Systems & Data
CRM, operations software and commerce: when integration is worth it.
Integration is useful when it removes a duplicated decision or exposes an important state—not when it simply moves data without ownership.
Symptoms of an ungoverned hand-off
Symptoms of an ungoverned hand-off
Copying data is not always a problem: it can be the right human control. It becomes friction when the same information is reinterpreted, two tools show different states or nobody knows which record to correct.
Another signal is manual state reconstruction: orders checked across multiple panels, contacts without owners, or spreadsheets used to rebuild what the system should have made explicit.
- Duplicated data with different meanings
- State reconstructed manually
- Corrections made in multiple tools
- Exceptions without an owner
Synchronising less can be the better choice
Synchronising less can be the better choice
Not everything needs to be bidirectional. Often it is enough to send an event, create a review queue or expose a datum without copying it. Every additional write increases conflicts and ownership.
Options range from an assisted procedure to one-way synchronisation and explicit orchestration with error handling. The right level depends on the damage caused by delay, duplication or incorrect data.
Source, event, owner
Source, event, owner
For every hand-off, name the authoritative source, the event that enables transfer and the person or role handling the unexpected case. This triad matters more than the chosen technology.
Idempotency must also be defined: a repeated event must not create two orders, contacts or tasks. Audit and rollback matter when a write has operational consequences.
- 01SourceCommerce
Order and customer state
- 02EventOrchestration
Checks, deduplication, queue
- 03OwnerCRM / Operations
Ownership and progression
Integrating fields without integrating meaning
Integrating fields without integrating meaning
Two fields with the same name may describe different moments. Mapping columns without clarifying state creates technically successful but operationally wrong synchronisation.
Hiding errors to keep the flow green is risky too. A visible queue with reason and possible action is often more useful than infinite retry.
When to keep the hand-off manual
When to keep the hand-off manual
If volume is low, exceptions dominate or the decision requires interpretation, a well-designed manual hand-off may be safer. It must still be explicit, measurable and assigned.
Do not integrate tools that are about to be replaced or processes that remain unstable. Clarify the operating contract first, then automate transfer.
Next insight
When to build custom software — and when not to.