Blog & Insights

Someone built an app with an AI coding tool. What should IT check before it goes live?

Check six things before the business depends on it: the data, who can get in, where it runs, the code, whether anyone else can change it, and who owns it.

Check six things before the business depends on it: what data it touches, who can get in, where it runs, what the code is made of, whether anyone but its builder can change it, and who owns it from here. A working demo proves the idea is worth having. It does not show that the app is safe to connect to company data or that anyone can maintain it.

Go through the list with the person who built it. They know what the app is supposed to do, and they should hear what you find.

1. The data

  • List every kind of data the app reads or writes. You cannot protect what you have not listed.
  • Find where that data is stored. A database in the builder’s personal cloud account is company data outside the company.
  • Check whether real customer or employee data was used while it was being built. Test data that is real data counts as a copy you now have to account for.
  • Search the code and its history for passwords and API keys. A key written into the code is readable by anyone who can see the repository. Replace any you find.
  • Ask what was pasted into the AI tool during the build. Prompts often include real records or credentials, and the tool’s vendor now holds them.

2. Who can get in

  • Check how people sign in. A shared password or no login at all is common in a first version. It should use the company’s sign-in.
  • Check what each kind of user can see and do. A first version usually lets every user see everything.
  • Check whether the app or its database can be reached from the internet. A test address that was never taken down is a way in.
  • Find out who the administrators are. There should be more than one, and none of them should be a personal account.

3. Where it runs

  • Find out whose account hosts it and who pays for it. If the answer is the builder’s own card, the company does not control it.
  • Ask how it is backed up, and restore it once. A backup that has never been restored has not been tested.
  • Check whether there is a separate place to test changes. Changing the live app directly means every mistake reaches the users.
  • Check what is logged. When something goes wrong you will need to know who did what.

4. The code

  • Put the code in a repository the company controls. A copy on one laptop is one accident away from gone.
  • List the libraries it depends on and check them for known vulnerabilities. AI tools pull in whatever works, including old versions.
  • Check how it handles input from users. Unchecked input is how data gets read or changed by someone who should not have access.
  • Look for automated tests. If there are none, nobody can tell what a change will break.
  • Check the licenses of what it uses. Some open-source licenses carry conditions the company may not want.

5. Whether anyone else can change it

  • Ask the builder to explain how it works to someone who can read the code. If the explanation is “the AI wrote that part,” nobody understands that part.
  • Have a second person make a small change and release it. This is the quickest test of whether the app can be maintained.
  • Write down how to run it, release it and recover it. One page is enough to start.

6. Who owns it from here

  • Name an owner in the business and an owner in IT. The business owner decides what it should do, and IT is responsible for keeping it running safely.
  • Decide who fixes it when it breaks. The builder has another job.
  • Decide what happens if the builder leaves. An app only one person understands stops the day that person does.

If the app itself uses AI

  • List what the app sends to an AI model. Company data leaves your environment with every request.
  • Decide what happens when the model is wrong. For anything that reaches a customer or the books, a person should approve it first.
  • Log the requests and the answers. Without a record you cannot explain what the app did.

What the answers usually mean

Most apps come out in one of three places. Some need hardening: the idea and most of the code are sound, and the work is in sign-in, hosting, secrets and backups. Some need parts rebuilt, usually the data model or the parts that handle access. A few should be retired because a product you already own does the same job.

Keeping what is sound is normal. VisionLink Advisory Group came to us after it was unhappy with a previous development partner. In his review on Clutch, its president, Tom Miller, says the first work was to clean up and redo some of what the earlier developers had done, keeping what both sides agreed could be kept, before new development began. That code was not written with an AI tool. The decision about what to keep is the same one.

For the business owner’s side of this, see Before an AI-Built System Runs Your Business. If the app turns out to be a prototype, You built a prototype, not a product. That’s fine. covers what comes next.

Common questions

The app works. Why not just let people use it? Working on the builder’s laptop with a few users is a different test from running with company data, real traffic and nobody watching. The checks above take far less time than recovering from a leak or an outage.

Does AI-written code have to be thrown away? No. Much of it can be kept. The usual problems are in what surrounds the code: where secrets are stored, who can get in, where it is hosted, and whether anyone else understands it.

Who should do the review? Someone who did not build it and who can read the code. If nobody on your team can, an outside review is the right size of job for it.

What if the person who built it objects? Bring them in. They proved the idea was worth building, and they know what the app is supposed to do. The review is how their work gets to stay in use.

The vibe check, our System Evaluation for AI-built code, is the fixed-fee first step.

Related service: Project Rescue

More like this, in your inbox. Subscribe for our latest thinking, resources, and events.

Get started

Not sure where to start? Start here.