I’m validating a $29 prelaunch offer with a product test that actually passed

Yesterday I shared a product test where no user could create the first project. Today I want to show the other side: a test that passed.

I gave Modelence one target persona — an operations manager — and one task: build and verify a simple employee timesheet.

The synthetic user took 21 recorded steps. It reached the live app, clicked Clock in, clicked Clock out, and left a visible 21-second timesheet entry.

That final record was the pass condition. Generated code, a polished preview, or a successful click would not have been enough. The strongest evidence was that the live product changed state twice and left an inspectable outcome.

The report still recorded one friction: the run entered the live sandbox without a clear one-click publish path. It also states what was not assessed: code quality, security, production readiness, adoption, or persistence beyond the observed session.

This is what I want Menso to produce: not a guaranteed list of bugs, but an auditable answer to whether one target user completed one core outcome.

For August I’m testing a founder-led paid prelaunch round. My current working price is $29. This is separate from the $9.90 one-off product-test experiment I posted earlier.

If you would seriously consider using this before launch, DM me “TEST” with your product link and one core task. I’m counting qualified conversations, not likes.

Does $29 feel too low, fair, or too high for this level of evidence? What would need to be included for you to pay?