The 8 Categories Every Launch Needs

If you've shipped more than one project, you already know this feeling. The product works. The UI looks good. You press deploy and something nags at you. What am I forgetting?

The answer is almost never the code. It's one of eight specific things that sit around the product. These are the categories that kill launches. Not the idea, not the features, not the engineering. The operational layer that nobody teaches and everyone skips.

Here is the complete map. If you can tick every box in every category, you're ready. If you can't, you already know where to look.

1. Brand

Brand is what people see in the first half-second. If your favicon is still the default template icon, if your OG image is a gray box, if your product name shows up with three different spellings across your site, that's a brand failure. It signals "not finished" before anyone reads a word.

What belongs in this category:

• Project name consistency (site, social, footer, email)
• A real logo, not placeholder text
• A favicon that isn't the framework default
• Tab and browser title (not "Untitled" or "localhost:3000")
• Social preview image (Open Graph, 1200x630)
• Metadata brand consistency across pages

2. Trust and Legal

This is the category that gets people in the most trouble. Stripe freezes accounts over missing policies. Apple rejects apps over broken privacy links. Customers bounce when a footer has no contact info. None of this is about actually being a lawyer. It's about having the pages exist, in the right places, with clear language.

What belongs in this category:

• About page (who is behind this)
• Contact page with a real email address
• Privacy policy
• Terms of service
• Refund policy (required if you take payments)
• Shipping policy (if you ship physical things)
• Support contact path that actually works
• Business or founder identity clarity

For the full breakdown of legal pages, see the legal pages every SaaS actually needs.

3. Discoverability

Search engines and AI answer engines can't share what they can't find. Most indie builders don't ship with a sitemap, leave a noindex tag from staging, or write a meta description that's just the page title duplicated. Three months later they wonder why Google hasn't indexed anything.

What belongs in this category:

• Unique page title per page
• Real meta description (not blank, not duplicated)
• A sitemap.xml
• A robots.txt that doesn't block the whole site
• Canonical URL basics
• No leftover noindex tags from development
• Structured data (JSON-LD) for at least the homepage
• Clean internal page structure
• Basic AI visibility setup (clear H1, structured content)

4. Conversion

This is the category most people think about as "marketing." It's not. It's the difference between a visitor who closes the tab in three seconds and a visitor who reads the next paragraph. Your hero has to say what this is and who it's for in under five seconds. Your CTA has to be obvious. Your pricing has to exist.

What belongs in this category:

• Hero clarity (what this is, who it's for)
• Value proposition in the first paragraph
• CTA clarity (one primary action, not ten)
• Pricing page if you charge anything
• Trust indicators visible above the fold
• Social proof where relevant
• Basic objection handling (FAQ or near it)
• Onboarding clarity (first action after signup is obvious)

5. Monetization

If your project takes money, this category is non-negotiable. The "checkout works on my machine" era ends the minute a stranger hands you a credit card. Check that your payment processor is fully onboarded, your refund logic is written down, your subscription lifecycle actually handles cancellations, and your purchase confirmation reaches the buyer.

What belongs in this category:

• Processor choice (Stripe, Paddle, Razorpay, LemonSqueezy)
• Full onboarding with the processor (not just API keys)
• Pricing model locked in
• Refund logic written down
• Subscription basics (if subscriptions)
• Purchase flow sanity-checked
• Delivery or confirmation flow after purchase

6. Analytics

The week after launch is the highest-traffic week your project will ever have relative to audience size. If you don't have analytics installed before you ship, that data is gone forever. You cannot get it back. This is the most expensive category to skip because you don't know what you're missing until you need it.

What belongs in this category:

• Analytics installed (Plausible, GA4, Fathom, Umami)
• Basic page view tracking working
• Conversion tracking for the main action (signup, purchase)
• Event tracking for key flows
• Revenue tracking (if relevant)

7. Launch Ops

The infrastructure layer. Custom domain, SSL, 404 page, release readiness. This is where you make sure the site actually loads over HTTPS without a certificate warning and that broken links don't dump users into a framework error page.

What belongs in this category:

• Custom domain (not a vercel.app or netlify.app URL)
• SSL working correctly
• Store assets ready (if mobile)
• Release readiness (no debug mode in production)
• Support route live
• 404 page that isn't the framework default
• Final launch review of everything above

8. Support

The category everyone remembers on launch day and forgets the day before. Where do users report bugs? How do they contact you? How do you collect feedback that actually reaches your inbox? If the answer is "I guess they can tweet at me," you're not ready.

What belongs in this category:

• Support email or contact route
• Feedback collection mechanism
• Bug report path
• Basic maintenance plan
• Internal source of truth for issues

Why these eight, and not more

You could slice this differently. You could have twenty categories. But the more categories you have, the less any single one means. Eight is the number where every category is distinct enough to be useful and narrow enough to be actionable.

If you're scoring yourself, you want to be strong in every category, not perfect in one and blank in another. A beautiful landing page with no analytics and no privacy policy is a launch failure in two categories. A fully legal-compliant project with a broken hero is a launch failure in one. Balance matters more than total.

What to do with this

Print it out. Or read it before your next deploy. Or use a tool that does this automatically for you, scoped to your specific project type and current stage, and tells you what matters now versus what can wait until next week.

That's what CalmLaunch does. 112 specific constants across these eight categories, adapted to fifteen project types, scored by how ready you actually are. The free plan covers three projects and never expires. Most solo founders never need anything else.