Phase 2 - Build. The assessments are deliberately short: weeks, fixed price, a document you own. Most of what we actually do comes after one - or instead of one, when you already know what you need. An assessment is not a prerequisite.
Three kinds of work
Custom models and systems
Vision, language, prediction - built the way how we build describes: a foundation model adapted to your domain, a fast model on top, calibrated uncertainty on everything, and a deployment that learns from its own mistakes. From a scoped prototype to a system your team runs.
Scientific and industrial R&D
Materials, microscopy, life sciences, process data. Work where the model has to respect the physics or biology, and where the result has to survive a reviewer. Often alongside your own scientists, sometimes in place of a hire you cannot make.
Research partnerships
Horizon Europe, VLAIO, ESF and similar. We join consortia as the AI partner, act as subcontractor, or help write the proposal - with the experience of having sat on that side of the table through AID4GREENEST and AI4MI.
How a project starts
- 1
Scoping
Usually an assessment, sometimes just a conversation. Either way the first deliverable is a written scope with a price and what "done" means.
- 2
Prototype
The smallest thing that answers the real question - typically weeks, not months. With a measured result, including if the result is "this will not work".
- 3
Build
Milestones, each one shipping something usable. You see progress in working software, not in status reports.
- 4
Handover
Documentation, tests, and the monitoring that tells you when it is drifting. Built for your team to run without us - and we stay available if you would rather we did.
How it is priced. When the scope is clear - which it usually is after an assessment - a project is fixed price against milestones, each one shipping something you can use. When it genuinely is not clear yet, we work to a time budget with a ceiling and check in with you well before that ceiling, rather than inventing a number we would both regret. Research work follows whatever the funder's rules are.
Phase 3 - Run
Building it is not the end of it. A model in production drifts, the data behind it changes, and the people who understand it move on. So the last conversation of every project is about who runs this afterwards: handover with the documentation and tests, monitoring that tells you when something has shifted, retests on a cadence - or we keep operating it for you. Whichever it is, it is decided before the build ends, not discovered afterwards.
What we are careful about
We will tell you early if it is not a fit. A project we should not take costs you more than it costs us, and a scope we cannot deliver damages the one thing we sell. If the honest answer is "hire someone in-house" or "this is a software purchase, not a model", we say so.
Confidential by default. Most of this work is under NDA and stays there. What we publish is method, not client detail - and we ask before naming anyone.
Where to go next
Start with an assessment
Not sure yet? A short review is the cheapest way to find out what a project should be.
Science
The domains this work comes from, and the products it produced.
Cloud and deployment
What running a model in production actually involves.