UX Microcopy Writing

What is UX microcopy writing?

UX microcopy writing is writing the small pieces of text inside a website or app that guide people through it: button labels, form hints, error messages, empty states, tooltips, onboarding steps and confirmations. Each piece is short, but together they decide whether people get through a sign-up, checkout or setup flow, or give up. Good microcopy is clear, specific and calm, and tells users exactly what to do next.

Who is UX microcopy writing for?

• SaaS teams whose onboarding or setup has a high drop-off rate
• Product teams launching new features or flows
• Ecommerce stores with checkout friction
• Designers and developers writing interface text themselves and wanting it reviewed
• Companies whose product voice varies from screen to screen

Why do small words matter so much?

Users don't read interfaces; they scan for the next step. When a button says "Submit" instead of "Create account", or an error says "Invalid input" instead of "Use at least 8 characters", people hesitate, guess or leave. Microcopy problems rarely show up in analytics as "bad copy". They show up as abandoned forms, support tickets and features nobody uses.

Examples of microcopy that works better

Element	Unclear	Clearer (illustrative)
Button	Submit	Start my free trial
Error	Invalid input	Enter a date in the format DD/MM/YYYY
Empty state	No data	No invoices yet. Create your first one in under a minute.
Confirmation	Success	Done. We've emailed your receipt to sam@example.com
Password hint	Password requirements not met	Add a number to make your password stronger

How I approach microcopy projects

1. Walk through the flows as a new user would, noting every point of confusion.
2. Map every string in the flow: labels, hints, errors, states and messages.
3. Rewrite for clarity first, then consistency, then voice.
4. Write for every state, including errors, loading, empty and success, not just the happy path.
5. Deliver in a usable format, such as a spreadsheet of strings or annotated screens your developers can work from.

What principles guide good microcopy?

• Say what happens next. Buttons describe the action, not the generic step.
• Explain errors and how to fix them. Never blame the user.
• Use the user's words, not internal feature names.
• Be consistent. If it's "workspace" in one place, it's "workspace" everywhere.
• Keep it short, but never at the cost of clarity.

Where should you start?

If you can't review everything at once, start with the flows that affect revenue and support load most: sign-up and onboarding, checkout or upgrade, and the most common error messages. These are the screens every user sees, so small improvements there reach the most people. Once the core flows are clear, a voice and tone guide keeps new features consistent as your team builds them.

Common microcopy problems I fix

• Generic buttons like "Submit", "OK" and "Continue" with no context
• Error messages written by developers for developers
• Empty states that show nothing instead of guiding the next step
• Onboarding that explains every feature instead of the first useful one
• Different names for the same thing across the product

For worked before-and-after versions of these, see UX microcopy examples that cut support tickets.

How much does UX microcopy writing cost?

UX microcopy writing starts from $399 for a defined flow, such as onboarding or checkout. Larger projects covering a whole product, or including a voice and tone guide, are quoted on scope. You get a fixed quote before any work starts.

Microcopy works best alongside clear marketing pages. See SaaS copywriting for the website side, read SaaS homepage copy tips, or start with a website copy audit if you're not sure where users get stuck.