When no tool exists, we build it.
Some jobs do not fit an off-the-shelf product: the data is yours, the rules are yours, the regulator is specific. We build the tool around them, prove it in two weeks, and run it for as long as you want.
What we tend to build.
Checking and verification tools
Names against lists, documents against rules, applications against criteria, with the reasoning shown and an audit trail kept. Trace, our client-verification product for Monaco, is one.
Search and assistants over your own documents
Ask a question, get the answer with the source: contracts, procedures, past projects, product sheets. Private, inside your company, in your language.
Client and partner portals
A place where clients upload documents, see where their file stands and get answers, so your team stops being the portal.
Automation between your systems
The accounting software that does not talk to the CRM, the booking tool that does not talk to the calendar: we make them, with checks at every join.
Dashboards that explain themselves
Numbers from several systems in one place, with the “why” written next to the “what”, refreshed without anyone exporting a spreadsheet.
Websites, apps and stores, where they still matter
We have built more than two hundred since 2019. We still do, when the site is the product, and we build them so that AI search can read them.
Trace: built this way, run every day.
Monaco’s regulated professions must verify every new client. No tool did it well for them, so we built one: 18+ official sources, politically exposed persons, offshore registers and the press, in one dated PDF report. It runs in production at tracemonaco.com.
How a build goes.
A 30-minute call
You tell us where the hours go. Within two days you get a short written note: the two or three jobs AI should take first, and what each would take to build.
A working prototype on your real data
Not a slide deck. One job, built for real, running on a sample of your actual inbox, calls or documents, so you decide on evidence.
Into your tools, tested, handed over
The prototype becomes a system inside the tools you already use, with the exceptions routed to a person, documented, and your team trained to run it.
Kept working, measured, extended
We keep it running, count the hours it gives back every month, and add the next job when your team finds it.
what you get
- Working software, on your data, in two weeksA prototype your team can click through and judge, before you commit to the build.
- Code you ownEverything we build for you is yours: source, data, documentation. You can take it elsewhere at any time.
- Someone to run itHosting, monitoring, updates and a person to call. Or we hand it to your IT; both work.
what it takes
- A real sample of the dataAnonymised if needed. Prototypes built on invented data prove nothing.
- The rules, from the person who knows themAn hour or two with your compliance officer, your head of sales, your office manager.
- A decision after two weeksBuild it, change it, or stop. All three are fine; the prototype is paid for either way.
Asked before every build.
Which technology do you use?
Modern, boring and well supported: TypeScript and Next.js for applications, Postgres for data, EU-hosted infrastructure, and whichever AI models fit the job, with EU options by default. Trace is built on exactly this.
Can you take over something another agency built?
Usually, yes. We review it first and tell you plainly whether it is worth keeping.
How long until it is in production?
Two weeks to a prototype, then three to eight weeks to a system in production, depending on how many systems it touches. The note from the quick-check gives you the estimate for your case.
Start with a 30-minute call. Keep what it finds.
You tell us where the hours go. We tell you which two or three jobs AI should take first, in a short written note. Free, in English or French.