From the first question to a controlled position

Step 1: you call us

You tell us where the app stands and what it needs to support next: opening up, a contract, fundraising, compliance or a technical handover. We first locate the transition point: is the idea still being explored, or does the product now need to become transferable and predictable? You then give us read-only access to your app: an invitation on your platform or access to your GitHub repository, including projects built with Claude Code, Codex or Antigravity. We sign an NDA if you want. This first exchange is free, and sometimes it's enough: three pieces of advice occasionally settle the matter.

Step 2: we assess

The Scan takes 72 hours and covers four areas: security, control of components, maintainability and ability to scale. For the code, the Takeover Index scores 10 criteria out of 20. The report is readable by a decision-maker and usable by an engineer, with evidence, priorities and budget ranges. It usually recommends targeted work, and sometimes a rebuild. When everything is fine, it confirms that too.

Step 3: we carry out the priorities

The Production Upgrade runs the roadmap, workstream by workstream: address confirmed risks, migrate the components concerned, make the code maintainable and strengthen production. Each workstream has its price on the quote, you choose what we do and in what order. Your app stays online during the work: we operate on a copy and switch when everything is verified.

Step 4: you take back control

The handover of the keys, literally: your code in your repo, your access documented in your name, your backups running, and the handover doc for the next developer. You can continue with us, another team or internally. The ability to hand over the project is part of the expected result.

The rules of the game, in writing

• Read-only to start. Nothing gets modified without your written go-ahead.
• NDA on request. Your project stays your project.
• Data in Belgium, GDPR. Processed by the team at KERN-IT, a Belgian agency.
• Documented conclusion. Every recommendation points to a finding in the report and an estimated budget range.
• Written for humans. Reports and explanations in plain language. You understand what you pay for and why.
• AI-native and accountable. KERN-IT uses AI in its own process, with versioning, reviews, tests and acceptance criteria. The team remains responsible for the result.

Where to start

If your app exists and users are waiting: the Scan. If you're still building: the basics checklist and the free workshop put you on the right track, for free. If you are between those stages, read the six signals that make an audit useful.