← All services

03 · UX Writing & Microcopy

Your product should sound like a person wrote it.

Onboarding, empty states, error messages, and CTAs that sound human and keep users moving.

For B2B SaaS teams whose product is confusing users or whose interface sounds nothing like the marketing site.

Book a call Get a microcopy audit

Trusted by teams at

Tide Jedox Teamwork Dentsu

The problem

The product is where trust is either kept or broken.

The interface sounds like it was written by a different company than the marketing site.

Error messages explain what went wrong to the system, not to the user.

Users abandon setup because the next step is not obvious.

Clear labels, concise instructions, useful error messages, consistent terminology. The product should not make users guess what to do next.

What you keep

Materials your team can use without us.

The engagement ends with a fixed flow and a guide that keeps the language consistent after we leave.

Microcopy audit

A review of a key flow, with every line that loses users flagged and explained.

Rewritten flow copy

Onboarding, upgrade, and error states rewritten to sound human and move users forward.

UX writing guideline

A short, practical guide so the language holds after the engagement ends.

How we build it

Four phases. No big reveals.

We test the current flow, find where it loses people, and fix the words that carry the weight.

Read: test the current flow. Find where users stop or get confused.
Map: identify every word the user sees in that flow.
Write: rewrite the copy. Cut anything that does not help the user take the next step.
Hand off: deliver the rewrite and the guideline so the team can apply it to future features.

When to call us

The moments this work pays for itself.

The "sound human" principle. Many B2B products sound institutional inside the product. Microcopy must sound like something a person would actually say out loud. When it does not, users mistrust it.

Before / after

The interface is a conversation.

The words in the product are the ones users see most often. They should read like a person wrote them.

Before

Error 403: Invalid input.

Tells the user nothing they can act on.

After

That email already has an account. Try logging in instead.

Explains the problem and the next step.

Before

No data.

A blank screen with no way forward.

After

No projects yet. Create your first one to see it here.

Explains what should be here and how to start.

One engagement

Onboarding that stopped confusing users.

Project management · Growth stage

The UI copy was technically correct and emotionally cold.

Situation Support tickets about onboarding were high. Users were dropping off before completing setup.

Diagnosis The UI copy was technically correct and emotionally cold. Users did not know why they were being asked for information.

What we did Microcopy audit, rewritten onboarding flow, UX writing guideline.

Onboarding completion up 34%. Support tickets about setup down 22%.

The microcopy audit alone paid for the engagement. Users stopped emailing support about things the UI should have told them.
VP of Customer Experience Project management tool

Fit

Who this is not for.

API documentation. We write for the end user, not the developer.
UI design. We fix the words inside the interface, not the layout.
Marketing copy only. We are looking at the product, not just the landing page.

Next step

Ready to fix the interface?

Book a 30-minute call. We will talk about your current product, where users get stuck, and whether we are the right fit.

hello@saaswords.co

Connect on LinkedIn