I built a $9.90 synthetic-user test for one core product flow
I am building Menso, a service that sends a synthetic target user through one core flow in your live product.
You provide a product link, a persona, and one task. Menso records the browser replay and the user's decisions, then I deliver screenshots and a prioritized friction report within 24 hours.
The latest test covered a first-project flow. Across eight included runs, one hit a circular empty-workspace setup path and seven surfaced the same permission error. No run created the project. I also excluded a ninth run with automation input anomalies and documented what the test did not reach.
Here is the full evidence-backed case, including the animated replay and report preview:
https://www.indiehackers.com/post/8-tests-2-blockers-0-projects-created-137a9fcbcd
For August I am testing a simple offer: $9.90 for one flow, one target user, and delivery within 24 hours.
I would value feedback on the offer itself: is the useful unit one flow, one persona, or one report?
I would keep the offer as one flow, but make the headline less about the report type and more about the decision it enables. Something like: find the first blocker before you spend another week building. The replay and screenshots make the finding tangible, but the buying reason is certainty about the next action. Do you see teams wanting this before a launch, after a funnel drop, or only once they already know something feels broken?
I agree — “synthetic-user report” describes the mechanism, while “find the first blocker before another week of building” describes the decision.
The strongest initial use case looks like pre-launch or immediately before a major release: the scope is clear, the cost of finding a blocker early is obvious, and the team can still act on it. A funnel drop is valuable too, but it needs analytics context before choosing the right flow.
I’m testing the pre-launch positioning first. What proof would make that promise credible to you before buying: a sample verdict, a redacted replay, or a concrete before/after case?
Excluding the ninth run instead of quietly folding it into the average is the detail that builds the most trust here, most usability-testing services would either hide the anomaly or smooth it into an aggregate score, and documenting what the test didn't reach is a stronger credibility signal than a clean 8/8 would've been.
On your actual question, I'd say the flow is the real unit, not the persona or the report. Reports and personas are just how the finding gets packaged and who's looking through it; the thing that actually has a fixed cost and a fixed "did it work or not" outcome is the flow itself. If you price per persona instead, you risk people treating it like a discount-multiplier ("test 3 personas for barely more"), when the actual value is catching a blocker like the permission error you found, which any persona running that same flow would've hit.
The fact that you’re testing the offer itself at $9.90 is interesting.
Have any buyers or prospects reacted differently to “one flow,” “one persona,” or “one report” yet, or is that the question you’re trying to get evidence on now?
That’s exactly the question I’m collecting evidence on now. I’m watching whether people respond more clearly to “one flow,” “one persona,” or “one report,” and I don’t have a strong conclusion yet. I’d be happy to come back and share what I learn once I have enough signal.
That’s helpful context. I appreciate you sharing what you’re testing and keeping the conclusion open until you have stronger signal.
I’d like to continue the conversation outside the thread. What’s the best email to reach you on?
Sure, my email address is siqli@menso.io
You can also follow me on X, my account is @MENSO_Liu
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.