What we do · Integrations
Your systems agree with each other
Your ERP, CRM, accounting package and online store, each holding part of the truth. We connect them so a record entered once is right everywhere, and prove it with a daily reconciliation.
- Price
- From $2,500 one-time; most builds $5,000 to $15,000
- Time
- 2 to 6 weeks
- For
- Teams whose tools each hold part of the truth and who re-key data between them every day.
- You own
- The integrations and any code, in your accounts and repository
In short
Integrations connect the systems your business already runs, such as the ERP, CRM, accounting package and online store, so a record entered once appears everywhere it is needed. We build with APIs and webhooks, on n8n, Make, Zapier or code, with two-way syncs where both sides change. Every integration has reconciliation, retries and monitoring. Builds start at $2,500, one-time.
Is this you?
If three of these sound like your week, integrations is the place to start.
- Orders, invoices or contacts are re-keyed from one system to another
- Stock or prices differ between your store and your ERP
- Finance reconciles two systems by hand at month end
- A sync exists but nobody knows when it last failed
- A vendor told you the systems cannot talk to each other
What this is not
So the scope is clear before the call.
- A one-off data import with no ongoing sync. That is a migration, priced under Modernise.
- Syncs with no agreed rule for which system wins when they disagree. We settle that first.
Most often for
What we have built
Integrations in practice.
- E-commerce
One product record, every channel
Listings, stock and prices synced across three marketplaces with zero mismatches.
Read the story - Distribution
Enquiry to order with SAP
RFQs matched against the SAP item master and tracked through to the order.
Read the story - Sales
Leads synced into the CRM
Capture, enrichment and CRM sync in one flow, with no manual entry.
Read the story - Manufacturing
Cashback with automated payouts
QR scans, customer records and UPI payouts connected end to end on Make.
Read the story
Integrations
Entered once, right everywhere.
Tell us which two systems your team copies between most. We will show you the sync, the rule for conflicts and how you would know it failed.
Show us the systems
How it runs
Integrations, step by step.
- 1Week 1
Every system in scope is mapped: which fields, which direction, which system wins when they disagree. API access and limits are confirmed.
- 2Weeks 2 to 3
The first sync is built and run against a copy of real data. Mismatches are listed and resolved with your owner.
- 3Weeks 4 to 5
Remaining syncs, retries for failed calls, a dead-letter queue for records that need a person, and a daily reconciliation report.
- 4Go-live
Live on real data, with the manual re-keying stopped only once reconciliation has run clean. Hypercare begins.
What you get
- The integrations, running in your accounts or your infrastructure
- A field map and the rule for which system wins each field
- Retries, a queue for failed records and alerts to a named person
- A daily reconciliation report between the systems
- Documentation of every endpoint, credential and schedule
How we know it is done
- Reconciliation shows the systems in agreement for an agreed period
- A failed call is retried, and a record that still fails reaches a person
- Your team can see the status of every sync without asking us
What you own
- The integrations and any code, in your accounts and repository
- The field map and sync rules
- The API credentials, in your name
- The documentation
of small and mid-size business leaders say data is inconsistent across their business tools
Source: Salesforce SMB Trends, 6th editionBuilt on
The tools you already run, where we can.
Proof
Customer stories.
“An integration is not finished when data moves. It is finished when you can prove both sides agree, every day.”
How it starts
Every project starts with an audit.
One to two weeks with the people who do the work. A costed blueprint in order of payback. The $500 is credited in full to the build.
- Audit1 to 2 weeks. $500, credited to your build.
- BlueprintIncluded in the audit’s second week. Included with the Audit; quoted separately for multi-phase programmes.
- Build2 to 8 weeks. From $2,500 one-time; most builds $5,000 to $15,000.
- Run60 days of hypercare, then monthly. Hypercare included; care plans from $50/month.
Questions
What people ask about integrations.
Middleware or custom code?
Middleware such as n8n, Make or Zapier when volume is modest and your team wants to see and edit the flow. Code when volume is high, the logic is heavy or the data must stay in your infrastructure. The choice and its running cost are written into the blueprint.
What if our system has no API?
We look for webhooks, scheduled exports, a database connection or email parsing, in that order. The audit establishes what is possible before anything is priced.
What happens when a sync fails?
It retries automatically. If it still fails, the record goes to a queue and a named person is alerted with the reason. Nothing is dropped silently.
Can you integrate with SAP, Tally, Zoho or QuickBooks?
Usually, yes. We have worked with SAP from enquiry to order. Each system is checked for API access and limits in the first week.
Who owns the code, the workflows and the accounts?
You do, from the first sprint. Every tool, automation and database lives in accounts in your name. Code sits in your repository. Documentation is part of the deliverable. If you stop working with us, everything keeps running.
Reading
- Strategy
Does an AI agent still need Zapier?
A widely shared post argues Zapier goes to zero because agents click buttons and call APIs themselves. We run both every day. Where the argument is right, where it is wrong, and what we use for each job.
- Pricing
n8n self-hosted or cloud for a team under 50?
Self-hosting n8n costs a few dollars a month for the server and a lot more for the person who keeps it up. The break-even in executions, what you take on when you host, and the answer we give most teams of 1 to 50.
- Operations
Who noticed when the workflow stopped?
Most automation failures are silent. The run shows green, the trigger is armed, and nothing happens for six weeks. How silent failure works in Zapier and n8n, what it costs, and the four checks we put on every build.
Also what we do
- What we do
Automate
Teams re-typing data between tools, chasing status by hand, or waiting a day for a report.
- What we do
Modernise
Companies running a $5M to $100M operation on spreadsheets, a legacy ERP or a tool nobody dares change.
- What we do
Advise
Founders and COOs making technology decisions without anyone senior to check them.
- What we do
Extend
Teams that already run a platform but are out of capacity, or need a skill they do not have in-house.
- What we do
Harden
Founders who shipped something real with an AI builder and need it to survive real customers, investors or an audit.
- What we do
AI agents
Teams with a multi-step task that needs reading or judgement, a clear goal and a person willing to approve the outcome.
- What we do
Internal tools and portals
Teams running the business from spreadsheets and inboxes, or sending customers and suppliers status by email.
- What we do
Dashboards and reporting
Teams that export, clean and paste reports every week, or argue about whose number is right.
Related: Automate, Dashboards and reporting, Run
Integrations
Talk to the people who would build it.
A discovery call. Bring the work your team still does by hand. You leave with a yes or no on fit and the first thing we would build.
Book a discovery call