For founders shipping an AI-built product

Is your prototype ready for real users?

14 checks before you launch

Access and data

  1. 1

    Ready when: Every request is checked on the server, not just hidden in the interface.

  2. 2

    Ready when: In a secrets manager. None in the code, none in the browser.

  3. 3

    Ready when: Named people with two-factor login. No shared accounts.

When things break

  1. 4

    Ready when: An alert reaches you before a customer does.

  2. 5

    Ready when: One step back to the last version, in minutes.

  3. 6

    Ready when: Once, for real, and you timed it.

  4. 7

    Ready when: A clear message. No blank screen, no error code dump.

Load and cost

  1. 8

    Ready when: You ran a load test and know what breaks first.

  2. 9

    Ready when: You know the number, AI calls included.

  3. 10

    Ready when: Rate limits on your API and a spending cap with your AI provider.

The AI-built part

New on the list
  1. 11

    Ready when: Someone can explain every part that touches login, money or personal data.

  2. 12

    Ready when: The code is in your own repository and deploys to your own cloud account.

  3. 13

    Ready when: Automated tests on login, payment and the main flow, before every release.

  4. 14

    Ready when: AI output is treated as untrusted and checked before it acts.

Your answers stay in your browser.

How to use this page

  1. 1

    Tick what is true today.

    Not what is planned.

  2. 2

    Open on 1, 2 or 11? Fix before launch.

    These are the ones that end companies.

  3. 3

    The rest can follow.

    With a date next to each.

More than three open?

30 minutes with Benjamin Heinke, founder of Cloudnonic. We show you what to fix first and what can wait.

Raising soon? See the 14 tech due diligence questions.

CLOUDNONICCLOUDNONICCLOUDNONIC