What happens to your application if the tool that created it disappears?

Platforms closing, prices tripling, acquisitions: the scenario deserves a rehearsal before you choose. Two assets determine what happens next: your code and your specification. The exit test comes down to three questions.

If the tool that built your application closed tomorrow, two assets would determine what happens next: standard-format code and a human-readable specification. With both in your possession, a provider can take over within days. Without them, you buy your product again at the new-build price: an agency median of €30,000.

The exit test in three questions

Ask your tool these three questions before depending on it. One: can you download all the code today without contacting support? Two: does that code run outside the platform on ordinary hosting? Three: does a readable document describe what the application does, its rules and exceptions? Three yeses: you are an owner. One no: you are a tenant, and the lease is renegotiated without you. Ask these questions in writing; a salesperson's spoken answer commits them to nothing.

Why code alone is not enough

A retrieved code folder without a document explaining it resembles a house without plans: it stands, and the next tradesperson probes it blindly. Whoever takes over must infer your business rules from the lines and will miss some. Approved specifications, the brief, rules and success criteria, make code replaceable: they let someone audit, evolve or rebuild it elsewhere. As we wrote in an earlier article: code is an interpretation; your specification is the score.

Closed platforms: a long-term bet

An application built in a hosted no-code editor lives with its vendor: without code export, the exit question is settled in advance, against you. The bet may hold while the tool prospers; an acquisition, tripled price or closure brings it back at the worst moment. AI generation tools differ on the same criterion: some produce standard code you take away; others keep the project in their cloud. The same questions also apply to a human provider: a freelancer keeping the repository on their side reproduces platform dependence on a smaller scale.

How Maestro makes itself replaceable

A Maestro project is a folder on your machine: code in standard web technologies, French documents alongside it, brief, requirements, rules, and versions retained through a proven archiving system. The test takes thirty seconds: open the folder without launching Maestro; everything is there. The specification follows the same route: every approved document goes into the project folder, dated, in its current version. We insist that you can leave the tool; that is the only honest guarantee a vendor can give, and it applies to us as to others.

What to demand, wherever you build

Before choosing a tool or provider, run the three-question test in writing. Add one requirement: every important product decision must exist in a document you can read, correct and take away. When the tool disappears, changes its price or stops suiting you, that document and your code make the difference between moving and starting from zero, at the €30,000 median for new agency development.