Priced against the hours it gives back.

Every engagement starts from a baseline: what a workflow costs you in person-hours today. We scope the agent or the system against that number, and after launch we report against it.

Agent build
from €15k
Delivery partnership
from €7,500/mo
Payback in our worked examples
2–6 months
§ 01PlansTwo doors · published anchors
Door 01 · ProductizedMost popular

AI agent build

from €15k
Per agent · weeks to production
  • One scoped workflow taken to a live pilot
  • Typed MCP tools on your systems of record
  • Guardrails, monitoring and escalation to a person
  • Every tool call logged and auditable
Scope an agent
Door 02 · Delivery

Delivery partnership

from €7,500
Per month · we build & run
  • A senior team designing, building and hosting
  • Platforms, mobile apps and frameworks from our primitives
  • Compliance-ready delivery for regulated industries
  • Data stays in your environment
Talk delivery
§ 02How an agent worksSystems · Agent · Person

The agent does the routine. A person signs the exceptions.

Most of the hours in a back-office workflow go to gathering, checking and drafting. That is the part an agent takes over. Judgement and signature stay with the people accountable for them.

Your systemsAgentPerson
01 · Your systems

Trigger

An invoice, a site diary or a lab deviation lands in the system that already receives it.

02 · Agent

Read

Typed MCP tools read the records it needs: ERP, LIMS, document store, e-mail. Read-only by default.

03 · Agent

Check & draft

Matches against contracts, price lists, SOPs and history, then drafts the output with its reasons.

04 · Agent

Guardrails

Thresholds and role permissions decide: within bounds it proceeds, outside them it stops and asks.

05 · Person

Approve

A person reviews what the agent flagged and signs. The routine part is already done.

06 · Your systems

Act & log

It writes back to the system of record, files and sends. Every tool call is logged.

Fig. 01 · Agent loop Every call logged
  • Agent

    What the agent takes

    Reading records across systems, matching them against rules and history, drafting the output with its reasons. Seconds per case, at any volume.

  • Person

    What stays with a person

    Exceptions, judgement calls and the signature. The agent stops at every threshold you set and asks, with the evidence already gathered.

  • Measure

    What we measure

    Volume, person-minutes per case and error rate before launch; the same three from the log after. That difference is the return.

§ 03Worked examples3 cases · illustrative

Where the hours go, case by case.

Three workflows we see often, with volumes and times typical for companies of that size. Every figure is computed from the stated assumptions; the free audit replaces them with yours.

Case A · Construction · general contractor

Monthly progress valuations and subcontractor claims

12 active sites, 38 subcontractors. Every month the site engineers produce 12 valuations for the client and check 38 subcontractor claims before they are paid.

Today

The engineer collects site diaries, photos and measured quantities, prices every line against the bill of quantities, reconciles it with last month’s valuation and checks each subcontractor claim line by line. About three and a half hours per document.

With the agent

The agent reads the diary app, the bill of quantities in the ERP and the previous valuation, prices each line and drafts the valuation. It flags quantities above contract or more than 5% away from the diary and drafts the query to the subcontractor. The engineer reviews only the flagged lines.

Moved to the agent
Quantity take-off from diariesPricing against the BoQReconciliation with last monthDraft query to subcontractor
Where the hours go · person-hours a month
Today175 h
  • Collect diaries, photos, quantities50 × 60 min = 50 h
  • Price lines against the BoQ50 × 85 min = 71 h
  • Reconcile with the previous valuation50 × 40 min = 33 h
  • Chase and document discrepancies50 × 25 min = 21 h
With agent29 h
  • Review flagged lines and sign50 × 35 min = 29 h
Hours returned / month146≈ 1.0 full-time people
Net saving / year€85,500
Payback3.9 months
Net in year one, after the build€57,500

Not counted above · Claims above contract are caught before payment, not at the final account, and valuations go out days earlier each month.

Assumptions · loaded cost €55/h · build €28,000 · running €900/month
Case B · Life sciences · accredited laboratory

Deviation triage and CAPA drafting

A GMP laboratory running a LIMS logs about 160 deviations a month. Quality assurance must classify each one, look for recurrence and open a CAPA where needed.

Today

