Skip to content
Our approach

Decide before building.

No jargon, no overselling, no opaque dependency. Our job is to turn a real need into a reliable product — and then stay useful over time.

Diagram: scattered files brought together into a single tool, connected to the teams tableur boîte mail fichier partagé outil unique terrain bureau direction 01 · sources 02 · business rules 03 · uses
From the real need to a product in servicediagram
Scoping in writing Delivery in batches Long-term support
Our principles

Four rules that decide for us.

These are not values on a wall: they are the trade-offs we apply when a project has to choose between fast, complete and durable.

Proof before promises

We show, measure and document. The free tools published on this site, and the platform that runs it, are our demonstration.

Scoping that commits

The scope of the first release is written down and settled with you. The quote comes after, not before.

No asset held hostage

Many suppliers keep the domain or the hosting “to keep things simple”. We do the opposite: everything is in your name from day one.

Security by default

Encryption, named permissions and tested backups are handled from the design stage — never bolted on afterwards.

Method

Ship early, improve fast.

Incremental progress: a useful foundation first, then enrichment. You move forward from the first phase, with a visible product at every milestone.

01

Understand

Workshops, mapping of the real need, exceptions, roles and data. That is where the product’s usefulness is decided.

02

Scope

What goes into the first release, what waits, what gets dropped. The budget follows from those trade-offs.

03

Build

Short batches, a real environment, fast feedback from use. We correct course early rather than late.

04

Operate

Go-live, monitoring, documentation, training, then further work within an agreed framework.

“Knowing how to say no is the best sales argument an engineering studio has.”
What we answer when pushed to sell more
Scoping workshop
The decisive moment

One hour of workshop saves three weeks of development.

It is by bringing the people who specify and the people who use it around one table that the real constraints surface. The rest is just technical translation.

Our honesty

What we will not sell you.

Five refusals we stand by. Each would cost you dearly for a questionable benefit — ruling them out is part of the job.

01

Needless custom builds

If an existing tool solves your need for a fraction of the cost, we say so — even when it loses us the project.

02

Opaque packages

The scope and the pricing are itemised. No black box, no cost appearing halfway through.

03

Technological “magic”

AI-assisted features stay supervised on any sensitive action. A gimmick that disappoints costs more than it brings in.

04

Rental in disguise

You are never locked in: your assets belong to you, and the code stays maintainable by other teams.

05

Unverifiable promises

Nobody guarantees first place in search. We guarantee a rigorous method and honest follow-up.

Technical foundation

Technologies other teams know how to pick up.

The "maintainable by others" principle only holds if the stack is standard and documented.

  • PHP
  • JavaScript
  • TypeScript
  • Python
  • Swift
  • Kotlin
  • Go
  • Dart
  • Laravel
  • Symfony
  • React
  • Vue.js
  • Next.js
  • Node.js
  • Tailwind CSS
  • Livewire
  • Alpine.js
  • Vite
  • Flutter
  • PostgreSQL
  • MySQL
  • MariaDB
  • Redis
  • MongoDB
  • SQLite
  • Docker
  • Git
  • GitHub
  • GitLab
  • Linux
  • Nginx
  • Vercel
  • Cloudflare
  • Ubuntu
  • Oracle
Put it to the test

Shall we talk straight?

Bring us a need you doubt yourself. That is the best test of the method described above.

Get the right levers to equip your business.

Once a month: automation, security, performance and field reports from SMBs that took back control of their tools.

No spam. Unsubscribe at any time.