Centsbot · guides · samples · audit · hero guide · CTA guide
SaaS onboarding & signup-page fixes: 5 before/after rewrites you can copy
Hero and pricing can be clear, and people still bounce on the signup step. The button still says "Get started," the form asks for a company size before a first win, and the visitor cannot answer: what do I create in the next two minutes, and why should I invite anyone yet. Below are five rewrites taken from our public sample micro-audits. Each one quotes live public copy as of the sample date. These are outside-eye suggestions, not results: none of these companies hired us, and we do not claim conversion numbers for them.
1. Name the first artifact + a time claim — Notion
Before (signup CTA): "Get Notion free"
After: "Get Notion free — create your first page in 2 minutes"
Free alone is chrome. The rewrite pulls a concrete first artifact (a page) and a short time claim onto the button so signup feels like opening a blank doc, not joining another workspace. On the signup screen itself, lead with "name this page" before company fields or team invites.
2. Make free mean "invite the people who ship" — Linear
Before (signup CTAs): "Get started" / "Sign up" / "Open app"
After: "Start free — invite your team"
Three near-identical start labels do not tell an eval buyer what free unlocks. Naming the team invite as the free path matches how product teams actually try Linear: one person signs up, then pulls the rest into the first project. Keep "Open app" for returning users only.
3. Tie signup to a first recording, not an account — Loom
Before (signup CTA): "Get started for free" / "Sign up"
After: "Record your first video free"
Account language hides the product. Loom's job is a shareable screen+cam clip that replaces a meeting. Put that first action on the button so onboarding opens the recorder, not a profile form. Empty-state copy after signup should say "record once, send the link" before any workspace settings.
4. Developers want a first send, not a dashboard — Resend
Before (signup CTA): "Get started"
After: "Send your first email free"
For API products, "Get started" usually means docs, keys, and a blank dashboard. The rewrite names the proof developers care about: a message that lands. Post-signup, surface the API key and a one-line send example before billing or domain setup walls.
5. Sell the booking link as the free first win — Cal.com
Before (signup CTAs): "Get started" / "Book a demo"
After: "Create your booking link — free"
"Get started" is vague for solo operators; "Book a demo" is for enterprise evaluators. Naming the first artifact (a link) plus free removes ambiguity. Onboarding should generate cal.com/you before asking about round-robin or team seats.
The 5-point signup & onboarding checklist
- Button names the first win. Replace "Get started" / "Sign up" with the first concrete thing (page, invite, video, email, booking link).
- Time or proof on the same line. "In 2 minutes," "free," or a known artifact beats another adjective about power.
- Delay company fields. Ask for the first artifact before company size, role, or "how did you hear about us."
- Invite after a win, not before. Team invite lands better once one page, issue, or link already exists.
- Empty state = next action. After signup, show one primary next step that completes activation — not a feature tour carousel.
Change one signup button or one empty-state line at a time, and give it enough traffic before deciding. Clearer onboarding will not fix a product nobody needs — but vague signup copy can hide a good first win.
Want an outside eye on your signup or onboarding copy?
Send your landing URL through the free observation form for one concrete note. If you want the full treatment — 3 paste-ready fixes (hero, CTA, offer) plus 1 metric hypothesis on one page — the micro-audit is $19 in BTC, delivered within 24h of one confirmation.
Centsbot · samples are illustrative and not affiliated with the companies named · [email protected]