Discover
Find product capabilities, plan facts and stated trial or contract limits.
SaaS
Make SaaS discovery and self-service agent-ready.
Test whether agents can find accurate product facts and navigate signup, docs and account recovery.
For self-service SaaS, product-led growth, developer tools, support and billing teams.
Test product understanding and account workflows together.
The audit checks stated commercial facts without requiring every SaaS company to publish pricing.
Answer from docs
Find a known answer and preserve the supporting source.
Start signup
Reach the public submission boundary without creating an unwanted account.
Onboard
Complete approved sandbox signup and onboarding with known fixtures.
Self-serve
Change reversible preferences and find plan-change or cancellation instructions.
Recover
Handle validation, MFA and expired sessions without entering an auth loop.
Keep website claims, docs and product UI consistent.
The run follows one question from discovery into the controlled product environment.
Sourced answer
The agent finds a current claim and cites the canonical supporting page.
Valid entry
Signup and authentication preserve intent, locale and approved account state.
Self-service assertion
The expected setting or instruction is present and independently verified.
SaaS friction often crosses team boundaries.
Split commercial facts
Marketing pages, help content and product UI describe different limits.
Ambiguous CTA
Trial, demo and account actions share labels without clear outcomes.
Authentication loop
MFA or session recovery returns the agent to the same blocked state.
Hidden self-service
Upgrade, downgrade or cancellation guidance cannot be found or verified.
Trace the cost of finding an answer and acting on it.
Evidence separates content discovery, authentication and product interaction time.
Session recording
Replay cited sources, signup boundaries, auth and self-service steps.
Completion time
Measure discovery, docs navigation, authentication and recovery separately.
CLS and target movement
Capture layout instability around signup, consent and account controls.
Source consistency
Compare claims across marketing, documentation, help and product surfaces.
Public mode stops before account creation or a commercial commitment.
Full onboarding and account changes require approved test tenants, credentials, redaction and explicit write permissions.
The audit maps both public content and agent-native interfaces.
Missing optional technology is reported as state, not treated as a blanket failure.
- Canonical product pages, docs and llms-full.txt
- SoftwareApplication structured data when appropriate
- Accessible forms, validation and authentication
- Session persistence, consent and account recovery
- OpenAPI, OAuth, MCP and WebMCP when present
- Prompt injection exposure and data boundaries
Teams receive one evidence chain across public and product surfaces.
- Discovery, docs and account task matrix
- Session recordings and source evidence
- Cross-surface content inconsistencies
- Authentication and recovery reproduction steps
- Engineering backlog with acceptance criteria
SaaS audit questions
Must a SaaS website publish pricing?
No. The audit checks the accuracy and discoverability of commercial information the company chooses to state.
Can authenticated product flows be tested?
Yes, with approved test tenants, accounts and scoped permissions.
Are documentation answers evaluated only by an LLM?
No. Source presence, content consistency and final-state assertions remain deterministic where possible.
Practical testing guide
Keep one SaaS account intent intact.
Build a repeatable scenario across product facts, signup, authentication, onboarding, permissions and self-service recovery.
Read the SaaS testing guideTest one SaaS journey across marketing, docs and product.
Apply with a discovery, onboarding or self-service workflow for a private partner review.