# A $29 tool with a broken password field and no signup, 7% completion says it all

> The core flow collapsed at account creation. Users couldn't type into forms.

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

## The headline pattern: vague value, buried details

Across 12 AI user runs in the last 7 days, the average score landed at 39/100. Only 7 percent of simulated users completed the full flow. The recurring friction points tell a story of unclear messaging layered on top of a broken experience.

The hero copy promises to show you exactly where users quit, but doesn't say why that matters. Is it about speed to market? Conversion gains? Better retention? That ambiguity sent at least one user out the door. The 'Free Roast' CTA confused others: they assumed it meant a landing page review, not an actual signup flow test, and bounced before pricing clarified the gap.

When users did push forward, the pricing page introduced more friction. A strikethrough shows '$39 $29' with a qualifier: 'one-time per app Launch week.' No one knew if 'launch week' meant a calendar week, a rolling 7-day window, or something else. The discount deadline stayed fuzzy.

There's no changelog, no 'what changed' history. A footer copyright reading '© 2026' adds to the sense that no one has looked at this in a while. Worst: the note that roasts are public by default hid in fine print below the main CTA, exactly where users stop reading.

## Where the flow broke: password field failure, no accounts

The critical failure wasn't messaging. It was mechanics. There is no account creation flow anywhere on the site. Users navigated to what should have been a signup and found nothing.

When the product does ask for a password, the field refuses input. Seven different AI users hit this same wall. They tried once, tried twice, tried three or four times. Nothing worked. On the third failed attempt, most users invoked their abandon rule: if a basic form field doesn't work after two tries, the app is broken and I'm leaving.

One user mentioned verification never arrived. Another noted the password field couldn't be filled by any method. This wasn't a UX complaint, it was a blocker. The flow couldn't physically proceed.

## What to do: fix mechanics first, then clarity

Before rewriting copy or adjusting pricing terms, make the password field actually accept input. Test it. Make sure verification emails land. Add a visible account creation pathway, users should never wonder where to sign up.

Then define 'launch week' in plain terms. Explain what 'core flow' means. Surface the public-by-default roast policy above the fold, not beneath it. Add a changelog so users know whether this shipped yesterday or six months ago.

These are simulated AI users, not real people, but they're following real rules: stop at the third failure, assume silence means vagueness, bounce when the basic flow breaks.

Test your own signup at https://indiecru.sh/roast.

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