Services

Product

Tools

Resources

Thinking

ESCAEN
Let's talk
Product · Home buying

A property CRM on the buyer's side

Portals show the house. Nobody keeps its history.

A CRM for the person buying a home—or for the agency helping them: every listing with its status, its price history, its fit score and its checklist. What the portals don't offer because they don't work for the buyer.

Status today Seed

An idea validated by hand on two real searches. There's no product yet: it'll be built when there's a distribution partner, and not before.

Who it's for
Buying agencies and buyers with a long search on their hands
Base
The relationship engine
What happens today

Three things people say quietly.

  1. ‘Price reduced’, but no history.

    The portal alerts you and doesn't keep anything. You discover the reduction by looking again, and nobody has the history of what that house has done since it came on the market.

  2. The same house with three identities.

    Every portal and every agency calls it something different, they disagree on the basic details and sometimes place it on another street. Small agencies don't even have a reference.

  3. Listings lie a little.

    Recreated photos, gross floor area sold as usable, habitability certificate ‘in progress’, unauthorised building work. And the filters that decide—commute time, mortgage viability, flood risk—don't exist.

The idea

The buyer is the only one who sees the whole search. Let the record be theirs.

It was born from a real house hunt. The tracking system we set up by hand—a status per listing, a fit score, a risk column and our own price history—was already a CRM. What didn't exist was the software: identity resolution across portals and a record per home that outlives the listing.

What's included

Every module, with its status.

Not everything here exists in the same way. Each piece carries the status it's in today, with the same criterion we use in a proposal: what hasn't run isn't presented as proven.

Designed
Exists as a prototype or as a manual process; not as software in production.
To be built
Doesn't exist. It's named in the future tense or not at all.

What was validated by hand

Every module existed as a process in two real searches. None exists as software.

  • Listing statuses New, still listed, price reduced, withdrawn, excluded. Designed
  • Own price history What that house has done since it came on the market, kept by the buyer. Designed
  • Fit and risk score From zero to a hundred, with the reason alongside. Designed
  • Checklist per home Photos, square metres, certificate, building work, occupancy. Before the viewing. Designed
  • Decision filters Time to two anchors at rush hour, financing viability, risk mapping. Designed
  • Data confidence What we know for sure and what the listing says. Designed

What needs building

  • Identity resolution The same house on three portals and one agency, as a single record. To be built
  • Record per home Outlives the listing and builds up what's learnt. To be built
  • Conversation with the agency The engine's inbox, centred on the home. To be built
What it doesn't do

Said before you ask.

The other products

What shares an engine with this one.

Seed · Home buying

Talk to us if you have an agency.

We're looking for a buying agency that wants to try it with its clients. If it's yours, write to us.