How I work

The Method

You understand everything I build.
And you can carry on without me.

Every engagement follows the same process: we discuss, I propose an architecture, you approve, I build, and you receive the entirety of the work. No black box.

The process, step by step

1
First contact

You reach out with your problem, your idea, or simply a question. No need for a structured brief — a message is enough.

2
In-depth discussion

We take the time to discuss your needs, your constraints, and what you concretely expect. This is often the most important part of the work.

3
Architecture plan

I submit a complete architecture document: context, technical principle, functional breakdown, data flows, model choices, decision points. The goal is clear: you approve the strategy before I touch anything.

Every architecture is guaranteed for 12 months for minor changes, at no extra cost.
4
Approval then build

Once you approve the plan, I get to work. You know exactly what will be built, how, and why. No surprises.

5
Full delivery

You receive the working system, but also everything that allowed me to build it. The architecture, the explained choices, the guides, the forward-looking perspectives. You are autonomous from day one.

What an architecture plan looks like

Before building anything, I present you with a structured document that covers all aspects of the solution. Here is an example of an actual table of contents:

Example · Sovereign Multi-LLM Architecture
1
Context and Vision
Stakes, positioning, why this project exists
2
Architectural Principle
Overview of the circuit: how the pieces fit together
3
Functional Breakdown
Each block detailed: role, model, rationale
4
Defense in Depth
The layers of protection: why and how
5
Data Flows
What flows between each block, within what perimeter
6
Model Gradient
Which model for which task: risk / complexity calibration
7
Decision Points
The open choices: what remains to be decided together
8
Summary
Consolidated view and next steps

What you receive at the end

The deliverable is never limited to the working system. You receive all the elements that allowed me to build it, so you can understand, maintain, and evolve it.

The working system

The finished product, deployed, tested, operational. Ready to use from the moment of delivery.

Operating guide

A document that explains how the system works, how to use it, and how to maintain it on a daily basis.

AI-ready guide

A structured file you can feed directly into an LLM to query it about the built system. The AI understands what was done.

Evolution roadmap

What you can evolve on your own, what would require support, and the possible directions forward. With or without me.

No black box

You don't depend on me after delivery. Everything is documented, everything is explained, everything belongs to you. If you want to carry on alone, you can. If you want to come back, I'll be here.