What we do · Integrations
Keeping your systems in agreement
Your ERP, CRM, accounting package and online store each hold part of the picture. We connect them so a record entered once reaches the others, and check it with a daily reconciliation.
- Price
- From $1,000 one-time; fixed after the audit
- Time
- 2 to 6 weeks
- For
- Teams whose tools each hold part of the picture and who re-key data between them daily.
- You own
- The integrations and any code, in your accounts and repository
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 $1,000, one-time, at a fixed price set after the audit.
One record, everywhere it is needed
The systems you run, connected with retries and reconciliation.
-
Entered once, everywhere
The CRM, accounting package, store and ERP stay in step.
-
A rule for every field
Which system wins when both change.
-
Failed records are caught
Retries, a queue and an alert to a named person.
-
A daily reconciliation
The two systems checked against each other every day.
Before and after
Today
- 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
With Integrations
- A record entered once appears everywhere it is needed
- Each field has one source of truth
- Failed syncs are caught and retried
- The systems are reconciled every day
Out of scope: a one-off data import with no ongoing sync; syncs with no agreed rule for which system wins when they disagree.
Integrations, step by step
- Week 1
We map each system in scope: which fields move, in which direction, and which system wins when they disagree. API access and limits are confirmed.
- Weeks 2 to 3
The first sync is built and run against a copy of real data. Mismatches are listed and resolved with your owner.
- Weeks 4 to 5
We build the remaining syncs, retries for failed calls, a dead-letter queue for records that need a person, and a daily reconciliation report.
- Go-live
Live on real data, with the manual re-keying stopped only once reconciliation has run clean. Hypercare begins.
Measured in production
“We call an integration finished when a daily check shows both sides agree.”
Enter a record once
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
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 editionWhat 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 on a schedule. If it still fails, the record goes to a queue and a named person is alerted with the reason, so failed records are visible.
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. Tools, automations and databases live in accounts in your name, code sits in your repository, and documentation is part of the deliverable. If you stop working with us, it all keeps running.
Reading
- Strategy
Does an AI agent still need Zapier?
A widely shared post argues agents will take Zapier to zero. We run both daily. 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 far more for the person who runs it. The break-even, what you take on, and our advice.
- Operations
Who noticed when the workflow stopped?
Most automation failures are silent: the run shows green and nothing happens for weeks. How it happens in Zapier and n8n, its cost, and the four checks we add.
Also what we do
Automate
Teams re-typing data between tools, chasing status by hand, or waiting a day for a report.
Modernise
Companies running a $5M to $100M operation on spreadsheets, a legacy ERP or a tool nobody dares change.
Advise
Founders and COOs making technology decisions without anyone senior to check them.
Forward deployed engineers
Leadership teams that expect AI and automation to change how the company runs and want engineers working in the room with their teams.
Extend
Teams that already run a platform but are out of capacity, or need a skill they do not have in-house.
Harden
Founders who shipped an app with an AI builder and now need it to hold up for customers, investors or an audit.
Zapier to n8n migration
Teams whose Zapier bill grows with task volume, or who need code, self-hosting or AI steps that Zapier makes hard.
Airtable to Supabase migration
Teams whose Airtable base is slow, near its record limits, hitting API rate limits, or now used by outside people who must see only their own data.
AI agents
Teams with a multi-step task that needs reading or judgement, a clear goal and a person willing to approve the outcome.
Internal tools and portals
Teams running the business from spreadsheets and inboxes, or sending customers and suppliers status by email.
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
Every project starts with an audit
We spend one to two weeks with the people who do the work and give you a costed blueprint, ordered by 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 $1,000 one-time; internal tools from $3,000.
- Run60 days of hypercare, then monthly. Hypercare included; care plans from $50/month.















