EN

AI Agents

We build agents for a defined task.

An agent can move a piece of work through several steps, using the permissions it has been given. We define the task, the conditions for continuing and the point where a person takes over.

An agent is a piece of software, not a colleague. It has no judgement about your business beyond the rules you write with us, and it holds none of the responsibility.

The work

Pick a job. Watch where the agent stops.

Six jobs people ask us for. Each one repeats, has a written rule for the ordinary case, and has a moment software should not decide.

A customer writes an order the way they speak, on WhatsApp or by email. It is matched to your items and prices, checked against stock and the delivery cutoff, and prepared.

  1. A message
  2. Matched to your items
  3. Draft order
    1. You post itStops and waits for a person

Log

  1. A message
  2. Matched to your items
  3. Draft order
  4. You post it

What one is made of

  1. The trigger

    Where work arrives: one number, one inbox, one folder.

  2. What it may touch

    Each system is a tool with its own limits. What it was never given, it cannot use.

  3. The steps

    The procedure, written in your words, where your team can read it and change it.

  4. The stop

    Every case it must not decide, written down before it runs.

  5. The approval

    A named person decides, and someone else when they are away.

  6. The log

    What it did and why, in sentences you can search.

If the job is answering questions from your own documents rather than carrying work through its steps, that is AI Integration.

The stop condition

Where it stops is written down before it starts.

This is the procedure one of our agents runs with, word for word. Six of its eight clauses let it carry on by itself. Two hand the decision to a person.

A jobRead against the procedure It runs to its resultIt goes to a person
A job the procedure allows runs to its result.A job that meets a stop clause goes to a person.

Carries on by itself6

  1. Clause 1

    Match every sender to a customer or supplier record before acting on their message.

  2. Clause 2

    Check supplier invoices line by line against the purchase order, the goods receipt and the contract prices. Put an invoice with any discrepancy on hold.

  3. Clause 4

    Parts orders up to 50 EUR for a customer repair can be placed without approval.

  4. Clause 5

    Quote customers from the workshop price list. Hold a slot for up to 24 hours while they decide.

  5. Clause 7

    Write to customers and suppliers in the language and tone they used. Address suppliers formally.

  6. Clause 8

    Before every step, note briefly what you are checking and why.

Hands the decision to a person2

  1. Clause 3

    Never pay, dispute or accept an invoice alone. Prepare the dispute and ask the owner to approve it before anything goes to a supplier.

    The workshop owner approves

    In the recorded invoice run, the dispute letter waits for this approval.

  2. Clause 6

    Brakes, a crash or an injury go to the mechanic on duty. Safety warnings are fine; do-it-yourself repair instructions are not.

    The mechanic on duty takes over

    In the recorded photo run, the crash inspection goes to the mechanic on duty.

One of ours, working

Relay reads a bike workshop’s inbox.

Relay is ours. The workshop, its customers and its invoices are records we wrote so that the agent has real work to do. Every step is a recording of an actual model run, kept in the order it happened.

It stops at the approval and waits. Sending the letter it prepared, or taking the job over, is the decision a person makes.

Relay

Lanac Bike Service

Built by Version2

Velo Parts d.o.o.

Email, racuni@veloparts.example

CV-3109

SubjectRačun VP-2026-0917

Poštovani,

u privitku Vam šaljemo račun VP-2026-0917 za Vašu narudžbu PO-5521. Molimo uplatu do 14.10.2026.

