About
A studio built around one architect.
The person who designs the system is the person who builds it.
- Founder
- Eric Chautems
- Based
- Suisse romande
- Languages
- French native · English professional
Who you work with
Eric Chautems
Founder and architect. On every engagement, from the first call to the handover.
Building software professionally since 2015: content platforms, online shops, and the internal systems behind both.
Devocracy also maintains NetScript, an open-source framework for services that agree their interfaces up front, under Apache-2.0.
- 2016
- Computer science, HEIG-VD
- 2022
- Professional Scrum Master I
- Today
- Author and maintainer of NetScript, Apache-2.0
Trajectory
Two kinds of experience, earned separately.
Old systems and new ones are usually sold by two different companies. These four stages are where both came from.
- 01
Inside an enterprise migration
Front-end and experience work within a large-scale ERP migration.
- 02
From agency delivery to engineering
Built content platforms and storefronts, then led the engineering side of an agency.
- 03
Co-founder and CTO
Built a commerce, ERP and delivery platform from empty repository to paying customers.
- 04
Embedded modernisation lead
Nearly two years inside a multi-country industrial group as lead developer.
The studio
Understand it first. Then change it.
Most companies already run the system they need. What they are missing is a clear picture of it.
Three things: mapping systems nobody documented, building the platform and the rules that decide whether an order happens, and setting the limits a team needs before it lets AI near its own code.
Team
You get the people named in the offer.
Shape 01
Architect and one engineer
Shape 02
Architect and a small build team
Shape 03
Working inside your team
The network
Specialists brought in when the work needs one.
Each one named for a specific job, on a specific project.
How it works
- Named in the offer before the project starts
- One architect accountable, whatever the headcount
- Senior rates only for senior people
How we work
Five rules, on every project.
They decide which platform we recommend, and occasionally why we turn work down.
- 01
Architecture before price
The first thing you get is a document you keep: what you have, where the risk is, and what order to do it in.
- 02
Clear joins between systems
Where two systems meet, what they exchange is written down and checked. A change on one side cannot quietly break the other.
- 03
Monitoring from the first release
You should not find out about an outage from a customer.
- 04
You own everything
The code, the data, the infrastructure and the reasoning behind every choice.
- 05
Small team, senior people
A studio this size cannot win on headcount. It competes on who is doing the work.
Next step
Start with a call.
Forty-five minutes is usually enough to know whether we can help.