The Essential 5 Help Articles Every New SaaS Needs
Type: media · article
Stage: Stage 7: Support Proof
Difficulty: beginner
A founder doesn't need a massive knowledge base at Stage 7 — just the five articles that prevent the most obvious confusion. The Essential 5: Getting started, Account setup, Billing and subscriptions, Troubleshooting the most common error, How to contact support. Each article should answer one job. Bad title: 'Platform Configuration Overview.' Good title: 'How to connect your Stripe account.'
Overview
A founder does not need a massive knowledge base at Stage 7. They need the first five articles that prevent the most obvious confusion. Most early knowledge bases fail because founders try to document everything. That creates a graveyard of thin articles nobody reads. The better approach is to document the first five moments where customers are most likely to get stuck.
The Essential 5
1. **Getting started** — the first thing a new user should do
2. **Account setup** — connecting integrations, inviting teammates, verifying settings
3. **Billing and subscription questions** — what they're charged for, when, and how to manage it
4. **Troubleshooting the most common error** — the specific failure state most users hit
5. **How to contact support when self-service fails** — a clear escalation path
Each article should answer one job. Not five. Not the entire product. One job.
What a good help article includes
A good article has a plain-language title, a short answer first, screenshots or steps, expected outcome, and a fallback path if the user still cannot solve the issue.
Bad title: "Platform Configuration Overview"
Good title: "How to connect your Stripe account"
The beginner action
Create one article for each of the Essential 5. Then add a link to the most relevant article inside the product at the moment the user needs it. A knowledge base is not documentation for the founder. It is navigation for the customer.