Back to Works

Estater Markets

RoleLead Product Designer
/
CompanyEstater
/
Year2022 – 2024
/
ScopeStrategy · UX · UI · Data Visualization

Led the end-to-end transformation of a legacy reporting product into a modern self-serve analytics platform — serving banks, ministries, valuators, brokers, and developers across the Gulf.

50+Enterprise clients across the Gulf
5User segments served from one platform
End-to-endStrategy · UX · UI · data-viz
2022–24First in-house designer, full ownership
Estater Markets — case study cover
01 — Context

A reporting tool masquerading as a platform

When I joined Estater in 2022, Markets was primarily a static reporting tool. Users selected a report type, applied filters, and viewed tables and charts. The experience functioned more like a PDF on a screen than a modern analytics platform — capable on the surface, but fundamentally passive underneath.

For enterprise users making high-value investment, regulatory, and development decisions, the product created friction at every stage of their workflow — and had no room to grow with their needs.

02 — The Problem

Six constraints. One pattern: the product worked against its users.

Each limitation compounded the others. For enterprises making high-stakes financial and planning decisions, the accumulated friction wasn't an inconvenience — it was a blocker.

Static report-first workflowUsers were locked into a fixed sequence: select a report type, apply filters, view output. No ability to explore freely or deviate from the preset path.
Data trapped in tablesReal estate is inherently geographic, but location lived only as rows and columns. There was no map and no spatial context — users had to picture the geography in their heads.
A flat, confusing filter modelFilters were presented as one undifferentiated list, so users could never tell what was applied globally versus to a single view — the product's single biggest source of support requests.
One rigid path for five very different usersBanks, ministries, valuators, brokers, and developers each came with different goals, but the product offered all of them the same fixed workflow — serving none of them well.
No self-serve — everything waited on engineeringAny new report type or view had to be scoped and built by the engineering team. Power users couldn't answer their own questions without filing a request.
Passive by designThe product could display data but not help users interrogate it. It behaved like a PDF on a screen — capable on the surface, with no room to explore, compare, or grow with the user's needs.
03 — My Role

First in-house designer. Full product ownership.

I joined as the sole product designer — which meant not just designing screens, but defining what the product should become, coordinating directly with engineering, and eventually building the internal design function as the company scaled.

04 — Product Strategy

The reframe that unlocked everything

Rather than proposing UI improvements to the existing structure, I made the case for a more fundamental repositioning of the product — one that redefined what Markets was for, not just how it looked.

This repositioning was the decision that made every other solution possible. Without reframing the product's purpose, the dual-mode layout, spatial intelligence, and self-serve sandboxing would never have been scoped or approved. The strategy didn't just change the design direction — it changed the product roadmap.

The Decision I Owned

The easy path was to polish the existing screens. Instead — as the first and only designer, with no PM buffer — I made the case to leadership and engineering to reposition Markets from a report viewer into an intelligence workspace. That reframe is what put the dual-mode layout, spatial intelligence, and self-serve sandbox on the roadmap at all.

05 — Key Design Solutions

Four interventions that changed how users access intelligence

SOLUTION A

Map + Panel Dual Workspace

Introduced a flexible, toggleable layout system with three working modes — Map Only for geographic exploration, Panel Only for data-heavy review, and Split View for both simultaneously. Users could shift between modes based on the task at hand, rather than adapting to a fixed interface.

↑ Dramatically improved usability across all user types and tasks
Project screen
SOLUTION B

Interactive Spatial Intelligence

Added a full map-driven workflow with configurable data layers — heatmaps for transaction density, zoning overlays for regulatory context, geographic market views for macro analysis, and location-based drill-down for site-specific research. This transformed passive consumption into active geographic decision-making.

↑ Location-first workflows that were previously impossible
Project screen
SOLUTION C

Two-Tier Filter Architecture

Redesigned the filtering system from a flat, confusing model into two clearly scoped tiers. Separating global from contextual filters eliminated the core usability failure of the original system — users always knew what was applied and why.

~35% reduction in filter-related support requests post-launch
Project screen
SOLUTION D

Self-Serve Sandbox Reporting

After the initial redesign gained strong adoption, Markets evolved further into a sandbox model — giving advanced users the ability to build custom studies, configure their own report logic, use prebuilt templates, and generate on-demand insights without waiting for preset reports.

68% of enterprise accounts adopted sandbox within 6 months
Project screen
06 — Business Impact

From product improvement to revenue growth driver

The redesign was well received by users across all five enterprise segments — and directly contributed to measurable product and business growth.

Faster insight generation vs. previous baseline
68%Sandbox adoption among enterprise accounts (6 mo.)
Enterprise contract renewals post-redesign
5Enterprise segments served from one unified platform
Increased sales velocity after redesign rollout

Enterprise sales cycles shortened as the platform's differentiated capabilities became demonstrably clearer during procurement evaluations and demos. The intelligence workspace framing gave the sales team a stronger, sharper narrative.

Stronger enterprise product positioning

Repositioning Markets as an intelligence workspace — not just a data viewer — enabled higher contract values, longer retention, and conversations with clients who would have previously dismissed the product.

Foundation for future monetization

The sandbox model and tiered architecture created natural product-led upgrade paths and usage-based pricing opportunities that simply didn't exist in the original fixed-content structure.

Advanced workflows unlocked for power users

Users at banks and valuation firms could now run multi-variable studies that previously required custom engineering work — dramatically reducing the product team's support burden while increasing user satisfaction.

07 — Challenges

What made this hard

C1 · Five incompatible mental models in one productBanks, ministries, valuators, brokers, and developers approach market data with completely different goals and workflows. The design had to serve all of them without fracturing into five separate products.
C2 · Balancing depth with legibilityReal estate market data is genuinely complex. Oversimplifying it for usability would have alienated expert users. The challenge was creating depth that was discoverable — not overwhelming on first use.
C3 · Evolving a live product without disruptionEnterprise users had established workflows built around the old system. Introducing new interaction models required careful migration design to avoid breaking what they already relied on to do their jobs.
C4 · Advocating for strategy without a PM bufferAs the first in-house designer, I had to make the case for the larger product repositioning — not just new screens. That meant translating design decisions into business outcomes that engineering and leadership could act on.
08 — What I Learned

Enterprise users don't just need dashboards. They need tools that adapt to how they think, investigate, and decide — not the other way around.

This project confirmed something I now treat as a foundational principle: the most important design question in enterprise software isn't "what should this screen show?" — it's "what does this user need to be able to do that they can't do today?" The answer to that question is what leads to real transformation, not incremental UI polish.

It also taught me that being the first designer in a company is a uniquely powerful position. You're not just designing — you're defining what design means to the organization, shaping what gets built, and setting a standard that others will build on long after you.