The Phoenux way
Phoenux designs the screens people work in every day, including the states most teams never get around to.
Product interface design is the design of the screens people work in, together with the states a product enters when something is missing, slow, or wrong.
Designing reality
The happy path is the easy part
Most interface work covers the flow where every field is filled in and every request succeeds. Real users do not arrive there. They arrive with empty accounts, half-finished records, expired sessions, and a button their permissions will not let them press.
Those moments are where products lose people. They are also, almost always, designed last or not at all.
What we design
- 01
The core surfaces
The screens your users spend actual hours in, designed for repeated use rather than a first impression.
- 02
The state matrix
Empty, loading, partial, error, permission-blocked, and edge case. Every surface, every state, specified rather than left to the framework default.
- 03
Interaction detail
What happens on click, on failure, on retry, and on the second attempt. This is where most handoffs get vague and engineering guesses.
- 04
Handoff
Specs and components your engineers do not have to interpret, so the built version matches the designed one.
In practice
What this looks like in real work
Unlayer
No-code embeddable email design and template builder
For Unlayer, the problem was depth without chaos. An embed editor used at enterprise scale had to keep growing in capability without becoming unusable for the people who only needed the simple path.
Read case study →
Sendoso
Corporate gifting & B2B engagement platform
For Sendoso, creating a send was fragmented enough that people were cloning existing ones just to change a funding source. Phoenux consolidated it into a single guided flow covering recipients, gift, billing and source of funds, Salesforce linking, limits, and expiry, with required and optional settings clearly separated. Monthly active users rose 30%.
Read case study →What you get
A production-ready product foundation with complete states, robust interactions, and clear specifications your engineers can build against.
- 01
The core product surfaces designed for repeated daily use
- 02
A complete state matrix, including the states currently left to defaults
- 03
Interaction specifications covering failure and retry, not just success
- 04
Components and handoff your engineers can build against directly
- 05
A written list of the decisions we made and why, so future work stays consistent
Frequently asked questions
Do you design every screen, or just the important ones?+
Phoenux designs the surfaces that carry real usage and the patterns that let your team produce the rest consistently. Designing every screen individually is usually the wrong spend, because a documented pattern covers the long tail better than a bespoke layout does.
What does designing the states actually mean?+
It means specifying what the interface shows when there is no data, when data is loading, when only some of it arrives, when something fails, and when the user lacks permission. Phoenux treats these as designed screens rather than defaults, because they are where most support tickets originate.
Do you hand off to our engineers, or build it?+
Either, and the choice usually comes down to your team's capacity rather than capability. Phoenux produces specifications engineers can build directly against, or delivers a working build on the lightest honest stack.
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