AGENTIC AGENCY/ RESOURCES

Resources / Build & launch

Build & launchLaunch checklist11 MIN READ

20 checks before you launch a vibe-coded app

A pre-launch checklist for AI-assisted apps: security, reliability, usability, and ownership.

↓ Download guide Read online ↓

Free to read and download. No signup required.

/// THE_OUTCOME

Catch the important problems before you invite the first real users.

WHO THIS IS FOR

Indie builders, founders, and AI-assisted developers

/// THE_GUIDE

20 actionable checks.

Tick off each item as you work. Your progress is saved in this browser.

PART 01

Product and data

01. Validate the core taskCan a new user complete the main job from start to finish?
02. Confirm data ownershipKnow which database, service, or tenant owns every record.
03. Review privacy expectationsPublish accurate notices and collect only required data.
04. Separate development and productionNever test destructive changes against live users.
05. Create a restore planTest backup and recovery, not just backup creation.

PART 02

Security

06. Protect secretsMove API keys to server-side environment variables.
07. Audit authenticationTest account creation, sessions, reset flows, and logout.
08. Enforce authorizationCheck access per user and per resource on the server.
09. Validate inputsReject malformed, oversized, and unsupported requests.
10. Review dependenciesCheck known vulnerabilities and remove unused packages.

PART 03

Reliability

11. Test error statesShow clear messages for failures, offline mode, and timeouts.
12. Check performanceLoad-test the routes and queries that matter.
13. Add observabilityCapture errors, request context, and useful alerts.
14. Make deploys reversibleHave a rollback plan for broken releases.
15. Test across devicesVerify responsive layouts, keyboards, and browsers.

PART 04

Operations

16. Connect a real domainVerify DNS, HTTPS, and redirects.
17. Set sensible usage limitsPrevent runaway API spending and abusive requests.
18. Check accessibilityUse semantic labels, visible focus, and adequate contrast.
19. Test email flowsVerify delivery, links, sender reputation, and unsubscribe actions.
20. Write the support pathMake it easy for a real user to report an issue.

/// NEXT_STEPS

Useful work starts with clearer decisions.

Keep a copy of this guide or explore another resource.

↓ Download guide All resources →