I start from the way your teams actually work. I decide what to build, and what to leave alone. AI speeds up the building, and I make sure the tool holds up in production.
30 minutes, free, nothing to prepare on your side.
They trusted me
Three projects that started from a business problem, not a feature list. The others remain confidential.
Numiscollection and Emonnaie.fr · E-commerce
+€1M
in revenue in the first year
The starting point: products sold on several marketplaces, listings created by hand, stock out of sync and overselling.
What I built: a PIM built from scratch that feeds both of the group's online shops, now over 100,000 products in 5 languages on 5 marketplaces. The tool helped win a major contract.
See the project
Sogedis · Distribution and after-sales
140 h / month
of manual work removed, €84,000 recovered per year
The starting point: a 20-year-old after-sales system, surrounded by Excel files copied by hand to produce the reports.
What I built: a back office and three extranets for 15,000 clients and 130 service providers, synchronised with the ERP and accounting. Without stopping the business.
See the projectJouéClub · Toy retail chain
2 days → 1 h
of processing per supplier file
The starting point: the product sourcing team compared supplier Excel files by hand, with lookups and copy-paste. Lost data and endless data entry.
What I built: a tool that surfaces every change from one supplier file to the next, connected to their software including their PIM.
See the projectI build the tool that removes that work, and we measure it in hours and euros.
I build the product or take it over, make it solid, and keep it maintainable after me.
Before talking features, I look at how your teams work: what, how long, with which tools. That is where the real need hides.
The need written down, the trade-offs made, what we will not build. Then a price, a scope and a timeline signed before we start.
You see the tool take shape and test it with your teams at every step. No black box, no surprise at the end.
A tool that works sparks ideas. I keep improving it with you, in small batches priced in advance.
I build with AI every day, with my own agents and tooling. It speeds up delivery: on some projects, the delivery cycle is 5 to 10 times shorter. But AI does not know what your team needs. Badly steered, it just hits the wall faster.
What you are buying is judgement: what to build, what to leave alone, and every generated line reviewed like an auditor would.
Operations, catalogue, PIM, after-sales, client and supplier extranets. The tools that run the company, where Excel re-typing disappears.
Supplier files, ERP, accounting, marketplaces, large volumes. Reliable, monitored data flows rather than an export that breaks on a Monday morning.
From idea to product in production: payments and subscriptions, customer accounts, roles and permissions, dashboards. A product that handles growth.
Assistants that answer from your real data, smart imports, generated content. Plugged into your tools, with your rules.
Ageing software, fragile MVP, technical debt. Rewriting from scratch is not always the answer: I measure before deciding.
MSc in information systems security. Permissions, access, customer data, backups. One night of hacking undoes years of reputation.
You have a process to tool up, software to replace or a product to launch.
Ageing software, a fragile MVP, code nobody fully understands any more.
You have a team, and a project that needs a senior architect.
Innovative project in France? I am approved for the Innovation Tax Credit (CII). For a product that is new to your company and not yet on the market, a French SME can recover 20 % of eligible spending as a tax credit. A redesign or a takeover of existing software does not qualify: I tell you from the first conversation, and your accountant validates the amounts.
Web software architect with 20 years in the trade, 12 of them as technical director of a web agency, leading 25 developers and 5 designers. Independent since 2017 through my company NCOO DEV, fully remote for 10 years. Based near Valencia, Spain.
Leading a team taught me to read a need, to make trade-offs, and to say no to a request when it does not serve the business. I still build myself, every week. My detailed background is in my online CV (in French) and on LinkedIn.
Both. A freelance Laravel developer for 10 years, I build things myself. An architect, because I decide what to build before writing the first line: that is what makes a tool pay off instead of cost.
No, it is the most common case. I start from what you do today: your meetings, your files, your tools, the way you work. I write the specification during scoping, and you approve it.
It depends on the scope, which is exactly why I scope before pricing. What you can count on: a fixed price, in writing, before the first line of code.
I design, steer and build every project myself, with AI as an accelerator. When a skill outside my scope is needed, I bring in senior people from my network, under my responsibility.
And I build with standard technologies, tested and documented code: another developer can take it over. No home-made tool that only its author understands.
The specification comes before generation, the agent that writes is not the one that reviews, and every generated change goes through the same review as a human one. On some projects, the delivery cycle is 5 to 10 times shorter, with the same testing standards. What you are buying is not a tool: it is the judgement of someone who decides what deserves to be built.
If that is the right answer, yes, without stopping the business: I did it for a 20-year-old after-sales system. But sometimes it is enough to make it reliable or connect it to your other tools, and I will tell you. We measure and analyse before deciding.
It is my original training: an MSc in information systems security. I review permissions, access, customer data handling and backups as seriously as the rest. And I review generated code like an auditor.
I do not disappear. A tool that works sparks ideas: new features, new uses, automations. I keep improving it with you, in small batches priced in advance or through a monthly retainer.
Yes. French is my native language, I work in English on technical projects, and I live in Spain. I work remotely across Europe, with occasional travel when the project needs it.
Tell me how your teams work today. In 30 minutes, I will tell you what I would build, what I would leave alone, and whether your project could qualify for the French innovation tax credit. If I am not the right person, I will tell you.