System integration services
We connect the systems your business runs on so data moves between them reliably, without manual exports or double entry. Your teams work from consistent information, and new tools or AI features can plug into it without months of groundwork.
Integrations services
Built around the systems already in place: Datum.
Datum, the quoting and shop-floor software we built for sheet-metal and CNC suppliers, is integrated with the systems a shop already runs on. Microsoft 365 and Google Workspace feed it the requests, drawings attached. Invoices and customers go back to Exact Online, so the accounting stays where it is.
Everything in between, from the drawing read on intake to the work order at the machine, lives in one set of records with an audit trail. That is what system integration looks like when the systems stay. Read the full Datum case study.
The work arrives. The AI column says what it did per request. Read, two questions, new mail since reading, or the scan was unreadable. Saying it cannot read something is part of the job.
It reaches the machine. One work order holds the drawing, the route, the hours booked against each operation and the outsourced step with its return date.
Six agents propose. Each agent has one task, a credit budget and an autonomy setting. The column that matters is what it proposed this week and how often that was taken, adjusted or refused.
The morning briefing. The briefing is written at half seven and every sentence carries the record it came from, so anyone can check it.
Screenshots show sample data.
What systems integration is.
Systems integration connects the separate software a business runs on, such as the ERP, CRM, accounting package and warehouse system, so data moves between them automatically and each record has one source of truth. It replaces exports, spreadsheets and re-typing with connections that are logged, monitored and documented.
| Approach | What it does | Where we cover it |
|---|---|---|
| API integrations | Connect systems through their APIs and webhooks, one flow at a time | API integrations |
| Data pipelines | Move data into a warehouse for reporting and AI features | Data pipelines |
| Legacy system integration | Put an API around older software and replace it step by step | Legacy systems |
| Integration platform | Build flows in a tool such as n8n, Make or Zapier when volume and mappings are simple | API integrations |
Our explainer on API integrations walks through how one works, with examples, and what tends to go wrong.
How we work on it
Agree who owns each piece of data
Every integration starts with a clear source of truth per field. Most sync problems come from skipping this step.
Change one thing at a time
We connect and replace systems in small, reversible steps so operations do not hang on a single risky cutover.
Assume things will fail
APIs go down and vendors change formats. Retries, queues, alerts and replay tools are part of the first release.
Visible and documented
Every flow is logged and documented, so your team can see what moved, when, and why a record looks the way it does.
Related work
- Manufacturing
Quoting and shop-floor software where AI proposes and people decide
6agents, each with one task and a named owner- TypeScript
- React
- Hono
- Retail and ecommerce
Every product change writes its own Shopify listing, in four languages
30.7sfrom product change to a listing ready for review- Shopify
- n8n
- Cloudflare Workers
- Financial services
A lending product that sets the limit, issues the card and takes the money back
30days from nothing to a working product- Stripe
- Plaid
- TypeScript
Built with
All technologiesFurther reading
What is an API integration? With examples
An API integration lets two systems exchange data without anyone re-typing it. How one works, examples from finance and operations, the ways to get one built, what can go wrong and what drives the cost.
10 min read
Embeddings explained: a practical guide for product teams
How embeddings power semantic search, how to choose a model and a vector store, and how to measure whether your results improved.
5 min read
Common questions
ERP systems such as SAP, Odoo, Exact and AFAS, CRMs such as Salesforce and HubSpot, Microsoft 365, payment and e-commerce platforms, data warehouses and internal databases. If a system exposes data in any reliable way, we can usually connect it.
A few direct connections are fine for a small estate. As the number of systems grows, a central integration layer or event stream keeps things maintainable and avoids a web of fragile links. We recommend based on how many systems you have and how fast they change.
We map which personal data moves where, limit it to what each system needs, keep processing in the EU by default and support deletion requests across connected systems. Data processing agreements are in place before we touch any live data.
We offer monitoring and support agreements, or hand over to your team with documentation, runbooks and tests. You own the integration code once invoices are paid.