Lijep pozdrav,
Sanja
Računovodstvo, Velo Parts d.o.o.

    Client work

    Maestral works through a wholesaler’s evening orders.

    Tramontana Gastro supplies hotels and restaurants on the Dalmatian coast. Maestral, the company agent we built for them, turns orders sent on WhatsApp into draft orders overnight. Anything that commits the company to money, a price or a new promise goes to a named person in Slack.

    Ordered on WhatsApp at 22:47, drafted as order 18834 at 22:48, a credit note sent to the director for approval in Slack at 23:14, and on the van at 5:40.

    WhatsAppAn evening order, written the way the customer speaks
    Order deskEvery draft line traced to the customer’s words
    SlackA credit note waiting for the director’s approval
    KaštelaOn the van, route Makarska 2

    Screens from Tramontana’s workspace, in Croatian
    It may
    Draft orders in the ERP, reply to customers inside WhatsApp’s service window, and answer the team in Slack with its sources.
    It stops before
    Moving money, changing a price, a credit limit or a customer’s terms, and posting any document in the ERP.
    Who approves
    Credit notes go to customer service, finance or the director depending on the amount. Out of hours, finance approvals go to the director.

    Rules it follows: Fiskalizacija 2.0, EU AI Act transparency, GDPR, processing in the EU

    Limits

    What an agent will not fix.

    • A process without clear rules

      If two people on your team would answer the same case differently, that is the work to do first, and it is yours rather than ours.

    • A decision nobody owns

      Approving a payment or sending a binding reply needs a named person and an approval boundary. An agent does not create an owner where there is none.

    • A job with no judgement in it

      Sometimes a rule and a form are enough. Ordinary automation is cheaper to build, cheaper to run and easier to check, and we will say so when it fits.

    • A rule nobody updates

      Procedures change. An agent’s rules and checks need reviewing after launch, which is what care is for. A rule left stale goes wrong quietly.

    Responsibility

    Your process owner decides which actions may run and which need review. We define the workflow and its checks, and a named person handles the cases it cannot complete.

    Questions

    The things worth asking first.

    What is an AI agent, in one sentence?

    Software that carries one repeating job through its steps inside permissions you set, and stops at the cases you told it not to decide.

    Will it do things without asking?

    Only the things you listed. Everything else waits for a named person, and that list is a document you can read and change, not a setting hidden inside a model.

    What happens when it gets something wrong?

    The work goes to the person who owns it, with what the agent read and the likeliest answers, and the log says why it chose what it chose. Before launch it runs in parallel with your team on your own past cases, so the wrong answers surface while nothing is at stake.

    Can it work with the systems we already have?

    It goes through the same door a person uses, so your system’s own checks still apply. Inboxes, WhatsApp, Slack, calendars, an ERP, a web shop, bank exports and e-invoices are all ordinary. If a system has no door at all, that is a finding in the first week rather than a surprise in the sixth.

    How long does it take?

    3 to 5 weeks for one job end to end, 6 to 9 weeks for three to five that share what they know. The first of those weeks goes on your real cases rather than on our software.

    What does it cost to run after the build?

    Care is €190 a month, and the models are billed at what they cost. Usage depends on how much work the agent does, and it is read back to you every month with the rest of the review.

    Who is responsible for what it does?

    You are, the same as for anything sent in your company’s name. Your process owner decides which actions may run alone. We define the workflow, its checks and its exceptions, and we answer for those being what we agreed.

    Do our customers have to be told?

    Yes. Article 50 of the EU AI Act has applied since 2 August 2026: a person must be told they are dealing with an AI system at the first interaction. Every reply an agent sends carries that line, and a person stays one tap away.

    Do we own it?

    Yes. The code, the rules and the records are yours and they sit in your accounts. The handover includes the procedure your team wrote, so the part that decides how the agent behaves is a document you keep.

    Scope and price

    The first engagement ends in a written verdict.

    We map one task and its exceptions, then test a bounded version against agreed examples. The written verdict records whether it is ready for a pilot and what remains unresolved.

    Get an agent quote Free 10-minute call

    AI Agent

    One workflow run end to end, human approval on exceptions, guardrails, and a dashboard that shows what the agent did.

    from €3,300per project, 3 to 5 weeks

    Several AI Agents

    Three to five workflows with shared memory, escalation to your team, and evaluations on your own cases.

    from €7,400per project, 6 to 9 weeks

    Agent Care

    Monitoring, guardrail updates and a monthly review of what the agent did. Model usage is billed at cost.

    €190a month, from handover

    The build and the care are separate lines on the quote.

    ContactWhatsApp