Product design · Real estate

Emura: one dashboard to run a real estate operation

Properties, agents, customers and revenue analytics brought together in one web platform for real estate managers.

Emura real estate dashboard design on a laptop: property, customer and agent counts, sales chart, goals and listings
Project
Designed by Maniruzzaman Jubayer
Industry
Real estate, Real estate work
Topics
Real estate case studies, Dashboard design case studies, SaaS case studies
Year
2025
Tools
Photoshop, After Effects, Figma
Featured on
Development, Amsterdam, Product design, Dhaka

Overview

This case study walks through a real estate dashboard design for Emura, a management platform where managers run the whole operation from one place: properties, agents, customers and revenue. I designed the web app, a mobile layout of its dashboard and the design system behind both.

The deck sums up the brief as making data work for managers instead of fighting them.

The challenge

The deck names three problems the design had to fix.

  • Property, agent and customer data sat on separate pages and felt disconnected.
  • Overloaded dashboards buried the numbers that matter.
  • Revenue and performance data had no clear hierarchy.

Each problem got a matching answer: one dashboard with organised navigation and grouped sections, clean layouts with focused metrics, and charts that make revenue easy to read.

The process

  1. Discovery: industry research and a competitive analysis.
  2. Information architecture: Home, Property, Agent, Customer and Analysis.
  3. A moodboard, then wireframes and layouts.
  4. High fidelity visual design.
  5. A prototype and a design system: Inter, one green accent and a grey scale.
Emura type sheet with Inter in Regular, Semibold and Bold
Emura type sheet with Inter in Regular, Semibold and Bold

The solution

Every record lives in one web app, with the same sidebar on every screen: Home, Property, Agent, Customer and Analysis, with security, help and settings below.

Main dashboard

Three count cards (properties, customers and agents) each carry a change against last week and a small trend chart. A sales breakdown chart with a chart type switch sits below, beside a goals gauge with week and month tabs, achieved against target and results by channel: website, email and social media. An active property list closes the screen with location, contact, views, status and price, so the day starts with the whole operation in view.

Property list and map

Listing cards show the photo, price, address, beds, baths and floor area, with share and save buttons. A map fills the right half with house pins, and selecting one opens a small card with the photo and price. Location is the first question about any property, so the map gets as much room as the list.

Property details

One page holds the listing and its seller. Photos, title, price and address lead, then the description, a "What this place offers" amenity grid and lot details with the sale status. The right column shows the assigned agent with reviews, rating, years of experience, phone, area, email and a Get in Touch button, then ratings and a 3D preview.

Agents

The agent list is a grid of cards with an ID, phone, email, properties sold, rating and years of experience, so a manager can compare people at a glance. An agent's page adds a profile, tabs for previous sales, properties and certificates, and a deals chart.

Customers

Customer cards lead with what each person wants, for example a first-time homebuyer exploring city centre apartments or an investor after high-return rentals, then a phone number, a Message button and a view link. Whoever picks up the card reads the need before making the call.

Revenue analytics

Four cards sit at the top: total revenue, net profit, property sales value and rental income, each against last year. Below, a monthly bar chart splits property sales from rental income, beside track progress and a revenue growth meter, then a revenue against expense chart. The money reads top to bottom, from totals to the months behind them.

Mobile dashboard

The mobile layout stacks the same count cards for properties, customers and agents in one column, each with its weekly change and mini chart, above the sales breakdown. A manager away from a desk sees the same numbers first, in the same order.

Emura property list on a laptop, beside a map of property pins
Emura property list on a laptop, beside a map of property pins

The result

  • The web app, which the deck lists as 40+ screens: dashboard, properties, agents, customers and analytics.
  • A mobile layout of the dashboard cards.
  • A design system foundation and a prototype.

How it helps the client

Emura can give managers one place to check stock, people and money, instead of three tools that don't talk to each other. Pending listings, sales and progress against the goal share one screen, and every listing shows the agent behind it. Planning something similar? See how I approach product design for real estate platforms, or browse more real estate case studies.

Frequently asked questions

  • On Emura it came down to five areas: a dashboard with totals and goal progress, a property list with a map, property details with the assigned agent, agent and customer directories, and revenue analytics. Each one answers a question a manager asks every day, so nothing needs a separate tool.

  • I start with industry research and a competitive analysis, then set the information architecture before drawing a single screen. Wireframes come next, then high fidelity design and a prototype. On Emura that order kept property, agent and customer data in fixed places, so managers always know where to look.

  • The numbers a manager checks before anything else: how many properties, customers and agents there are, and how each moved since last week. Emura puts those three cards at the top, then sales over time and progress against the goal, then the live list of active properties with their status. Revenue detail lives on its own analytics page, so the home screen stays readable. Start from the questions asked every morning and let everything else sit one click away.

  • Give the map real space. On Emura listing cards fill the left half and the map fills the right, with a pin per property and a small preview card on the selected pin showing photo, price and size. Each card carries the same facts in the same order (price, address, beds, baths, floor area), so people can scan a row quickly. Share and save sit on the card itself, so a shortlist builds without opening every listing.

  • On Emura I worked in Figma for the wireframes, screens, design system and prototype, alongside Photoshop, Illustrator, XD and After Effects. Every project runs in weekly design sprints in Figma, with a written update from me every 48 hours, so you always know where the work stands.

  • Yes. I build web apps and front ends in React and Next.js, working from a documented design system and developer handoff. This case study covers the design work on Emura. A project starts with a free 30 minute intro call, then a written scope and one fixed quote for the whole project.

More case studies

Lyvio AI real estate app and website design cover: the Lyvio name over a desert dune and terracotta villa

Real estate · 2026

Lyvio

Website and product screens for an AI property advisor

Real estate landing page design for Homelo on a laptop: a huge Homelo name over a modern glass house

Real estate · 2024

Homelo

A landing page for a real estate company

AQARI investor web app dashboard in Arabic with portfolio value chart, wallet balance and sidebar

Real estate · 2026

AQARI

A Shariah-compliant fractional real estate investing web app for Saudi Arabia

Planning a product like Emura?

A free 30 minute call. You leave with a clear next step, whether we work together or not.

Book a free intro call