Skip to content
Integrations

We build around what you already run

Replacement is almost never the answer. The cost of the systems you own is already sunk, and the business case for automation is strongest when it sits alongside them. Below are the 116 systems we build against routinely, across 14 categories — search for yours, or read how we reach the ones that are not on the list.

116 systems

ERP & finance

10

Reading and posting against the systems of record without replacing them — through supported APIs, database views or the same interface a person uses.

  • SAP
  • SAP S/4HANA
  • Oracle NetSuite
  • Oracle Fusion
  • Microsoft Dynamics 365 Finance
  • Infor
  • Sage
  • Workday Financial Management
  • Coupa
  • SAP Concur

CRM & customer service

10

Contact classification, agent assist, routing and interaction assurance, wired into the CRM and telephony the operation already runs on.

  • Salesforce Sales Cloud
  • Salesforce Service Cloud
  • HubSpot
  • Microsoft Dynamics 365 Customer Service
  • Zendesk
  • Freshdesk
  • Intercom
  • Genesys
  • Amazon Connect
  • Twilio

IT service management

6

Ticket creation, enrichment, routing and change records, so automation produces the process evidence the service organisation needs.

  • ServiceNow
  • ServiceNow CSM
  • Jira Service Management
  • Jira
  • Linear
  • Archer

Identity & access

6

Access inherited from your provider rather than reimplemented, so people and automations only reach what they are already entitled to.

  • Okta
  • Microsoft Entra ID
  • Active Directory
  • Auth0
  • HashiCorp Vault
  • Azure Key Vault

Data & analytics

18

Warehouses, transformation, streaming and cataloguing — plus the lineage that makes a published figure defensible to an auditor.

  • Snowflake
  • Google BigQuery
  • Databricks
  • PostgreSQL
  • Microsoft SQL Server
  • Oracle Database
  • MongoDB
  • dbt
  • Apache Kafka
  • Azure Event Hubs
  • Amazon Kinesis
  • Fivetran
  • Airbyte
  • Power BI
  • Tableau
  • Looker
  • Microsoft Purview
  • Collibra

Cloud & platform

11

Wherever the work runs: defined as code, promoted through environments, and deployed into your tenancy when residency requires it.

  • Microsoft Azure
  • Amazon Web Services
  • Google Cloud Platform
  • Kubernetes
  • Docker
  • Terraform
  • Pulumi
  • OpenTelemetry
  • GitHub Actions
  • Azure DevOps
  • GitLab CI

Automation & RPA

7

We orchestrate existing bot estates and low-code flows rather than forcing a choice between them and code — deterministic steps stay deterministic.

  • UiPath
  • UiPath Orchestrator
  • Power Automate
  • Blue Prism
  • Automation Anywhere
  • Camunda
  • Temporal

AI & document intelligence

11

Models for genuinely unstructured input — supplier PDFs, free-text emails, scanned forms — with confidence thresholds and a human review path.

  • OpenAI
  • Anthropic Claude
  • Azure OpenAI
  • Azure AI Services
  • AWS Bedrock
  • Google Vertex AI
  • AWS Textract
  • Azure Document Intelligence
  • Google Document AI
  • MLflow
  • Weights & Biases

Documents & content

6

Document stores and records platforms, including retrieval grounded in your approved corpus so generated answers can cite their source.

  • SharePoint
  • Microsoft 365
  • Google Workspace
  • Box
  • DocuSign
  • Alfresco

Communication & collaboration

3

Alerts, approvals and exception notifications delivered into the tools people already have open, rather than another inbox to check.

  • Slack
  • Microsoft Teams
  • Zoom

HR & people

4

Joiner, mover and leaver processes, role and population data, and the skills records that make enablement measurable.

  • Workday HCM
  • SuccessFactors
  • BambooHR
  • Personio

Testing & release

14

Regression, contract and performance testing in the pipeline, so a release is a routinely reversible event rather than a gamble.

  • Playwright
  • Cypress
  • Selenium
  • Postman
  • Pact
  • k6
  • JMeter
  • Gatling
  • TestRail
  • Xray
  • Zephyr
  • Tricentis
  • BrowserStack
  • Sauce Labs

Observability & incident

7

Logs, traces, metrics and alert routing — because automation that nobody watches degrades quietly and takes the business case with it.

  • Datadog
  • Grafana
  • New Relic
  • PagerDuty
  • Opsgenie
  • Azure Monitor
  • Amazon CloudWatch

Commerce & billing

3

Order, subscription and payment data, so quote-to-cash and revenue reporting can be automated end to end.

  • Stripe Billing
  • Shopify
  • Magento

Not on the list

Anything with an interface is reachable

The catalogue above is what we meet most often, not the limit of what we can connect. There are four ways into a system, and we work down them in order of how well they survive the vendor's next release.
Preferred

API or webhook

The first choice wherever it exists. Supported, versioned, and the interface the vendor intends you to use, which means it survives their upgrades far better than anything else on this list.

Common

Database or view

Read-only views where the application layer is too slow or too limited, with a stable contract so a schema change upstream surfaces as a broken build rather than a silent wrong number.

Accepted

File or document exchange

SFTP drops, CSV and XML extracts, and document folders. Unglamorous, but it is how a great deal of enterprise data still moves, and it can be made reliable with validation and alerting on arrival.

Last resort

The interface a person uses

Where no other route exists, automation drives the same screen a human drives. It is the most fragile option, so we treat it as a deliberate last resort with monitoring that detects the layout change before a user does.

Running something older, or something bespoke?

Mainframes, on-premise ERP, twenty-year-old internal tools and industry-specific systems that predate modern APIs are normal on the estates we work in. The approach is the same: find the most stable interface the system actually exposes, put monitoring and validation around it, and keep the risk visible rather than assumed.

Ask about your stack
Loading bay and distribution operation

Bring us the process you already know is costing too much

Thirty minutes with an engineer is usually enough to tell whether it is worth automating, roughly what it would save, and whether the payback is inside a window your finance team will accept. If the answer is no, we will say so on the call.

SOC 2 Type IIISO 27001GDPR & UK GDPRHIPAA-aligned deliveryAWS & Azure partnersCyber Essentials Plus