An AI readiness review of the tool, agent or app you built with AI, before more people rely on it

You or your team built it with Lovable, Replit, Cursor, Claude or similar, and people are starting to rely on it. I check who can see your customers' data, whether you own the accounts and could move off the platform, who would notice a mistake and, when there is AI inside, what it does on your real cases. Then I tell you in plain words whether it is ready and what to fix first. Whoever built it, or a developer, makes the fixes, so there is no repair work to sell you afterwards.

Dr Colin Kelly

PhD in NLP (Cambridge)

Former Head of Applied AI Research

Step 1 of the independent AI architect

Who the review is for

It is for an owner, MD or founder, often not technical, whose team built a business tool that people are starting to rely on, with or without AI inside.

The filter: it touches customer or client data, or it acts on the business's behalf, such as sending messages, booking, making payments or changing records. If it's a personal tool or a hobby project, the free check below is the right level.

What the review covers

Seven checks run on every review:

  1. 1

    Whether the keys that connect it to other services are hidden from visitors.

  2. 2

    Whether one customer can see, change or delete another customer's records.

  3. 3

    How customer data is deleted when someone asks.

  4. 4

    Whether you own the accounts and the data, and could export the data and move off the platform.

  5. 5

    How you would switch it off, and what happens when the platform or a provider changes or goes down.

  6. 6

    Whether you could trace what happened if a customer complained.

  7. 7

    Who in the business answers for it.

Five more run when there is AI inside it:

  1. 8

    Whether it gives the right answer on 20 of your real cases, plus 5 harder ones I write.

  2. 9

    Whether someone can type, paste or upload text that makes it ignore its instructions.

  3. 10

    What it can do on its own, and which actions need a person to confirm.

  4. 11

    Which customer data goes to which AI provider.

  5. 12

    Whether users know it is AI and can reach a person.

Three others run where they apply, for example when it searches stored documents or lets the public sign up. The checks are mapped to the OWASP Top 10 for LLM Applications and the UK Code of Practice for the Cyber Security of AI, to show which known risks each one looks at. That mapping is not a claim that it meets either.

What you get

A report of four to six pages, written so you can show it to a client or an IT team, and a 30-minute readout with you. Whoever built it, and a developer if you have one, are invited.

  • What it is now and what I could and couldn't access.
  • A verdict: Ready, Ready with conditions, or Not yet. It reports what I checked, on the cases you supplied, on the dates of the review.
  • The check table. Each finding has a severity and is marked Verified, Contradicted or Unverifiable.
  • A target sketch of what it should be, and the gap between the two.
  • The order of fixes, to hand over to whoever makes them, and what the review didn't cover.

What it isn't

Some people call this a pre-production audit: a fixed set of checks on it as it runs today. It is not a penetration test or a certification, and it gives no compliance or legal opinion, including on UK GDPR. The review leaves code and settings as they are, and there is no load testing. Nothing in the report guarantees that it is secure or accurate. If you need a penetration test, the report says so.

Price and how it works

$6,000 fixed, or $8,000 fixed when there is AI inside, for one tool, agent or app, one week. Larger scopes are priced before work starts. AI inside means the tool sends your data to an AI model, such as ChatGPT or Claude, to answer, decide or act. A tool built with Lovable, Cursor or similar that doesn't call a model when it runs is the $6,000 review. About three days of my time, or four with AI inside, are written into the engagement letter; if I use them up, I stop and report what I didn't reach. Half is paid on signing and half on delivery, whatever the findings. USD, plus VAT where it applies.

What I need from you

  • Read-only access to the code: the GitHub repository, or the project on the platform it was built on. Without it, the review runs from the outside and marks code-dependent findings Unverifiable.
  • A 30 to 45 minute walkthrough on your own screen.
  • Read-only access to the hosting, database, build tool project and AI provider settings, or a screen-share where read-only access isn't possible.
  • When there is AI inside, 20 real cases, each with the answer you would accept.
  • Two test accounts, so I can check one customer can't reach another's data.
  • Written permission to try to talk it into misbehaving, plus any data processing agreements and terms in force.

The free AI go/no-go check

Eleven plain questions about a tool, agent or app with AI inside. The full result, with questions for whoever built it, appears on this page with no email needed. It reports what you can show today, and can't tell you it will work.

  1. What will people rely on it for?
  2. How was this work done before the app?
  3. Who has said it works, and on what evidence?
  4. How many real cases has it handled, and did a person check them?
  5. When it gets something wrong, how would anyone notice?
  6. What can it do without a person approving it?
  7. What data does it read, and which accounts and services can it reach?
  8. Which AI provider and model does it rely on, and what happens if that changes?
  9. Who built it, who can change it, and what is written down?
  10. What does it cost to run now, and at full use?
  11. What does "live" mean for it: who, how many, and from when?
0 of 11 answered

When it leads to the architect

Where the fixes are a setting, a permission, a prompt, a log or a person checking, the review is the whole job.

If the fixes go deeper, such as redrawing the workflow or who can see what, moving off the platform or changing AI supplier, or there is no written design and you plan to keep building, the report says so. It offers the independent AI architect's design and business case (from $12,000, about two weeks) as the next step. The choice is yours.

FAQ

Is there an advisor who reviews AI-built apps before launch?

Agathon offers an independent AI readiness review of business tools, agents and apps built with AI tools, for non-technical owners and founders. I check the setup and, when there is AI inside, what it does on your real cases, then give a verdict and the order of fixes for whoever built it or a developer.

How much does an AI readiness review of an AI-built app cost?

Agathon's AI readiness review costs $6,000 fixed, or $8,000 fixed when the tool has AI inside, and takes one week for one tool, agent or app. AI inside means the tool sends your data to an AI model, such as ChatGPT or Claude, to answer, decide or act. Larger scopes are priced before work starts. Half is paid on signing and half on delivery, whatever the findings.

Is an AI readiness review a penetration test or a certification?

Agathon's AI readiness review is neither a penetration test nor a certification. It makes a few attempts to make the tool misbehave, with your written permission, through the inputs a real user could reach. If the tool needs a penetration test, the report says so.

What do I need to provide for an AI readiness review?

Agathon's AI readiness review needs read-only access to the code (on GitHub or the platform it was built on) and to the settings, a 30 to 45 minute walkthrough, two test accounts and, when there is AI inside, 20 real cases with the answers you would accept. Without the code, the review runs from the outside and marks code-dependent findings, such as whether a developer could take it over, as Unverifiable. Where settings access isn't possible, you can show me them on a screen-share instead, and the report marks those findings as seen rather than checked directly.

Will an AI readiness review fix the problems it finds?

Agathon's AI readiness review doesn't fix anything. Whoever built the tool or a developer makes the fixes, in the order the report gives, and is invited to the readout.

What happens if an AI readiness review finds an AI-built app needs redesigning?

Agathon's AI readiness review says so in the report when the app needs redesigning, and the next step is the independent AI architect's design and business case: from $12,000, about two weeks. That applies when the fixes go deeper, such as redrawing the workflow or who can see what, moving off the platform or changing AI supplier.

Is the free go/no-go check enough on its own?

Agathon's free go/no-go check tests nothing; it reports what you can show today, from your own answers. The AI readiness review tests the items your result marks Not shown yet, on your real cases.

Before more people rely on what you built

Tell me what it does, who relies on it and from when. I'll tell you quickly if it's not a fit.

The Agathon Briefing
A regular note with two or three thoughts on seeing the whole AI system clearly, people included, from someone who assesses those systems for a living. Written by hand, read in five minutes.
No more than one briefing a month