Beachfront residences
Meta ad, form
- 09:14:02
Ad form received
- 09:14:03
First WhatsApp message sent
- 09:14:05
Duty rotation: next agent up
- 09:15:47
Agent replied in the conversation
OwnerAgent on duty
Homebuilders and developers
The ad delivers the lead.What happens next, nobody measures.
Homio keeps the whole lead journey in one place: where it came from, who answered, what was proposed and why it closed or did not. No spreadsheet, no personal WhatsApp and no separate system for each piece.
Running today at a developer with seven projects on sale at once, over a thousand agents and partner brokerages on file and hundreds of ad leads a week.
Lead journeyall recorded
Ad
Campaign, ad and project
Agent
Next in the rotation, in seconds
Proposal
Unit reserved, instalments and contract
Outcome
Won, or lost for which reason
The lead goes through five systems, and none of them talk
The ad platform knows what the click cost. The form knows the name. The agent knows what was said, on their own phone. The sales manager knows who has whom, in her spreadsheet. And the proposal lives in a system the CRM has never seen. Every piece is right, and nobody has the whole.
Where the lead goes today
Ad dashboard
Clicks and cost per lead
Form and WhatsApp
Where the lead came in
Agent’s phone
Where the conversation happens
Manager’s spreadsheet
Who has whom
Proposal system
Which the CRM cannot see
What lives in one placeHomio
- Where each lead came from, stored on it until the sale
- Who answered, how fast, and whether the owner changed
- The proposal, the reserved unit and the contract
- The full history, and the reason for every loss
It is not a lack of tools. It is that five good tools do not add up to control. The lead journey needs to exist in one place, and that place is what this page shows.
Four stretches of the journey where control slips
None of them is a lack of effort from the team. They are the four points where the lead changes systems, and that is where the data gets lost. The page covers each one, in order.
You pay for the lead and lose the trail
The ad dashboard says how many leads it delivered. The pipeline says how many sales came out. Nobody can say which ad produced which sale, and marketing and sales argue looking at the same lead with two numbers.
The lead waits, and the owner changes unseen
A lead that waits goes cold. And the contact who comes back six months later through another ad lands with another agent, and the commission becomes a fight.
The proposal lives outside the CRM
The unit, the instalments and the contract are done in another system, or by hand. The deal in the pipeline knows neither the value nor the real stage of the negotiation.
The agent leaves and takes the book of clients
The conversation is on the phone of whoever answered. When that person leaves, the history leaves with them. And the loss reason is spelled so many ways that the report never adds up.
From ad to lead: whoever pays knows what they bought
Every lead comes in with its source stored on it: the source, the campaign, the ad, the project and the point it came through. Ads, website, printed material and WhatsApp, all by the same path. The source travels with the deal to the sale stage, so the question "which ad sold last month" has an answer, with no spreadsheet.
Adform or WhatsApp
Leads from the Meta form and from the WhatsApp button arrive with campaign and ad identified, and the project is inferred from the ad.
Website and landing pageform
It is the form that says which project, not the page address. Every form is born knowing which product it speaks for.
Printed material and direct WhatsAppQR and link
Hoarding QR codes and flyer links come in with the prefilled text that identifies the piece. That text is what makes the lead born with the right source.
What the record keeps
- Source, medium and channel, in three fields the report filters on
- Campaign and ad, named the way the Meta dashboard names them
- Project, inferred from the ad or the form
- Conversion point: form, WhatsApp, QR or phone call
At one developer, the Meta dashboard reported 322 conversions in a fortnight and the CRM counted 345 leads from the same ads. It is the same number seen from both sides, with the difference explained. Before the source was stored, 974 of 1,541 leads in a month were born not knowing where they came from.
What already came in without a source gets one too: at the same developer, 911 deals from two months received their source afterwards, with no errors and without touching stage or owner.
From lead to agent: the right one, right away, and the owner does not vanish
The moment the form comes in, the lead gets its first WhatsApp message and drops into the rotation of that project’s duty roster. One pipeline for every launch, segmented by project instead of one pipeline per product, so the same automation serves all of them. And a contact who returns through another ad does not switch agents by accident: every change of owner is recorded, with who changed it and when.
At a developer with seven projects on sale, 97 to 211 leads a week go through distribution. An audit over 30,000 deals showed that 29% of leads belong to a contact that already had a deal, and it was the history that showed when and to whom the owner had changed.
DealJust in
- Returning contactKept the agent from April
- Website leadDuty rotation: next agent up
ProposalTower 2, apt 1204
Unit
Tower 2, apt 1204
ReservedValue
R$ 1,240,000
Instalments
- Depositat signingR$ 124,000
- 24 monthlyof R$ 8,500R$ 204,000
- HandoverfinancingR$ 912,000
Approve proposal
On approval
- Deal moved to the Proposal stage
- Value stored on the deal
- Financial clause with the SPV account
- Contract draft generated
From agent to proposal: the unit, the instalments and the contract come out of the CRM
The proposal is born inside the deal. The agent picks the unit, which is reserved on the spot, sets up the instalments for deposit, monthly payments and handover, and sends it. Approval does the rest on its own: it moves the deal to the proposal stage, stores the value, builds the financial clause with the bank account of that project’s SPV and leaves the contract draft ready. If it is declined, the unit becomes available again.
In one real approval, the deal went from zero to R$ 4 million, at the right stage and with the right SPV bank account, in under a minute. Nobody typed the value into the CRM.
From proposal to outcome: won, lost for which reason, and the book stays
The WhatsApp conversation, the visit note, the call and the proposal stay on the client record, which belongs to the company. An agent who leaves takes nobody, and whoever takes over sees what was agreed. And when the deal closes or is lost, the reason is picked from a list with a single spelling, so the loss report adds up.
At one developer, 5,000 WhatsApp conversations sit in the company inbox. And 15,835 lost deals with 145 different reasons became a list of 124, without deleting any: "does not answer contact attempts" was the most common reason, with 3,093, and it was spelled more than one way.
Client recordBuyer of apt 1204
- WhatsApp12 days ago
"Can I visit the show flat on Saturday?"
- Visit note9 days ago
Liked the 3-bedroom plan, found the parking tight
- Call6 days ago
6 min, asked for a simulation with a smaller deposit
- Proposal2 days ago
Sent, unit 1204 reserved
Loss reason
Does not answer contact attempts
- Stopped replying
- No interest right now
- Bought from a competitor
The people who implement are the people who answer
Many builders buy a CRM and never manage to use it, because the tool arrives and the team is left alone with it. Here the rollout is accompanied until the team is using it, and support comes from whoever built the integration, not from a desk that opens a ticket.
SupportWhatsApp
Sales manager
I exported the August leads and the Source column is empty on several. Checked one by one, screenshots attached.
7 screenshots08:41
Homio
Checked all of them. The empty ones came in before the 19 Aug deploy; the later ones are filled. Sent you the sheet with each date.
09:15
Homio
One case was a real defect: the first-message phrase was missing from the map. Fixed and live.
11:02
Answered the same day
Rollout alongside your team
Pipeline, fields, rotation and automations set up with the people who will use them, on the projects on sale right now, not on a generic template.
Answers with data, not with "we will check"
At one developer, the sales manager checked an export field by field, in 18 messages and 7 screenshots. All seven questions were answered with data the same day, and one of them became a fix in production.
Change without stopping the operation
When the notes automation changed technology, the operation did not stop for a day: the new one ran beside the old one until it was validated with a real lead.
And the rest of the sales operation comes with it
The lead journey is what this page shows. Underneath it is the whole platform, in the same place.
Official WhatsApp in the same inbox
The conversation stays on the client record, not on the phone of whoever answered.
Show flat visit reminders
Confirmation the day before and a heads-up hours ahead, on WhatsApp, without the agent remembering to send it.
Follow-up tasks by stage
A lead who owes a reply becomes a task with a deadline in the agent’s hands, and disappears when they answer.
Material sent when the stage changes
Price list, brochure and specification go out on their own when the deal moves forward, no file hunting.
Calendar with agent rotation
A visit booked by the lead lands on the next agent up, with the right duration for each project.
Dashboard by project and by agent
How many came in, from where, who answered and how far they got, with no spreadsheet.
Bring your projects to the conversation
Forty-five minutes with the people who implement. You show where the lead comes in today and where it gets lost, and we tell you what can be connected, in what order and how long it takes.
Want to see pricing first? The plans are here.Loading times…