Find what's making your product hard to use.

Drop in a screenshot of any screen. Hayes brings in UX, accessibility and design specialists, names the principle behind every fix, then turns it into a plan and a PRD you can hand to Claude Code.

Describe it here for a free plan. Members drop in a screenshot and get the full review.

See a UX review ↓

Invite-only while I open it up in small batches.

Attached: signup.png. People start this signup and don't finish. What's wrong? You're asking for 12 things to do one job. Cut it to two and ask the rest later. Keep email and password. Move the rest to after signup. Put labels above the fields and errors next to each one. Track drop-off by field, not just signups. Saved to Signup redesign.

How it works

You bring the screen. Hayes brings the team.

  1. 01

    Show it or say it.

    Drop in a screenshot, or just describe the problem: "People start our signup and don't finish." No prompt engineering.

  2. 02

    Hayes picks the specialists.

    A confusing form goes to forms, accessibility and content design. A pricing question goes to positioning and metrics. You don't need to know who to ask.

  3. 03

    You get one ranked answer.

    What to fix first, the principle behind each fix, and how you'll know it worked. Where it's a judgment call, Hayes tells you a quick usability test would confirm it.

  4. 04

    Save it, then spec it.

    Keep it in a project so Hayes picks up the thread next time. When you're ready, turn it into a PRD for Claude Code.

What Hayes does

Three things Hayes is good at.

  • 01 · UX & design

    Find what's making a screen hard to use, and fix it for a reason.

    Drop in a screenshot and say what the screen is for. Hayes checks it against usability heuristics, WCAG 2.2, form and interaction guidance, content design and visual hierarchy, then ranks what to fix first. The biggest group on the team is UX and design.

    • Expert reviews against Nielsen's 10 heuristics
    • Accessibility barriers, with the WCAG criterion named
    • Forms, flows and error messages
    • Labels, empty states and calls to action
    • Hierarchy, spacing and consistency
    • Usability test plans you can run this week

    Hayes reviews the screenshots and text you give it. It doesn't crawl sites or open Figma files.

    See a signup review ↓

  • 02 · Strategy

    Make the product call.

    Positioning, pricing, metrics and funding. Hayes gives you a verdict, the reasoning and what to check next.

    See a real example ↓

  • 03 · AI-product PRDs

    Spec it for Claude Code.

    Turn a fix or a feature into a structured PRD, with acceptance checks and eval cases, exported ready for Claude Code.

Illustrative example

"People start our signup and don't finish."

A made-up trial signup for a project-tracking app, with the kind of problems most signup forms have. One screenshot and one line went in. Hayes brought in forms, accessibility, content design and research specialists, and came back with a ranked list of fixes, each tied to a named principle.

Illustrative, not a real customer. The form is invented; the review format is what members get.

signup-form.png

Attached: signup-form.png. People start this and don't finish.

  • UX review, done
  • interaction & forms, done
  • accessibility, done
  • content design, done
  • UX research, done

Mock signup form with 12 fields in two columns, placeholder-only labels, a distorted-text CAPTCHA and a small grey Submit button.

All seven fixes applied.

Three fixes matter most. Here's the principle behind each, and how you'll know it worked.

Fix first

  1. Fix 1.

    Critical (4).

    12 fields up front, including company size, phone, a 14-option role dropdown and "How did you hear about us?"

    Ask for email and password only. Ask role and company size after signup.

    Principles:
    • Hick's law
    • progressive disclosure
    • ask only what the task needs

  2. Fix 2.

    Critical (4).

    Placeholder text used as labels, in two columns. The labels vanish as you type.

    Put visible labels above each field, in one column.

    Principles:
    • WCAG 3.3.2 Labels or Instructions
    • single-column form guidance

  3. Fix 3.

    Critical (4).

    Errors appear all at once at the top, saying only "Invalid input."

    Check each field when people leave it, and put the error next to the field with how to fix it.

    Principles:
    • Nielsen heuristic 9
    • WCAG 3.3.1 Error Identification
    • WCAG 3.3.3 Error Suggestion

