● UI/UX Case Study — Consumer Real Estate Web Platform

Meridian Realty
Group — Property
& Agent Portal

Client Meridian Realty Group, Austin TX
Year 2023 – 2024
My Role UX Lead, UI Designer & Creative Director
Platform React / Tailwind CSS — Consumer Web
Consumer Web App Design System UX Strategy

A modern consumer real estate platform for a US boutique agency — property search with live map, Neighbourhood Intelligence layered insights, agent performance dashboard, and a Kanban offer tracker. Delivered as a complete design system implemented in React/Tailwind with Figma design tokens.

Project Overview

Boutique Agency, Modern Platform

Meridian Realty Group is an independent boutique real estate agency operating in Austin, Texas. They engaged Moonfire Private Limited / Pixelgeometry for a full platform redesign and rebuild — their existing website was a static property listing page with no search capability, no neighbourhood data, and no agent tools. The brief was ambitious: create a consumer-facing property search experience that could compete with Zillow and Realtor.com while preserving the boutique agency feel, and build agent-side tools that would replace a chaos of spreadsheets, email chains, and manual offer tracking.

I led UX strategy, information architecture, wireframing, UI design, and creative direction. I defined the design system (Tailwind CSS config, component library, design tokens) and worked closely with the React development team to implement it. The signature feature was Neighbourhood Intelligence — a layered data visualisation combining school ratings, commute times, walkability scores, crime index, and value trend data on a live map overlay, giving buyers contextual information they couldn't get from listings alone. The agent dashboard and offer Kanban were later additions driven by agent feedback during beta.

My Role & Team

UX Lead, UI Designer & Creative Director

My Role UX Lead, UI Designer, Creative Director
Client Meridian Realty Group, Austin TX (US)
Delivered via Moonfire Private Limited / Pixelgeometry
Team Me (UX/UI/Creative) + 2 React devs + 1 backend dev
Screens 45+ screens, complete design system
React Tailwind CSS Figma Design Tokens Mapbox GL MLS Data Integration Kanban UX
Design Process

Research-Led, Token-Driven, System-First

🔍 01
Discovery
Interviews with 5 buyer personas and 4 Meridian agents. Competitive audit of Zillow, Realtor.com, and Austin boutique sites. Key finding: buyers wanted neighbourhood context, not just listing photos.
🗺️ 02
IA & Flow
Information architecture across 3 user flows: Consumer search, Property detail + Neighbourhood Intelligence, Agent dashboard + offer management. All flows mapped in FigJam before wireframes.
🎨 03
Design System
Tailwind CSS config defined as design tokens first in Figma — color palette, typography scale, spacing, component variants. Design tokens exported to Tailwind config for zero-drift implementation.
✏️ 04
UI Design
45+ screens in Figma with full component library. Responsive variants for all key views. Interactive prototypes for the map/search and offer Kanban flows validated with 3 Meridian agents.
⚙️ 05
Implement & Iterate
Worked directly with React team — reviewed component builds, QA'd on breakpoints, iterated designs based on Mapbox GL constraints. Two sprints of agent beta testing before launch.
Key Contributions

