Skip to main content

S4. Choose your path

What this page helps you do​

Choose the app path that best matches what you are building.

Why it matters​

Different apps fail in different ways. A simple marketing site does not need the same launch checklist as an AI app with file uploads and background work.

You should already have​

  • a rough idea of what your app does

Skip this page if​

  • you already know your app path

Then jump to the page that fits:

What to do​

Choose the closest fit, not the perfect fit.

Pick P1 if​

  • the site is mostly public pages
  • there is little or no user data
  • there is no login

Pick P2 if​

  • users sign in
  • you store user data
  • the app feels like a normal web product

Pick P3 if​

  • the app depends on models, prompts, retrieval, or AI-generated output
  • costs, rate limits, and fallback behavior matter

Pick P4 if​

  • the tool is mainly for your team or a small known group
  • access control matters more than marketing polish

Pick P5 if​

  • the main thing you ship is an API or backend service
  • other apps or clients depend on it

If you are unsure, start with P2. SaaS web app path. It usually covers the common risks most builders miss.

Common mistakes​

  • choosing the simplest path because it feels less scary, even when login and data are involved
  • assuming an AI feature does not change launch risk
  • trying to follow two different paths equally

Next step​

Pick one:

Advanced notes​

If your app mixes categories, pick the path that carries the highest risk and then branch from there.