The ranking is an expert review. A five-person usability test would confirm the order.

What to measure after

  • Primary:

    Start-to-complete rate, and drop-off by field

  • Validation errors per submit

  • Time to complete

  • A five-person usability test, with the SEQ after the task

  • Guardrail: trial-to-activation shouldn't fall. It tells you asking less up front didn't bring in worse signups.

Saved to Signup redesign

Turn into PRD

One click for members: exports a PRD for Claude Code.

Saved in the Signup redesign project, ready to turn into a PRD.

A typical AI answer

Great question! Here are 10 best practices for high-converting signup forms:

  • Keep it short: only ask for what you really need…
  • Use clear labels so users know what to enter…
  • Optimize your CTA: try testing different button colors…

By following these best practices, you can create a better user experience.

The Hayes answer

Three fixes matter most. You're asking for 12 things to do one job, the labels vanish as people type, and "Invalid input" doesn't say what's wrong.

  1. Cut to email and password and ask the rest after signup.

    Principles:
    • Hick's law
    • progressive disclosure

  2. Put labels above the fields, in one column.

    Principles:
    • WCAG 3.3.2

  3. Show each error next to its field, with how to fix it.

    Principles:
    • heuristic 9
    • WCAG 3.3.3

Then watch drop-off by field. A five-person usability test would confirm the order.

Here's the full review: seven fixes, ranked →
Same screenshot. One gives you a checklist. One tells you what to fix first, and why.

Not another chat window.

  • It remembers what you've worked out.

    Most AI chats start from scratch every time. Hayes checks your saved projects first and tells you when it's building on a review or decision you already made.

  • A UX team behind every answer, not one generalist guessing.

    63 specialists, including 13 dedicated to UX and design: accessibility, interaction, content and research. Hayes brings in only the ones your question needs, then pulls their thinking into one answer.

  • Every fix names the principle behind it.

    Not "make it cleaner." Hayes tells you which usability heuristic or WCAG success criterion a problem breaks, so you can check it yourself and defend it in a design review. No filler, and if your plan has a hole in it, Hayes says so.

How Hayes talks

Like a colleague who's on your side.

Hayes is easygoing and direct. It'll tell you plainly when an idea has a hole in it, including when the problem isn't the design. It says "I don't know" instead of guessing, and it doesn't pad an answer to look thorough.

  • We looked at this in your Signup redesign project last month. Picking up from there.

  • Honest take: the form isn't too long because of design. It's too long because sales wants the phone number. Let's talk about that.

  • I can't measure contrast from a screenshot. That button looks low, so check it against WCAG 1.4.3 before you ship.

Prefer to listen? Turn on voice and Hayes reads its answers aloud.

Built and used daily

Built by Aaron Dence. In daily use since March 2026.

I built Hayes for my own research, and I use it every day on real client and product work before opening it to anyone else. A few things it has done for me:

  • Decided whether HelloAlfie should raise $500K or bootstrap
  • Helped a friend plan recruitment for a leadership course
  • Turned rough notes into Jira tickets
How I built Hayes

Strategy, too: a real example

"Should I raise $500K or bootstrap?"

I was deciding how to fund HelloAlfie, a scheduling app I'm building. Hayes brought in market sizing, positioning, product architecture, growth and metrics specialists.

The verdict

Don't raise yet. Bootstrap for 90 days, pass three gates, then raise from strength.

See the 8-part report
  • market sizing, done
  • positioning, done
  • product architecture, done
  • growth, done
  • metrics, done
The beachhead
Boutique professional-services agencies, 5 to 50 people.
The north-star metric
Meetings successfully booked per week, with a checklist for product-market fit.
The scope
What a $0 MVP builds, and what $500K would speed up.

Saved to Alfie Research

Want in early?

I'm letting people in a few at a time so I can listen closely. Tell Hayes a bit about you and you'll hear back personally.

Hayes

Step 1 of 3

A sentence is plenty. Real problems get priority.