Questions, answered
Frequently asked questions
Trailee is an early product in a category that needs evidence. Here is what we can say clearly today.
How is this different from scripted QA?+
Scripted QA checks whether a known sequence works technically. Trailee is being built to explore whether a first-time user can understand what to do and complete the flow.
How is this different from analytics or session replay?+
Analytics and replay explain behavior after real traffic reaches a product. Trailee is designed for controlled usability checks before a release or campaign sends more users into the flow.
Are the scouts real users?+
No. Scouts are autonomous browser-based testers following consistent behavioral profiles. Their findings are signals to inspect, not a substitute for claims made by real customers.
How is confidence calculated?+
The planned confidence model weighs repeated, reproducible friction across independent sessions and different profiles. A live report will explain the evidence behind the rating instead of presenting an unexplained score.
What happens when only one scout gets stuck?+
A single failure is not automatically treated as product friction. It is separated for review until the issue repeats, can be reproduced, or is confirmed by a human reviewer.
Can Trailee test authenticated products?+
Authenticated SaaS flows are planned for early access. Access requirements and test credentials will be agreed before a run; joining the waitlist never starts an automated session.
What kinds of flows can Trailee test?+
The initial focus is SaaS onboarding, signup, activation, checkout or upgrade, dashboard navigation, and feature discovery in web applications.
When will early access be available?+
Trailee has not launched yet. Join the waitlist to hear when early access opens and receive the early-joiner discount when paid plans become available.