Rahul Sharma
Stonehaus Realty property page: a photo gallery of a modern house with a pool, the price and address, and a Request a meeting button

Hausleads · Product design

Redesigning a real-estate platform, from a buyer's first search to an agent's follow-up.

Client
Stonehaus Realty · Canada
Role
Sole product designer · Freelance
Team
7 people: PM, developers, QA and me
Timeline
2022–23, launched in 2023
Scope
Marketing site, agent CRM, iOS and Android apps
Platform
Web, iOS and Android

In short · 30-second read

Stonehaus Realty's agents were working leads in a platform they found hard to use. In 2022–23 I redesigned the buyer website and the agent CRM, so what a buyer does on the site shows up for the agent as something useful.

01 / The problem

Buyers take weeks to decide. Agents were getting a name and a number.

Nobody picks a house in one visit. People come back, change their budget, compare, and bring a partner in. Every visit says something about what they want, but on Stonehaus's old platform very little of it reached the agent. A new lead arrived as a name and a phone number, and the agent had to call to find out the rest.

Stonehaus wanted a public site that made searching easier and an agent app that turned all that browsing into follow-up. I treated it as one product with two sides.

02 / My role

The only designer, from the first map to launch.

This was freelance work, from 2022 into 2023. The team was seven people: a PM, developers, QA and me. I did the research for the marketing site, talked with four to six of Stonehaus's in-house agents about how they actually work their leads, and drew the whole product as information architecture before designing any screens. Those two maps, below, were what the team argued over and agreed on.

Some things came fixed. Regulation and the listing platforms decide what a site asks at sign-up, and the old site already asked it; there, my job was to make it less painful. The rest was mine: how agents see their numbers, the new email, calendar and team chat modules, and the two parts that took the most time, the lead dashboard and automation. I designed every component from scratch. There was no UI kit.

Information architecture of the Hausleads marketing site: the landing page branching to home, search, featured listings, about and sell a home, with login, account creation, My Notebook and account settings above
Information architecture of the Hausleads agent app: Leads with filters, saved filters, pipelines and labels, every list column and its sort order, the lead profile with its tabs, and the email, messages and Hauschat communication module
The marketing site, mapped from the landing page out: search, listing, property page, sign-up, My Notebook and account.

Part one

The buyer, on the marketing site

03 / Search

Search first.

The homepage opens with a search box over a photo, with Buy and Sell tabs and the areas you searched last time. Below it are recommended and featured homes, and quick links by neighbourhood for people who don't know what to type yet.

Results have filters for beds, baths, price, size and type along the top, with Save Search next to them. You can switch between a grid, which favours photos, and a list, which adds a description, and keep a map open alongside.

Homepage. The homepage: a search card over the hero, then recommended properties, featured listings and quick searches by neighbourhood.
Grid view. Grid view: two cards per row beside an open map, with filters and Save Search along the top.
List view. List view: each card gains a description beside its photo, under the same filters.
Featured listings. Featured Listing: hand-picked homes in a three-column grid, with pagination and a count of listings shown.
The homepage: a search card over the hero, then recommended properties, featured listings and quick searches by neighbourhood.

04 / Property page

One page per home, with the request button close by.

A listing shows the gallery, price, address and the three numbers everyone checks first: size, bedrooms and bathrooms. Add to Favorites and Request a meeting sit right beside them. Further down, every section uses the same label-and-value rows, so comparing two homes is easy.

Buyers can write private notes and fill in a pro/con scorecard in the side column while they read. Where school data is missing, the page says so and offers to put them in touch with an agent, instead of showing an empty box.

Property page. A listing page: gallery, key numbers, Add to Favorites and Request a meeting, then detail sections with notes and a scorecard in the side column. The page scrolls.
A listing page: gallery, key numbers, Add to Favorites and Request a meeting, then detail sections with notes and a scorecard in the side column. The page scrolls.

05 / Sign up

Questions we had to ask, asked once.

Why
The fields and the four questions (mortgage pre-approval, first-time buyer, timeline, a house to sell) are required, and the old site asked them all on one long form. I split it in two: three fields to create the account, then the questions.
Trade-off
It's an extra screen. I was fine with that, because people finish short screens, and the answers still land on the lead's profile before the agent calls.

Saving a home needs an account. You can sign up with a name, email and phone number, or with Facebook or Google. The phone number doubles as the password; that rule came with the platform.

Create account and registration. Create new account (left): name, email and phone number, with Facebook and Google as shortcuts. Free Registration (right): four questions about mortgage prequalification, first-time buying, timeline and a home to sell.
Create new account (left): name, email and phone number, with Facebook and Google as shortcuts. Free Registration (right): four questions about mortgage prequalification, first-time buying, timeline and a home to sell.

06 / My Notebook

A place to come back to.