Platform Architecture to Pixel Delivery

  • 01
    Led UX strategy and information architecture

    Mapped three complete user flows — consumer property search, property detail with neighbourhood data, and agent-side tools — before any UI was designed. The IA decisions drove the entire React component hierarchy: Search Context, Property Context, and Agent Context as distinct application shells with shared component primitives.

  • 02
    Defined the Tailwind CSS design system as Figma design tokens

    Defined the complete Tailwind config — color palette (Meridian emerald scale + neutral scale), typography scale, border radius tokens, shadow tokens, spacing scale — in Figma first, then exported to `tailwind.config.js`. This meant designers and developers worked from identical values. Zero drift between Figma mockups and production components.

  • 03
    Designed the property search + live map interface

    The split-view search interface — filter panel left, live Mapbox map right with property pins — was the most complex UX challenge. Map pins needed to show price without cluttering the map at scale. Designed a dynamic pin system: price labels at zoom 12+, clustered dots with count at lower zoom, with individual property cards appearing on click as a floating panel over the map rather than a page navigation. This kept users oriented in geographic context throughout their search.

  • 04
    Designed Neighbourhood Intelligence data layers

    The signature differentiator: a toggle panel on the property detail view that overlays data layers on the map — School Ratings (district and specific school heat map), Commute (isochrone rings from the property by car/transit/walk), Walkability (Walk Score gradient overlay), Crime Index (low/medium/high heat map), and Market Value Trend (price per sq ft increase over 12 months). Each layer had a distinct colour range and a legend. Users could toggle multiple layers simultaneously. This was the feature Meridian agents said most impressed buyers during showings.

  • 05
    Designed the agent performance dashboard

    A real-time agent view showing: active listings (with days-on-market indicators), upcoming tours (calendar strip), performance metrics (views/enquiries/conversion this month vs last), and a client pipeline summary. Designed to give agents a morning briefing at a glance — the most important information visible without scrolling on a 13" laptop. Replaced 3 separate spreadsheets Meridian agents were maintaining manually.

  • 06
    Designed the Offer Tracker Kanban

    A Kanban board for tracking buyer offers across properties — columns: Draft, Submitted, Under Review, Counter-Offer, Accepted, Withdrawn. Cards show property address, offer amount, buyer name, and time-in-stage. Drag-and-drop between columns. Cards turn amber at 48h in stage, red at 72h. Designed specifically to make negotiation state visible at a glance rather than buried in email threads. This was added in sprint 3 based on direct agent feedback during beta.

  • 07
    Creative direction — brand visual language

    Meridian's existing brand was minimal to the point of non-existence — a wordmark only. I defined their visual language: Meridian Emerald as the signature accent, clean sans-serif type (Inter), generous white space, and photography direction guidelines for listing images. The "boutique feel" was achieved through white space discipline and card typography — not decoration. The design feels distinct from Zillow's information-density without sacrificing search utility.

UI Screens

Meridian Realty — React / Tailwind Web App (2023–2024)

Meridian Realty USA — UI Screen
Key UX Decisions

Design Thinking That Shaped the Platform

DECISION 01

Map-First Search Over List-First

Research showed buyers primarily think in geographic terms — "I want to be in East Austin, near Mueller" — not in price/bed/bath terms. The standard approach (list of results, map as secondary) inverts this mental model. I designed the search as a true split-view with the map equally prominent as the list, and made map pins the primary affordance for opening a property card. This kept buyers oriented in geographic context throughout their entire session, reduced pogo-sticking back to search results, and was cited in agent feedback as the feature that most impressed buyers during assisted showings.

DECISION 02

Neighbourhood Intelligence as the Core Differentiator

Boutique agencies can't out-data Zillow on listings — they'll always have fewer properties indexed. The differentiation had to come from insight, not volume. Neighbourhood Intelligence was designed as a layer system: contextual data overlaid on a map view that gave buyers answers they couldn't get from listing photos and square footage figures alone. The toggle-layer approach (vs a single combined score) let buyers prioritise what mattered to them — a family would weight schools heavily; a young professional might weight walkability and commute. This wasn't about adding data; it was about making data personally relevant.

DECISION 03

Offer Kanban — Time Pressure as Visual Signal

The most painful part of a buyer's agent job is that offer negotiation state lives in email threads — no one can see the whole picture at once. I designed a Kanban where the board represents negotiation state, not task state. The critical design decision was the time-in-stage indicator: cards turn amber at 48 hours in a stage, red at 72 hours. This makes stuck deals visually obvious without needing to read every card. Agents who tested the beta said this feature alone saved them 30-45 minutes per week on status chasing. The Kanban was added in sprint 3, after agents explicitly requested it during beta — which validated the discovery process had identified a real pain point we'd initially underweighted.

Outcomes & Impact

Platform Delivered, System in Production

45+ Figma Screens

Complete design system: property search, detail view, agent dashboard, Neighbourhood Intelligence layers, and offer Kanban.

5 NI Data Layers

Schools, Commute, Walkability, Crime Index, and Value Trend — each independently toggleable on the property map view.

0 Design/Dev Drift

Figma design tokens exported directly to tailwind.config.js — zero colour, spacing, or typography drift between design and production.

3+ Replaced Tools

Agents replaced 3+ manual spreadsheets with the Offer Tracker — citing 30-45 min/week saved on status tracking, per beta feedback.