ESTATE OS, 2025

Reduced sales conflicts by designing a centralized inventory ownership system for real estate teams

Reduced sales conflicts by designing a centralized inventory ownership system for real estate teams

Designed for real estate brokers managing shared inventory across multiple regions.

project details

Team

Solo Designer

Solo Designer

Duration

2-3 months

2-3 months

My Role

Conceptualization · System Design · Client Iterations · Multi-team coordination system

Conceptualization · System Design · Client Iterations · Multi-team coordination system

Status

Pitched, validated with stakeholders to align system design and workflows

Pitched, validated with stakeholders to align system design and workflows

Confidentiality Note

This case study is based on a confidential real estate project. The company name have been modified while preserving the original problem, process, and design decisions.

This case study is based on a confidential real estate project. The company name have been modified while preserving the original problem, process, and design decisions.

background

They asked for dashboards. What they actually needed was clarity.

The initial ask was to design dashboards for sales, supply, and admin teams.

As discussions progressed, it became clear the real issue wasn’t dashboards, but how inventory was being managed across teams.

THE REAL SHIFT

Ownership was the real problem

Inventory silos, overlapping sales outreach, and limited visibility all pointed to one gap:

Inventory silos, overlapping sales outreach, and limited visibility all pointed to one gap:

No clear ownership meant multiple agents contacted the same client, causing internal conflicts and poor client experience

This shifted the problem from UI design to system design.

This shifted the problem from UI design to system design.

IMPACT

Defined a single source of truth for commercial real estate operations

Eliminated duplicate outreach

Reduced

Sales Overlap

Reduced

Sales Overlap

Single lead ownership per sales executive

Single lead ownership per sales executive

Increased

Inventory Visibility

Increased

Inventory Visibility

Increased

Inventory Visibility

One centralized source of truth across teams

Single lead ownership per sales executive

One centralized source of truth across teams

Structured accountability across roles

Clear Role
Hierarchy

Clear
Role Hierarchy

Ownership, visibility, and control were clearly defined

Ownership, visibility, and control were clearly defined

How I approached the problem

I treated inventory as a system, not a screen

Instead of designing dashboards in isolation,I stepped back and asked:

  • Who owns inventory?

  • Who owns leads?

  • Who gets visibility, and when?

CORE DECISION 1 : INventory became the single source of truth

  • All teams worked off the same inventory

  • Eliminated conflicting inventory states across teams

  • Availability and ownership stayed consistent

  • All teams worked off the same inventory

  • Eliminated conflicting inventory states across teams

  • Availability and ownership stayed consistent

Ensured consistency and reduced coordination overhead

Ensured consistency and reduced coordination overhead

Made dependencies explicit

Made dependencies explicit

Required early agreement on ownership rules

Required early agreement on ownership rules

CORE DECISION 2 : Lead ownership was mandatory, not optional

  • One lead → one sales

  • Managers could reassign when required.

  • Sales overlap was no longer possible by default

Eliminated duplicate client outreach by enforcing single ownership

Eliminated duplicate client outreach by enforcing single ownership

Eliminated duplicate client outreach by enforcing single ownership

Improved accountability and client experience

Improved accountability and client experience

Improved accountability and client experience

CORE DECISION 3 : Visibility scaled with responsibility

  • Aligned visibility with responsibility, reducing unnecessary system noise

  • Scaled system without breaking ownership rules

Supply Team

Inventory Ownership

Full visibility into properties & inventory. No access to leads or other teams.

Sales Team

Assigned Workflows Only

Access to assigned leads, clients , meetings and tasks.

Managers

Team - Level Oversight

View team performance, leads, inventory, approvals and reports.

Admins

System - Wide Control

Complete platform visibility, user roles, settings and audit logs.

EXPLORING AI

AI was introduced only after system clarity — to reduce operational load, not define workflows

Once ownership and workflows were clear, I explored where AI could meaningfully reduce repetitive work—especially for sales and admin teams.

Used AI to:

  • Automate lead tagging and categorization

  • Assist reassignment workflows

  • Reduce repetitive admin effort

Impact : Sales and admin teams saved 8 - 10 hrs/week on repetitive tasks, improved response time, and focused more on high - value activities.

SALES EXPERIENCE

Designing sales around ownership, not volume

Optimized for :

  • Single ownership per lead

  • Faster action

  • Zero overlap

Sales see only what they own

Clear next action, no guessing

Read-only inventory view

One owner per lead

BLUF TAKEAWAY

Sales operated on ownership, not guesswork

SUpply EXPERIENCE

Supply managed inventory — not sales pressure

Optimized for :

  • Structured inventory input

  • Controlled updates

  • Higher data accuracy

Structured inventory entry

Availability & status updates

SUPPLY see only what they own

Controlled TASKS, fewer errors

BLUF TAKEAWAY

Clean inventory ensured downstream reliability.

CLIENT-FACING EXPERIENCE

Clients saw clarity, not internal complexity

Optimized for :

  • Clear property data

  • Direct contact mapping

AI-assisted intent capture

DIRECT CONTACT WITH SALES TEAM

Accurate availability & property details

Clear information, no ambiguity

BLUF TAKEAWAY

Clarity in system translated into trust for users.

Scalability Considerations

Designed to scale beyond day-to-day operations

Inventory, users, and approvals at a state level

Access control and visibility across regions

These roles ensured the system could scale across teams and regions without breaking ownership rules.

SIGNING OFF!

KEY TAKEAWAYS

This project involved navigating ambiguity, evolving requirements, and aligning with stakeholders need.

If I had to distill what stayed with me after the project, it would be this:

Clarity reduces complexity

Clarity reduces complexity

Clarity reduces complexity

Defining ownership and visibility simplified decisions more than adding features ever could.

AI should remove friction

AI should remove friction

AI should remove friction

AI added value when it reduced steps and effort—not when it tried to replace judgment.

System thinking aligned stakeholders before anything was built

System thinking aligned stakeholders before anything was built

System thinking aligned stakeholders before anything was built

Even without final UI or development, the system thinking helped align stakeholders and direction.

This project reinforced my approach: solve for systems first — interfaces follow.

Powered by caffeine, creativity & way too many “final_final” versions.

Powered by caffeine, creativity & way too many “final_final” versions.

Powered by caffeine, creativity & way too many “final_final” versions.

Create a free website with Framer, the website builder loved by startups, designers and agencies.