Automation Platforms
The platforms we build on, and the systems we connect
There is a useful distinction most automation agencies blur. Some tools orchestrate — they are where the logic lives. Others are systems of record — they hold your work, your customers and your tickets. Good automation connects the second through the first, without you replacing anything.
Orchestration — where the logic lives
Our default for anything with real branching, error handling or AI in the path. Self-hostable, so your data does not have to leave infrastructure you control — which matters if you are handling anything regulated. No per-task pricing, so a high-volume workflow does not become a monthly surprise.
Best when: the logic is complex, the volume is high, the data is sensitive, or you want to own the thing outright.
The fastest route from idea to working automation, and the right answer more often than purists admit. Enormous app library, no infrastructure to run.
Best when: the connection is straightforward, the volume is modest, and speed matters more than cost per task. Less suitable once you need real error handling or the task count climbs.
If your business runs on Microsoft 365, this is often already paid for and already approved by whoever handles your IT policy. Deep integration with Teams, SharePoint, Outlook and Excel.
Best when: you are a Microsoft shop, procurement is a hurdle, or the process lives inside Office documents and Teams channels.
Systems of record — what we connect
Issue creation and routing, status synchronisation with other systems, SLA tracking, and the reporting that otherwise gets rebuilt by hand every month. Also the escalation paths that only work when someone remembers them.
Ticket triage and routing, macro-assisted responses, deflection of repeat questions, CSAT follow-up, and syncing customer context from your CRM so agents stop switching tabs to answer a simple question.
Airtable and Notion as lightweight operational databases. WordPress and Shopify for publishing and commerce. Stripe for billing. Google Workspace and Microsoft 365. Slack and Teams for the notifications people actually read. WhatsApp Business where a conversational interface genuinely beats a form. Anything with a documented API, in practice.
How we choose
We do not lead with a platform. The choice falls out of four questions.
Where does your data have to live? Regulated or sensitive data often rules out hosted-only tools.
What volume are you running? Per-task pricing is fine at low volume and painful at high volume.
What already exists? If Power Automate is in your licence and already approved, that is usually a shorter path than introducing something new.
Who maintains it after we leave? The best platform is the one your team can actually operate.
Most builds end up using more than one. A Zapier connection feeding an n8n workflow that writes to Jira is a perfectly sensible architecture, and pretending otherwise is dogma rather than engineering.
And if your problem does not need automation, we will say so. Some processes should be simplified or stopped rather than automated — automating a bad process just means doing the wrong thing faster and more reliably.