# Free startup engineering checklists for decisions before and after launch

URL: https://pixelactstudio.com/resources

> Seven free startup engineering checklists: MVP readiness, AI-built app risk, security, scalability, tech debt, AI features, and choosing a dev partner.

Seven checklists, each answering one question startups worry about, such as what belongs in version one or what is likely to break in an app built fast with AI tools. Each one links to the related service if you want help with the gaps.

Pixelact's free startup engineering checklists answer seven questions founders and CTOs ask before and after launch: are we ready to build, what might break in an AI-built app, which security basics come first, will it hold up as usage grows, which tech debt to fix now, is an AI feature ready to ship, and how to choose a development partner. Each one explains why every check matters and ends with a way to score the result.

## Pages in this section

- [AI-built app risk checklist: is your app production ready?](https://pixelactstudio.com/resources/ai-built-app-risk-checklist): AI-built app risk checklist: 40 yes-or-no checks on secrets, authorization, input, migrations, monitoring, tests, and AI spend, plus what to fix first.
- [MVP readiness checklist: scope, data, team, and launch](https://pixelactstudio.com/resources/mvp-readiness-checklist): A 44-point MVP readiness checklist for funded founders: problem, scope, data, security basics, team, budget, and launch, plus which gaps to close first.
- [Startup security checklist: 43 SaaS security checks](https://pixelactstudio.com/resources/startup-security-checklist): Startup security checklist: 43 yes or no checks on access, secrets, tenancy, backups, and logging, with what to fix before a security questionnaire.
- [Web app performance and scalability checklist for SaaS](https://pixelactstudio.com/resources/performance-scalability-checklist): Web app performance and scalability checklist: 43 yes-or-no checks on Postgres, caching, jobs, Core Web Vitals, load tests, and cost, each with its risk.
- [Technical debt triage checklist: fix, schedule, or accept](https://pixelactstudio.com/resources/technical-debt-triage-checklist): A technical debt triage checklist: 42 checks that score debt by security, data, revenue, and speed risk, then sort each item into fix now, schedule, or accept.
- [AI feature readiness checklist: is it ready to ship?](https://pixelactstudio.com/resources/ai-feature-readiness-checklist): An AI feature readiness checklist: 44 yes-or-no checks on data boundaries, evals, human review, cost per task, and rollout, with the gaps that block launch.
- [Software development partner evaluation checklist: 43 checks](https://pixelactstudio.com/resources/software-partner-evaluation-checklist): Software development partner evaluation checklist: 43 checks on diagnosis, proof, team, engineering, ownership, contracts, and AI use, each with its reason.

## Frequently asked questions

### Are these startup engineering checklists free?

Yes. All seven checklists are free to read on this site without giving us an email address, so you can work through one in the browser or send the link to your team. Each shows the date it was last updated. If you want new checklists and articles as they come out, the [monthly newsletter](https://pixelactstudio.com/newsletter) sends them once a month.

### Which checklist should we start with?

Pick the one closest to the decision in front of you. Before a first build, use the [MVP readiness checklist](https://pixelactstudio.com/resources/mvp-readiness-checklist). If the product was built fast with AI tools, start with the [AI-built app risk checklist](https://pixelactstudio.com/resources/ai-built-app-risk-checklist). Before investors or enterprise buyers ask about security, use the [startup security checklist](https://pixelactstudio.com/resources/startup-security-checklist). When hiring outside help, use the [software partner evaluation checklist](https://pixelactstudio.com/resources/software-partner-evaluation-checklist).

### What should we do with the checks we miss?

Write each missed check down with the reason it matters to your product, then sort the list by the harm each gap could do. Your team can usually fix a short list itself. If the list is long, or nobody can tell whether a check passes, a fixed-fee [software audit](https://pixelactstudio.com/services/software-audits) reviews the code directly and ranks the fixes for you.