AI agents & LLM platforms
Assistants that do work rather than demo it: tool use, retrieval over your documents, evaluations, guardrails and a cost you can predict.
A small senior team. We design, build and run AI-backed software — and the ordinary product engineering around it that turns a model into a business.
Assistants that do work rather than demo it: tool use, retrieval over your documents, evaluations, guardrails and a cost you can predict.
Catalogue, cart, payments and the back office that runs them — with search, recommendations and generated content where they pay for themselves.
Diffusion wired into a product, not a notebook: fine-tunes, render queues, moderation, storage and a cost model that survives real traffic.
Detection, tracking, OCR and quality control on your own footage — trained on your data, deployed to your hardware, measured on a labelled set.
The read path first: events, aggregates and a warehouse designed before the screen. Then dashboards that answer in one screen, not five.
Consumer products where retention is the only honest metric: mobile apps, games, onboarding, and the analytics that say whether it worked.
Every step ends with something you own and can take elsewhere.
What the model must do, what data exists, what "working" means in numbers. You get a scope, an architecture sketch and a fixed quote.
3 – 5 days · fixed priceThe riskiest part first, running on a URL, with the evaluation set that says whether the quality is there before anyone commits.
2 – 3 weeksTwo-week increments, each deployed behind a flag, with tests, monitoring and the numbers that show it did what it should.
6 – 12 weeksWe keep it running — cost, latency, quality drift — or hand it to your team with docs and a fortnight of pairing.
monthly · cancel any timeMost of it sits inside somebody's company under an NDA, so it is described by shape and result rather than by client name. All cases in detail →
Feed, author profiles with real money attached, and a leaderboard on settled results.
Quizzes sat in scheduled windows, with an LMS and a knowledge base reporting in by event.
Campaign, real-time arena and raids on one combat engine, on Android and iOS.
Custom filters, a batch approval action and a moderation form replaced a shared mailbox.
Three thousand SKUs with forty properties each and a nightly import from the price list.
Three thousand SKUs with forty properties each and a nightly import from the price list.
Campaign, real-time arena and raids on one combat engine, on Android and iOS.
Feed, author profiles with real money attached, and a leaderboard on settled results.
Custom filters, a batch approval action and a moderation form replaced a shared mailbox.
Quizzes sat in scheduled windows, with an LMS and a knowledge base reporting in by event.
Discovery is a fixed price. After that, a fixed scope for a fixed price or a monthly team rate — whichever fits the risk.
You do, from the first commit — repositories, fine-tunes trained on your data, and infrastructure described as code so you can move it without us.
No. We run open-weight models on your hardware or in your cloud region, and we tell you plainly what that costs in quality and in money.
Then we say so in discovery and you have spent days instead of a quarter. A search index or a better data model often beats a language model.
A paragraph is enough. If it is a fit we come back with questions and a first step; if it is not, we say so.