How I work
A clear process, before writing any code.
From the first call to production, every step is designed to reduce ambiguity, define responsibilities and build the right product with clear expectations on both sides.
Before we start
You know what we're building, why, and under which conditions.
Clear scope and priorities
We define what is actually needed and what stays outside the project.
Defined costs and timelines
You receive a concrete proposal before development starts.
Everything agreed in writing
Responsibilities and conditions are formalized to protect both sides.
No blind development and no surprises once the project has started.
Before starting
From the first contact to a defined project.
I don't start from a generic estimate. I first gather the context, identify the problem and define what actually makes sense to build.
01 — 05
Initial feasibility checked.
You briefly tell me about the project, the problem you want to solve and the context you're working in.
Problem and goals defined.
We have a roughly 30-minute call to go deeper into goals, processes, constraints, priorities and expectations.
Requirements and constraints collected.
When needed, I collect documentation, workflows, access, examples and additional requirements useful for designing the solution.
Clear technical and commercial proposal.
I define the proposed solution, scope, included functionality, expected timeline and related investment.
Agreement signed, project ready.
Before starting, we formalize the agreement. The contract clarifies commitments, responsibilities and conditions and protects both sides.
Everything in writing
A contract doesn't complicate the project. It makes it clearer.
It helps prevent misunderstandings and defines in advance what we can expect from each other. Its contents are adapted to the type of collaboration and the characteristics of the project.
What is included in the project and what stays outside it.
What will actually be developed and delivered.
Milestones, deadlines and dependencies required to meet them.
Fees, payment methods, deposits and agreed deadlines.
How new requests or functionality are handled during the project.
What I handle and which information or activities depend on the client.
Conditions regarding code, materials and rights to the completed work.
What happens after release and which support is included.
During the project
Development without the black box effect.
You don't have to wait weeks to find out what has been built. The project moves through verifiable stages, with updates and feedback throughout development.
We confirm the roadmap, priorities, access and everything required to start without unnecessary blockers.
I work independently on implementation, organizing the work into milestones and keeping relevant progress visible.
Features are reviewed, tested and checked against the agreed goals before release.
I handle release preparation, deployment and the checks required to bring the product into production.
Collaboration
Technical autonomy, transparent communication.
I independently handle the technical execution while keeping the client involved in decisions that materially affect the product, budget or priorities.
Milestones and updates make progress visible without turning the project into a black box until delivery.
If a request affects scope, timing or cost, we evaluate the impact before moving forward.
When several solutions are possible, I explain the alternatives, advantages, limitations and consequences to identify the best fit for the context.
Let's start
The first step is understanding the problem.
Book a free discovery call. Tell me what you want to build or improve and we'll evaluate the most sensible next step.