Your Signup Form Explains Your Password Rules. It Never Explains Why You Want My Phone Number.

Most signup forms have three lines people actually read: the headline, the field labels, and the button. Everything else is furniture.

When signups stall, teams rebuild the page — new hero, new layout, another social-proof strip — and leave those three lines untouched.

Here's the specific failure. Your form will explain your password policy in a red error message after someone fails. It will never explain why you want a phone number, a company size, or a job title. Rules explained late, requests explained never. That asymmetry is where signups go.

The three lines that decide whether anyone finishes

• The headline. Read before the form is scanned. "Create your free account" describes your database, not their outcome.
• Labels and helper text. These answer "why now?" A label that raises that question without answering it costs you the field — and sometimes the whole form.
• The button. The last thing read and the only thing clicked. "Submit" says nothing about the next screen.

Layout changes touch none of this. Copy does.

Clarity, trust, and feedback — applied to one form

Heuristics are useless as a checklist and useful as a lens:

• Clarity: if a field needs a tooltip to make sense, the label failed.
• Trust: every unexplained field reads as lead-gen. A phone number with an asterisk is the classic.
• Feedback: validation shown after submit punishes; validation shown before submit guides.
• Guidance: the button should name the next screen, not the current action.
• Hierarchy: one primary action per screen. "Sign up with Google" plus "Create account" plus "Talk to sales" is three primary actions.

Before/after: four rewrites you can ship today

1. The headline Before: "Create Your Free Account" After: "Set up your first alert in under 3 minutes" Why: it promises the first win. The account is the receipt, not the offer.

2. The unexplained field Before: Phone number * (placeholder +1 555 000 0000) After: Phone (optional) — we'll text you if a job fails overnight Why: it names the payoff and drops the requirement. If the number isn't used in the first session, deleting the field beats rewriting it.

3. The password rule Before, shown after failure: "Password must be 8+ characters and include one uppercase letter, one number, and one symbol." After, shown above the field: "8+ characters. Letters and numbers — no symbols needed." Why: rules belong before the field, not after the failure. And if your policy doesn't need symbols, stop making people guess them.

4. The button Before: "Submit" → After: "Create my workspace" Before: "Next" → After: "Add my first project" Why: the button is a promise about the next screen. "Next" promises nothing.

P0/P1/P2 for your signup form

P0 — Delete or justify every field you don't use in the first session. Phone, company size, "how did you hear about us." If it isn't used for login, alerts, or first-run setup, it's a tax. Keep it only with one line of "why."

P0 — Rename the submit button. One-line change, highest read count on the page.

P1 — Move password and format rules above their fields. Write that copy before the error state exists, then save the error state for actual errors.

P1 — Rewrite the headline to promise the first outcome, not the account.

P2 — Polish error tone and the success state. "Something went wrong" and a blank screen after submit undo good form copy.

Guessing which line leaks is expensive. Run a free audit on your signup flow and start with the field-level P0s — those get flagged first.

The 20-minute signup copy pass

1. Read the form top to bottom, out loud, as a stranger.
2. Circle every field you can't justify in one sentence.
3. Delete the circled fields, or add a one-line "why."
4. Rename the button to the title of the next screen.
5. Read your error messages as an annoyed person in a hurry. Rewrite the worst one.

Do this before you touch the layout. Most signup pages don't need a redesign — they need three lines rewritten. If you want the same treatment applied to onboarding and checkout, the blog has teardowns.

You don't need a new layout. You need the headline, the labels, and the button rewritten. Start a free FlowAudit and you'll get a prioritized P0/P1/P2 list for your own signup flow in minutes — field copy included.