Case study · 2024 – 2025 · ~1 year
Lead Design | Real Estate Services | iOS, Android, Web & Brand
Introduction
The client
My RE Tasker is a digital assistance platform for Realtors and real estate organisations. Instead of losing hours to paperwork, Realtors buy specialised services, from document verification to marketing and task management, and hand the work to trained virtual assistants. Behind the scenes, admins and category managers route and quality-check every task.
My role
I joined as Lead Designer when the product was about 15% built and the web app design was already set. I owned the mobile apps and the brand end to end, improved the UX of the inherited web app within its existing design language, and guided a junior designer on the marketing website, while making the major design calls across all of it.
Impact
The platform launched on iOS, Android and the web with one consistent visual language, a shared component library and a new brand identity, turning a half-built web product into a complete multi-platform service.
platforms shipped: iOS, Android, web app and website
user roles designed for, from Realtor to Virtual Assistant
leading design from 15% built to launch
brand identity and logo, created from scratch
01 — The problem
Paperwork, document checks, listings, marketing and follow-ups pile up around every transaction. Each task is small, but together they pull Realtors away from clients. My RE Tasker set out to take that operational work off their plate, without making delegation feel like more work.
Time
Admin eats selling time
Document checks, listings and follow-ups take hours that could be spent with clients.
Trust
"Will it be done right?"
Real estate paperwork is high-stakes. Realtors need confidence that delegated work is accurate and on time.
Clarity
"What exactly am I buying?"
Vague service menus make delegation feel risky. People need to know what each service includes and what it needs from them.
The challenge
02 — Who it's for
Every service request passes through several hands: the Realtor who buys it, the admins and category managers who route it, and the virtual assistant who completes it. I designed for the whole chain, with the Realtor experience front and centre.
Mobile + web app
Individual Realtors and real estate organisations who want to hand off operational work and focus on clients.
What they need
• Find the right service in seconds
• Submit the right documents the first time
• Track progress without chasing anyone
What frustrates them
• Unclear service scope and pricing
• Back-and-forth over missing information
• No visibility once a task is handed off
Operations side
Admins, Category Managers and Virtual Assistants who receive, route and complete each request.
What they need
• Complete, structured information for every task
• Clear ownership and status for each request
• Tools that fit how each role actually works
What frustrates them
• Incomplete requests that stall work
• Tasks that fall between roles
• One generic view for very different jobs
03 — Research & strategy
I inherited an established web design and a team already building. Starting over wasn't an option, so I audited the existing web app, mapped every role and service flow, and found where the experience broke down. Then I planned improvements that worked within the existing design language, while leading the mobile apps and brand from scratch.
What the audit told me
Insight 01
Tasks without structure
Requests were organised as loose tasks, so Realtors weren't sure what they were buying or what it included.
Insight 02
One form doesn't fit all
Every service needs different information and documents, yet a generic form led to incomplete requests and delays.
Insight 03
Web and mobile must feel like one
Realtors move between desk and field. Mobile had to match the web app's language exactly, or the product would feel like two.
How I worked
UX audit
User flows
Wireframes
Mobile app design
Design system
Branding & logo
Responsive web
Team guidance
04 — Mapping the service
I mapped a single service request from purchase to delivery, across every role that touches it. The map showed exactly where information went missing and where ownership blurred, and it shaped both the forms and the status system.
Step 1
Choose
Realtor
Browses service categories and picks a service.
Operations
Sees new demand by category.
Step 2
Submit
Realtor
Fills a service-specific form and uploads documents.
Operations
Receives a complete, structured request.
Step 3
Assign
Realtor
Sees the task confirmed and assigned.
Operations
A Category Manager routes it to the right assistant.
Step 4
Complete
Realtor
Follows progress and answers questions in context.
Operations
The Virtual Assistant completes and submits the work.
Step 5
Review
Realtor
Reviews the result and books the next service.
Operations
An Admin closes the task and tracks performance.
05 — Key decisions
Each decision balanced what Realtors needed with how the operations team actually works, and with a web product that was already being built.
The problem
Loose, free-form tasks left Realtors unsure what they were buying, and made pricing, routing and quality control hard for operations.
Options I weighed
Keep a single "create task" flow with free text (flexible, but vague), or rebuild the product around a catalogue of clearly defined service categories.
What I chose
A service catalogue grouped into clear categories (document verification, marketing, task management), each service with its own scope, price and turnaround.
Why it worked
Realtors buy with confidence, and every request lands with the right category manager automatically.
The problem
A generic form produced incomplete requests: missing documents, wrong details and days of back-and-forth before work could start.
Options I weighed
One long universal form with optional fields, or a form system where each service defines exactly which fields and documents it needs.
What I chose
Service-specific forms built from a shared set of form components, so each service asks only for what it needs, with required documents made clear upfront.
Why it worked
Requests arrive complete, assistants can start straight away, and the team can add new services without designing new screens.
The problem
The web app's design language was already set. A mobile app that looked or behaved differently would have made the product feel like two separate tools.
Options I weighed
Design mobile as a fresh, separate experience, or extend the web language into native mobile patterns.
What I chose
Extend the existing web design language to iOS and Android: the same components, colours and terminology, adapted to native navigation and touch.
Why it worked
Realtors can start a request at their desk and follow it in the field without relearning anything.
06 — Brand & visual direction
Real estate runs on trust. I designed the logo and brand materials around a deep navy for reliability, with a confident yellow accent that feels helpful and energetic, so the brand reads as a dependable partner rather than another back-office tool.
07 — Design system
With three designers and four platforms, consistency couldn't depend on memory. I built a shared component library with Figma variables that the whole team designed from and developers built against.
Colour
Midnight Navy
#2D3A66
Golden Mustard
#D4AD2D
Deep Slate
#34424B
Graphite Grey
#4F4F4F
Canvas
#F9F9FA
Typeface
Geometric and confident, used across headings and UI for one consistent voice on every platform.
System
Colours, spacing and type defined once as variables, so updates reach every screen on every platform at the same time.
Components
Service cards, category navigation, dynamic form fields, document upload, status chips, task timelines, dashboards and responsive layouts, each with complete states, shared across mobile, web app and website.
08 — Final designs
A complete service platform: Realtors browse, buy and track services on mobile and web, while the operations team routes and completes every request.
Mobile app
Service catalogue
Services grouped by category, each with a clear scope and price.
Service request form
Only the fields and documents that service needs.
Task tracking
Every request's status and updates, in one place.
Web app & website
Realtor on-going task
Active tasks, recent services and quick actions on the web.
Operations view
Requests routed by category, with clear ownership.
Super Admin dashboard
Orders, users and top services across the whole platform, in one view.
09 — Outcome
My RE Tasker launched on iOS, Android, the web app and a marketing website, all built on one design system and one brand. A product that was 15% built when I joined became a complete, consistent service.
platforms live: App Store, Play Store, web app and website.
shared design system and brand used by the whole design team.
user roles supported in a single, connected workflow.
"Shreya brought structure to a product that was already moving fast, and made every platform feel like one My RE Tasker."
Product Manager, 4TYSIX
10 — Looking back
Rethink the inherited web experience
Working inside an existing web design limited what I could change. With more freedom, I'd rebuild the web app around the same service-first structure as mobile.
Design the relationships between roles
I'd spend more time on the hand-offs between Realtors, managers and assistants, the moments where tasks most often stalled.
Go deeper on multi-role workflows
I'd run research with admins and assistants earlier, to design their tools as carefully as the Realtor's.
Learnings
Simple UX sits on complex systems
Behind every clean service card is routing, pricing and permissions. Understanding that system made the interface simpler, not harder.
Think beyond single screens
Designing for five roles taught me to design flows and states across the whole product, not one screen at a time.
Leading is part of designing
Guiding a junior designer while owning major decisions taught me to explain the why, not just the what.
Enjoyed this case study?
© 2024 My RE Tasker. All rights reserved. Designed by Shreya Pandya.