/01.
From fractions to full ownership
Stake had already made property investing more accessible through fractional ownership. StakeOne was a different proposition: giving customers the chance to buy and own an entire property.
The business committed to it at a Product Council meeting, and it joined the roadmap as a new business line.
Buying a whole property is a much larger financial commitment than buying a fraction, and the process is more complex. The challenge was turning that proposition into a digital product while accounting for the real-world steps involved in buying property.

/02.
Making the vision tangible
The Head of Product first approached me to explore what StakeOne could look like.
There was no PRD or formal set of requirements at that point. We’d had some early conversations through user interviews, but most of the product experience was still open.
I started developing concepts and high-fidelity mobile screens to help communicate the vision to the wider Stake team and to investors. I deliberately built on Stake’s existing design system, so I could focus on how the product might work rather than jumping straight into a new visual identity.
Those concepts gave stakeholders something concrete to react to. After positive investor feedback and a full green light, StakeOne moved into a dedicated phase of product development.

/03.
From concept to dedicated squad
Once StakeOne moved forward, the Extend squad I was part of became the dedicated StakeOne squad, with a Product Manager and engineers. I stayed on as the product designer.
Our PM led most of the discovery, research and requirements work. I contributed to user interviews, competitor research and workshops, and mapped the high-level customer journeys with the squad.
Together we worked through the stages of buying and owning a property, what customers would need to understand at each one, and where the experience depended on other teams. My focus was turning those conversations into flows, prototypes and designs we could review and refine together.
/04.
The app was only one part of the experience
One of the biggest challenges was that not everything could happen inside the app.
Buying an entire property involved Sales, Real Estate, Operations and Finance. Some stages could be handled digitally, while others still needed manual coordination behind the scenes. We spent time with each team to understand their requirements, dependencies and the situations customers might run into.
That changed how we approached the experience. Rather than treating ownership as a simple checkout, we had to account for what happened before, during and after a reservation. For me, the challenge was making it feel clear and connected to the customer, even when parts of the process were happening elsewhere.
Making reservations and money understandable
A reservation wasn’t necessarily the same as confirmed ownership. We had to think about expressions of interest, reservations, allocation outcomes, financial commitments and what happened to customers’ money in different circumstances.
That meant being deliberate about payment breakdowns, confirmation messaging, reservation statuses and potential refunds, so customers knew what they were committing to and what would happen next.
Connecting digital and manual processes
Not every part of buying a property could be automated from day one. Documentation, verification and internal coordination all had to happen somewhere.
This raised practical questions. What should customers see while they wait? When do they need to act? When should they speak to someone from Sales? The product needed to support both self-service and human help.
Designing beyond the happy path
What if a property became unavailable? What if an allocation changed, a payment failed or a customer wanted to withdraw?
Customers were making significant financial decisions, so these scenarios mattered. We explored alternative states and flows to make the next steps clear when things didn’t go to plan.
/05.
Bringing the ownership journey together
As the product took shape, we worked across several connected parts of the experience.
Discovering the right property
Discovery had to help customers explore opportunities and understand what made each property relevant to them. We worked on listings, detailed property pages and ways to surface opportunities based on preferences and investment goals, giving enough information to evaluate a big purchase without overwhelming anyone.
Expressing interest and reserving
The reservation journey brought together some of the most complex requirements. Customers needed to understand the difference between expressing interest, reserving a property and progressing towards ownership, with the financial details and possible outcomes clear at each step.
Understanding what happens next
After a reservation, the experience had to explain what came next. Some steps depended on internal teams, so the app needed to accommodate waiting periods, changing statuses and assisted processes.
Moving towards ownership
The longer-term vision went beyond the purchase itself. We also explored how owners could view and manage their properties, and the information and services they might need after buying. These were concepts for later rather than part of the pre-launch.
/06.
Finding an identity of its own
At first, I assumed StakeOne could simply use the Stake design system. That made sense for the early concepts, but as the proposition became clearer I started exploring whether it needed its own identity.
Buying a whole property is a different experience from fractional investing. I wanted StakeOne to feel more premium and considered while staying connected to Stake. I explored a darker visual direction, early logo concepts and how the identity could extend beyond the app. One idea built the number 1 into the letter O, for owning one whole property.
The direction was well received by the founders and approved by the CTPO, and an external designer later refined the logo. The exploration also fed into early marketing, waitlist and presentation materials.
I wrote more about this in Creating the early brand identity for StakeOne.


/07.
From vision to private pre-launch
StakeOne went from exploratory concepts to a dedicated product initiative, reaching a private pre-launch in the UAE in October 2025.
Not every stage was automated, and pre-launch wasn’t the end of the product’s development. But it was an important step in turning a new business proposition into something customers could use.
- Developed early product concepts for internal and investor vision-building
- Continued as product designer when Extend became the dedicated StakeOne squad
- Contributed to discovery, journey mapping and defining the product experience
- Designed across property discovery, reservation and ownership journeys
- Explored the early brand direction that informed StakeOne’s identity
- Supported the product’s progression towards private pre-launch
/08.
What I took away
StakeOne reminded me that building a new product isn’t just about deciding what happens on screen.
The early concepts were relatively easy to explore. The harder work came once we understood the real processes behind buying a property and the different teams involved.
It also reinforced the value of designing before every requirement is defined. Those first explorations gave the team something to react to, while the later work meant revisiting assumptions and accounting for messier scenarios.
Looking back, the most valuable part was being involved in both stages: helping show what the product could become, then working with the squad to make it practical.