You shouldn’t have to guess how your tech partner works. Six phases, in order — this is our standard process.
Nos six règles d'atelier — pas un cadre marketing, un protocole. Chaque projet les traverse, dans l'ordre, sans saut.
Workshops, goals, constraints, and estimates. Two to four weeks to align business and technical teams on what we will build — and, above all, what we won’t.
Illustration · ScopingInspired by Thoughtworks, adapted to our reality. Four quadrants, four rings. Click a technology to see where we stand.
Standard pour tout nouveau code.
Choose the model that fits your needs and your team’s maturity. A hybrid approach works too: a scoped project for the MVP, a dedicated team as it evolves, then ongoing maintenance.
Step 01
Fixed price · milestonesFor a defined scope.
Specifications → approved milestones → phased delivery with acceptance testing. Fixed scope, fixed price, dated deliverables. Ideal when you know exactly what you want and need budget certainty.
Step 02
Time & materials · sprintsFor evolving products.
Dedicated developers, designers, DevOps engineers, and PMs working within your roadmap. One- to two-week sprints, monthly billing, and full visibility into time spent. Ideal when needs change every quarter.
Step 03
Monthly · SLAFor the long term.
A monthly plan to track, monitor, fix, and improve a product already in production. A defined SLA, supervision, a ticket allowance, and quarterly reviews.
