Resources
Evidence, analysis and announcements.
Case studies, insight articles and company news from the teams implementing customer experience, integration, infrastructure and artificial intelligence programmes.
Implementations, described end to end
Illustrative walk-throughs of enterprise technology programmes: the business problem, the architecture decisions and what changes operationally.
- One customer record across sales, service and commerce15 October 2026
- Order-to-invoice flow across commerce, ERP and logistics6 August 2026
Engineering notes from live programmes
Practical writing on customer experience, marketing automation, enterprise integration, cloud infrastructure and artificial intelligence.
- Designing integrations for the failure case5 November 2026
- Designing a CRM your sales team will actually use28 October 2026
Announcements and product development
Company announcements, platform releases and developments across the Sapier, Evoyse, Indurant and ZeoPulse portfolio.
- ZeoPulse monitoring console reaches general availability10 November 2026
- Integration practice extended for SAP Emarsys programmes3 September 2026
Latest across resources
ZeoPulse monitoring console reaches general availability
Our infrastructure monitoring platform moves into general availability, with a consolidated console for health, alerting and operational reporting across managed environments.
Designing integrations for the failure case
The happy path is the easy part. Retries, idempotency, dead-letter queues and ownership are what decide whether an integration survives its first bad night.
Designing a CRM your sales team will actually use
Most CRM problems are design problems, not software problems. A practical view of module structure, pipeline logic and the fields that decide whether adoption holds.
One customer record across sales, service and commerce
An illustrative retail programme: three CRM instances, two support inboxes and a commerce platform consolidated into a single customer record that sales and service both trust.
Working on something similar?
Describe the systems, the constraints and what needs to change. We will outline a realistic path and the trade-offs behind it.