Build update: Menso can now report a product pass, not only a blocker
Most of the Menso cases I have shared so far were blocker stories: a permission error, a setup loop, or a session handoff that prevented the user from reaching the product.
This week I forced myself to design the opposite verdict honestly: what evidence is strong enough to say a product passed?
The Modelence run gave me a useful test case:
- One operations-manager persona
- One concrete task
- 21 recorded steps
- One documented friction
- One completed live loop
The evaluator built a timesheet, entered the live app, clocked in, clocked out, and left a visible 21-second entry.
The report UI now separates Cover, Step Details, Journey & Conclusion, and Replay. That lets a founder trace the verdict back to the observed evidence instead of trusting a generated summary.
The other design decision I care about is the test boundary. The report explicitly says that this run did not assess code quality, security, production readiness, adoption, or persistence beyond the observed session.
My next August experiment is a founder-led paid prelaunch round. The current working price is $29. I’m looking for willingness-to-pay evidence, not just likes.
If you would try it, DM me “TEST” with your product link and the one core flow you need verified.
Which screen should a founder see first in a report like this: the verdict, the replay, or the step details?
