Systems, built with AI
Internal tools, integrations, automation. Whatever the thing is that your people are doing by hand. The build method is the advantage: what used to take a quarter takes a couple of weeks.
I'm Mike. I build the systems companies actually need — compliance tooling, product data, internal automation — with AI as the build method. Working software in weeks, not slideware in quarters.
What I do
Internal tools, integrations, automation. Whatever the thing is that your people are doing by hand. The build method is the advantage: what used to take a quarter takes a couple of weeks.
The project that stalled. The data nobody can untangle. The integration that was supposed to land last year.
Product passports, GS1 resolvers, traceability data. The regulation has a date on it, so the software should be ready before it arrives.
Where to start
A session with your team is the cheapest way to find out which. We use your own processes as the material, not generic examples, and your people learn the tools on the work they actually do.
You leave with a team that can use it and a shortlist of what is worth building, in the order worth building it. If nothing on that list is worth building, I will tell you that.
Things I've built
Product-passport resolver for a manufacturer's traceability pilot — spec-compliant, cloud-hosted, built against a hard regulatory deadline.
Translation that holds a company's tone of voice across languages, instead of flattening it into generic machine output.
Audio and video to transcript and summary, running on internal infrastructure. Shipped as a web tool and an iOS app.
Scans marketing copy against sustainability-claim rules before it goes out, so legal review catches problems earlier and cheaper.
Trade-fair lead capture with offline OCR, a product visualisation and engraving tool, and a dashboard measuring what all of it actually saves.
Day one
Juiceworks started on 28 August 2026 with a domain, a camera, and a long career spent building systems inside a company that makes real things.
Most consultancies show you the polished end state. I'm showing the whole thing instead — what I charge, what I win, what I get wrong, and how the work actually gets built. If that's useful to watch, the channel starts at zero. If it's useful to hire, that's the same email either way.
The build log
The wins, the dead ends, the invoices and the things that didn't work. Published as it happens, not cleaned up afterwards.