A map of what moves where
Before any code, one page lists each event, the tool it starts in and every place it has to land.
Software integrations
Make the software you already pay for talk to each other.
We connect the tools your business already runs on, so an order or a booking is typed once and shows up everywhere it should. When one tool refuses something, it is held and you are told why.
Why the gap matters
Typed in by hand, 3.7% of the numbers came out wrong.
That is from a study of 60 outpatient clinics. Nurses and medical assistants typed blood sugar readings into patient records while the meters sent the same readings electronically, so the two could be compared.
Between your shop and your books, the same job is done with whole orders. An integration takes the retyping out.
3.7%of hand-typed readings didn’t match the original
260mismatches in 6,930 typed entries
37of them off by more than 20%
60clinics, with records from 2015 to 2017
Sometimes a ready-made connector is enough.
Zapier and Make link common tools without code, and you can set them up yourself. If one thing happens a few times a day, updates one other tool and can arrive a little late, use one. We’ll say so on the first call.
Their limits are on their own price lists. Zapier’s free plan checks every 15 minutes, does one action per workflow and counts each action as a task, with 100 tasks a month. Make’s free plan has 1,000 credits a month and the same 15-minute gap. Paid plans raise both and charge by volume.
Custom work makes sense when each order touches several tools many times a day, or when a missed one would cost you a customer.
What you’d get
The connection, and a way to see it working.
Picked up as it happens
Where a tool offers webhooks the order is on its way at once, and where it doesn’t the program asks on a timer.
Checked before it’s written
Repeats are ignored, and customers and products are matched across tools so nobody is created twice.
A held list, with reasons
Whatever a tool refuses waits in one list with that tool’s own explanation and a retry button.
A log you can read
Every item that moved, where it went and when, searchable by order number when a customer asks.
A second pass that compares
Google says its calendar notifications are not 100% reliable, so a scheduled check fills in what a message missed.
The part nobody sees
Passing one order from one tool to the next is the short part. What keeps it working in month eight, when a tool changes something or goes down for an hour, is what sits underneath. See what it takes ›
- Access keys for each tool, stored safely and renewed
- Retries that wait longer each time a tool is busy
- Each tool’s API changes, followed and applied
- An alert when something has waited too long
How a project goes
- 1
Talk
A free call. You describe the problem in your own words, and we tell you honestly whether software is the answer.
- 2
Proposal
A written scope, timeline and price before any work starts.
- 3
Build
We design, code and test in phases. You see working software at the end of each one.
- 4
Launch
We put it live: app stores, hosting, domains, the lot.
- 5
Keep it running
Monthly maintenance if you want it: updates, fixes and regular reviews.
Before you ask
Which tools can be connected?
Any tool that offers an API, which is an official way for other programs to read and write its data. Online shops, payment systems, booking calendars and accounting packages commonly have one. Stripe, Square, Shopify and Google Calendar, for example, each publish theirs. If a tool has none, we look at what it can export or email, and tell you what is possible before we quote.
Do I need custom work, or will Zapier or Make do?
Often a ready-made connector will do, and we’ll say so on the first call. It suits a simple job: one thing happens, one other tool is updated, and volume is low. Custom work makes sense when each order touches several tools and the rules have exceptions, or when a missed item would cost you a customer.
What happens if one of the tools is down?
The tool that sent the message keeps trying for a while. Stripe says up to three days, Square up to 24 hours, and Shopify eight times over four hours. After that the sender gives up, so the program doesn’t depend on messages alone. It holds and retries whatever it could not write, and on a schedule it asks each tool what changed and fills in what it missed.
Will it create duplicates?
It is built not to. Stripe, Square and Shopify each warn that the same message can arrive more than once, so the program records every message it has handled and ignores repeats. Before it creates a customer or a product in another tool, it looks for an existing one.
What does it cost, and who owns it?
The price depends on how many tools are involved and how many kinds of event move between them. You get a written scope, timeline and price before any work starts. The code is yours, and it runs on an account in your business’s name.