The Builds — automation & agents

Automate your processes, without creating a black box

We automate SME processes across Europe — invoices, email, quotes, reports — starting from a documented process sheet. Every automation is logged, hosted under your jurisdiction, and maintainable by someone other than its author.

What we automate

Proven typical builds, tested on the processes that cost SMEs the most time. Each one is traced back to a process sheet from The Baseline.

Supplier invoice processing

Receipt, extraction, order-delivery-invoice matching, payment preparation. The human validates, the machine prepares.

Sorting and replying to inbound email

Classification by intent, routing to the right person, draft replies for recurring requests — never sent without a defined control.

Quote preparation

From customer request to a quote ready for review: product data, history, pricing rules. Your sales team sells instead of retyping.

Recurring reports

Weekly or monthly reports assembled automatically from your systems, with figures traceable back to the source.

Supervised AI agents

Agents that act within a documented scope: every action logged, a human in the loop at decision points, reversibility built in.

The difference with a freelancer’s script

The same automation a freelance Make or n8n contractor would build — but documented, hosted under your jurisdiction, and maintainable by someone other than its author.

A typical automation architecture

A typical architecture diagram: self-hosted n8n under your jurisdiction, connectors to your existing systems, logging of every execution, a human validation point before any consequential action.

Architecture diagram and documented scope
Operations documentation (error recovery, supervision)
Full logging of every execution
Reversibility procedure: nothing dies with its author

Illustrative example — a typical architecture, not a client system

What a typical engagement looks like

1. Scoping from a process sheet

We start from the process sheet in The Baseline: volumes, exceptions, systems. The scope is fixed in writing — a fixed-scope engagement, never open-ended time and materials.

2. Build

Self-hosted n8n, RPA or custom development depending on the case. Exceptions are handled, not ignored: that’s where scripts die.

3. Testing under real conditions

The automation runs in parallel with the manual process until the figures match. It goes live once proven, not before.

4. Handover and maintenance

Operations documentation delivered, teams trained. After that: your teams, or The Engine Room under SLA. You choose.

And all of it passes the audit

Supervised agents, not left unattended

A documented scope of action, every execution logged, a human in the loop at decision points. It’s exactly what an auditor will ask to see.

AI Act classification upfront

Every automation embedding AI is classified before it’s built. High-risk system obligations apply from 2 August 2026; AI literacy (Article 4) since 2 February 2025.

GDPR by design

Data minimised, hosting under your jurisdiction, subprocessors documented. The automation feeds your record of processing activities instead of bypassing it.

Frequently asked questions

n8n, Make, or custom development?

Whatever the process requires, not what a commercial partnership makes convenient. By default: self-hosted n8n, under your jurisdiction and reversible. Make or Zapier when the context justifies it, custom development when no-code tools no longer suffice. We are independent of vendors.

Who maintains the automation?

Your choice: your teams — the operations documentation makes that possible, that’s the point — or The Engine Room, our subscription-and-SLA run offer: supervision, updates, compliance kept alive.

What’s the difference with a freelance n8n or Make contractor?

The same automation, but documented, hosted under your jurisdiction and maintainable by someone other than its author. An undocumented script dies with its author; yours will outlive ours.

Do we need a Baseline before automating?

It’s the recommended path: automation only works well on a process that’s understood and documented. If your need is already precise, a short scoping exercise on the specific process is enough — but we never build without documenting what we automate.

Is a process costing you too much time?

Start with a free Express Scan: 90 minutes with an engineer to see whether automation pays off in your case — and if not, we’ll tell you.

Request an Express Scan See the method