Answers to the questions asked before starting

It starts with a free one-hour framing call to understand your context and check whether an engagement makes sense. If we proceed, you receive a written proposal covering scope, deliverables, schedule and terms. The work then begins with a short analysis phase and continues in deliverable increments, each closed with a demo and a progress review.

An audit or architecture framing typically takes two to eight weeks. Development or industrialisation work usually spans two to six months, part-time or full-time. Ongoing advisory can be limited to one or two days a month and continue over several quarters.

Pricing is fixed-price for clearly bounded deliverables, or time and materials for advisory and evolving engagements. The indicative figures shown on this demonstration site are examples only and do not constitute a contractual offer: every proposal is priced after framing, based on scope, duration and urgency.

Yes, most engagements run remotely with regular video checkpoints. I travel for the phases that justify it: framing workshops, architecture reviews, audit restitution and training sessions. Travel is planned in advance and invoiced at cost.

Transfer is built into the engagement rather than added at the end. Technical decisions are explained when they are made, code reviews are collective, and every deliverable comes with usable documentation. On longer engagements I pair with one or two internal developers so they can take over when I leave.

Code, documentation and deliverables produced specifically for your project belong to you, with rights of use assigned under the contract terms. Methods, templates and generic components created outside the engagement remain their author's property, but their use in your project is guaranteed and documented.

A non-disclosure agreement is signed before access to sensitive material. Documents and extracts stay on your environments where possible, and no client material is ever used in publications, demonstrations or training datasets. Access granted to me is listed in the contract and revoked at the end of the engagement.

Yes. Engagements longer than two weeks start with a two-week mutual trial, cancellable by either party with three working days' notice. This period validates the working method and communication quality at low risk before committing to the full scope.

Fixed-price work is invoiced against milestones: a starting deposit, then invoices tied to validated deliverables. Time and materials is invoiced monthly based on an activity report. Travel and meal expenses are invoiced at cost with receipts. Payments are due thirty days from invoice date.

Depending on availability and the nature of the problem, yes. An urgent engagement starts with a half-day assessment to qualify the situation and immediate risks before any action on the system. This type of work is invoiced with a surcharge stated in the proposal.

Mainly Java and Spring Boot on the server side, Angular on the front end, and the industrialisation tooling around Docker, Kubernetes, Terraform and CI/CD pipelines. Application security, observability and generative AI use cases complete the picture. I tell you clearly when a topic falls outside my expertise and point you to a specialist rather than accepting work beyond my competence.

Yes, that is a common setup. I join your ceremonies, follow your conventions and contribute to code reviews like any team member. Technical disagreements are argued and documented, and arbitration always stays with your technical lead.

It begins with a half-day framing session to define scope, evaluation criteria and required access. Interviews and analysis take one to four weeks depending on size. The report is delivered to the person named during framing, and its distribution remains under your control.

No, and I say so when that is the case. A use case becomes credible when the need is repetitive, the underlying documents or data exist at sufficient quality, and a wrong answer remains recoverable. If the corpus is incomplete or errors are irreversible, an automated approach is unsuitable and I say so before any build starts.

I commit to deliverables, schedule and verifiable quality criteria, not to business effects that depend on factors beyond my work. For engagements with performance objectives, we define a baseline measurement before work starts and track its evolution throughout.

For some topics, yes: penetration testing, interface design or highly specialised expertise. In that case I present the proposed partners, their roles and costs before any commitment, and remain your single point of contact for coordination and final quality.

The projects, testimonials and figures shown on this site are demonstration samples intended to illustrate the working method; they do not correspond to real client engagements. During a conversation I can describe situations in detail while respecting confidentiality agreements, and introduce you to contacts who agree to be named.

The final weeks focus on handover: up-to-date documentation, review of open items, a transfer session with the team and a list of items to watch. If follow-up support is useful, it can take the form of a few days per quarter with no duration commitment.