Frontier
MatchMaker AI
Matches a buyer's stated budget, configuration and commute to live inventory, and says plainly when nothing in the book fits.
Match requests
9,120
Twelve-week shape, pilot window
Matched to stock
72%
At least one unit inside budget
No-fit outcomes
28%
Recorded, not hidden
Match → visit
24%
+7 pts vs manualTwelve-week shape, pilot window
Why matches fail
A no-fit is a product signal. Eleven hundred buyers wanting stock below our entry price is the clearest gap in the portfolio.
Ranked by requests
Top rows from the table below, largest first
Read off the same table, sorted so the concentration is visible. Ties are ordered as they appear in the register.
Match quality by budget band
| Budget band | Requests | Matched | Median options | Visit rate | Booked |
|---|---|---|---|---|---|
| Under ₹60 L | 1840 | 18% | 1 | 9% | 6 |
| ₹60 L – ₹1 Cr | 2610 | 68% | 3 | 21% | 34 |
| ₹1 – 2 Cr | 2980 | 92% | 6 | 28% | 88 |
| ₹2 – 4 Cr | 1180 | 89% | 5 | 31% | 61 |
| Above ₹4 Cr | 510 | 74% | 2 | 26% | 30 |
What the misses are telling us
Eighteen hundred requests, an eighteen per cent match rate. Either stop buying that demand or add an affordable partner.
Leadership · this quarter
Six hundred and twenty matches failed on geography alone. That is money spent on buyers we cannot serve.
Growth · immediate
How to read this page
Frontier · MatchMaker AI
Window
Rolling 90 days of the India Realty pilot, refreshed nightly at 02:00 IST.
Sources
Aiera call logs, WhatsApp Business API, CRM stages, Meta and portal spend exports.
Joins
Every number is joined to a booking where one exists, not to leads, so cost lines stay comparable.
Limits
Ninety days is short for a ₹1.5 Cr purchase. Late-window cohorts are still open, so treat conversion as a floor.