Concept case studyReal Estate
From listing enquiries to a pipeline every agent can see.
How NairobiX would connect enquiries from portals, social media, WhatsApp and referrals into one pipeline organised around properties as well as people.
Concept engagement — illustrative scenario, not historical client results.
Is the 2-bedroom in Kileleshwa (ref KL-204) still available?
Saturday · 8:40pm
Yes — KL-204 is available from the 1st. Viewings this week: Tue 4pm, Thu 10am. Brian will confirm.
Automated · unit details from listing
- Prospect
- Enquiry via portal → WhatsApp
- Agent
- Brian O.
- Move-in
- Within 4 weeks
- Viewing
- Tue 16:00
- Industry
- Real Estate
- Focus
- Lead-to-sales system
- Reading time
- 9 min
02The context
A business that works — up to a point.
Consider a Nairobi property agency handling lettings and sales for residential developments and individual landlords. Listings appear on property portals, the agency's social accounts, signboards and its own website.
A prospective tenant typically enquires about a specific unit — often on WhatsApp, often in the evening or at the weekend — and is usually talking to several agencies at once. Buyers take longer, involve family and financing, and need to be kept warm over weeks.
The agents work hard and many are excellent at closing. But each agent runs their own enquiries on their own phone, and management's view of demand is whatever the agents report on Monday.
What already works
- A good inventory of listings
- Agents with real local knowledge
- Steady enquiry volume from portals and social media
- Relationships with developers and landlords
What the team manages by hand
- Copying portal enquiries into WhatsApp conversations
- Deciding which agent takes each enquiry
- Booking, confirming and re-confirming viewings
- Assembling activity updates for landlords by hand
03The problem
Not a lead problem. A system problem.
In property, interest is perishable and prospects compare agencies in parallel. The system problem is less about the number of enquiries than about speed, ownership and memory — and about a pipeline that has two dimensions, people and units.
Marketing
Listings are promoted on several portals and social accounts, with no view of which produce viewings.
Spend follows habit rather than results.
Capture
Enquiries land in portal inboxes, direct messages, agents' phones and the office line.
Evening and weekend enquiries wait until someone happens to notice.
Qualification
Budget, move-in date and requirements are asked inconsistently.
Viewings are booked for prospects who were never a fit, while good prospects wait.
Follow-up
After a viewing, the next step depends on the agent's memory.
Interested prospects drift to the agency that called back.
Sales
Deal status sits with individual agents.
Management cannot see which units are close to letting or selling.
Reporting
Landlords ask what is happening with their property; the answer is assembled by hand.
The agency cannot show the work it does — or learn from it.
Recognise some of this in your own business?
04The opportunity
The opportunity is to answer faster than competitors, keep every prospect attached to the right unit and the right agent, and give management and landlords a true picture of activity.
A pipeline that tracks only people loses the question landlords care about most: what is happening with my property? A pipeline that tracks only units loses the prospect who would have taken a different one. The design links the two.
Speed matters here more than in most sectors, because the prospect is comparing agencies in real time. The first priority is therefore the first hour after an enquiry, including evenings and weekends — without asking agents to be on call around the clock.
01
Attention
02
Capture (focus of this engagement)
03
Qualify (focus of this engagement)
04
Nurture (focus of this engagement)
05
Convert (focus of this engagement)
06
Deliver
07
Retain
08
Measure (focus of this engagement)
Where this engagement concentrates first, within the NairobiX growth system.
05The system design
The architecture, layer by layer.
The proposed architecture has eight layers, organised so that every enquiry is attached to a unit, an agent and a next step within minutes of arriving. Select a layer to see what it does and why.
- Why it exists
- So every enquiry arrives already attached to a unit and a source.
- What moves through it
- Unit reference, channel and campaign.
- What happens next
- Prospects enquire through the channel they prefer.
- Why it exists
- An enquiry held only on one agent's phone is invisible to everyone else — and lost if that agent is busy or leaves.
- What moves through it
- Contact details, unit reference, source and the first message.
- What happens next
- The enquiry is matched to its unit and assigned.
- Why it exists
- It answers both questions — who is this prospect, and what is happening with this property.
- What moves through it
- Prospect history, unit status, agent and stage.
- What happens next
- Each new deal is assigned to an agent.
- Why it exists
- Ownership decided by rule is faster and fairer than ownership decided by whoever saw it first.
- What moves through it
- Owner, and the time assigned.
- What happens next
- The agent qualifies the prospect.
- Why it exists
- So agents spend viewing time on prospects who fit — and can suggest other units to those who don't.
- What moves through it
- Qualification answers and fit.
- What happens next
- Qualified prospects are offered viewing slots.
- Why it exists
- Viewings are where letting decisions are made; no-shows waste the agent's most valuable time.
- What moves through it
- Viewing time, attendance and the agent's notes afterwards.
- What happens next
- After the viewing, a follow-up task is created.
- Why it exists
- So agents and management see the same picture, and stalled deals are visible.
- What moves through it
- Stage, expected close and loss reasons.
- What happens next
- Closed deals move to lease or sale administration; data flows to reporting.
- Why it exists
- It turns the agency's work into something landlords can see, and shows which channels produce viewings.
- What moves through it
- Enquiries, viewings, applications and outcomes.
- What happens next
- Marketing and pricing conversations with landlords are based on evidence.
Layer 01 of 08
Listings & campaigns
Portal listings, social posts and paid promotion, each carrying the unit reference and a tagged link or pre-filled WhatsApp message.
- Why it exists
- So every enquiry arrives already attached to a unit and a source.
- What moves through it
- Unit reference, channel and campaign.
- What happens next
- Prospects enquire through the channel they prefer.
Every business needs a different version of this architecture.
06Before / after
From a disconnected pattern to a connected one.
The same people and much of the same technology — organised as one system instead of several.
Before · current operating pattern
- Portal inbox emails
- Agents' personal WhatsApp
- The office phone line
- A listings spreadsheet
- Viewings in agents' own calendars
- Landlord updates written by hand
Every agent runs a private system. The agency has no shared memory.
After · designed future-state system
- 01Listings & campaigns
- 02Capture
- 03CRM: people + units
- 04Assignment
- 05Qualification
- 06Viewings
- 07Deal pipeline
- 08Reporting
Every enquiry attached to a unit, an agent and a next step.
An architectural comparison of operating patterns — not a record of measured results.
07The customer journey
One customer, through the designed system.
What the customer experiences at each step, and what the system does behind it. Names and details are illustrative.
What the customer experiences
What happens in the system
01
Discover
Customer
On a Saturday evening, a young professional sees a 2-bedroom apartment on a property portal.
System
The listing carries the unit reference and a WhatsApp link with a pre-filled message.
02
Enquire
Customer
She taps the link; the message already names the unit. She asks if it's still available.
System
A new conversation arrives on the agency's business number, not an agent's personal phone.
Agency · Business accountHi, I'm interested in KL-204, the 2-bedroom in Kileleshwa. Still available?
Yes, KL-204 is available from the 1st. Rent and deposit details are below. Brian, the listing agent, will be in touch to arrange a viewing.
Automated · from listing data
03
Capture
Customer
Within a minute she has the key facts — and knows a named person will follow up.
System
The CRM matches the reference, creates a deal linked to KL-204 and assigns it to the listing agent.
Deal · KL-204New- Source
- Portal → WhatsApp
- Unit
- KL-204 · 2-bed · Kileleshwa
- Agent
- Brian O.
- Next action
- Qualify · by Sun 10:00
04
Qualify
Customer
The next morning, Brian asks three questions: move-in date, budget, anything essential.
System
Her answers are recorded. She fits; he also notes a similar unit nearby, in case.
05
View
Customer
She books Tuesday at 4pm, gets a confirmation with a location pin, and a reminder on Monday.
System
The viewing is on the unit's schedule; the agent's day plan updates.
Viewing reminder sent · KL-204
Mon 09:00 · Automated
Reminder with location pin sent to prospect. Brian's schedule: 3 viewings Tue, including KL-204 at 16:00.
06
Follow up
Customer
The day after the viewing, Brian calls to answer her remaining questions.
System
A follow-up task was created automatically when the viewing was marked attended.
07
Convert
Customer
She applies. The next steps — documents, deposit, lease — are clear.
System
The deal moves to Application, then Let. The unit's status updates on every channel.
Lettings pipeline · this week
Viewing booked
RW-110 · 3-bed
KL-310 · studio
Application
KL-204 · 2-bed
Let
LV-022 · 1-bed
08
Deliver
Customer
Lease signing and handover follow a checklist; she knows whom to contact after moving in.
System
Handover tasks are created from the closed deal; her record is kept for future moves and referrals.
09
Measure
Customer
Her landlord receives a clear report of the activity on the unit.
System
Weekly reporting shows enquiries, viewings and lets by unit, agent and source.
Viewings by source · layout
Portal A
Instagram
Signboards
Referrals
Illustrative layout — not data
08The technology layer
Technology, chosen last.
The requirements — people linked to units, fast routing, scheduled messages and reporting per property — decide the stack. Much of it may already exist in the agency; the work is connecting it.
Proposed stack · example architecture
Each technology fills a capability the system design called for. Remove the requirement, and the tool goes with it.
CRM: Zoho CRM
Messaging: WhatsApp Business Platform
Social acquisition: Meta — Facebook & Instagram
Website: WordPress
- Business requirement
- System design
- Technology
CRM
Zoho CRM
CRM · Assignment · Pipeline · Reporting
Role
Contacts and deals, with a module for units so each deal is linked to a property.
Why it fits
Custom modules, assignment rules and workflow automation without custom software.
Messaging
WhatsApp Business Platform
Capture · Viewings · Follow-up
Role
The channel most prospects use to enquire and confirm viewings.
Why it fits
Connected to the CRM, it lets acknowledgements and viewing confirmations run from the record — with approved templates outside the 24-hour window.
Social acquisition
Meta — Facebook & Instagram
Listings & campaigns
Role
Promotion of featured listings, and the social channels where many enquiries start.
Why it fits
Where the audience already is; campaign links carry the unit and source.
Website
WordPress
Listings · Capture
Role
The agency's website and listing pages, where the site already runs on it.
Why it fits
No need to rebuild what works — listing pages gain viewing requests and WhatsApp entry points.
Illustrative technology choices for this concept scenario. They are not a record of a client implementation, imply no partnership with any vendor, and are not the only suitable stack.
09The automation layer
Rules first. Then workflows. Then automation.
Two workflows carry most of the load: the first hour after an enquiry, and the days around a viewing. Both end in a person.
- Process
- The sequence of work the business agrees to follow.
- Rule
- A condition written down — “if no reply in three days”.
- Workflow
- A rule connected to the actions it should cause.
- Automation
- The workflow running without anyone starting it.
- Technology
- The tools that carry it out.
New listing enquiry
- Trigger
A portal enquiry email, WhatsApp message or website form arrives.
- Rule
Identify the unit reference; if it's missing, ask the prospect which property they mean.
- Action
Create or match the contact, and create a deal linked to the unit.
- Notification
Assign to the listing agent — or the rota agent if they are unavailable — and notify them.
- Follow-up
Send an immediate acknowledgement with the unit's key facts and the agent's name.
- Human
The agent qualifies the prospect and offers viewing times.
- Measure
Record time to acknowledgement and to first agent contact, by source.
10Designed outcomes
What the system is designed to improve.
01
Fast, consistent first response
Every enquiry is acknowledged with real unit information — including evenings and weekends.
02
Clear ownership
Each prospect is attached to a named agent and a specific unit.
03
No lost weekend enquiries
Enquiries wait in a shared system with an owner, not on a phone nobody is checking.
04
Pipeline visibility per listing
Management can see which units are close to letting or selling, and which are stuck.
05
Better landlord reporting
Activity reports come from the same data the agents use.
06
Spend guided by viewings
Promotion decisions can be based on which channels produce viewings, not views.
07
Continuity when people change
An agent's prospects and history stay with the agency.
08
A foundation for more
Clean unit and deal data make further automation — and AI drafting from listing sheets — practical.
Design objectives the system is built around — not measured client results.
11Measurement framework
What we would measure.
No invented numbers — a plan for knowing whether the system is working, set before it is built.
Acquisition
- Enquiries by source and unit
- Where demand comes from, per listing.
- Cost per viewing
- Where paid promotion is used.
Conversion
- Enquiry → qualified
- Share of enquiries that fit the unit or another listing.
- Qualified → viewing
- Share that book and attend a viewing.
- Viewing → application or offer
- By unit, agent and source.
- Application → let or sold
- And the reasons deals are lost.
Operations
- Time to first contact
- Including out-of-hours enquiries.
- Viewing no-show rate
- Before and after reminders are introduced.
- Post-viewing follow-up
- Share of viewings followed up within a day.
Client
- Landlord reporting
- Reports delivered on schedule.
- Repeat and referred clients
- Tenants, buyers and landlords who return or refer.
System
- Unit match rate
- Enquiries automatically linked to the correct unit.
- Assignment exceptions
- Enquiries that needed manual routing.
12The human layer
Where people stay responsible.
Technology supports people who make decisions.
Property is a relationship business. The system handles speed and memory so agents can spend their time on the parts that close deals: judgment, trust and negotiation.
What the system does
- Automation acknowledges, routes, reminds and records.
- The CRM keeps every prospect attached to the right unit and the right agent.
- Reporting shows landlords and management what is actually happening.
What the team decides
- Which prospect to prioritise for a unit in high demand
- Negotiating price and terms with landlords, tenants and buyers
- Assessing applications
- Handling complaints and disputes
- When to call rather than message
13What we would build
One system, built in stages.
01
Strategy
Pipeline and qualification design, source tracking and the landlord reporting model.
02
Digital
Listing pages with viewing requests and WhatsApp entry points that carry the unit reference.
03
CRM
Contacts, deals and units, with assignment rules.
04
Automation
Acknowledgements, viewing confirmations and post-viewing follow-up tasks.
05
Analytics
Activity by unit, agent and source, and landlord reports from the same data.
06
Later phase
AI — later
Drafting replies from listing sheets for agents to review, once unit data is reliable.
Components of one system, built in stages and connected to each other — not a list of separate services.
In this scenario, the agency's advantage isn't more listings. It's being the agency that answers first, remembers everything and can show landlords its work.
14 · The next step
Your business probably has a different version of this problem.
Every business has a different starting point. The right system depends on your goals, requirements, customers, processes and existing technology.