EN
Book a discovery call

AI agents · workflow automation · n8n, Make, code

AI agents and automations that take work off your team

An AI agent is a workflow that reads, decides within clear rules and acts in your tools: it sorts the inbox, updates the CRM, prepares a report or a document. We build them in n8n, Make or custom code, with a person approving every step that matters.

  • Built on the tools you already use
  • Human approval for sending, paying or deleting
  • Logs of every run, so you can see what happened

Price Custom quote, after scoping the process

01 · What we automate

Repetitive work agents handle well

  • Inbox triage

    Incoming inquiries and emails classified, summarised, routed to the right person, with a reply draft.

  • CRM updates

    New leads, call notes and email threads written into HubSpot, Pipedrive or Salesforce without retyping.

  • Reports

    Weekly sales, support or ops summaries pulled from several systems and written in plain language.

  • Documents

    Invoices, orders and RFQs extracted and checked. See AI document processing.

  • Customer replies

    Answers to common questions from your knowledge base. See AI customer service agents.

  • Internal requests

    Leave, purchase and IT requests collected in chat, validated and passed to the right system.

02 · Tools

n8n, Make, Zapier or custom code

We pick the tool for the process, not the other way round.

—n8nMake / ZapierCustom code
Best forComplex flows, AI steps, sensitive dataQuick links between SaaS appsHigh volume or unusual logic
HostingCloud or self-hosted on your EU serverVendor cloudYour infrastructure or ours
Who can maintain itA technical adminA trained business userA developer
Running costsServer or plan, plus AI API usagePlan based on operations, plus AI API usageHosting plus AI API usage

Most projects combine them: n8n or Make for orchestration, an AI model (OpenAI, Anthropic or Azure OpenAI) for reading and writing, and your systems' APIs.

03 · How we build an agent

From scope to a monitored workflow

  1. Scope

    One process, written down step by step: inputs, decisions, outputs, exceptions and who approves what.

  2. Prototype

    A working version on real (or anonymised) examples, tested against how your team handles the same cases today.

  3. Human in the loop

    Approval steps where a mistake is costly: sending to clients, changing records, money. The agent proposes, a person confirms.

  4. Monitoring and logging

    Every run logged, errors alerted, quality spot-checked. Rules are adjusted as edge cases appear.

04 · Example processes

What an automation could look like

Illustrative example

Inbound inquiry triage

B2B company, shared sales inbox

Trigger
New email in sales@
AI step
Classify: quote request, support, spam; extract company, product, quantity
Output
Deal created in the CRM, owner assigned, reply draft waiting for approval

Illustrative example

Weekly management report

Service company, several systems

Sources
CRM pipeline, helpdesk tickets, invoicing tool
AI step
Summarise changes and flag anomalies in plain language
Output
A one-page report in Teams or Slack every Monday

Scenarios show typical designs, not results of a specific client.

05 · Cost of ownership

What you pay for after launch

Running an agent has three parts: the automation platform (a plan or a server for n8n), AI model usage billed per amount of text processed, and maintenance when your systems or processes change.

AI usage scales with volume: a few hundred emails a month costs little, thousands of long documents a day is a budget line. We estimate this per process before building, and log usage so there are no surprises.

FAQ

AI agents and automation questions

What is the difference between an AI agent and an automation?

A classic automation follows fixed rules. An AI agent adds steps that read unstructured input, such as emails or PDFs, and choose between options. In practice we combine both, with fixed rules wherever possible.

Can an agent make mistakes?

Yes. That is why we add approval steps for anything that goes to clients or changes money and records, log every run and test on real examples before launch.

Do you work with n8n or Make?

Both, plus Zapier and custom code. n8n is our default when data is sensitive or flows are complex, because it can be self-hosted in the EU.

How long does it take to build an agent?

A focused workflow usually takes 2–4 weeks from scope to pilot. Agents that touch several systems or need approvals across teams take longer.

Who maintains it after launch?

Either your team, after a handover and training, or us under a support agreement. Either way you get documentation and access to every workflow.

Pick one process to automate first

A free call to find the workflow with the best payoff and the lowest risk.

Book a discovery call

Price: Custom quote, after scoping the process

Next step

Tell us about your business

A short form. We reply within one business day: whether we can help, and what the first step would be.

Price Custom quote, after scoping the process

What you need

We reply within one business day.