The launch tooling stack
Chapter — the operations tooling a SaaS needs on day one, what to get free or open-source, and what to skip until it hurts.
Ship the product, then get hit by questions you have no tools for: where do feature requests go? where do bugs go? how does a user reach a human? You don't need a big stack — you need one analytics tool that does five jobs, a human-monitored inbox, and a place where bugs are written down.
The principle: integrated while small, standalone when it hurts
Early on, every tool is a surface to configure and a bill to remember. Favor one provider covering many jobs while volume is low, and keep exactly one thing standalone: the support inbox (a human reading mail — no SaaS needed). Graduate to dedicated tools only when a capability outgrows the bundle — and let usage data, not tool envy, make that call.
The checklist
| # | Capability | Why it matters on day one | Free / low-cost pick | Integrate or standalone |
|---|---|---|---|---|
| 1 | Product + web analytics | Know which pages convert and which features get used | PostHog free tier (1M events/mo) | Integrated (SDK) |
| 2 | Session replay | See the bug the user described in their words | PostHog replay (5k sessions/mo free, hard-stopped) | Integrated (same SDK) |
| 3 | Error / exception tracking | Users often won't report crashes; they just leave | Client: PostHog exception events + Error tracking. Server: your host's runtime logs; add Sentry free tier when volume justifies | Integrated (client); standalone (server, later) |
| 4 | Surveys — NPS / CSAT | The only honest "would you pay / would you recommend" signal | PostHog surveys (free) | Integrated (same SDK) |
| 5 | Feature request board | Turns "you should..." into a ranked list you can point at | PostHog hosted-link survey — no code at all. Alternatives: Featurebase free tier, Fider (self-host OSS), Canny ($$$) | Standalone URL (footer link) |
| 6 | Help desk / reach a human | One unanswerable email to a real address burns more trust than ten bugs | Shared inbox on your domain via email routing (Cloudflare/Resend) — $0. Add Crisp (free live chat) or Chatwoot (self-host OSS) when volume demands | Standalone by design |
| 7 | Knowledge base / docs | Deflects tickets before they exist; also your SEO surface | Fumadocs / Nextra / Docusaurus — static, self-hosted, $0 hosting | Integrated (own Next.js) |
| 8 | Transactional email | Signup, password reset, billing receipts must arrive | Resend free tier (3k emails/mo) | Integrated (API) |
| 9 | Lifecycle / onboarding email | Trials die quietly without nudges; winbacks recover them | Same provider as #8 + a cron | Integrated |
| 10 | Billing & subscriptions | The product must be able to charge | Clerk Billing (Stripe-powered) or Stripe + a meter | Integrated |
| 11 | Internal bug/task tracking | Bugs that aren't written down are wished away | GitHub Issues + Projects (free with the repo) or Linear free tier | Standalone (your repo) |
| 12 | Feature flags / A-B tests | Ship dark, flip gradually, roll back without a deploy | PostHog feature flags (free) | Integrated (same SDK) |
| 13 | Uptime monitoring + status page | You learn about downtime from users — or from a monitor | UptimeRobot / Better Stack free monitors; hosted status page free tiers | Standalone |
| 14 | Public changelog / announcements | "We ship every week" is retention; silence reads as abandonment | Featurebase free tier (also folds in #5), or a changelog route you own | Standalone or integrated route |
| 15 | Live chat widget | Human answer in 30 seconds converts trials | Crisp free / Chatwoot OSS | Standalone snippet |
| 16 | AI observability (if AI features) | LLM cost + latency + quality are invisible otherwise | Langfuse free tier / OSS | Integrated (API) |
| 17 | Community home | Where your ten first users talk to each other | Skool / Discord / r/YourSaaS | Standalone |
What we'd do in order (and did)
- Analytics first — one PostHog project covers #1, 2, 3-client, 4, 5, 12. Install once; every later decision gets evidence.
- The inbox and docs — costs $0 and answers 80% of day-one friction.
- Lifecycle email — set up before launch traffic, not after trials start dying.
- Only then dedicated tools — a status page when you have uptime worth reporting, a changelog when you have ships worth announcing, live chat when the inbox can't keep up.
Survey targeting: the gotcha that bites everyone
Surveys run per person, and a visitor on your marketing site is usually a different person than the same human logged into your app (anonymous ID vs. identified ID). Scope satisfaction surveys to the app host only via a URL condition — you want sentiment from activated users, not drive-by traffic — or your NPS popup will chase anonymous visitors around the marketing pages forever.
Where this ties into the product
This checklist is what SaaS Founder OS operationalizes: experiments and decisions logged with rationale (#11's discipline), economics that tell you when a paid tool earns its keep, and the playbook stage that forces the "go-to-market" answer before you build. The tooling is cheap; the habit of reading what it tells you is the product.