How do I test my signup flow before launch?

A signup check you can run today

1. Start where a stranger starts: signed out, in a private window, on the production address rather than staging.
2. Before the form: can someone tell what they get, what it costs and whether a card is needed, without opening the FAQ?
3. The button: does “Sign up” or “Get started” go straight to the form, or through a detour?
4. The form: ask only for what the first session needs. Every field has a visible label, and every error says exactly what to fix.
5. Passwords: are the rules shown before the first attempt, not after the error?
6. Verification: does the email arrive promptly, and does its link land you signed in on the same device?
7. Social sign-in: if you offer Google or another provider, do you end up with the same account as with email?
8. The first signed-in screen: does it tell a new user what to do next?
9. Coming back: log out, log in, mistype the password, reset it.
10. On a phone: do it all again at phone width.

Some of these are also what the persona in Menso's Sign up & log in template watches for: a senior product manager who expects an account to take two minutes, dislikes forms that ask for a phone number or company size first, and trusts validation messages that say exactly what to fix. The template does not test social sign-in, logging out and back in, password reset or phone-width layouts: web runs use a fixed desktop window.

What an AI user adds

• A first pass with no context. It has never seen your product, so it hesitates where a stranger might.
• Every step on the record. The replay shows what it saw, did and thought at each step, so a hesitation has a place you can point to.
• Your real signup, not a mock-up. It works on the live site with the email and password you put on the credentials card.
• The same task after a fix. Run the template again and compare the two replays and their TRACES scores.

Where it stops

• It has no inbox or phone of its own. A verification email pauses the run until you paste the code or link, for up to two hours; a phone or SMS code ends it.
• On the web app it signs up with email and password only. Google sign-in on your product works only in the Menso desktop app.
• Test only products you own or have permission to test, with an account made for testing: the AI user acts with the credentials you give it.
• One persona, one run. It shows one path through your signup, not how everyone moves through it.

Two real runs, and what they show

These public runs used Menso's Purchase intent template, not Sign up & log in: the AI user decided whether to sign up and stopped before any form. They show the step just before a signup form, where a visitor decides whether to start at all. One said yes; one said no after the usual pricing address returned a not-found page.

The board's review kept only two week-38 runs for citing, each with a qualification shown as its note, so n=2. Read them as examples, not as a rate. The Product Hunt board has the whole week.

Every run here used Menso's Purchase intent template: the persona Zainab Salazar, a freelance UX consultant, reads the homepage, the pricing page and the FAQ, decides whether she would buy or sign up, and stops before paying. It is a route-specific diagnostic, not a product-wide score.

Made one of these products? Write to support@menso.io and we will correct or remove the example as soon as we can.