Systems We Connect
The systems we have already built against.
Every product named on this page is one we have integrated with or built against. None of it is a partnership, an endorsement or a vendor agreement: it is a record of what we have done. If yours is not listed, ask, because the answer depends on what it exposes rather than on whether we have heard of it.
What You Get
The parts that decide whether it works.
Payments And Checkout
We have built against PayFast and Yoco, so a paid order can confirm itself to the customer, start a job and update your stock without anybody watching for the notification.
WhatsApp And Messaging
We have built against the WhatsApp Business platform for order confirmations and appointment reminders. It is a metered channel with rules of its own, and we explain both up front.
Online Stores
We integrate with Shopify and WooCommerce: a paid order out to the systems behind it, stock levels back in, and customer records kept in one place rather than three.
Mail And Documents
We integrate with Google Workspace and Microsoft 365, reading an inbox, filing an attachment, writing a sheet or booking a slot, using accounts your business owns.
Payroll And Timesheets
We integrate with SimplePay, so hours approved in one place become a payroll run without somebody rebuilding the same spreadsheet at the end of every month.
Whatever You Run
A system not named here is not a refusal. We look at what it exposes, an API, an export, a database or a screen, and tell you which it is.
What decides whether a system can be connected at all.
The payment gateways, stores, mailboxes and messaging platforms we have already built against, named in full so you can check yours is on the list.
Not every product can be automated, and the marketing page never says which. What matters is what the vendor exposes to you rather than what the software can do on screen: a documented API is easy, a scheduled export is workable, and a system that offers neither leaves only the screen itself. We check that first and tell you where yours sits before quoting anything.
What we check first
- Whether the vendor publishes a documented API
- Whether your plan includes API access at all
- Whether a scheduled export or webhook exists
- Who owns the account the credentials belong to
- What the vendor charges for calls or messages
- How the vendor handles two-factor sign-in
- What breaks if they redesign the interface
What lands in your hands
Most enquiries here start with the same question: will this work with what we already run? So the systems are named rather than described, and the list is what we have actually built against rather than everything that exists. If yours is not on it, the answer depends on what it exposes: an API is easy, an export is workable, and we will tell you when neither is there.
What's included
- A feasibility note on each system named
- Integrations built against PayFast and Yoco
- Integrations built against the WhatsApp Business platform
- Integrations built against Shopify or WooCommerce
- Integrations built against Google Workspace or Microsoft 365
- Integrations built against SimplePay for payroll
- Credentials stored in a vault you control
- A written record of every connection made
How An Engagement Runs
Audit first, then build what earns its keep.
Four stages, in order. Nothing is built before the audit says it is worth building, and nothing goes live before you have watched it run beside the manual process.
01. Audit
We sit with the people doing the work and record where the hours actually go, task by task. You get the findings in writing whether or not we build anything.
02. Pilot
One task, built and run beside the manual process rather than instead of it, so you can compare the output before anything is trusted with real work.
03. Deploy
The agent goes into your existing systems, with the handover, the access and the written record of what it does and where a person has to approve it.
04. Operate
We watch what it gets right and what it gets wrong, fix the second, and tell you when a task has changed enough that the agent should be retired.
Questions
Before you commit.
Do you work with PayFast and Yoco?
Yes, we have built against both, and they are the two we know best. A paid order can confirm itself to the customer, start a job and update stock without anybody watching for the notification, and the awkward parts — a failed payment, a duplicate notification, a refund — are handled rather than assumed away. Which gateway you are on changes the detail, so tell us on the first call.
Are you a certified partner of any of these?
No. We have no partnership, reseller agreement or certification with any product named on this page, and we do not claim one. What we have is a record of having built against them. That distinction matters to you as well as to us: it means we have no commercial reason to recommend one gateway or platform over another, and no vendor to hide behind when something does not work.
What if my system is not on this list?
Then we check it rather than guess. What decides the answer is what the vendor exposes to you: a documented API is straightforward, a scheduled export or a webhook is workable, and a system offering neither leaves only screen-level automation — software driving the interface the way a person would — which is slower, more fragile and breaks every time a button moves. Sometimes that is worth paying for. Often we will tell you it is not.
Where are our passwords and API keys kept, and who can see them?
In a credential vault on the account that owns the system, not in a spreadsheet and not in the workflow itself. Where a product offers a scoped API key or a service account, that is what we ask for rather than your own login, so the access can be limited and revoked without locking you out. Access is limited to the people doing the work, and you can revoke ours the day we finish.
Can you connect two systems that have nothing to do with each other?
Usually, yes, and that is most of this work. Neither vendor has to know the other exists: each one is reached on its own terms and the logic in the middle is ours. What we will not do is promise it before checking. The first thing on any integration job is confirming what each side actually exposes, which is a short piece of work and saves a long argument later.
Ready to bring your idea to life?
Let's create something amazing together.
Firm quote against a scoped roadmap before any work begins.