We build AI products and we build them for you.
We run our own SaaS, and build explainable, GDPR-ready automation for other companies to the same standard.
How we work
- You describe how it works today.
- We map it.
- You try a first version on your own data and tell us what is missing.
- It goes live and we keep it running.
If you can describe it, we can build it.
Products you can use today
Two products we build and run ourselves. Open them and judge for yourself.
Management software for bands, choirs and orchestras: roll call, paid gigs and payouts. Free for any size of society.
- Free plan
- Offline roll call
- Data in the EU

European contract management with explainable AI, GDPR and eIDAS signing.
- GDPR and eIDAS
- 5 languages
- Data in the EU

The studio that owns what it builds
We own our products
A small house of brands we build and run ourselves. You can use them today.
And we build yours
The same standard, applied to your processes, with us as your team. Automation that holds up once it is live.
How one feature got built, commit by commit.
On 5 October we decided what Atellio's music schools needed next: families type their week in their own words and see it drawn as a timetable to confirm. The decision was written down as a spec; our own automation turned it into code and went over it looking for faults, and 5,020 backend checks passed. It shipped when a person said yes. Each mark on this line is a real commit, and the last one is the release.
- Decision written down as a spec.
ec9a6eb3 - Server side: the reader and its daily limits.
e83206c1 - Screens: type the week, answer the reader's questions, see it drawn.
b4aede1e - Review finds that an empty answer could wipe a saved week, and fixes it.
30438ae6 - More fixes: limits per person, never on the public demo.
7974bea5 - Merged, 2 h 45 min after the decision.
e4cdb73b - Deployed to production in release 4.6 Oct
Every change to Atellio, our software for music societies, has to pass these automated checks.
- 5,745
- backend checks
- 4,458
- frontend tests
- 4,061
- interface strings kept in step across languages
Everything we do, listed in full.
Five lines of work. The first four are automations we deliver into your stack; the fifth is the whole product, built the way we build our own.
- Document & contract intelligenceExtraction you can auditClauses, dates, totals and obligations pulled out of PDFs and scans, every field citing the line it came from. The same engine that runs EUCLM in production.
- Agentic workflowsAgents that do the workMulti-step agents that read, decide and act across your tools, with a human checkpoint wherever being wrong is expensive.
- Internal tools & dashboardsOne screen instead of six tabsThe view your ops team currently rebuilds in a spreadsheet every Monday, on your data and behind your permissions.
- Systems integrationYour stack, actually connectedCRM, ERP, inbox, drive, e-signature. We wire what you already pay for instead of selling you a replacement.
- AI product buildFrom idea to shipped SaaSStrategy, design, build, deploy, operate. We have taken this route twice for ourselves: EUCLM and Atellio are both ours.
- 2
- SaaS products we own and operate
- 3 wks
- To a working prototype on your data
- EU
- Data residency, by default
- 100%
- Of the code and data is yours
Explainable, European, and built to keep running
- Built to product standard
- We build for you to the same standard we hold our own SaaS.
- EU-native by default
- GDPR, eIDAS, EU data and explainable AI, designed in from the start rather than added to pass a review.
- Reliable once it is live
- Automation you can watch running, with alerts when something needs a person.
The questions we get in the first call.
Not here? Write to us and we answer within one working day.
How soon do we see something working?
A working prototype of your highest-volume process in about three weeks, running on your data. If we cannot get there in three weeks, the process is usually the wrong one to start with, and we will say so.
Do we own what you build?
Fully. Code, prompts, infrastructure config and data are yours from the first commit. There is no runtime licence to us and nothing stops working if you stop working with us.
What happens when the AI gets it wrong?
You see why. Every extracted field cites the source line it came from, low-confidence cases route to a person instead of guessing, and nothing irreversible happens without an approval step. Explainability is the product, not a feature we bolted on.
Where does our data live?
By default, what we build for you runs on EU infrastructure and keeps your data in the EU. Enquiries sent through this site are handled differently, and we would rather say so than bury it: they reach us by email and are recorded in HubSpot, our CRM. HubSpot, our email provider and our hosting and CDN provider are US-headquartered, so any access from outside the EEA sits under Standard Contractual Clauses. Our privacy policy names every processor and what each one touches.
Do we have to replace the tools we already use?
Almost never. Your CRM, accounting and signature tools stay where they are, and we build the automation around them; in our list of building blocks, those are the ones tagged Connects. Replacing working software is the most expensive way to automate anything.
Fixed price or time and materials?
The first automation is a fixed price against a written scope, so you can approve a number rather than a rate. Work after that runs in monthly cycles you can stop at the end of any month.
Shall we build something that lands on its feet?
Tell us your challenge. We reply with a plan you can act on.