A QA specialist opens the deviation, pulls the batch record and the instrument log, finds the relevant SOP clause, searches the last twelve months for similar events, sets the severity and writes the CAPA draft. Around seventy minutes each.

With the agent

The agent reads the LIMS record, the instrument logs and the SOP library. It proposes a severity with its reasons, lists similar deviations, drafts root-cause hypotheses and a CAPA that cites the SOP clause. Critical deviations always go to a person first. QA reviews, edits and signs.

Moved to the agent
Evidence gathering from LIMS and logsRecurrence search over 12 monthsSeverity proposal with reasonsCAPA draft citing the SOP
Where the hours go · person-hours a month
Today187 h
  • Gather batch record and instrument logs160 × 20 min = 53 h
  • Find SOP clause and past recurrences160 × 25 min = 67 h
  • Classify severity and write the CAPA160 × 25 min = 67 h
With agent53 h
  • Review, edit and sign160 × 20 min = 53 h
Hours returned / month133≈ 1.0 full-time people
Net saving / year€70,000
Payback5.5 months
Net in year one, after the build€38,000

Not counted above · Every classification carries its evidence trail, which is what an auditor asks for, and recurrences surface in days instead of at the quarterly review.

Assumptions · loaded cost €52/h · build €32,000 · running €1,100/month
Case C · Distribution · food & beverage wholesaler

Three-way match on supplier invoices

About 2,600 supplier e-invoices a month; roughly 22% carry a discrepancy on price, quantity or a missing delivery note.

Today

Accounts payable matches every invoice to its purchase order and delivery note in the ERP: about 5 minutes for a clean one, 30 minutes for a discrepancy, with calls to the warehouse, a check of the price list and an e-mail to the supplier.

With the agent

The agent reads the e-invoice XML, the purchase order and the delivery note. Clean invoices within tolerance are matched and queued for batch approval. For each discrepancy it explains the cause line by line and drafts the credit-note request. The clerk handles exceptions only.

Moved to the agent
Line-level PO and delivery-note matchTolerance check against the price listCause of each discrepancyDraft credit-note request
Where the hours go · person-hours a month
Today455 h
  • Match clean invoices2,028 × 5 min = 169 h
  • Investigate discrepancies572 × 30 min = 286 h
With agent112 h
  • Approve clean invoices in batch2,028 × 0.5 min = 17 h
  • Resolve exceptions572 × 10 min = 95 h
Hours returned / month343≈ 2.4 full-time people
Net saving / year€139,500
Payback2.6 months
Net in year one, after the build€109,500

Not counted above · Over-billing is disputed on every invoice instead of the ones someone had time for, and the monthly close no longer waits on AP.

Assumptions · loaded cost €38/h · build €30,000 · running €1,400/month
§ 04Payback calculatorYour numbers · live

Run your own numbers.

Pick one workflow: how many cases a month, how long each takes a person today, and how long a review would take with an agent doing the rest.

Your workflow
Estimate
Payback3.1 months
Hours returned a month127≈ 0.9 full-time people
Net saving a year€58,800
Net over three years€161,400

An estimate, not a quote. The free audit measures the real baseline on your data.

Check them in a free audit

Prefer a fixed price?

Scoped software projects from €25k, with a clear milestone plan and a fixed first deliverable.

Scope a project
§ 05Engagement questions
01Do you charge per user, like SaaS?

No. Agents are built for you as a project, not licensed per seat. Delivery partnerships are a fixed monthly fee for a senior team.

02What does hosting and maintenance cost?

For delivery partnerships it is included in the monthly fee. For a one-off agent build we scope hosting and maintenance separately and transparently; you can also self-host.

03Can we start smaller than a full build?

Yes. Start with a free AI-agent audit: we map one workflow and estimate hours saved before you commit to anything.

04How do you measure the return after launch?

The audit records a baseline: volume, person-minutes per case and error rate. After launch every tool call is logged, so hours returned are counted from the log against that baseline and reported every month.

05What if our volume is too small for an agent to pay back?

Then we say so in the audit. Often the answer is to group two or three related workflows into one agent, or to start with a lighter automation.

06How do we exit if it isn’t working?

We document everything and hand over; the software keeps running whether or not we stay involved.

§ 06

Let’s find the workflow worth opening to AI.

Book a 30-minute scoping call: one workflow, the modules it needs, a scoped proposal.