Checklist
The SaaS launch checklist
A SaaS launch checklist is what to verify before real users and payments arrive. This one has 39 checks in 9 sections, and you can tick them here without an account.
Seed covers 24 of 39 out of the box, marked below. The rest are yours.
By Anton ShubinUpdated
A practical checklist, not legal, tax or security advice. Check what applies in your country.
39 items in 9 sections
Items marked “Built into Seed” come with Seed. The link shows how, and what you still set up yourself.
7 items
People and regulators read it against what your product really does, so a copied policy is worse than none.
Partly built into Seed The page is there; you rewrite it for your own data and services.
Official source: the GDPR on EUR-Lex
Terms set what you owe a customer and what you don't, before the first dispute does.
Partly built into Seed The page is there; the terms themselves are yours.
People have a right to a copy of their data, and a button answers that request in seconds.
Official source: the GDPR on EUR-Lex
A deleted account whose data lives on is a promise you broke without knowing it.
Partly built into Seed Backups still hold the data until they expire; say how long in your policy.
Official source: the GDPR on EUR-Lex
Your privacy policy must name them, and you answer for what they do with the data.
Official source: the GDPR on EUR-Lex
6 items
Live keys, webhooks and tax settings differ from test mode, and the first real customer shouldn't find out for you.
Cards expire every month, and without retries and a grace period you lose customers who meant to pay.
Selling abroad can make you liable for tax in your customers' countries from the first sale.
Partly built into Seed The billing guide covers a price's tax behaviour in Stripe; registering and filing are yours.
Official source: the EU VAT One Stop Shop
7 items
HSTS tells browsers never to try plain HTTP, so no one on the network can strip the encryption.
A content security policy stops most injected scripts from running, even when a bug lets one in.
A reused password is the most common way into an account, and two-factor authentication (2FA) closes it.
A secret in a repository's history stays readable to anyone who ever gets a copy.
Partly built into Seed The deploy reads secrets from an env file; making and guarding them is yours.
Most attacks use flaws already fixed upstream, in a version nobody installed.
Partly built into Seed Seed lists outdated packages; vulnerability alerts are yours to switch on.
3 items
A backup on the same server is gone with the server, and one you run by hand is skipped the week you need it.
Built into Seed It's off until you turn it on.
4 items
A launch day sends traffic in one burst, and you want to know the limit before it does.
4 items
A reply is often the first support request, and a no-reply address throws it away.
Partly built into Seed The sender is a setting; a mailbox that someone reads is yours.
3 items
Search engines, AI assistants and chat apps read these first, and a shared link without a card gets fewer clicks.
Without it, search engines show people the wrong language or treat translations as copies.
A budget stops a slow page from shipping, and Search Console tells you what search engines can't index.
Partly built into Seed The budget runs in CI; verifying the site in Search Console is yours.
1 item
Page views say people came; a funnel shows where they stop before signing up or paying.
Partly built into Seed The events are sent; you choose the goal and build the funnel.
4 items
A customer who can't reach anyone writes a review or a chargeback instead.
Partly built into Seed The contact links are a setting; answering is yours.
Support without one means reading the database by hand, with all the risk that brings.
A bare error page looks like the product is broken, and a helpful one sends people back to work.
Start your next SaaS with part of this list done
Seed is a free, MIT-licensed SaaS starter. The items marked “Built into Seed” come with it, so you start with fewer boxes to tick.