Engagements
Eight engagement models, each with a clear scope, a typical duration and named deliverables. Pick the closest one, and we shape it to your situation in a first conversation. Each is delivered by a core team and a network of dedicated engineers.
01 / How a quote works
We do not publish prices, because scope decides the price. Every engagement is quoted after a first conversation, with a fixed scope where possible.
30 minutes about your situation. No preparation needed, and no obligation.
Deliverables, duration, what we need from you and what is out of scope.
A quote against that scope, fixed where possible. You decide whether to start.
02 / Engagement models
Durations are typical. Your scope decides the exact plan.
Typical duration: 2 to 3 days
In 2 to 3 days we map how data and documents flow today and rank the three AI or data use cases with the best value for effort.
What you get
Typical duration: 3 days
We check cost, security with the Security Analysis Tool, governance with Unity Catalog and delivery with Asset Bundles and CI/CD, and give you a prioritised fix list.
What you get
Typical duration: 3 to 4 weeks
We turn one document stream into structured data with a human check, running in your own Azure tenant.
What you get
Typical duration: 4 to 8 weeks
Landing zone, Databricks, Unity Catalog, CI/CD and Terraform modules, delivered secure by design.
What you get
Typical duration: 3 to 8 weeks
A portal, planning tool or self-service app on Azure with Entra ID sign-in.
What you get
Typical duration: A few days a week, ongoing
A senior data and AI lead for a few days a week: roadmap, vendor choice and delivery oversight.
What you get
Typical duration: Half day, full day or a multi-day series
A hands-on session for your team on AI engineering, tailored to your stack and your own use case, on-site or online.
What you get
Typical duration: Half day, full day or a multi-day series
Hands-on AI engineering sessions for universities, bootcamps and student associations, from a first agent to evaluating it.
What you get
Build and automate
Besides the engagement models above, three offers start from an operational problem. Each has its own page with scope, phases and a way to start.
Run and evolve
Software that people depend on needs an owner on call. If you want one, we keep running and improving what we built, under a written agreement. It is optional: the code and the documentation are yours, so your own team can take over at any time.
The service level agreement is written per client: cover hours, how an issue is classified and how fast we respond. We do not publish standard response times, because they depend on the system and on what your operation needs.
03 / FAQ
Scope decides the price, and two organisations rarely have the same scope.
Start with the Data & AI quick scan. In 2 to 3 days it maps how data and documents flow and ranks the three use cases with the best value for effort.
You do. Infrastructure and applications are code in your repositories, documented and handed over with knowledge transfer.
Yes. The quick scan and the health check are short and fixed in scope, and each ends in a written result you can act on.
Next step
Bring one process, one platform or one idea. We reply within two working days and say plainly whether we are the right team for it.
Currently accepting projects for Q4 2026