Once you sign in, My Notebook holds everything: favourites, saved and recent searches, an activity feed, scheduled showings, and your search team, the people you invite to see your notes and add their own. Each showing has its own page with the facts, photos, map, notes and scorecard.

Account settings are where buyers choose how they hear from Stonehaus: email, text, property alerts. That matters later, because automated messages only go out on the channels a buyer has allowed.

Favourites. Favourites: shortlisted homes with the number of people who saved each one, and shortcuts to a note and a scorecard.
Saved searches. Saved searches: criteria, how often to send matching listings, and View, Edit and delete actions.
Updates. Updates: everything the buyer has done, newest first.
Notes & scorecards. Notes & Scorecard: the buyer's own notes and pro or con ratings, filtered out of the feed.
Schedule. Schedule: each planned showing with its date, a Cancel action and a button to the property details.
Showing details. Showing details: key facts, photos, map and virtual tour, team and market updates, notes, and the scorecard. The page scrolls.
My Search Team. My Search Team: invite someone by email to see notes and ratings and add their own.
My subscriptions. My Subscriptions: email, text message, property alerts and updates on favourited homes.
Favourites: shortlisted homes with the number of people who saved each one, and shortcuts to a note and a scorecard.

Part two

The link between them

07 / The request

Asking about a home.

On a property page, Request a showing opens a side panel. You can book a tour (pick a date, in person or video) or just send a question. The request shows up in the buyer's Notebook, and on the agent's side as an alert, an email and an event on their calendar. The email says who asked and suggests what to check before calling: saved homes, recent activity, notes.

Request a showing panel open over a property page, with a date picker, In Person and Video Chat options, Schedule Tour, and a Request Info form
Buyer: recorded. The buyer's side: each enquiry is listed in Updates, with when it was sent.
Agent: the alerts. The agent's side: alert settings for new leads, requested showings, inquiries and appointment requests, by channel. The page scrolls.
Agent: the email. An Appointment Action email: who asked, where to check the request, and what to prepare.
Agent: the calendar. The appointment lands in the calendar to confirm, with teammates' calendars alongside.
The Request a showing panel opens over the property page: pick a date and In Person or Video Chat to schedule a tour, or use Request Info to send a question.

Part three

The agent, in the app

08 / Lead routing

Who gets the lead.

New leads are assigned by rules, so nobody has to grab them by hand. Each agent, loan officer and listing agent has a status, a weight and a price range. The Advanced tab covers lead caps, reassigning a lead if nobody picks it up within a few hours, availability and pond routing.

Agents. Routing, Basic: status, weight and price range for each agent.
Loan officers. The same controls for loan officers.
Listing agents. The same controls for listing agents.
Advanced. Advanced: lead cap, reassign, auto-assign, availability, overflow and pond routing.
Routing, Basic: status, weight and price range for each agent.

09 / The lead list

The screen agents start their day on.

Why
When I talked to agents, the morning question was always the same: who do I call first? I put the answer in the row: last login, last touch, the next reminder, and counts for searches, favourites, saves and views, so they don't have to open each lead to find out.
Trade-off
That makes a dense row on a wide table. To keep it scannable, every column sorts on its own, and labels and pipeline stage sit as coloured chips under the name. On the phone, the row became a card.

Filters, saved filters, pipelines and labels live in the sidebar, and Mass Action handles many leads at once.

Leads. The lead list: contact, labels, price and city, registration, timeframe, last login and touch, next reminder, activity counts, and pipeline chips.
The lead list: contact, labels, price and city, registration, timeframe, last login and touch, next reminder, activity counts, and pipeline chips.

10 / The lead profile

Everything about one person.

Open a lead and the left side stays put: pipeline stage, labels, saved searches, and buttons to call, text, email or recommend a property. The right side holds the history in tabs. Activity opens first because it's the quickest way to understand someone: homes they viewed, the automatic note with their sign-up answers, and the emails they opened or clicked.

Activity. Activity: a property view, an automatic note, and an email with its opens and clicks.
Information. Information, Details: key information, assignment and user data. The page scrolls.
Reminders & plans. Reminder + Plans: reminders to notify an agent, and plans such as Attempted First Contact.
Secondary contacts. Secondary Contacts: a second person on the same lead.
Custom fields. Custom Field: fields a team adds for its own needs.
Activity: a property view, an automatic note, and an email with its opens and clicks.

11 / Communicate and plan

Email, texts, team chat and a calendar, inside the CRM.

All four were new. Before, conversations about a lead happened in other tools, so they never showed up in the lead's history. I kept each one close to something agents already use: an inbox with a reading pane, a texting thread, Slack-style channels for the team (we called it Hauschat), and a normal calendar with day, week, month and agenda views where you can overlay teammates' calendars.

Email templates show their open and click rates, so agents can see which ones work.

