Science of Apps - Launchpad · Checklist

SaaS audit checklist:
100 checks before you scale

A SaaS audit should check the whole customer journey: discoverability, the landing and pricing pages, trust and speed (Arrive); sign-up, sign-in and onboarding (Join); the home screen, core workflow, dashboards, navigation, copy and error states (Use); the paywall and checkout (Pay); notifications, account, settings and help (Stay); and accessibility and design on every screen. Then check activation, retention and revenue numbers.

By , FounderUpdated 12 min read

Share

Quick answer: What should a SaaS audit check?

  1. 100 checks organised by 22 areas and six stages: Arrive, Join, Use, Pay, Stay, Every screen.
  2. Mark each check pass or fail, with a screenshot or measurement as evidence.
  3. Speed and accessibility have published standards: web.dev thresholds and WCAG 2.2.
  4. Finish with a SaaS health check of activation, retention and revenue.
  5. Get the checks run free at baseline when you list on the Science of Apps Launchpad.

Key takeaways

  • Audit the journey in the order customers live it.
  • A failed check without evidence is an opinion.
  • Join and Pay are where SaaS revenue leaks most visibly.
  • Run the checks on a phone as well as a laptop.
  • Re-run the audit after fixes and before every growth push.

Before you pour money into ads, sales hires or a launch, check that the product can hold the people it's about to receive. A SaaS audit does that: it walks the journey a customer takes, from search result to renewal, and marks each step pass or fail with evidence. This SaaS audit checklist has 100 checks organised by the 22 areas of the Science of Apps product investigation, grouped into six stages, followed by a SaaS health check of the numbers. Standards were checked on web.dev, the W3C and Google's own pages on 18 November 2026. Jump to how to use it, the 100 checks or the health check.

Checks in this SaaS audit checklist
100
Areas, the same as the product investigation
22
Stages: Arrive, Join, Use, Pay, Stay, Every screen
6
Verdicts to give each failed check
5

How to use this SaaS audit checklist

StageAreasChecks
ArriveDiscoverability; landing page; pricing and plans; trust, privacy and security; speed and stability25
JoinSign up; sign in and recovery; onboarding15
UseHome; core task; dashboards; search and navigation; microcopy; empty, loading and error states27
PayPaywall and upgrade; checkout and payments10
StayNotifications; account; settings; help14
Every screenAccessibility (WCAG 2.2); visual design and consistency9
Bar chart: How to use this SaaS audit checklist — Arrive: 25; Join: 15; Use: 27; Pay: 10; Stay: 14; Every screen: 9.
How to use this SaaS audit checklist

Table: The SaaS audit checklist at a glance (areas from the Science of Apps product investigation, checked 18 Nov 2026)

Work through it in a clean browser with a new account, once on a laptop and once on a phone. For every failed check, save evidence (a screenshot or a measurement) and give it a verdict: Good, Needs improvement, Needs to be fixed, Critical or Recommendation. Then fix Critical first.

Arrive: checks 1–25

Discoverability: search, AI and social (5)

