UI / UX Design
Property Management
A role-based property management platform connecting owners, tenants, and maintenance staff in one system.
Year :
2025
Industry :
PropTech / Real Estate
Tools :
Figma
Project Duration :
3 Week
Overview :
A property management platform built around three connected experiences rather than one generic app. Property owners get a full command center for their portfolio — properties, units, tenants, agreements, billing, and reports. Tenants get a lightweight self-service portal for invoices and their lease. Maintainers get a focused queue for handling repair tickets. Instead of designing one bloated app trying to serve everyone, the product was split into three role-specific interfaces sharing a single visual language, so each user only ever sees what's relevant to them.
Problem :
Independent landlords and small property management teams typically run their operations across a patchwork of spreadsheets, WhatsApp threads, and paper agreements. Nothing talks to anything else, and neither tenants nor maintenance staff have any visibility into the process once a request leaves their hands.
Key pain points identified:
Rent and invoice tracking scattered across spreadsheets and manual receipts
No centralized place for lease agreements and property documents
Maintenance requests routed by phone or message, with no status tracking
Owners lacking a real-time view of occupancy, income, and expenses
Tenants with no self-service way to view invoices or track a repair request
Solution :
A single connected system delivered as three role-based apps — Owner, Tenant, and Maintainer — sharing one design language but each scoped tightly to what that role actually needs to do day to day, from listing a new property to closing a maintenance ticket.
Key screens:
Design Decisions:
A single primary indigo/blue action color used consistently for CTAs, active nav states, and status highlights across all three apps, so the product reads as one system even though the interfaces differ.
Chunky KPI stat tiles (Total Property, Total Tenants, Total Units, Total Maintainer) on the Owner home screen for at-a-glance portfolio health, instead of burying numbers in menus.
A consistent floating pill-style bottom navigation across all three apps, with role-specific tabs (Owner: Home / Properties / Tenants / Billing / Profile; Maintainer: Home / Tickets / Tools / Issues / Alerts).
Status-driven color coding — orange for "In Processing," distinct tones for "Closed" and "Resolved" — applied consistently to both maintenance tickets and invoices, so state is scannable without reading labels.
A Gold Membership card surfaced prominently on the owner profile to reinforce account tier and renewal date.
A shared component library — search bars, list cards, avatar chips, status pills — reused across Owner, Tenant, and Maintainer apps to keep the three experiences visually consistent while speeding up design and handoff.
Challenges:
Three roles, one design system. The hardest part wasn't designing any single screen — it was keeping Owner, Tenant, and Maintainer visually unified while their information needs and permissions are completely different. Shared components had to be flexible enough to serve a data-dense owner dashboard and a lightweight tenant portal without feeling like two different products bolted together.
Dense financial data on mobile. Billing Center, invoice history, expense reports, and earnings all needed to live comfortably on a phone screen without turning into a spreadsheet. Solved with card-based summaries and drill-down detail views rather than dense tables.
Making the maintenance lifecycle legible. A ticket moves through several states and hands off between tenant and maintainer. Getting that status change to read clearly at a glance — not just in a detail view — took several rounds on the color and label system.
Long-form property pages. Property View pages combine photos, unit details, documents, and history in a single scroll. Structuring that much content so it stays scannable, rather than becoming an endless feed, needed a clear section hierarchy and sticky navigation.
Outcomes:
Three role-based apps (Owner, Tenant, Maintainer) designed as one connected system
77 exported screens covering onboarding, dashboards, financials, documents, reports, and ticketing
A reusable component library (cards, stat tiles, status pills, navigation) shared across all three apps
A complete property and unit management flow, from listing creation through tenant assignment
Learnings:
A shared design system across multiple role-based apps only works if the components are built flexible from day one — retrofitting consistency later is much harder.
Financial and reporting screens deserve their own pattern language early; treating them as an afterthought shows immediately on data-heavy screens.
Status and lifecycle states (tickets, invoices, agreements) need a consistent visual vocabulary from the start, not bolted on once every screen already exists.
Designing three connected apps in parallel surfaced reusable patterns much earlier than designing them one at a time would have.
More Projects
UI / UX Design
Property Management
A role-based property management platform connecting owners, tenants, and maintenance staff in one system.
Year :
2025
Industry :
PropTech / Real Estate
Tools :
Figma
Project Duration :
3 Week
Overview :
A property management platform built around three connected experiences rather than one generic app. Property owners get a full command center for their portfolio — properties, units, tenants, agreements, billing, and reports. Tenants get a lightweight self-service portal for invoices and their lease. Maintainers get a focused queue for handling repair tickets. Instead of designing one bloated app trying to serve everyone, the product was split into three role-specific interfaces sharing a single visual language, so each user only ever sees what's relevant to them.
Problem :
Independent landlords and small property management teams typically run their operations across a patchwork of spreadsheets, WhatsApp threads, and paper agreements. Nothing talks to anything else, and neither tenants nor maintenance staff have any visibility into the process once a request leaves their hands.
Key pain points identified:
Rent and invoice tracking scattered across spreadsheets and manual receipts
No centralized place for lease agreements and property documents
Maintenance requests routed by phone or message, with no status tracking
Owners lacking a real-time view of occupancy, income, and expenses
Tenants with no self-service way to view invoices or track a repair request
Solution :
A single connected system delivered as three role-based apps — Owner, Tenant, and Maintainer — sharing one design language but each scoped tightly to what that role actually needs to do day to day, from listing a new property to closing a maintenance ticket.
Key screens:
Design Decisions:
A single primary indigo/blue action color used consistently for CTAs, active nav states, and status highlights across all three apps, so the product reads as one system even though the interfaces differ.
Chunky KPI stat tiles (Total Property, Total Tenants, Total Units, Total Maintainer) on the Owner home screen for at-a-glance portfolio health, instead of burying numbers in menus.
A consistent floating pill-style bottom navigation across all three apps, with role-specific tabs (Owner: Home / Properties / Tenants / Billing / Profile; Maintainer: Home / Tickets / Tools / Issues / Alerts).
Status-driven color coding — orange for "In Processing," distinct tones for "Closed" and "Resolved" — applied consistently to both maintenance tickets and invoices, so state is scannable without reading labels.
A Gold Membership card surfaced prominently on the owner profile to reinforce account tier and renewal date.
A shared component library — search bars, list cards, avatar chips, status pills — reused across Owner, Tenant, and Maintainer apps to keep the three experiences visually consistent while speeding up design and handoff.
Challenges:
Three roles, one design system. The hardest part wasn't designing any single screen — it was keeping Owner, Tenant, and Maintainer visually unified while their information needs and permissions are completely different. Shared components had to be flexible enough to serve a data-dense owner dashboard and a lightweight tenant portal without feeling like two different products bolted together.
Dense financial data on mobile. Billing Center, invoice history, expense reports, and earnings all needed to live comfortably on a phone screen without turning into a spreadsheet. Solved with card-based summaries and drill-down detail views rather than dense tables.
Making the maintenance lifecycle legible. A ticket moves through several states and hands off between tenant and maintainer. Getting that status change to read clearly at a glance — not just in a detail view — took several rounds on the color and label system.
Long-form property pages. Property View pages combine photos, unit details, documents, and history in a single scroll. Structuring that much content so it stays scannable, rather than becoming an endless feed, needed a clear section hierarchy and sticky navigation.
Outcomes:
Three role-based apps (Owner, Tenant, Maintainer) designed as one connected system
77 exported screens covering onboarding, dashboards, financials, documents, reports, and ticketing
A reusable component library (cards, stat tiles, status pills, navigation) shared across all three apps
A complete property and unit management flow, from listing creation through tenant assignment
Learnings:
A shared design system across multiple role-based apps only works if the components are built flexible from day one — retrofitting consistency later is much harder.
Financial and reporting screens deserve their own pattern language early; treating them as an afterthought shows immediately on data-heavy screens.
Status and lifecycle states (tickets, invoices, agreements) need a consistent visual vocabulary from the start, not bolted on once every screen already exists.
Designing three connected apps in parallel surfaced reusable patterns much earlier than designing them one at a time would have.
More Projects
UI / UX Design
Property Management
A role-based property management platform connecting owners, tenants, and maintenance staff in one system.
Year :
2025
Industry :
PropTech / Real Estate
Tools :
Figma
Project Duration :
3 Week
Overview :
A property management platform built around three connected experiences rather than one generic app. Property owners get a full command center for their portfolio — properties, units, tenants, agreements, billing, and reports. Tenants get a lightweight self-service portal for invoices and their lease. Maintainers get a focused queue for handling repair tickets. Instead of designing one bloated app trying to serve everyone, the product was split into three role-specific interfaces sharing a single visual language, so each user only ever sees what's relevant to them.
Problem :
Independent landlords and small property management teams typically run their operations across a patchwork of spreadsheets, WhatsApp threads, and paper agreements. Nothing talks to anything else, and neither tenants nor maintenance staff have any visibility into the process once a request leaves their hands.
Key pain points identified:
Rent and invoice tracking scattered across spreadsheets and manual receipts
No centralized place for lease agreements and property documents
Maintenance requests routed by phone or message, with no status tracking
Owners lacking a real-time view of occupancy, income, and expenses
Tenants with no self-service way to view invoices or track a repair request
Solution :
A single connected system delivered as three role-based apps — Owner, Tenant, and Maintainer — sharing one design language but each scoped tightly to what that role actually needs to do day to day, from listing a new property to closing a maintenance ticket.
Key screens:
Design Decisions:
A single primary indigo/blue action color used consistently for CTAs, active nav states, and status highlights across all three apps, so the product reads as one system even though the interfaces differ.
Chunky KPI stat tiles (Total Property, Total Tenants, Total Units, Total Maintainer) on the Owner home screen for at-a-glance portfolio health, instead of burying numbers in menus.
A consistent floating pill-style bottom navigation across all three apps, with role-specific tabs (Owner: Home / Properties / Tenants / Billing / Profile; Maintainer: Home / Tickets / Tools / Issues / Alerts).
Status-driven color coding — orange for "In Processing," distinct tones for "Closed" and "Resolved" — applied consistently to both maintenance tickets and invoices, so state is scannable without reading labels.
A Gold Membership card surfaced prominently on the owner profile to reinforce account tier and renewal date.
A shared component library — search bars, list cards, avatar chips, status pills — reused across Owner, Tenant, and Maintainer apps to keep the three experiences visually consistent while speeding up design and handoff.
Challenges:
Three roles, one design system. The hardest part wasn't designing any single screen — it was keeping Owner, Tenant, and Maintainer visually unified while their information needs and permissions are completely different. Shared components had to be flexible enough to serve a data-dense owner dashboard and a lightweight tenant portal without feeling like two different products bolted together.
Dense financial data on mobile. Billing Center, invoice history, expense reports, and earnings all needed to live comfortably on a phone screen without turning into a spreadsheet. Solved with card-based summaries and drill-down detail views rather than dense tables.
Making the maintenance lifecycle legible. A ticket moves through several states and hands off between tenant and maintainer. Getting that status change to read clearly at a glance — not just in a detail view — took several rounds on the color and label system.
Long-form property pages. Property View pages combine photos, unit details, documents, and history in a single scroll. Structuring that much content so it stays scannable, rather than becoming an endless feed, needed a clear section hierarchy and sticky navigation.
Outcomes:
Three role-based apps (Owner, Tenant, Maintainer) designed as one connected system
77 exported screens covering onboarding, dashboards, financials, documents, reports, and ticketing
A reusable component library (cards, stat tiles, status pills, navigation) shared across all three apps
A complete property and unit management flow, from listing creation through tenant assignment
Learnings:
A shared design system across multiple role-based apps only works if the components are built flexible from day one — retrofitting consistency later is much harder.
Financial and reporting screens deserve their own pattern language early; treating them as an afterthought shows immediately on data-heavy screens.
Status and lifecycle states (tickets, invoices, agreements) need a consistent visual vocabulary from the start, not bolted on once every screen already exists.
Designing three connected apps in parallel surfaced reusable patterns much earlier than designing them one at a time would have.