We are human beings first. Technology comes next — the center of gravity stays you and your teams: what drains you, what blocks you, what should no longer be this way.
Your ideas deservea tool of your own.
I craft IT architectures by hand: before anything else, we talk. You describe what drains you daily — repetitive tasks, blockages that keep returning, what does not work — for you and your teams.
These irritants are not a technical footnote: they are signals. I listen, make them visible, then shape a viable foundation — custom fit and pilotable.
No form to fill in: what matters is that a person talks to me. A conversation — call, workshop or message — and we move forward together, whether you start from zero, a prototype in progress, or the wish for early autonomy.
Free · No commitment · Human first
Your path
From conversation to pilotable foundation
You talk
Time-consuming tasks, recurring pains, what does not work — for you and your teams.
We map
Tools, data, prototypes already started: without throwing everything away.
I shape the foundation
The bare minimum to run your business — then we build on it, toward your goals.
It's not a software problem
Generalist platforms do a lot — the real issue is what you and your teams live daily: tasks that drain energy, blockages that return, what does not work as it should. Naming these pains is already opening the door to concrete action.
Repetitive, time-consuming tasks
Data entry, copy-paste, follow-ups, exports… for you and your collaborators: what eats time instead of moving the business forward.
What does not work as it should
The same blockages keep coming back — ill-fitting tools, workarounds, habits taken. Topics to name, not fate.
Wide coverage, little custom fit
Generalist platforms cover a maximum of cases — but not your exact flow, your exceptions, your way of working.
Tool patchwork
Spreadsheets, email, tool A + tool B: it still works, but nobody has a unified view of the business.
Promising vibe coding attempt
You moved forward alone — screens, scripts, drafts — and got good first results. What often remains: wiring the pieces, stabilizing, naming the need and seeing the possibilities.
"I'm not a developer"
Yet nobody knows your business better than you. Shaping makes the abstract concrete — for you and your teams.
Where do you start?
Three common situations — find yourself in one sentence, the path adapts from there.
I want a piloting tool
You are not starting from a technical patchwork: you want clarity on the business without becoming a developer.
Discovery call or feasibility workshop
I tried vibe coding
You got encouraging results on your own. What remains is wiring, structuring, stabilizing — and knowing what is possible when practice or technical vocabulary is still missing.
Recovery, wiring & framing workshop
I want autonomy early
You want to evolve the tool yourself — on a solid foundation with a safety net, not DIY without structure.
Foundation + handover path
From your business to a pilotable foundation
The foundation is the bare minimum to pilot the business. Then we build on it — step by step — to converge toward your goals.
Human exchange
We talk: what drains you, what blocks you, what does not work — for you and your teams.
Mapping
Tools, data, flows, prototypes already started: we see what exists without throwing everything away.
The foundation
The bare minimum to pilot day-to-day activity — usable right away, not a big bang.
We build on it
Evolutions, modules, automation: we converge toward your goals, at your pace.
When the company has several employees, the foundation also targets added value for them — not only a dashboard for the leader.
Two life paths — you choose
Piloting the business is yours again. Who shapes technical evolutions is a decision — not forced on day one.
Creative delegation
You commission evolutions — I remain the shaper: modules, sync, screens, integrations.
Pour qui · Little internal time, confidence in my ability to deliver for you.
Imaginative autonomy
A lead wires a creation agent to the foundation (code editor coupled to tools or equivalent) for on-the-moment requests.
Pour qui · Want to create yourself — with architecture and security backup.
« Fresh start » or « already tried » doors: some choose delegation; others discover autonomy once they see the foundation. Both are valid.
Shaping: making the abstract visible
I translate your business into a usable tool — with 30+ years of IT, from a human exchange and a well-understood foundation.
What the shaper does — and what agents do
My role: listen, map, build the foundation, connect your tools, give you real visibility on the business. I remain the architect and guarantor of coherence.
AI agents come next: assistants wired to your foundation to automate, alert or evolve the tool — not a generic chatbot. Over time they become more useful, provided we start from your real needs.
The foundation: bare minimum, then we build
The foundation is not software that does everything at once. It is the bare minimum to run your business — see clearly, decide, act day to day. Once in place, we build on it: evolutions, modules, AI agents… to converge toward your goals, without starting from scratch each time.
Example: first a client cockpit and follow-ups; then, if the need keeps returning, we structure prospecting — not the other way around.
AI agents: what they actually are
An AI agent here is not ChatGPT in a tab. It is an assistant wired to your foundation — your data, your processes — able to act: sync, alert, propose an evolution, run a repetitive task.
Two useful families once the foundation is in place: business agents (understand and pilot your data) and creation agents (evolve the tool as needs arise).
Business agents
Natural language, sync, alerts — connected to your data at the right cloud or local level (GDPR).
Creation agents
Wired to your infra and foundation: on-the-moment requests, vibe-code, evolutions without waiting for a dedicated button per wish.
Right choice per use
Internal draft with no sensitive data? Cloud may be enough. Clients, files, piloting? Local or self-hosted AI — integrated into the shaped foundation.
Models and tools: what actually makes the difference
The agent environments we use — code editor coupled to repo, terminal, browser — run on current AI models as needed. Product names alone are not what changes everything.
The power comes from the code editor coupled with tools: automated browser piloting, terminal, repository, APIs, plugins, business context wired to the foundation. That agentic layer — not a simple chat — speeds up shaping. I pick and wire the most effective combination of the day, with no loyalty to a single vendor.
Black, white, and every shade of gray in between
There are two extremes in my line of work. In between: every shade of gray — based on your leadership decision, not mine.
Black
Pure commercial cloud
Commercial cloud and AI hosted by large vendors. Powerful, fast, plug & play. But it's a black box: your data leaves your premises, you depend on a foreign vendor, you lose control.
Gray
The balance you choose
Part of your AI workloads run locally on dedicated GPUs; the rest uses the cloud for less sensitive tasks. The right mix of performance, cost, sovereignty and GDPR compliance — calibrated with you.
White
Sovereign on-premise infrastructure
Everything on your site. Servers with dedicated GPUs — the same class of chips that power large AI models — installed in your offices, under your full control. Open-source models, site-to-site VPN, zero data leakage.
I work with an international client base — SMBs, startups, IT leadership. Every solution is unique. Every solution is secure. And every solution belongs to you.
Five modalities — based on where you start
Not everything must be decided on day one. The delegation / autonomy fork is chosen when the foundation has proven itself.
Human listen
A real conversation to name daily irritants, the existing setup and first priorities — ideal when everything still feels abstract.
Pour qui · Leader who wants to talk before committing — no form, no jargon.
Recovery & framing
Audit of what already exists: prototype, scripts, no-code app, shared spreadsheet, exports… What we keep, wire and structure properly.
Pour qui · Already started with vibe coding or AI tinkering — an encouraging initiative to turn into a tool that holds up.
Foundation shaping
First viable cockpit: data, APIs, piloting, value for collaborators when there is a team.
Pour qui · Company ready to invest in a tool of its own.
Ongoing shaping
You commission evolutions — I remain the shaper over time.
Pour qui · Little internal time, confidence in my ability to create for you.
Agentic handover
After proof: a lead wires an agent editor to the infra to evolve the tool.
Pour qui · Leader or technical profile ready for imaginative ownership.
See concrete journey examples
Solo leader, team with collaborators, after the foundation, on-the-moment request… Detailed examples on a dedicated page — essentials only if you are short on time.
- Door 1: piloting tool without starting from technical scratch
- Door 2: stuck prototype → recovery or guided finish
- Door 3: early autonomy — on foundation, not on sand
Concrete proof — not a CRM sales pitch
The live demo (e.g. client management) shows the shaping principle. The same spirit applies to inventory, accounting, field work…
Trilingual FR / EN / ES · automatic demo logins · database restored nightly at 2am · everything is testable and editable.
Open the live demo"What about my current tools?"
« We don't start from zero by default. What's mandatory or already working, we keep and connect. What slows you down daily, we shape. The question isn't "replace everything" but "what to keep, what to create". »
From business listen to a pilotable foundation: my craft is making your activity visible and actionable — so you and your teams regain room to maneuver.
Tools change — the method holds
AI tools change fast; my daily work is picking and wiring what serves your business, so you keep control over activity without absorbing all the technical complexity.