Capability 03
System Integrations
Your ERP stays your ERP. Usually no system needs replacing — what is needed is the path between two of them that a person currently walks with copy and paste.
Contributes to
A capability is a means. The linked areas describe what it is used for.
Scope
What specifically gets built.
Every line is a commitment about future work — none of it is a claim about completed projects.
Connection to existing interfaces
Synchronisation between systems with one clear source of truth
When a system is unreachable: the case is not lost, it is transferred again later, and you are informed
A record of every transferred item
Connection even where no interface exists — via file transfer or email
Technology
The decisions behind it.
Categories rather than vendor names — which product is used depends on your existing systems.
- REST and webhooks where available
- Queues so that a case is not lost when something fails
- The same message twice does not create two records
- Separate credentials per system, stored traceably
Out of scope
What is not included.
So that no time in the intro call is spent on an expectation we do not meet anyway.
- No changes inside the source system itself
- No circumvention of licence or support terms
- No data migration without agreed rules
These eight capabilities are means, not offerings. Which of them are used follows from the process — not the other way round. If you are not sure which ones you need, that is the normal case and not a problem.