Checklist: Arrive: checks 1–25 — 1. Indexed; 2. Brand search; 3. Unique titles and descriptions; 4. Sitemap and robots.txt; 5. AI answers.
Arrive: checks 1–25
  • 1. Indexed — site:yourdomain in Google returns your key pages
  • 2. Brand search — searching your product name shows your site first
  • 3. Unique titles and descriptions — on every public page (Google's starter guide)
  • 4. Sitemap and robots.txt — present and not blocking pages you want found
  • 5. AI answers — ask three AI assistants about your category; note whether you appear

Landing page and entry point (6)

Checklist: Arrive: checks 1–25 — 6. Five-second test; 7. Primary CTA visible on mobile; 8. One primary action; 9. The real product shown; 10. Honest proof; 11. Promise matches the source.
Arrive: checks 1–25
  • 6. Five-second test — an outsider can say what you do and who it's for
  • 7. Primary CTA visible on mobile — without scrolling
  • 8. One primary action — not five competing buttons
  • 9. The real product shown — screens or a demo, not only illustrations
  • 10. Honest proof — customers, numbers or reviews you can stand behind
  • 11. Promise matches the source — the page repeats what the ad or post said

Pricing and plans (5)

Checklist: Arrive: checks 1–25 — 12. Prices visible; 13. Plans named for who they're for; 14. Free tier or trial explained; 15. Yearly toggle shows the saving; 16. Billing FAQ.
Arrive: checks 1–25
  • 12. Prices visible — for every self-serve plan
  • 13. Plans named for who they're for — not only Basic, Pro, Premium
  • 14. Free tier or trial explained — including what happens when it ends
  • 15. Yearly toggle shows the saving — both prices visible
  • 16. Billing FAQ — cancellation, refunds and taxes answered

Trust, privacy and security (5)

Checklist: Arrive: checks 1–25 — 17. HTTPS everywhere; 18. Privacy policy and terms; 19. Who you are; 20. Data handling explained; 21. Cookie choices respected.
Arrive: checks 1–25
  • 17. HTTPS everywhere — no mixed-content warnings
  • 18. Privacy policy and terms — linked from every page and current
  • 19. Who you are — company name, contact route and address where required
  • 20. Data handling explained — a security or trust page for B2B buyers
  • 21. Cookie choices respected — declining actually declines

Speed and stability (4)

  • 22. LCP 2.5 s or less — mobile, per web.dev
  • 23. INP 200 ms or less — taps respond quickly
  • 24. CLS 0.1 or less — nothing jumps while loading
  • 25. Third-party scripts audited — remove what you don't use; see our Core Web Vitals guide

Join: checks 26–40

Sign up (6)

  • 26. Minimal fields — email (or single sign-on) and little else
  • 27. Single sign-on offered — where your buyers expect it
  • 28. Password rules shown up front — not only after a failed attempt
  • 29. Inline validation — errors appear next to the field, as you type
  • 30. Works with a mobile keyboard — the right keyboard type; the button isn't hidden
  • 31. Verification email arrives — within a minute, with a resend link

Sign in and account recovery (4)

  • 32. Password reset works end to end — on a phone, from a fresh inbox
  • 33. Sensible session length — users aren't logged out mid-task
  • 34. Two-factor authentication available — expected by B2B buyers
  • 35. Clear sign-in errors — helpful without revealing which accounts exist

Onboarding (5)

  • 36. First value in one session — the user gets a real result before leaving
  • 37. Skippable tours — experienced users can get straight in
  • 38. Only necessary questions — each one changes what the user sees
  • 39. Progress shown — users know how many steps remain (goal-gradient effect)
  • 40. Templates or sample data — no blank canvas; see our SaaS onboarding audit

Use: checks 41–67

Home screen (4)

  • 41. Clear next action — the screen suggests what to do now
  • 42. What changed — recent activity or updates are visible
  • 43. Fits the role — different users see what matters to them
  • 44. No dead ends — every state leads somewhere

Core task flow (6)

  • 45. Five users, no help — target users complete the main job unaided
  • 46. Steps counted — no step you could remove
  • 47. Undo — for actions users regret
  • 48. Autosave — work survives a closed tab
  • 49. Confirmation for destructive actions — delete asks once, clearly
  • 50. Shortcuts for power users — keyboard or bulk actions where frequent

Dashboard and insights (4)

  • 51. Answers a question — each chart says what it shows and why it matters
  • 52. Sensible default range — the first view is useful without changing filters
  • 53. No-data states explained — new accounts see why it's empty
  • 54. Export — users can take their data out

Search and navigation (4)

  • 55. Labels in users' words — not internal team names
  • 56. Forgiving search — partial words and typos still find results
  • 57. Current location clear — users know where they are
  • 58. Consistent navigation — the same place on every screen

Content and microcopy (4)

  • 59. Plain language — no unexplained jargon
  • 60. Buttons say the outcome — "Create invoice", not "Submit"
  • 61. Consistent terms — one word for one thing
  • 62. Helpful tooltips — only where needed, not everywhere

Empty, loading and error states (5)

  • 63. Empty states teach — each one shows the next step
  • 64. Loading feedback — skeletons or progress for waits over a second
  • 65. Errors say what and how — what went wrong and how to fix it, in plain words
  • 66. Timeouts and offline handled — no silent failures
  • 67. A helpful 404 — with search or a way back

Pay: checks 68–77

Paywall and upgrade (5)

  • 68. Upgrade prompts at moments of value — not on the first screen
  • 69. Limits shown before they're hit — usage meters, not surprises
  • 70. Trial-end reminder — sent before the trial ends
  • 71. Plan comparison in the app — users don't have to leave to compare
  • 72. A fair downgrade path — easy to find and honest; see our paywall audit

Checkout and payments (5)

  • 73. Total shown before payment — including tax where it applies
  • 74. Local payment methods and currencies — for your main markets
  • 75. Clear card errors — say what to change
  • 76. Receipts and invoices — sent automatically and downloadable
  • 77. Failed-payment recovery — retries and reminder emails before cancellation

Stay: checks 78–91

Notifications and messaging (4)

  • 78. Opt-in with a reason — users know what they'll get
  • 79. Granular preferences — turn off one type without losing all
  • 80. Email authentication — Gmail's sender guidelines require SPF or DKIM for all senders, and SPF, DKIM and DMARC for bulk senders
  • 81. No notification spam — each message is useful

My account and profile (3)

  • 82. Edit email and profile — without contacting support
  • 83. Data export — users can download their data
  • 84. Account deletion — findable and clear about what happens

Settings and preferences (3)

  • 85. Grouped logically — users find a setting in one or two tries
  • 86. Save confirmation — changes are clearly saved
  • 87. Sensible defaults — most users never need to change them

Help and support (4)

  • 88. Help reachable in the app — from every screen
  • 89. Searchable docs — answers to the top ten questions
  • 90. Response time stated — users know when to expect a reply
  • 91. Status page — for outages and incidents

Every screen: checks 92–100

Accessibility to WCAG 2.2 (5)

  • 92. Text contrast — meets WCAG 2.2 AA
  • 93. Keyboard access — every action works without a mouse
  • 94. Visible focus — users can see where they are
  • 95. Labels and alt text — every field labelled; meaningful images described
  • 96. Target size — at least 24 by 24 CSS pixels (WCAG 2.2, SC 2.5.8, Level AA)

Visual design and consistency (4)

  • 97. Consistent components — one button style per role
  • 98. Type and spacing scale — consistent hierarchy across screens
  • 99. Works at 320 px — no sideways scrolling on small phones
  • 100. Themes consistent — dark mode, if offered, works on every screen

The SaaS health check: the numbers behind the checklist

The 100 checks find problems on screens. A SaaS health check shows which problems cost you most. Track these alongside the audit.

MetricQuestionPoints to stage
Visitor-to-sign-up rateDo visitors start?Arrive
Activation rateDo sign-ups reach first value?Join
Retention by cohortDo users come back?Use, Stay
Free or trial to paidDo users pay?Pay
Revenue churn and expansionDo customers stay and grow?Stay
Support tickets per customerWhere do users get stuck?Use, Help

Table: A SaaS health check to pair with the audit

A SaaS product audit, done for you

Science of Apps product investigation page with the headline Product intelligence that shows its work
The product investigation: the same 22 areas, with evidence for every finding.Image: Science of Apps · © Science of Apps · source

The Science of Apps Launchpad is a free, permanent listing for SaaS and other products, ranked by relevance, editorial picks and community interest, never payment. As your listing goes live, a free baseline diagnosis checks your landing page, discoverability and speed. The full product investigation is a SaaS product audit across the same 22 areas: 39 automatic measurements in a real browser on desktop and mobile, 74 expert checks on the screens behind your login, five verdicts, and an analyst's review before you see it.

  1. Arrive

    First impression

    Discoverability, landing page, pricing, trust and speed.

  2. Join

    The first minutes

    Sign up, sign in and recovery, onboarding.

  3. Use

    The everyday job

    Home, core task, dashboards, search, microcopy, empty and error states.

  4. Pay

    Value into revenue

    Paywall and upgrade, checkout and payments.

  5. Stay

    Coming back

    Notifications, account, settings, help.

  6. Every screen

    Throughout

    Accessibility to WCAG 2.2, visual design and consistency.

Your SaaS audit, in print

From checklist to action plan

List free, then order the report that fits your stage.

Economy

See what new customers see

  • Store listing and homepage, screen by screen
  • Scorecard against 60 Laws of UX
  • The fixes worth most
≈ 40 pagesDelivered within 3 hours
Most popular
Premium

The full diagnosis and the plan

  • Every screen, every finding, every flow
  • All 60 laws with evidence and fixes
  • 8 strategy chapters and a 90-day roadmap
≈ 95 pagesDelivered within 24 hours

Fact-checked against the evidence. Private by default.

A three-day audit plan

  1. Day 1

    Arrive and Join

    Checks 1–40 on a laptop and a phone; list on the Launchpad for the baseline diagnosis.

  2. Day 2

    Use, Pay and Stay

    Checks 41–91 with a fresh account; five users on the core task.

  3. Day 3

    Every screen and prioritise

    Checks 92–100; give every failure a verdict; plan the Critical fixes.

Mistakes when auditing a SaaS

  • Using your own admin account — test as a new user with no data
  • Skipping the phone pass — many checks fail only on small screens
  • Ticking without evidence — save a screenshot or a number for every failure
  • Auditing only the public site — most of the checklist sits behind the login
  • Fixing in list order — fix by verdict, Critical first

Ready to audit your SaaS?

How we know

The 22 areas and six stages come from launchpad.scienceofapps.com/investigate; speed thresholds from web.dev; the target-size rule from the W3C; email authentication from Gmail's sender guidelines; all read on 18 November 2026. The 100 checks are Science of Apps' editorial checklist, informed by Nielsen's heuristics and Google's SEO starter guide. Science of Apps runs the Launchpad.

Key terms, defined

  • SaaS audit: an evidence-based check of a software-as-a-service product across the customer journey.
  • SaaS health check: a review of activation, retention, conversion and revenue metrics.
  • Activation: the point where a new user first gets real value from the product.
  • Paywall: the point where the product asks a user to pay to continue or unlock more.
  • Dunning: the process of retrying failed payments and reminding customers to update them.
  • WCAG 2.2: the W3C's current Web Content Accessibility Guidelines.

Frequently asked questions

What should a SaaS audit check?

The whole customer journey: discoverability, landing page, pricing, trust and speed; sign-up, sign-in and onboarding; the home screen, core workflow, dashboards, navigation, microcopy and error states; the paywall and checkout; notifications, account, settings and help; and accessibility and visual consistency on every screen. Finish with a health check of activation, retention and revenue numbers.

What is a SaaS product audit?

A SaaS product audit is an evidence-based review of a software-as-a-service product from first visit to renewal. Each check is marked pass or fail with a screenshot or measurement, failures get a severity, and the result is a priority list of fixes. It differs from a financial or security audit, which look at accounts or infrastructure rather than the customer experience.

What's in a SaaS UX audit checklist?

A SaaS UX audit checklist covers usability of the screens and flows: sign-up and onboarding, the core workflow, navigation and search, copy, empty, loading and error states, and accessibility. This checklist adds the business-critical areas around it: discoverability, pricing, trust, speed, the paywall, checkout and retention features such as notifications and help.

What is a SaaS health check?

A SaaS health check looks at the numbers behind the product: activation rate, retention by cohort, conversion from trial or free to paid, revenue churn and expansion, and support volume. Pair it with the product checklist: the numbers show where the business is weak, and the checklist shows which screens cause it.

How long does a SaaS audit take?

A founder can run this 100-point checklist in two to three days for one product, including a phone pass and five user tests. A professional audit with measurements and an expert review takes longer by hand. On the Science of Apps Launchpad, the Economy report arrives within 3 hours and the Premium report within 24 hours.

How often should I audit my SaaS?

Before any major acquisition push, before fundraising, after big releases and redesigns, and at least once or twice a year. Many teams re-run a short version, such as speed, sign-up and the core task, every quarter, because releases often break things nobody tests again.

Sources

  1. Science of Apps — Product investigation: 22 areas (checked 18 Nov 2026)
  2. Science of Apps — Launchpad pricing: Economy and Premium reports (checked 18 Nov 2026)
  3. web.dev — Web Vitals (checked 18 Nov 2026)
  4. W3C — Understanding SC 2.5.8 Target Size (Minimum) (checked 18 Nov 2026)
  5. W3C — Web Content Accessibility Guidelines (WCAG) 2.2
  6. Gmail Help — Email sender guidelines (checked 18 Nov 2026)
  7. Nielsen Norman Group — 10 Usability Heuristics for User Interface Design
  8. Google Search Central — SEO Starter Guide
  9. Checked November 18, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

Launch day ends. Your listing shouldn't.

List free on the Science of Apps Launchpad: a baseline diagnosis of your landing page, discoverability and speed runs as you go live, and the product investigation runs checks like these across all 22 areas.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition