Weekly demos, AI Act–aligned milestones
You see working software every week. Each milestone maps to an Annex IV clause — so the technical file grows with the build, not after it.
04— How We Work
Our delivery principles
Transparency, conformity, and measurable progress. Here is how we operate.
01— PRINCIPLES
Delivery principles
EU-hosted by default
Scaleway, OVHcloud, Clever Cloud. Your data and your model never leave the continent unless you ask them to. SecNumCloud-compatible on request.
Conformity by design
Security, data governance, human oversight, transparency — built into the topology, not bolted on. Every output carries its trace.
02— ENGAGEMENT MODELS
Engagement models
Choose the model that fits your project scope and timeline.
EU AI Act Readiness Audit
We map your AI system against Annex IV, identify the architectural gaps that block conformity, and return a clause-mapped remediation roadmap.
- 01Article 6 risk classification (high-risk vs. limited)
- 02Annex IV technical-file gap analysis
- 03Articles 9–15 obligations mapping
- 04Prioritised remediation roadmap
Compliance-First AI Build
Senior engineers rebuild or refactor the system so conformity is a property of the architecture — not a document added after the fact.
▪ Most engagements start here
- 01Retrieval, reasoning and verification split
- 02EU-hosted deployment (Scaleway / OVHcloud)
- 03Annex IV technical file produced as we build
- 04Eval harness and post-market monitoring
Continuous AI Compliance & Operations
Embedded team keeping the conformity posture current as the system, the regulation, and the threat surface evolve.
- 01Technical file kept live across changes
- 02Post-market monitoring (Article 72)
- 03Serious-incident playbooks (Article 73)
- 04Quarterly conformity review
03— WHAT'S INCLUDED
What's included
- 01Direct access to senior engineers
- 02Weekly progress reports with clause-mapped milestones
- 03Code review and pair-programming sessions
- 04Technical file and knowledge transfer
- 05Post-launch conformity support period
04— QUESTIONS
Frequently asked questions
We are French-incorporated and EU-based. Delivery is remote-first within Europe, with significant overlap for synchronous collaboration. When the engagement requires SecNumCloud-compatible delivery, we operate end-to-end from the EU.
We adapt to your tools. Typically: Slack or Discord for day-to-day, Linear or Jira for tracking, GitHub for code, Loom for async demos. Weekly video calls for planning and retrospectives, with a written record for the technical file.
Yes, before any detailed discussion. We also sign Data Processing Agreements under GDPR and can commit contractually to EU data residency from the first engagement day.
All code and deliverables are owned by you. We provide full source access from day one, documented in your repositories. No lock-in, no surprises — including the technical file itself.
Readiness audits are fixed-price. Builds and continuous operations are time-and-materials with weekly billing. Fixed-price options available for well-scoped projects after the audit phase.