When the connector does not exist, we write it.
Two systems that will not talk, a weekly CSV export, or a connector that covers three fields when you need eleven. We build the integration properly, in your infrastructure.
- REST
- SOAP
- Webhooks
- SFTP
- Direct database
- EDI
That weekly export is not a process. It is a missing integration.
Someone exports a CSV every Friday, opens it in Excel, fixes the two columns that always come through wrong, and imports it somewhere else. It costs you the hour, and it costs you six days of stale data in between.
The Friday export
- An hour of a senior person, every week
- Data that is six days old by Thursday
- The transformation rules live in one spreadsheet
- It breaks entirely when they are on holiday
- Errors are found downstream, weeks later
An integration
- Runs hourly, or on the change itself
- Both systems agree within the minute
- Rules in code, version controlled, reviewable
- Runs whoever is in the office
- Bad records queue with a reason attached
Field by field, signed off before we build
Which system wins when both change, what happens on delete, and which fields are derived rather than copied. Those answers are the integration.
- Conflict rules you have approved in writing
- Idempotent, so a retry cannot duplicate
- A dry run against a copy before anything is live
Including the system with no API
An old ERP, a portal, something on a server in the office. There is usually a route, and we price the fragility honestly rather than discovering it later.
- Scheduled export, database read or email bridge
- Browser automation only as a last resort
- We will say when the honest answer is to wait
Sync lag is a failure too
We alert on the quiet ones as well as the loud ones: a scenario that stopped triggering, a queue growing, a sync falling behind its schedule.
- Health checks on lag, not just hard failure
- Structured logs you can actually search
- A documented manual recovery procedure
Six shapes this usually takes
Two-way sync
CRM, ERP and accounting kept level, with rules for when both sides change.
Custom API clients
For platforms with no connector: their pagination, limits and auth, handled.
Middleware
Sits between systems, normalizes the data, one place to look when it breaks.
Legacy bridges
SFTP, direct database reads, fixed-width files and email attachments.
Webhook infrastructure
Signature checks, replay handling and a dead letter queue, so nothing is lost quietly.
Data migrations
Mapping signed off, a dry run against a copy, and a rollback documented first.
Work out whether it is worth doing at all
Count the hour the export takes, and the people who touch it. The stale data costs more, but this is the part you can measure.
That work currently costs you
$1,974every month in wages alone, before the errors and the waiting.
A $2,500 build pays for itself in 1.3 months.
What drives the price
A connector between two systems is $2,500, fixed before work starts, then $175 a change or a plan. API quality on both ends moves it most, then whether the sync is one-way or two-way.
Common questions
Our vendor says their system has no API.
Usually there is a route, in this order: an undocumented but working API, a database connection, a scheduled export to SFTP, a parsable email report, and browser automation last. Each step down is less robust, and we price and flag that.
Where does the integration run?
In your automation platform if the logic fits, otherwise as a small service on infrastructure you own. Always in your accounts, because hosting it on ours would make you dependent on us.
What if a vendor changes their API?
Every integration outlives at least one API change. Ours fail loudly and alert rather than corrupt data quietly. On a plan the fix is included; otherwise it is a $175 change.
Can you do a one-off migration?
Yes. Mapping signed off, a dry run against a copy, a validation report you review, and a documented rollback. Record count and source cleanup are what move the quote.
Do you work under our security requirements?
Yes, and we sign NDAs. Least-privilege service accounts created on your side, credentials in your vault, access you can revoke without breaking anything you own.
Which two systems refuse to talk?
Tell us what they are and what needs to move between them. Thirty minutes, no charge, and a straight answer on whether it is feasible.
You will talk to Fayez or Kareem. Nobody else.
Related: Workflow automation · Scoping and proposal · Automation support