Blueprint / Software EngineeringIntegration Blueprint
Three weeks mapping the systems, the data contracts and the failure modes, before anyone writes integration code.
How the weeks run
Every step ends with something you can use. Hover or scroll to follow the plan.
Week 1
Map the systems
Systems, owners and the manual handoffs between them are mapped as they are today.
You getThe system landscape
Week 2
Design the contracts
APIs, events and data contracts are designed, with the trade-offs written down.
You getThe target architecture
Week 3
Plan for failure
What breaks, how it is detected and who is called, plus the delivery plan.
You getFailure-mode catalogue and plan
What you get
Target architecture
APIs, events and queues, with the trade-offs written down.
Failure-mode catalogue
What breaks, how it is detected, who is paged.
Tools we typically use here
Grouped by when they come in. Where you already run a platform, we start from it.
Build
How it is priced
- Commercial model
- Fixed fee
- Fixed scope / 3 weeks
- When you get a number
- In writing, after a short scoping call once we have seen the process. Nothing starts before the number is agreed.
Questions buyers ask
What do you need from our side?
A sponsor who can make decisions, one person who knows the process well, and access to the data or systems in scope. We agree how much of their time it takes before we start.
Do we need to have chosen a platform?
No. We work with the platforms you already run and recommend a new one only when the evidence supports it.
What happens at the end?
You keep everything we produce. If there is a sensible next step we propose it with its own scope and price, and there is no obligation to continue.
How is it priced?
As a fixed fee, agreed in writing after a short scoping call and before any work starts.
Where this has worked
Energy & Utilities~120group companies covered every monthEnergyLink Invoice Reconciliation Automation for a US Oil ProducerOil and gas producer · United States · NYSE-listed, about 120 group companiesRead the case
Energy & Utilities20+automations in productionIntelligent Automation Program for an Italian Multi-UtilityListed multi-utility · Italy · five provinces, energy, water, waste and public servicesRead the case
Retail & E-commerce7sister companies in one routineSAP and Esker Invoice Integration for a Luxury Fashion HouseLuxury fashion · Italy · part of a global luxury group, seven sister companies in the processRead the case
Start with a short call.
We will tell you whether this is the right first step, including when it is not.