Password field breaks the flow: 0% completion across 11 AI user runs

The Pattern: Form Failures Block Entry

Over the last 7 days, we ran 11 simulated AI users through 3 distinct products. The average score was 37 out of 100. Zero users completed the flow. The primary culprit: a password field that refuses input across multiple attempts.

This is not a niche edge case. Multiple users hit the exact same wall, they tried to enter a password, the field did not accept it, they tried again, and it still failed. By the third or fourth attempt, the users applied their abandon rules (two failed tries on the same step = leave) and left.

Where Users Gave Up: The Broken Form Field

Users reported the password field as unresponsive on step 4 of the flow. They tried typing, nothing registered. They tried again. Same result. A few users persisted into steps 5, 6, and 7 with the same action failing repeatedly, burning time and patience until they quit.

One user had a call in two minutes and did not have bandwidth to debug a form. Another noted they are a founder, not a QA engineer. All of them applied the same logic: if a basic signup field does not work after two attempts, the product is broken and not worth the friction.

A secondary issue emerged across the early flow: the product states 'No account needed' on the homepage, yet users expected and looked for an account creation entry point. The absence of a clear signup path, combined with the broken password field, created confusion about whether signup was even possible.

One user also reported a verification email that never arrived, extending the friction beyond the form itself.

What To Do

Test the password field in your signup flow immediately. Verify it accepts input across browsers and devices. If it is genuinely broken, fix it before users see it. If it works in your environment but fails for users, investigate the technical stack, JavaScript event listeners, form validation, browser compatibility.

Second, clarify the account creation path. If accounts are optional, say so plainly and show how to proceed without one. If they are required, make signup the obvious first step.

See the full roast and test your own flow at https://indiecru.sh/roast