Custom API integrations between the systems you already run.
When two systems need a person to copy data between them, that person is your integration. Our custom API integration services replace the copying with code that moves the data once, in order, and tells someone when it can't.
On this page
What we connect
- CRMs: Salesforce, HubSpot and Microsoft Dynamics 365.
- Accounting and ERP: QuickBooks, Xero and NetSuite.
- Commerce: Shopify.
- Microsoft Power Platform: Power Automate and Power Apps, and Power BI dashboards.
- Scheduling and practice systems, such as the dental scheduling system our voice agent books into.
- Phones and messaging: Twilio, Microsoft Teams and Slack.
- Your own databases and internal tools, including the spreadsheets that currently act as a database.
- Anything with a documented API. If a system has no usable interface, the audit says so before you pay for a build.
If your system isn't listed, ask. If it has a usable interface, we can connect it, and the audit tells you how before you commit to a build.
Native connector, automation platform or custom code
Start with the cheapest option that works, and move on when it stops working.
| Option | Good for | Watch out for |
|---|---|---|
| A connector built into one of the products | Standard fields, standard direction, low volume | Fields it doesn't map, rules it can't express, and errors nobody sees |
| An automation platform such as Power Automate, Zapier or Make | Simple flows you want running this week | Per-task pricing at volume, silent failures, and logic spread across dozens of small flows |
| Custom code | High volume, business rules, an audit trail, sensitive data | It has to be built, hosted and maintained, and it should be yours |
If a connector or a platform flow does the job, we will recommend it. Custom code is for the integrations where a quiet failure costs you money or a customer.
How we build an integration
We build integrations to one pattern, because they tend to fail in the same few ways:
- Changes are picked up as they happen, from webhooks or change feeds, instead of a nightly export.
- Every payload is checked against an agreed schema, so malformed data is rejected before it is written.
- Each change is applied once, even if it arrives twice or the target system retries.
- After repeated timeouts, a change moves to a review queue that someone can see and act on.
- You get a runbook that explains how it works and what to do when it stops.
There is a reference design for a CRM and ERP sync on our Workflow Automation page. The failure modes this pattern guards against are written up in why integrations fail silently.
Integrations we have built
- A distributor running 500 routes across twelve states had its routing, stock and demand in separate spreadsheets. We put them on one data model that takes traffic and weather into account. Read the case study.
- For a B2B services firm we built a calling agent connected to Salesforce, HubSpot, Twilio, Microsoft Teams and Slack, so every qualified lead and callback lands in the CRM. Read the case study.
- For a 26-provider dental group we built a voice agent that books directly in the practice's scheduling system, against the practice's own rules. Read the case study.
What it costs
A single, well-documented connection between two modern systems is a small project. Several systems with business rules and an old API are not. We fix the price once the integration inventory exists, which is the list of every system, every field and every rule involved. For market figures, see what custom software development costs.
Start by mapping the workflow
The Automation Audit
One workflow you name, mapped end to end, with the arithmetic done before anyone writes code.
- Scope
- One workflow you choose, traced end to end, including the steps nobody documented.
- Duration
- Two weeks, fixed.
- Fee
- Fixed, and quoted in full before we start. No hourly drift.
- You get
- A written map: what can be automated, what it would save in hours, what building it would cost, and what we would leave alone.
- You keep it
- The map is yours whether or not you hire us to build anything.
And if the audit shows the automation will not pay for itself inside twelve months, we will tell you, and we will not quote the build.
Questions we get asked about integrations
What if a system's API is poor or missing?
Then there are three options: its database, file exports, or a different approach altogether. We will tell you which is safe, and which one we would refuse to build on.
Who maintains it after launch?
We do if you want us to, under published support commitments that start at a one-hour response for an outage. Or your own team does, using the runbook and the code, which you own.
What happens when a vendor changes its API?
Monitoring flags the failed calls, and the review queue holds the data until the fix is in, so nothing is lost while the connector is updated. Handling vendor changes can be written into the support agreement, so it never arrives as a surprise invoice.
Can you work with our IT team or our existing developers?
Yes. We can build the integration and hand it over, or work inside your team as embedded engineers. Either way the code lives in your repository.
