Section

Method and guarantees

Code ownership, reversibility, timelines, adoption: the questions you ask when a software project has already let you down.

4 articles

The questions in this section are the ones you ask when a software project has already gone wrong. Who owns the code. What happens if the supplier disappears. How you take back control.

They all have a written answer, and that is the point: under French law, assignment of copyright is never presumed. A general formula such as "the client owns the code" is not enough — article L131-3 requires each assigned right to be mentioned distinctly.

This section also covers method in the plain sense: where to start, how to take stock of what already exists, and why connecting what works usually beats replacing everything.

Method and guarantees4 min readA first working version in a few weeks, not a yearHow long before an application built for your business is usable? The method that gets a first working version live in a few weeks, not after a year of specifications.ByJérôme KnopsRead the article
Method and guarantees5 min readWhy software projects go off the rails, and how to prevent itAn application project meant to take three months takes twelve, and the team won't use it. The five causes that keep coming back, and the safeguards to set before you sign.ByJérôme KnopsRead the article
Method and guarantees6 min readHow many tools are you actually running?Almost nobody can list every tool in their business from memory. How to take stock in half a day, and what the result tells you.ByJérôme KnopsRead the article
Method and guarantees6 min readWho owns the code of a custom application?Paying for development does not make you the owner of the code: the assignment must be in writing. Six questions to ask before signing.ByJérôme KnopsRead the article

Ask your questions before we talk budget.

Talk it through

Other sections