Skip to main content
29M UK properties, one API call. Get an API key →
Customer stories / Property CRM

CRM Providers

How the platform cut property setup time from 15 minutes to 90 seconds

1,400 estate agents manually typing property details into CRM. A 23% error rate. Nine API calls changed the product entirely.

90 sec
Property setup time, down from 12–15 minutes
2.1%
Data error rate, down from 23%
+26 pts
Customer NPS, highest in company history
Industry
Property CRM
Company size
1,400 estate agency users · 180 branches
Products used
Address Match · Address Retrieve · Property Record · EPC

The challenge

The crm platform was built for estate agents who needed a clean, professional way to manage instructions from instruction to completion. Over four years, they'd grown to 1,400 users across 180 branches. The product worked. But one workflow had never been properly solved: adding a new property instruction.

When an agent took on a new instruction, they'd open a new property record in the platform and begin typing. Address. Bedrooms. Property type. Floor area. Tenure. Council tax band. EPC rating and score. Each field had to be populated manually, from memory or from the vendor's paperwork. For experienced agents working quickly, the setup took 12 minutes. For newer team members still finding their way around the system, 15 wasn't unusual.

The error rate was the deeper problem. A 23% data error rate (discovered through an internal audit that cross-referenced CRM entries against Land Registry records) was causing downstream failures across the business. Property portal exports with incorrect floor areas. Compliance reports with wrong EPC ratings. Marketing emails with the wrong bedroom count. Every error that escaped into production created remediation work somewhere else in the business.

Priya Nair, CPO, had been tracking NPS for three years. The manual entry workflow was consistently cited in detractor feedback. The fix was obvious: auto-fill from a reliable data source. The question was finding an API that covered all the fields at a cost that made sense at scale for a CRM that charged per-user SaaS pricing.

"Property intelligence auto-fill went from a nice-to-have to our most-talked-about feature in three months. It didn't just improve data quality: it changed how agents feel about using our product."

CPO

The solution

Nine API calls on address selection. Bedrooms, property type, floor area, tenure, council tax band, EPC rating and score, all auto-filled before the agent has moved to the next field.

the platform built the auto-fill feature as a four-step pipeline triggered by address selection in the instruction creation form. As soon as an agent selects an address from the autocomplete dropdown, the pipeline fires in the background, the agent sees nothing but a brief loading state before the form populates.

Step one is address resolution: submit the complete address and postcode to /address/match/. A successful match costs 5 tokens and returns the address-level retrieve body plus address_resolution. HTTP 422 no_match or multiple_matches is never charged. Use the matched UPRN for the property record and EPC calls.

The property record (/properties/{'{uprn}'}/) returns bedrooms, property type, floor area, tenure, and council tax band. The EPC endpoint (/epc-checker/{'{uprn}'}/) returns the current energy rating (A–G) and efficiency score. Together, they populate every key field in the instruction form.

The impact was immediate and measurable. Data errors dropped from 23% to 2.1%. Setup time fell from 12–15 minutes to under 90 seconds. NPS improved by 26 points: the highest score in Their four-year history. In the three months after launch, auto-fill was cited as the number one reason for new sign-ups in post-sale surveys. Among the 1,400 users who used the feature, churn in the 6 months post-launch was zero.

Address match 2 tokens
Browser address widget

Autocomplete from typed address. Returns suggestions with UPRN. 36M UK addresses.

Address retrieve 5 tokens
/api/public/address/retrieve/

Full Royal Mail formatted address and confirmed UPRN for the selected result.

Property record 1 token
/properties/{'{uprn}'}/

Bedrooms, property type, floor area, tenure, council tax band, lat/lng. Auto-fills 5 form fields.

EPC data 1 token
/epc-checker/{'{uprn}'}/

Current energy rating A–G and efficiency score. Auto-fills EPC fields. Always current: never stale.

Total: 9 tokens

Address match (5) + property record (1) + EPC (1): 7 tokens on success. All completing before the agent has moved to the next field.

The results

90 sec
Property setup time, down from 12–15 minutes
2.1%
Data error rate, down from 23%
+26 pts
Customer NPS, highest score in company history
Zero
Churn among users who activated auto-fill in 6 months post-launch

Integration

The matching pipeline runs server-side: submit the address and postcode once, handle 422 no_match or multiple_matches without a charge, then use the successful match’s UPRN for property record and EPC calls. Keep the API key on the backend. The browser widget remains available for typeahead forms.

"Property intelligence auto-fill went from a nice-to-have to our most-talked-about feature in three months. It didn't just improve data quality: it changed how agents feel about using our product."

Read more customer stories

See how estate agents, proptech platforms, surveyors, and mortgage brokers use Homedata.

All customer stories →

Get your API key

Pay as you go: 100 tokens = £1, first top-up matched 100%. Build your own property auto-fill in a day. The full pipeline is 9 tokens.

Get an API key

Pay as you go · No subscription needed · Bonus tokens with an optional monthly subscription