An AI agent is a program with one job

An agent carries out one task in your process: read an incoming order, look up the customer in your system, create the order. The AI model does the reading. Anything it can't read with confidence goes to a person on your team.

Orders read into your system
Orders that arrive as PDF, Excel or email go into your order or transport system, whatever their layout.
Documents in the right client folder
Receipts, bank and tax letters that clients email in are filed per client, with a list of what is still missing.
Supplier price lists in one table
Price lists from wholesalers, each in its own layout, read into the table your quotes use. Large price changes wait for a person.
Site reports from a voice note
A voice note from the site becomes a report in your own template. Often there is nothing to build: Copilot or ChatGPT with your template does it.

The AI part of these tools is small. Most of the work is around it: logins, permissions, backups, and where your data is stored.

The examples, with sums you can redo with your own numbers

Replace one tool, if the sum works

A job-planning app billed per technician

If your planners use its calendar and your technicians one job sheet, a version built for just that can cost less. Set our build price plus maintenance against the €12,000 a year. You get that price before we start.

When building isn't worth it

  • The process isn't settled yet. If the way you work changes every month, you rebuild every month. A few months on an off-the-shelf tool first is cheaper.
  • Many departments use the tool. You don't replace your accounting package, CRM or ERP with something home-made. Years of features and integrations sit in there.
  • Payback takes longer than three years.
  • A good tool exists at a fair price. Then we recommend it, and at most help you set it up.

In your name, in writing

The contract says the same as this page.

The code lives in your repository
On GitHub or GitLab, under your company's organisation. We work in it as guests, and you can revoke our access at any time.
It runs on your accounts
Hosting, database and AI service are in your company's name. Their invoices go straight to you, so you see what it costs to run.
Your data stays in the EU
We pick a European region for the database and an AI service with a European endpoint that doesn't train on your data. The scope names which ones.
Documentation someone else can follow
How to run and deploy it, where the keys are, what each part does and how to switch AI provider. Written for a developer who has never met us.

If Sinto Labs stopped tomorrow

Your tool keeps running, because it runs on your accounts. You hand the repository and the documentation to another developer, and they carry on.

How we handle your data, with the services and regions we use

What it costs

We work at a fixed day rate or at a fixed price per outcome. You know the price before we start.

Build: a fixed price
After the AI scan, or after a call if you already know which tool you want to replace. You get the scope and the price in writing before we start.
Changes: at the day rate
New features or a different way of working after delivery. We estimate the number of days up front.
Maintenance: monthly
Cancel any month. If you stop, everything stays yours and keeps running on your own accounts.

What maintenance covers

  • Framework and library updates, so the tool doesn't go stale.
  • Security patches, when a vulnerability turns up in something the tool depends on.
  • Backups checked: we make sure they run and that you can restore them.
  • Small changes up to 1 hour a month, such as an extra field or new wording in an email.
  • New features. We charge those at the day rate, after an estimate.
  • Hosting and AI usage. You pay those directly to the provider.

An engineer in your office

In Ghent, we can work from your office one day a week. That day we keep building, answer your team's questions and review what colleagues put together with AI themselves. We agree it month by month, with a notice period of two weeks.

How a project runs

  1. Scope and fixed price. What the tool does, what it doesn't, what it costs a month to run and what the build costs.
  2. Built on your accounts. From day one. Along the way we show you what works, on your own examples.
  3. Handover. A walkthrough with the people who will use it, and the documentation.
  4. Maintenance, or not. Your choice.