Skip to content
CleanSofts AMHB

About

Behind CleanSofts AMHB, one engineer

CleanSofts AMHB is run by a single person: the one who answers you, designs the system and writes the code.

I am an independent software engineer. There is no salesperson, no intermediate project manager and no delivery team your file would be handed over to: you talk to the person doing the work. That is a constraint, since I only take on what I can see through; it is also what makes a commitment verifiable.

Background

I have been building software for almost 10 years — web applications, APIs and line-of-business tools, mainly for management control, finance, e-commerce and audio-visual rights industry. I have worked inside in-house teams as well as on taking over existing applications: that is what taught me how a system ages, and what an undocumented decision ends up costing.

I do not take on every engagement. A need that calls for a team of ten, a deadline that is already out of reach, a technology I do not practise: I say so at the first conversation, and point you to someone whose trade it is whenever I can. A badly started engagement costs more than a declined one.

View my interactive CV

How I work

  • Scope before building

    I start by understanding the business, then write down what the software must do and what it will not do. A written scope beats an optimistic quote.

  • Deliver in increments

    You see something running early, then regularly. Every increment ships with its tests, its documentation and its deployment pipeline.

  • Use the tooling, keep the judgement

    I rely on AI at every stage — scoping, audit, writing code. It widens what I can cover in a given time; it does not decide, and nothing ships that I have not reviewed.

  • Leave you self-sufficient

    The repository, the credentials and the documentation are yours from the first day to the last. I work to be replaceable, not indispensable.

What I commit to

  • You keep ownership

    Code, documentation and infrastructure belong to you. Nothing that ships depends on me to keep running.

  • A single point of contact

    The person who answers your first message is the one who scopes the work, builds it and puts it into production.

  • A stated workload

    I do not take on more engagements than I can carry. If a deadline becomes untenable, you hear about it before it is missed.

  • Continuity planned upfront

    Every engagement plans for what happens if I am no longer available: documentation kept current, shared credentials, handover to a third-party team made possible.

A project to scope?

Tell me about your context in a few lines: you will get an opinion, not a brochure.

Write to me