We don't care if you
still bill by the hour.
We build bespoke tools that kill the boring parts of your job. Sometimes with AI, sometimes with no-code, sometimes with plain old automation.
Why “New Adventures in AI-Fi”? I work a lot with music, and it's a straight-up homage to R.E.M.'s New Adventures in Hi-Fi. I did briefly consider Automatic for the People instead — then remembered they still have lawyers.
Live tools, not slideware
Every card below is a working prototype you can open right now. This is roughly what a first build looks like — yours would be shaped around your own documents and playbooks.
Document generation
Try itDocument review
Try itRelationship & obligation maps
Try itClient intake & support chat
Try itDocument retrieval
Ask us about thisDocument classification
Try itClient outreach
Ask us about thisCustom workflows
Ask us about thisFrom first call to your own software
Four phases, same order every time. You own everything that comes out the other end.
Understand
A quick 30-minute chat, then a longer session where you walk us through the pain point, the flow, and the stack you're already running.
Scope & collect
We quote the project and gather what we need — templates, playbooks, house rules — without ever touching your client data.
Build & test
We ship a working MVP you can actually use. You test it, we fix it, we go round again until it's genuinely useful.
Hand over
We deploy the finished tool on your own servers. It's yours.
Tools we work with
No-code, automation and AI platforms we reach for, depending on what the build actually needs.
What this looks like by trade
Illustrative examples of the kind of build each type of firm tends to need first.
Retyping the same details into every new contract
An in-house team had to draft a separate contract for each prospective client, retyping the same data into a single template every time.
Built: document generation tool connected to their own spreadsheet — the data is pulled in automatically and the contract fills itself · drafting time cut from 40 minutes to under 3.
Three years of client files, no order to any of it
Engagement letters, correspondence and statements were dumped into one folder per client, undated and unsorted.
Built: document classification & retrieval · folders sorted and searchable overnight.
Client onboarding tangled up in paperwork
Onboarding a new client meant forms, and a lot of back-and-forth to get the right answers out of them.
Built: an intake form wired to Airtable that triggers document generation · answers flow straight into the CRM and the engagement letter is drafted automatically.
The same policy question, answered by a human, every time
An HR consultancy was answering near-identical leave and benefits questions across every client account, all by email.
Built: client intake & support chat · 8 in 10 queries resolved with no human involved.
Every supplier contract read line by line
A small operator reviewed every new supplier and vendor agreement personally, with no legal team to lean on.
Built: document review tool, RAG-augmented against open-source playbooks · risky clauses flagged automatically, with the source highlighted.
Filing and sending applications to collecting societies
Notifying collecting societies about every concert was time-consuming and overwhelmed the admin team at a music production company.
Built: automated document creation and submission, connected directly to their concert database · no more re-typing the same details by hand.
Straight answers
How much does this cost?
It depends on scope, but most projects land between €2,000–€5,000. Factor in ongoing costs for hosting, external no-code tools and any AI API usage on top.
Isn't it cheaper to just buy a SaaS?
Not necessarily. It comes down to how complex the task is, how many people need to use it, and how much customisation you actually need. Sometimes I advise a hybrid system — a no-code platform plus custom development. Sometimes it's just cheaper to invest in a SaaS and integrate it with your current stack. I'm happy to take a look at your needs and suggest the best course of action.
Does every build involve AI?
No. Document generation, for instance, is often plain automation — no model required. We also use a lot of no-code tools.
How long does a project take?
A simple automation can be live in a couple of weeks. Bigger builds take longer, roughly in line with the price.
What if I don't like the first version?
That's exactly what the testing phase is for. We keep adjusting until it works the way you need it to.
Who owns the code once it's built?
You do. It runs on your own servers, not ours.