The Phoenux way
Phoenux settles who the product is for, what it replaces, and why anyone would switch, before a single screen gets designed.
Product positioning is the decision about who a product is for, what it replaces, and why someone would change what they currently do.
Strategic alignment
If the team cannot say it, the site cannot sell it
The tell is easy to spot. Ask three people what the product does and you get three answers. The homepage explains features because nobody agreed on the value. Every new page restarts the same argument, and the argument gets settled by whoever is most senior in the room that day.
None of that is a copywriting problem. It is an unresolved decision, and design keeps paying for it.
What we do
- 01
Who it is for
The segment, and the difference between the person who buys and the person who uses. Those are often not the same, and the product usually only speaks to one.
- 02
What it replaces
The real alternative, including doing nothing. Most products lose to a spreadsheet and inertia rather than to a competitor.
- 03
Why anyone switches
The claim you can actually defend, separated from the ones you would like to make.
- 04
How it gets said
A message hierarchy, the proof behind each claim, and the terminology the whole product and site use consistently.
In practice
What this looks like in real work
Imgry
Marketing tech / creative tools
For Imgry, the market had tools that were either powerful or approachable, not both. Phoenux built a branding strategy and visual identity around being credibly professional and genuinely easy, because that gap was the position worth owning.
Read case study →
Akbar Khan Hospital
Community-focused healthcare system
For Akbar Khan Hospital, the brief arrived as "the website looks outdated." Phoenux changed the question to "what does this community actually need from the hospital," and that reframe redirected the whole project. Positioning is often the difference between redesigning a page and solving the problem.
Read case study →What you get
A clear messaging foundation your team can use across the product, site, and sales deck, so everyone knows what to say, what to prove, and what to leave out.
- 01
A written positioning statement your team can repeat without checking a doc
- 02
A message hierarchy: the one claim, the three supports, and the order they go in
- 03
A proof map tying each claim to evidence you actually have
- 04
Terminology your product, site, and sales deck all share
- 05
A list of what not to claim, and why leaving it out makes the rest credible
Frequently asked questions
Is positioning a marketing job or a design job?+
It is a product decision that both inherit. Phoenux runs positioning as part of design because the answer determines page structure, navigation labels, and what the interface emphasises, not just the words on the homepage.
We already have a positioning deck. Do we need this?+
Often not, and Phoenux will tell you if the existing one holds. The useful test is whether three people on your team describe the product the same way without looking it up. If they do, the deck is working and the money belongs elsewhere.
How long does positioning work take?+
Phoenux typically runs positioning in one to two weeks, usually alongside research rather than after it. The constraint is access to the people who know the customer, not the writing itself.
Can't get your team aligned on the product? Tell us about your project
Tell us what you sell and who keeps saying it differently. You will get back a position you can defend.
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