When is integrations the right choice?

The same data gets typed into two systems, and they’ve drifted apart. Someone exports a file from one tool every week and imports it into another. Your quoting, accounting, field app and store each work fine on their own, but none of them know about the others. A product you rely on has an API, and nobody’s had the time to use it.

Services · Integrations

Systems Integration

Most businesses don’t need another system. They need the ones they already pay for to share data, so nobody has to type the same number into each of them.

Talk about integrations Pricing

Your ledger, laptop and phone stay as they are. The work is the connection between them, and the shutoff valve for when one goes down.

What you get

No more typing it in twiceThe order, the invoice, the contact, the timesheet: entered once, in the system where it belongs, and showing up in the other one without anyone copying it over.
A record of every transferWhat moved, when, and what the other system said back. When someone asks why an invoice is wrong, the answer takes a minute to look up instead of an afternoon.
Built for when things failAutomatic retries, a queue that waits out the other system being down, and an alert to a person when something needs a decision.
The rules written where you can see themWhich system wins when two disagree, what happens to a record that matches nothing, and who gets told.

An invoice, a timesheet and a contact, entered once in the field app and sent on to accounting. While accounting is down, the connection I build holds them in a queue and retries, and the log keeps every attempt and what accounting said back.

Pricing

Fixed prices for the common jobs, and a quote after discovery for anything bigger. Prices in CAD, plus GST.

01 Fits most businesses
One integration
Two systems you already pay for, made to share one thing.

$12,500 fixed · 1 to 2 weeks

Two systems with APIs, one record type, one or two directions: retries, a queue that survives an outage, a log of every transfer, an alert to a person, and the rules written down.
- One record type, one or two directions
- Retries, and a queue that survives the other side being down
- A log of every transfer, and an alert to a person
- Which system wins when two disagree, written down
Start with One integration
02
A set
Up to 3 systems, through one hub.

$27,500 fixed · 3 to 4 weeks

Up to 3 systems and 3 record types through one hub, with a dashboard of what moved and the rules document.
- Up to 3 systems and 3 record types
- One hub, one place to look
- A dashboard of what moved and what failed
- The rules document
Start with A set
03
Custom
A system without an API, or years to reconcile.

from $25,000 after discovery

A system without an API, files instead of calls, or history to reconcile. Scoped in discovery.
- Files, exports and screens where there is no API
- History reconciled before it flows
- Paid by phase
Talk about Custom

Run plan · from $3,000 a year The infrastructure it runs on, kept up, backed up and watched. The server it runs on. Storage, and backups you can be restored from. Dependency and security updates. Monitoring, and someone who notices. Cancel at any renewal. You own the software either way.

That’s the starting price. A busier or more complex system costs more to run, and we agree on the number in writing along with the build, so it never comes as a surprise.
Not included: what you pay other companies. AI model and API keys, third-party licences and app subscriptions stay in your own accounts, at cost. I don’t mark them up.
The plan doesn’t include hours for changes. Each change gets its own price, agreed before I build it.
I’ll never take a percentage of what you sell: no royalties, no cut of transactions, no per-user fees for software you own.

If Zapier or Make already does the job, use that. I’ll set it up as part of a build or a discovery instead of selling you an integration.

When it’s the right choice

The same data gets typed into two systems, and they’ve drifted apart.
Someone exports a file from one tool every week and imports it into another.
Your quoting, accounting, field app and store each work fine on their own, but none of them know about the others.
A product you rely on has an API, and nobody’s had the time to use it.

When it isn’t

If it happens twice a month and takes 10 minutes, keep doing it by hand. If Zapier or Make already does it, use that, and I’ll help you set it up instead of selling you a build. An integration pays for itself when there’s a lot of volume, or when retyping causes costly mistakes. Without either, it’s just tidying up.