ACTIVATED HUMAN/ ai

Is your app ready for real customers?

Nine questions, each with a yes or a no. You do not need to read code to answer them. If you are not sure, the honest answer is no.

At the end you see which areas are covered and which are exposed, on this page. No email, no sign-up, nothing to unlock.

  1. 01 · Security · Sign-in and access
    Does every screen and every record check who is signed in and what they may reach?

    A sign-in on the front door is not enough. If the checks are missing underneath, anyone who knows the address can open what they should not.

  2. 02 · Security · Keys and secrets
    Are passwords, keys and other secrets kept out of the code and out of the browser?

    A key in the code or in the page can be read by anyone who looks, and it costs you whatever account it unlocks.

  3. 03 · Security · Patched dependencies
    Does someone find out when code you depend on has a known hole, and patch it?

    Most of an AI-built app is other people's code. Holes in it are published, and people go looking for apps that have not updated.

  4. 04 · Security · Abuse and runaway bills
    Are there limits on how often one person or script can use your app?

    Without limits, one script can empty an AI budget overnight or make the app unusable for everyone else.

  5. 05 · Reliability
    If your app or a service it depends on failed now, would it recover, and would you be told first?

    Every app depends on services that have bad days. What matters is whether it recovers, whether your data survives, and whether you hear first.

  6. 06 · Growth
    Do you know what gets slow, what falls over and what it costs when far more people show up?

    An app that works for ten people can slow down, fall over or run up a surprising bill for a thousand, and the first busy day is the wrong time to learn which.

  7. 07 · No regressions
    Before a change goes live, is it tested on the parts that make you money and reviewed, with an easy way back?

    Without that, fixing one thing can quietly break another, and the only way back is another fix.

  8. 08 · Edge cases
    When someone pays twice, stops halfway or sends the wrong thing, does the app cope without losing data or charging for nothing?

    Real people and real services misbehave. Each case the app does not handle is a support ticket, a refund or a lost customer.

  9. 09 · AI features
    If your product uses AI, are its answers checked against real cases on every change, and is its cost per use capped?

    A new prompt or model can make answers worse without a single error, and an AI feature with no limit can run up a bill overnight.

The six areas are the same ones we check in the first look, described on the home page under what ready for real customers means. More answers for founders building with AI are on the founders page.