How we build

Not a black box. Not a subscription forever.

Which tools we build with, what you end up owning, and the safety checks built into every automation from day one.

Our toolkit

We don’t force you onto one platform.

We pick the right tool for what you’re automating, often one you’ve already heard of.

Workflow tool

Zapier

The most widely used automation tool, with the largest library of app connections. Easy to learn, priced by how many actions your automations run each month. A good fit if your team already runs on it, or needs the widest app coverage fast.

Workflow tool

Make

More visual than Zapier, with stronger branching for complex, multi-step workflows. Priced by operations, which often works out cheaper at the same volume. A good fit for detailed workflows on a tighter budget.

Workflow tool, self-hostable

n8n

Open-source, and able to run on your own server. Self-hosted is our default when ownership matters: you pay for the server, not an escalating per-run bill, and the automation lives on infrastructure you control.

AI coding agent

Claude Code

Not a no-code tool at all: the AI coding agent our engineers use to build real custom software, such as dashboards, internal tools and integrations no platform reaches. It writes actual code into your own codebase, so you own real software, not a black box.

Rent or own

Why it can cost up to 50% less, and stay yours.

Subscriptions get more expensive as you grow, and you own nothing at the end. A build on self-hosted tools and AI-assisted custom code is close to a fixed cost, and what’s built is yours.

ToolEntry tierGrowth tierAs you scale
ZapierProfessional: from US$30–49/mo (750–2,000 tasks)Team: US$69–104/mo (2,000 tasks, up to 25 users)Task limits push you into a new pricing tier as volume grows
MakeCore: from US$9–11/mo (10,000 operations)Teams: US$29–34/mo (10,000 operations)More operations cost more, on a sliding scale
n8nCloud Starter: €20/mo (2,500 executions)Self-hosted: free software, about US$5–7/mo for a serverSelf-hosted has no per-run ceiling to upgrade past

Vendor list prices at the time of writing. Check each vendor’s site for current pricing.

Renting: three stacked subscriptions

A workflow tool, a chatbot platform and a dashboard tool, each billed monthly, each with a usage cap that pushes you into a pricier tier as you grow. Stop paying one, and that piece stops working.

Owning: one build, on your infrastructure

Workflows on a self-hosted n8n instance, plus dashboards and internal tools written into your own codebase with Claude Code. A one-off project cost, then light hosting and an optional care plan. It’s yours, whether or not we keep working together.

What we build

Three kinds of output.

Digital automations

Workflows that read, decide and act on their own: routing an enquiry, matching an invoice, chasing a quiet lead. Built on Zapier, Make or self-hosted n8n, chosen for your stack and budget.

Dashboards

A live view of what’s actually happening: leads in the pipeline, workflow runs, exceptions waiting for a person. Built as real software, so it’s fast and it’s yours.

Custom internal tools

Where off-the-shelf software doesn’t fit: a booking tool shaped like your process, a lookup tool for your team, or a bridge between two systems that don’t normally talk.

See the 2,000+ apps we connect

Built-in safety

Four phases, from day one.

Every automation follows the same discipline, whether it’s a five-minute workflow or a system touching customer data.

1

Before it goes live

  • Approval gate. Nothing launches until someone on your team signs off on exactly what it will do.
  • Shadow-mode trial. New automations run silently against real data first, so we can compare what they would have done before they take a real action.
  • Version history. Every build is tracked as waiting for approval, live, or replaced, with who approved it and when.
2

While it runs

  • Supervised mode. AI replies and actions wait for a person’s OK until you’re confident enough to let a step run on its own.
  • Least-privilege access. Each automation sees only the data and actions its one job needs, never a broader export “just in case”.
  • Credentials kept out of the automation. They’re supplied at the moment each action runs and never stored inside it, so switching off an integration cuts access everywhere at once.
  • Permissions checked on the server. Access can’t be bypassed by going around a button or calling the automation directly.
  • Rate limits and circuit breakers. An automation that suddenly tries an unusual volume of actions pauses itself and alerts a person.
3

If something goes wrong

  • Quick undo on reversible actions, within a set review window.
  • A kill switch your own team can hit at any time, not just us.
  • Instant rollback to the last working version.
  • A full activity log: every run recorded with the time, what triggered it and exactly what it did.
4

As trust grows

  • Earned access. Automations gain autonomy in stages: reading a copy of your data, then live access, then taking action, each only once the stage before is proven.
  • Monthly health reviews as part of our Kaizen step: what each automation is doing, its error rate, and whether its permissions are still right.

Questions

Before you commit

Do I need engineers on my own team?

No. We scope, build and maintain the automation. Your team reviews and approves what it does; nobody needs to write or read code to run it day to day.

If we part ways, do I keep what was built?

Yes. Workflows on a self-hosted n8n instance and any code we write live on your own infrastructure and in your own codebase. They’re yours either way.

What happens when the automation gets something wrong?

Early on, supervised mode means a person reviews before anything is sent. Later, rate limits, the kill switch and instant rollback catch anything unusual, and the activity log shows exactly what happened.

Can this work with tools I already pay for?

Yes. If you’re invested in Zapier or Make, we build inside what you have. We only suggest moving to self-hosted n8n when ownership and long-term cost matter more to you than convenience today.

How do you decide which tool to use?

We start from what you already pay for and what your team knows. If you’re invested in Zapier or Make, we build there. When ownership and long-term cost matter more, we recommend self-hosted n8n, and when no platform fits, we write custom software with Claude Code.

What is shadow mode?

A trial run. A new automation runs silently on real data and records what it would have done, without taking any real action. We compare that with what your team actually did, fix the gaps, and only then switch it on.

How long before an automation runs without supervision?

It depends on the process, not a fixed timeline. Some workflows earn full autonomy in weeks; others deliberately stay supervised, with a person approving each step, for as long as you prefer.

Can you work alongside our own IT team or developers?

Yes. Code lives in your codebase and workflows run on infrastructure you control, so your team can review, extend or take over anything we build. We hand over documentation either way.

Who looks after a self-hosted server?

We set it up, and keep it updated and monitored under a care plan if you’d like. If your IT team prefers to run it, we hand it over with documentation.

Which AI models do you use?

We choose the model for each task based on accuracy, speed, cost and where your data is allowed to go, and we tell you which one before anything is built.

Free consultation

Get 30 minutes with our experts.

Explore how AI can automate your most complex workflows. No obligation, just a clear plan for what to automate first.