Capability
Connected applications
Tools for teams that need to see and act on information held in several systems, without becoming yet another copy of it.

Scope
What we build
- Case and request handling that pulls customer details from your CRM and posts outcomes back.
- Approval tools with routing rules, delegation and an audit trail, writing decisions to the system of record.
- Operational views that bring together the few fields a team needs from several systems, with links back to each.
- Back-office utilities for bulk updates, imports and checks that are currently done by hand in spreadsheets.
Principles
Design principles
A connected application should never become a shadow database. We keep a clear line between data it owns (for example, a workflow state) and data it borrows (a customer address), and we write that line down. Borrowed data is fetched or synchronised with known freshness, so nobody is surprised by a stale value.
We design the interface around the job: fewer fields, sensible defaults, keyboard-friendly forms, and messages that tell people what to do next rather than just what went wrong.
Working together
Inputs and tradeoffs
We need
- Test accounts on each system to be connected
- Interface documentation, or permission to request it from vendors
- Time with two or three people who will use the tool
Expect to decide
- Real-time versus scheduled synchronisation
- Which system wins when two disagree
- Whether to retire an old tool or keep it read-only