Custom applications · SMEs and independents · 25 years of experience

A problem
to solve?
An app
to build?

Either way, you deal with one person: the one who listens to you is the one who writes the code. I design and build your application, whether an internal tool or a service for your customers, and I stay with you from the first conversation all the way to production.

Let's talk about your project

30-minute call.
A straight answer, not a quote.

Where projects go off course

Never the same companies. Always the same pitfalls.

“We thought it would be simple”

An idea floated in a meeting. Three months of development later, the true scale sinks in. I assess the complexity beforehand, from the very first discussions, and I often suggest something simpler, or a solution that already exists.

“That's not what we asked for”

Misunderstandings are paid for at delivery. We write the specifications together and you approve them before the first line of code. On larger projects, we split the work into phases, with a review at each stage.

“Nobody dares touch the code anymore”

Delivered fast, impossible to change. I write code for whoever takes over the project three years from now, with automated tests that keep quality up as the application grows.

“So who looks after it now?”

The application is live and your team doesn't have the bandwidth to look after it. I take over maintenance: fixes, improvements, monitoring.

The journey

Five steps, one course

You always know where things stand and what comes next. Review points are there to correct course while it is still cheap to do so.

  1. 01

    Listening

    I take part in your thinking from the start. I assess how complex each request is and suggest alternatives. Sometimes the best solution is not to build anything.

  2. 02

    Specifications

    We pin down what will be built, in plain language. It is the document we both commit to.

  3. 03

    Development

    In phases on larger projects, with a review at the end of each phase to make sure we are still aligned.

  4. 04

    Testing & go-live

    Automated tests rather than manual checks. Go-live day is not supposed to be a stressful day.

  5. 05

    Maintenance (optional)

    If you have no one in-house to look after the application in production, I stay at the helm.

AI in the process

AI pulls the oars.
I hold the helm.

I use AI for design, for development, and in the final application when it adds real value. It produces fast, and that is precisely the risk: plausible code nobody reviews, an architecture that piles up, technical debt that stays invisible for six months.

This is where my 25 years count. I can tell what will hold up over time and what will break at the first change. The project does not drift, because someone experienced signs off on every decision.

Nothing ships unreviewed

I understand and approve every line before it reaches production.

Maintainable is a requirement

Your team must be able to take over the code. That is not negotiable, even under pressure.

Automated tests, every time

Quality does not depend on how careful anyone feels that day. It is checked with every change.

You keep ownership

The code is yours, documented, and can be taken over by anyone you choose.

You already have a prototype

Your prototype works.
The final version doesn't, yet.

You built something with AI. It runs, the demo is convincing, everyone believes in it. Then came the real rollout, and since then nothing has moved.

It is not a failure, it is the rule. A prototype quickly covers 80% of what you can see. The remaining 20% never shows in a demo, and it takes the most time, because it decides whether the application lasts.

The real path

80%

The visible features. The prototype covers them.

20%

Everything else, and most of the work.

What you see

What it costs

What that 20% contains

  • Security and data protection
  • Automated tests
  • Handling real-world load
  • Code your teams can take over
  • Day-to-day operations
  • Changes that don't break everything

We start with an assessment

I look at what you have built: what is solid and stays, what needs reworking, what is still missing. You leave with the key steps to production, whether or not you continue with me.

What staysWhat gets reworkedWhat is missingThe steps to production
Let's assess it

30 minutes on your prototype

Who you will work with

One point of contact.
Three roles, first-hand.

Developer, then technical team lead, then IT director. In SMEs and in an international group. I have led projects on the technical side and on the decision-making side, and I know how to translate one for the other.

The person who listens to you in meetings is the one who writes the code, and the one who maintains it. Nothing gets lost along the way.

25

years in IT,
from code to leadership

2

scales of company: SMEs
and a global group

1

point of contact, from first
conversation to production

[VOTRE PRÉNOM NOM]

Tell me
where you stand.

A day-to-day headache, a clear idea, a prototype that has stalled: in a 30-minute video call, you explain the situation and I tell you honestly what is feasible, and how complex it would be.

Book 30 minutes

Custom applications only: internal tools, business management software, services for your customers.

Or email me: contact@cap-appli.fr