Email. Email: folders, a message list and a reading pane in one screen.
Templates. Template Manager: groups of templates with type, author, last edit and analytics.
Messages. Message: text conversations in a list and a thread, with Create New Message at the top.
Team chat. Hauschat: recent people, channels and direct messages, with a thread open beside them.
Week. Calendar, Week: a mini month, teammates' calendars, and the week's events.
Month. Calendar, Month.
Day. Calendar, Day.
Agenda. Calendar, My Agenda: events as cards with time, link, notes and attendees.
Email: folders, a message list and a reading pane in one screen.

12 / Automation

Automation agents can actually follow.

Why
This took the most time. Automation had grown piece by piece, and agents couldn't tell what was already going out to a lead. I reorganised it by what starts a message: something the lead did (behavioural messages), a sequence over days (AutoTracks), or a plan an agent runs. Each has its own screen, and the lead profile shows which ones are running for that person.
Trade-off
We capped behavioural messages at one a day, and one of each type every two weeks. Some triggers won't fire because of that. I'd rather that than a lead getting five texts in one afternoon.

Building an AutoTrack takes four steps: pick a template, edit each day's emails, texts and reminders, set what starts and stops it, then review the whole thing before saving.

Behavioural messaging. Behavioural Messaging: general and pipeline behaviours, each with a switch and its text and email versions.
AutoTracks. AutoTracks: active and paused sequences with open and click rates, leads, completed, touches and steps, expandable per lead.
Live plans. Live Plans: the plans running now, by lead, with their progress.
Plan templates. Plan Templates: reusable plans with status, author, actions and last edit.
1 · Choose. Step 1, Select template: templates grouped by lead type. The page scrolls.
2 · Edit. Step 2, Edit Template: lead type, sending hours, and each day's emails, texts and reminders.
3 · Triggers. Step 3, Adjust Settings: what starts it, what stops it, and what happens when it completes.
4 · Review. Step 4, Review & Finalize: the campaign at a glance before saving.
Behavioural Messaging: general and pipeline behaviours, each with a switch and its text and email versions.

13 / Oversight

The manager's view.

Why
How the numbers were shown was my call. A broker mostly wants to know which agents need help, so Launchpad leads with tasks and reminders due and a pipeline table by agent, with lead trends and top cities and sources beside it.
Trade-off
I stuck to bars, lines and a pie for sources, nothing fancier. Most numbers open the list of leads behind them, so a figure always leads back to people.
Launchpad. Launchpad: reminders and tasks due, lead trends, top cities and sources, and the pipeline by agent. Figures are sample data.
Lead trends. Lead Trends: registrations by week, and leads by channel over several periods. Figures are sample data.
Call summary. Call Summary: each agent's last login, leads, calls and voicemails.
Call detail. Opening an agent shows their leads, each with pipeline stage, activity and the latest note.
To-dos. To-dos: reminders and tasks due per agent, for a chosen view, plan and date range.
Launchpad: reminders and tasks due, lead trends, top cities and sources, and the pipeline by agent. Figures are sample data.

14 / On the phone

The same leads, between showings.

Why
Agents spend most of the day in cars and in other people's houses. The iOS and Android apps are for acting on leads: see who to call, open them, call.
Trade-off
The desktop table doesn't fit a phone, so each lead became a card that keeps the four activity counts. Everything else is one tap away in the profile.
Hausleads mobile app: the Launchpad screen
Launchpad. What to do now: new leads to call, follow-ups due today, appointments, then tasks, pipeline and statistics.
Hausleads mobile app: the Leads screen
Leads. Each lead is a card with labels, price, city and the same four activity counts as the desktop row.
Hausleads mobile app: the Lead profile screen
Lead profile. Source, pipeline, contacts and saved searches, with Call, Text, Email and Note fixed at the bottom.
Hausleads mobile app: the AutoTracks screen
AutoTracks. Each sequence running for this lead, with its status and progress.
Hausleads mobile app: the Plans screen
Plans. The plans running for this lead, and whether each is pending or done.

15 / Outcome

Launched in 2023.

2022–23From the first map to launch
7People on the team; I was the only designer

Stonehaus launched Hausleads in 2023. Feedback from agents in the first month was good: they found it easier than the platform they'd been using. We didn't publish usage numbers, so I'm not quoting any.

16 / Learnings

What I'd do again.

  • Keep context attached. Notes and history belong to the person or home they're about. Both sides of this product got better every time we did that.
  • Decide what each screen is for. Lists and dashboards are for scanning; profiles are for reading. Dense screens are fine once that's clear.
  • Give every step an obvious next one. Saving, comparing, asking, following up: if one of them has no clear place, people stop there.
  • Draw the map first. The two IA diagrams gave seven people one picture of the product, and saved a lot of arguing later.

Good ideas start with a conversation.

Start a conversation

Away from the keyboard. I reply within a day.

Back to top