# A scheduling tool breaks its own signup flow: 0% completion, password field won't accept input

> Critical form failures and undefined terminology stopped every AI user before finishing signup.

Published 2026-07-23 · IndieCrush Insights · https://www.indiecru.sh/insights/2026-07-23
Based on 11 simulated AI user panel runs across 3 products over 7 days.

## The headline pattern: vague value, broken execution

Across 11 simulation runs of a scheduling tool over the last 7 days, no AI user reached the end of the signup flow. The average experience score was 37 out of 100. The breakdowns cluster into two categories: messaging that doesn't explain why someone should care, and a password field that refuses input, sometimes on the first try, sometimes repeatedly across multiple attempts.

This is not a soft friction problem. This is a blocker.

## Where users gave up

Every single AI user either abandoned the flow or hit the password field failure. The specific failures:

- The password input field would not accept typed characters. Eight separate users encountered this on steps 4 through 7 of the flow. Some retried once or twice; most gave up after the second failure, reasoning that if a basic form doesn't work, the whole product is broken.
- Two users never found a sign-up entry point at all. The site states 'No account needed' somewhere on-page, which created genuine confusion about whether creating an account was even possible.
- One user arrived at a URL roast tool instead of the expected flow, and did not hunt for the correct page.
- One verification email never arrived.
- One user ran out of time budget before completing the flow.

The messaging issues, vague 'core flow' terminology, buried privacy language, unclear pricing window definitions, were minor friction compared to the form itself being non-functional.

## What to do about it

Test the password field in your actual signup flow before tomorrow. This is not a 'nice to have.' Run a real user through the exact form in production right now. If they can't type a password on the first try, nothing else matters.

Second: clarify navigation. If account creation is required, make the entry point obvious. If it's not required, say so plainly and remove the confusion.

Third: fix the messaging. Explain what the tool does and why someone would pay for it, not the feature set alone.

These are simulated AI users, not real people, but the failures are real. https://indiecru.sh/roast

---
Generated from aggregate panel data. AI users are simulated personas, not real people; no tested product is named.