Benoit Sadon. Solution architect.
Petit à petit, l’oiseau fait son nid.
Little by little, the bird builds its nest.
Every complex solution I’ve delivered was built the same way: one verified step at a time.
Where the rigour comes from
I started in aviation as a technicien méthodes, a manufacturing engineering technician, with a company that built aircraft cabin equipment: in-flight entertainment systems, ambient lighting, screens and keyboards, and the actuators that let a business class seat lie flat.
The methods department linked every other department. My job was to collect knowledge from all of them, from research and development through prototyping, quality and sales to the production floor itself, and turn it into the work instructions and inspection plans the production teams built from. Nothing I wrote reached the floor unverified. My manager reviewed and stamped every file, a dedicated team built a trial run from it, and the inspection department validated the finished product against it.
Aviation doesn’t tolerate ambiguity. It taught me that the most complex products in the world are not built in leaps. They are built in steps: clear requirements, precise documentation, constant communication between stakeholders, and verification before anything moves forward. It also taught me to love the questions behind the product. Why does this component exist? What is it for? How does it work? When a problem has no existing solution, those questions are how you find one.
The same discipline, applied to your business
Clients rarely bring me a tidy problem. They bring five gym sites that need one membership system: expiries, RFID entry after hours, equipment monitoring and repair tracking, tailgating detection at the door with automatic photo capture, and several vendors who have never spoken to each other.
My job is to capture the real requirements, get every stakeholder and supplier around the same table, design the solution, then manage scope, schedule and budget until the outcome matches what your business actually needs. I’m technical enough to go deep with your engineers, and to implement parts myself when that gives you better value. But the heart of the work is human. It is listening, translating, and keeping everyone building the same nest.
How I work
Requirements before solutions
I listen first, and I write down what your business needs before proposing anything.
Every stakeholder at the table
Vendors, engineers, your staff. The solution has to work for all of them.
Verification at every step
Nothing ships on trust alone. Each stage is checked before the next begins.
Who I work best with
I do my best work with established businesses facing real operational complexity, run by owners and managers who want a solution designed properly, delivered step by step, and documented well enough to outlive the project. If you’re after the cheapest possible patch or a miracle by Friday, I’m probably not your architect. If you want a system your business can stand on for years, we should talk.
The person behind the process
I’m French, and I live and work in Australia. I come from a culture that takes craft seriously, where a thing worth doing is worth doing properly, and where nobody is surprised that good work takes steps. The proverb at the top of this page is how I was taught to build. It’s still how I build today.
Tell me about the problem you’re trying to solveExplainer Why this page reads like a build sequence
This page does the same job a good solution does. It starts with a philosophy, proves it with a true story, shows the method, and then says plainly who it is for and who it is not for. Every factual claim on it comes from a recorded interview. Nothing is invented. Complex things get built little by little, one verified step at a time.