client work
Work with the studio.
The studio behind our own products takes on client work. Purpose-built software: systems with AI inside them, conventional software without, integration between what you already run, and consulting when you want a second opinion before the build starts.
- engagements
- Four shapes of work
- evidence
- One public product
- scope
- Agreed before the build starts
- route in
- One email address
engagements
What we take on.
Four shapes of work. A project can be one of them, or two of them together.
Tailored builds
A system built for your job rather than configured out of a template. We scope it, build it, and hand it over running.
AI-native systems
Products with AI inside them: the model does real work in the product, inside guardrails you set, and leaves records you can check. This is what our own products are made of.
Integration
Connecting the systems you already run, so data moves between them without a person copying it across.
Consulting
Architecture review, a second opinion on a build already underway, or help deciding whether AI belongs in a given workflow at all.
how we work
The same four rules, on your project.
Evidence over claims. If a feature is on the page, it works today.
Guardrails before autonomy. AI acts inside rules you set, with records you can check.
Purpose-built, not generic. Software shaped to the job, not a template.
Plain reporting. You hear what happened, including what failed.
evidence
The products are the proof.
One of these is public. You can open Myrlin Forge and judge the work directly, rather than take a case study on trust.
start here
Tell us what you are trying to build.
A paragraph about the problem is enough to start. If it is not work we should take, we will say so.