Solutions / 03
AI and automation
We put artificial intelligence into production and connect the systems a company already runs, taking out the steps a person performs today: answering, retyping, forwarding, remembering.
The problem
Every company has at least one point where a piece of data leaves one program and re-enters another by way of a person. The management system does not know what the website sold. Accounts are waiting on a file. And meanwhile the phone is ringing, because a call nobody answers is a customer calling somebody else.
Examples
What it looks like once it is handed over.
Not one project: below are six kinds of work that fall under this service, drawn one by one and shown two at a time. If yours resembles one of them, the starting point already exists.
Assistant
The assistant that answers out of your own documents
Specifications, manuals and internal procedures become one thing you can ask questions of in plain language. Every answer cites where it came from, and when it does not know it says so instead of inventing it.
- Answers with sources
- Your data only
- Permissions per department
Documents
Invoices and delivery notes nobody retypes
The document arrives by email or from the scanner and comes out already filled in: supplier, number, net amount, lines. Whatever the model is unsure of stays flagged, and a person confirms it.
- Reads PDFs and scans
- A human where it matters
- Posted to the back office
Automations
The steps nobody should still be doing by hand
One event starts a chain: one programme tells the next, the document is generated, the message goes out. Every run is on the record, and when something breaks we are the ones who find out.
- Programmes joined up
- A log of every run
- Automatic retries
Incoming enquiries
Enquiries read and sorted the moment they arrive
Every enquiry that comes in is summarised, classified and placed in the right column with the priority it deserves. Whoever answers reads three lines instead of six emails.
- Automatic summary
- Priority and assignment
- A drafted reply
Voice agent
The phone that somebody always answers
Callers speak normally and the appointment ends up in the diary, with the deposit and the reminder behind it. At nine in the evening and on a Saturday morning, when there is nobody in the office.
- Answers at any hour
- Books into the diary
- Hands over when needed
Forecasting
The figures you already have, read forwards
On the data already in the back office, the model estimates consumption, stock and delays, and flags whatever departs from how things have gone until now. Not prophecies: a short list of things to look at today.
- Consumption and stock forecasts
- Anomalies flagged
- On your own history
A drawing of the interface. The real installations sit behind a login, and that is where they stay.
Demonstration
One phone call, and the appointment is in the diary.
Nobody in the office picked up. Below, what the company is left with once the call ends.
Engineers' diary
This week
Details captured
- Reason
- —
- Customer
- —
- Appointment
- —
What the company is left with
- Appointment in the system
- Confirmation email to the customer
- Engineer notified
- Transcript on the customer record
A reconstruction of a typical call. Names, numbers and diary are examples.
Where it applies
The calls nobody needs to take by hand any more.
The same system changes job depending on what you ask of it.
Booking, moving and cancelling appointments
Opening a support request
Saying where an order has got to
Taking the details of a new enquiry
Answering at night and on closing days
Holding up when twenty calls arrive at once
Calling back whoever found the line engaged
Passing the conversation to the right person
What we build
Voice assistants
They answer the phone, understand natural language, handle recurring requests, book appointments and hand the conversation to a person when it is needed.
Virtual assistants
On the site, on messaging or inside internal applications, anchored to your documents and your data, with every answer traceable to the source it came from.
Automated document reading
Quotes, invoices, orders, contracts and forms read and classified, with the fields extracted and posted into the management system.
Connections between systems
Management system, online shop, accounting, CRM, warehouse, couriers, e-invoicing, bank. Data is entered once and arrives where it is needed.
Jobs that start themselves
Overnight syncs, scheduled extracts, reordering below a threshold, generated documents, deadline reminders. Things that work today because somebody remembers to do them.
Checks and alerts
Rules that watch the data and speak up when something is off: an order stalled too long, a price out of range, a sync that did not complete.
System integration & API
Connected to what you already run.
We do not replace the tools that work: we get them talking. Payments, app stores, messaging, cloud, accounting and language models hook into your software through their official interfaces. These are the services we touch most often.
- Stripe
- PayPal
- Google Cloud
- Firebase
- Supabase
- Netlify
- App Store
- Google Play
- Meta
- Slack
- Anthropic
- n8n
- Notion
- GitHub
- Java
- Your own system
Not on the list? If it exposes an API, or even just a scheduled export, it connects all the same. Ask us whether it can be done
What travels across each connection
Payments and collection
StripePayPal
Checkouts, recurring subscriptions, refunds and automatic reconciliation of what comes in.
Cloud, data and delivery
Google CloudFirebaseSupabaseNetlify
Infrastructure, managed databases, authentication and a release on every change to the code.
App distribution
App StoreGoogle Play
Publishing, updates and in-app purchases on both stores, with the signing and the listings in order.
Messaging and channels
WhatsAppMetaSlack
Notifications and conversations where your customers already write, and service alerts where the team already looks.
AI and automation
Anthropicn8n
Language models anchored to your own documents, and flows that start themselves when something happens.
Everyday work
GoogleNotion
Calendars, mail, sheets and knowledge bases read and written by the software instead of by hand.
Code and platform
GitHubJava
Where the source lives — it stays yours — and what the server side of the more demanding systems runs on.
The trademarks shown belong to their respective owners and appear here only to indicate the services the software we build integrates with.
What we deliver
We start from a map of the manual steps you have today and what they really cost in time. That map says what is worth automating and what is not: something that happens three times a year is usually better left to a person. Before committing the full budget we build a working prototype on your real data.
In production we deliver the connections live and watched, the rules for handing over to a human operator, a panel for following volumes, outcomes and costs, and documentation on how the data is handled. An automation that fails silently is worse than the manual work it replaced.
What is included
What comes with the work, and is not billed separately.
Software does not end on the day it is handed over. These are the terms we work under on every project, written down before signing rather than treated as an extra to quote for six months later.
12 months of support included
On every project we deliver, at no extra cost.
12 months of support included
Every project we deliver comes with twelve months of support in the price: defect fixes, security updates and the small adjustments that only show up once people are using it. It is not a separate retainer to sign.
GDPR, in writing
A data processing agreement under art. 28 of Regulation (EU) 2016/679, the list of sub-processors, privacy notices and consent capture. If the project touches special category data, the impact assessment happens before any code is written.
Encrypted, and hosted in Europe
Traffic always over TLS, data and backups encrypted at rest, credentials in a secrets store and never in the code. Infrastructure sits in European regions unless you ask otherwise and we record it.
Least access, and it is logged
Roles, permissions and a second factor on anything that touches your systems. Every access is named and recorded, and when the project closes our credentials are revoked: it is a line on the handover checklist.
Backups somebody has actually restored
Daily copies, a retention period stated in the contract, and restore drills on a separate environment. A backup nobody has ever read back is not a backup; it is a hope.
The code and the data stay yours
Source, credentials, infrastructure and data are your property from day one, with the documentation to pick them up. No technical or contractual lock if you decide to go elsewhere.
Related services
Get started
Is there something in your processes worth automating?
Describe the situation in a few lines. We come back with an assessment of feasibility, timing and the order of magnitude of the cost.