Services / Integrations & AI
Make your systems finally agree with each other.
Payments, CRMs, APIs and MCP connectors that let your systems — and your AI assistants — work as one. Built as monitored, versioned services, because the integration nobody notices is the one that is working.
Proof: Webtold and SchoolWare are both MCP-native. This website is maintained over MCP.
What we connect
The plumbing between the tools you already pay for, plus the newer layer that lets an assistant use them.
Payments & finance
Gateways, subscriptions and reconciliation wired so the money in your bank and the number in your system agree without a human checking.
CRM & sales systems
Enquiries, quotes and deals flowing between your website, your CRM and your inbox without anyone re-typing a name.
ERP & operations
Stock, pricing and fulfilment shared between the systems that need them, with one place that is authoritative.
MCP connectors
Your systems exposed to Claude and ChatGPT as safe, permission-scoped tools — the same standard our own products run on.
Document & data pipelines
Invoices, forms and PDFs read, validated and filed automatically, with the genuine exceptions routed to a person.
Monitoring & alerts
Every integration watched, so a silent failure becomes a notification instead of a discovery at month-end.
Integration, automation, or AI?
When integration is the answer
The same data lives in two places and someone keeps them in sync by hand, or a process stalls because one system cannot see what another one knows. Those are integration-shaped problems with payback you can count in hours.
When it isn’t
If nobody agrees what the process is, connecting the systems just makes the disagreement faster. We will help you pin it down first. And if a native connector already exists for $30 a month, use it — we will tell you.
An engagement like this
A retailer takes payments in one system, tracks stock in another and answers “where is my order?” by hand. We connect the two and add status notifications triggered by real events. Support volume drops because customers stop needing to ask, and the stock figure stops being wrong every afternoon.
Questions we hear a lot
What counts as an integration?
Anything that makes two systems agree. A payment gateway writing to your ledger, a CRM that updates when a form is submitted, an ERP feeding stock levels to a storefront, or an AI assistant that can read and act on all of it. The work is rarely the API call — it is deciding what happens when the two systems disagree.
Do we need AI, or just an integration?
Often just an integration, and we will say so. AI earns its place where judgment is involved — reading a document, classifying a message, drafting a reply. Where the rule is fixed, a scheduled job is cheaper, faster and easier to debug. You are paying for the outcome, not for the word.
What is MCP and do we need it?
MCP is the open standard that lets assistants like Claude and ChatGPT act on real systems. You need it if you want an assistant to do more than talk — to pull real numbers or create real records. We build MCP servers as a specialism; see the MCP development page for the detail.
What happens when a vendor changes their API?
Integrations are built as monitored, versioned services with alerts, not scripts taped between apps. When something upstream changes you get a fix, rather than discovering three weeks later that orders stopped syncing.
Is our data safe in an AI workflow?
Your data stays in your systems; models reach it through scoped, audited calls, and we configure providers with training-on-your-data disabled. Where the requirement is stricter, we deploy on infrastructure you control.
Which two systems refuse to talk?
Name them. We’ll come back with what we’d connect, what it costs, and what it saves — free, in plain English.