For funded founders building without a CTO

14 tech due diligence questions to answer before your next round

Ownership and people

  1. 1

    Who owns the code, the cloud accounts and the domains? Can you show it in writing?

    Strong answer: Everything sits in the company's name. Every contributor and agency has signed an IP assignment.

  2. 2

    What happens if your lead engineer or your agency is gone tomorrow?

    Strong answer: A written exit plan and shared ownership of every module.

  3. 3

    How long until a new engineer runs the product on their laptop?

    Strong answer: Under an hour. Longer is a bug.

Delivery and quality

  1. 4

    How long from a merged change to live in production?

    Strong answer: Minutes. Automated, no downtime, automatic rollback.

  2. 5

    Could you rebuild your infrastructure from code?

    Strong answer: Yes, in hours. Everything is defined and reviewed as code.

  3. 6

    What are your top five tech-debt items?

    Strong answer: A tracked list with owners. “We have none” ends a reviewer's trust.

  4. 7

    Can the platform handle ten times the users? Measured or assumed?

    Strong answer: A load test and a named bottleneck.

Security and resilience

  1. 8

    When did someone last try to break in on purpose?

    Strong answer: An external penetration test in the last twelve months.

  2. 9

    When did you last restore from a backup?

    Strong answer: A tested restore, with a recovery time in minutes.

  3. 10

    Which vendors can take your product down?

    Strong answer: A plan B for each, and the cost of switching.

AI in product and team

New on the list
  1. 11

    Who is accountable for the code your AI tools write?

    Strong answer: The engineer who submits it. Same review and tests as human code.

  2. 12

    What stops customer data or credentials from reaching an external model?

    Strong answer: A written AI policy and zero-retention plans.

  3. 13

    Do AI agents have access to production?

    Strong answer: No. Sandbox only, no production credentials.

  4. 14

    What happens when your AI provider changes its price or goes down?

    Strong answer: A fallback workflow and a human sign-off.

How to use this page

  1. 1

    Answer each in two sentences.

    If you can't, that is a gap.

  2. 2

    Gaps are expected.

    Not knowing them is the problem.

  3. 3

    Start with 1, 2 and 11.

    They take longest to fix.

Launching first? Run the production-readiness check.

Stuck on more than three?

30 minutes with Benjamin Heinke, founder of Cloudnonic. We show you where a reviewer would push.

CLOUDNONICCLOUDNONICCLOUDNONIC