The Phoenux way
Phoenux writes the words inside the product, where a label or an error message decides whether someone finishes or gives up.
Content design is the practice of writing and structuring the words inside a product so people can complete the task in front of them.
Product language
The interface is mostly words
Strip out the layout and what remains is labels, buttons, headings, errors, and empty states. Those words carry more of the experience than the visual design does.
They are also usually written last, at speed, by whoever was closest to the ticket. That is why products end up with three names for the same object and an error message that tells the user nothing they can act on.
What we write
- 01
Labels & terminology
One name per thing, used everywhere. This sounds small and it is the single biggest source of avoidable confusion in most products.
- 02
Empty and error states
The moments where people are most likely to leave, and the ones most often left to a default string.
- 03
Onboarding and first run
The empty account on day one, written so the first useful action is obvious rather than described in a tour.
- 04
Terminology & localisation
A glossary the product is built against, structured so translation later does not require a rewrite.
In practice
What this looks like in real work
Akbar Khan Hospital
Community-focused healthcare system
For Akbar Khan Hospital, the users were often anxious, unfamiliar with medical terms, and making decisions for someone else. Phoenux rewrote the information hierarchy and the healthcare content around being understood quickly. The goal was never an impressive interface. It was making the next step feel obvious.
Read case study →
Foodics
Restaurant tech
For Foodics, scaling into MENA meant more than translation. Phoenux trained designers on the brand's tone and UX language in Arabic, and built an Arabic-first content approach rather than a translated afterthought. Localisation is a content design problem before it is a language problem.
Read case study →What you get
A content system your product, site, and support team can all speak from, so people finish the task in front of them.
- 01
A glossary: one name per thing, used everywhere
- 02
Empty, error, and CTA language written as designed screens
- 03
UX writing for the journeys that pay the bills
- 04
Tone and voice guardrails so the next feature does not invent a third personality
- 05
Handoff notes so engineering, marketing, and support stay aligned
Frequently asked questions
Is UX writing just marketing copy?+
No. UX writing is task language inside the product: labels, errors, empty states, guidance. Marketing pages are adjacent, not the same job.
Can this ship with product design?+
Yes. Best results when content and UI move together on the same journeys and the same reviews.
Do you write marketing website copy?+
Scoped marketing pages can be included when they are tied to product IA and offers. Phoenux is not a content-marketing agency for ongoing publishing.
What's slowing your product down? Tell us about your project
Tell us whether you're building or fixing, the journey that pays the bills, and what "better" means in a metric you already track. You'll get back a scope, a duration, and a cut list. Or an honest no.
Start Here. Make It Happen.
Got a challenge?
Bring it here.
No polished brief. No homework. Just tell us what you’re working on, and we’ll take it from there.
- 01
Give us the context
A name, a way to reach you, and whatever’s on your mind.
- 02
We’ll dig in
We’ll look at what you’ve shared and figure out what questions matter.
- 03
Let’s make a move
If there’s a fit, we’ll map out the smartest way forward.
Prefer email? hello@phoenux.design