A better front-end for the CRM you already have
Built for agencies with three to thirty branches, whose CRM gave them a template website that looks like everyone else's. We read your listings from Reapit, Alto, Street, Rex or VaultRE, build property pages that rank on your patch, and write every enquiry back into the CRM against the right branch. Same on the app. The CRM stays; the front-end stops embarrassing you.
Illustration. Addresses and numbers are invented.
3–30
Branches
The agencies this is built for
Your CRM
Is the source of truth
We read from it. We never replace it.
Yours
Code, domain, data
In your accounts from the first commit
5 markets
CRM and portal standards
UK, Ireland, Australia, New Zealand, North America
Why the front-end costs you instructions
The CRM is usually fine. It is the website and app that came with it — or the one an agency built once and left — that loses the buyer, the vendor and the lead. Four things come up on almost every call:
The template site your CRM gave you
It came free with the software, it looks like every other agency on the platform, and the competitor in the next town has the same one. Buyers cannot tell you apart.
Your own listings rank on Rightmove, not on you
A search for "3 bed house in your town" finds the portal, not your site. The enquiry goes through the portal, the portal owns the relationship, and you pay for the lead you generated.
Slow on a phone, where every buyer is
Template sites load a whole CRM widget to show one property. Buyers on a train do not wait. The listing page is the one page that has to be fast.
Leads that do not reach the CRM
Valuation requests in an inbox, viewing requests in another, nobody sure which negotiator picked up which. The lead should land in the CRM against the right branch, automatically.
Three things, in the order an agency notices them
Listings that arrive on their own, pages that rank on your patch, and enquiries that land in the CRM against the right branch. The CRM you already run stays the source of truth throughout.
Listings from your CRM, automatically
Every property, branch, negotiator and status is read from the CRM through its API and kept current — a new instruction is on the site within minutes, a sold one comes off. Nobody re-keys anything, and the CRM stays the only place data is edited.
Property and area pages built to rank locally
One fast, indexable page per listing and per area, with the structured data search engines read, so a search for a street or a postcode can find you and not only the portal. The listing page is the one page that has to be fast, so it is server-rendered with no CRM widget in the way.
Branch pages, and leads back into the CRM
Each branch with its own page, its own listings and negotiators, and its own Google Business Profile link. Valuation requests, viewing requests and enquiries are written into the CRM against the right branch and property, with the source recorded, so the inbox stops being the system.
Three small uses, each with a person in the loop
Not a valuation robot and not a chatbot that promises viewings it cannot book. Three jobs where a model saves a negotiator an hour, every draft reviewed before it goes anywhere, and the CRM record always the source of truth.
We do not train models. We wire one into your workflow where it is worth the review.
Each of these is optional, priced on its own, and switched off by default. If an agency wants none of them, the site and app work exactly the same. If it wants one, it lives behind the same login and writes to the same CRM as everything else.
Listing copy from the CRM fields
A first draft of the description from the facts the CRM already holds — beds, baths, EPC, tenure, features — for the negotiator to edit. It saves the blank page; it does not publish unreviewed.
Enquiry routing
Incoming enquiries classified — valuation, viewing, general, spam — and assigned to the right branch and negotiator in the CRM. A human still replies; the model only sorts.
Area guides that stay current
Drafted from your own sold data and public sources, reviewed by you before they go live, refreshed on a schedule you set. Labelled as a guide, never as a valuation.
From the CRM record. Nothing re-typed.
A three-bedroom semi-detached house with a private garden and off-street parking, offered freehold. Close to excellent schools Five minutes' walk from Didsbury village. EPC rating C.
Illustration. Property and names are invented.
Which systems your market actually uses
There is no MLS outside North America. Listings live in the CRM and go to the portals from there; the site reads from the CRM. Same product, different plumbing — we build to whichever yours uses.
United Kingdom & Ireland
Reapit Foundations API · Alto (Zoopla) API · Street.co.uk API · Dezrez Rezi API · Jupix feed · Rightmove Real Time Data Feed · Zoopla listings API · OnTheMarket feed · Daft.ie and MyHome.ie feeds (IE)
Australia
Rex API · VaultRE API · AgentBox API · Box+Dice · REAXML into realestate.com.au and Domain
New Zealand
Trade Me Property API · realestate.co.nz feed
United States & Canada
RESO Web API (the current MLS standard) · RETS where an MLS still runs it
What an agency site or app actually talks to
API, GraphQL and feed integrations only — every name here has a documented interface we build against. Market in brackets where a system is regional.
Listings and CRM
The source of truth. Listings read from here, leads written back.
- Reapit Foundations API (UK)
- Alto API (UK)
- Street.co.uk API (UK)
- Dezrez Rezi API (UK)
- Jupix API (UK)
- Rex API (AU)
- VaultRE API (AU)
- AgentBox API (AU)
- Box+Dice API (AU)
- RESO Web API / MLS (US, CA)
- HubSpot
- Salesforce
Portals, outbound
Where a listing must be pushed to a portal from outside the CRM.
- Rightmove Real Time Data Feed
- Zoopla listings API
- OnTheMarket feed
- Daft.ie feed
- MyHome.ie feed
- REAXML → realestate.com.au, Domain
- Trade Me Property API
Maps, location and property data
Where it is, what is nearby, what it is worth.
- Google Maps Platform
- Mapbox
- what3words API
- Ordnance Survey Data Hub (UK)
- HM Land Registry Price Paid (UK)
- PropertyData API (UK)
- CoreLogic API (AU, NZ)
- Domain API (AU)
- ATTOM API (US)
- Get Information About Schools (UK)
- TfL Unified API (UK)
Media and tours
The listing page is the product; the media is most of it.
- Matterport API
- YouTube / Vimeo APIs
- Cloudinary
- imgix
Viewings, referencing, payments and mortgage
Sales viewings, lettings applications, deposits, rent, and the affordability question.
- Inspect Real Estate API (AU)
- Calendly / Cal.com
- Goodlord API (UK)
- Stripe
- GoCardless (UK)
- Twenty7Tec API (UK)
- Acre API (UK)
Identity, AML and signatures
Agents are regulated for money laundering; the check has to be in the flow.
- Thirdfort API (UK)
- Credas API (UK)
- Onfido
- Sumsub
- Yoti
- DocuSign
- Adobe Sign
- Signable (UK)
Communication
Reaching the buyer or tenant where they are, and logging it.
- Twilio
- WhatsApp Business API
- Postmark
- SendGrid
- Intercom
- Slack and Teams webhooks
Mobile apps
The pieces every agency app needs and none should build from scratch.
- Firebase (auth, push, crash)
- Apple Push Notification service
- OneSignal
- Sign in with Apple and Google
- Branch deep links
Analytics and marketing
What worked, by branch, by source.
- GA4 Measurement Protocol
- Google Tag Manager
- Meta Conversions API
- Google Ads API
- Mailchimp API
- Brevo API
Search and performance
Thousands of listings, filtered in under a second.
- Meilisearch
- Algolia
- Elasticsearch
- Redis
- PostgreSQL + PostGIS
Not on the list? If it has a documented API or feed specification, it is a scoping question. If it does not, we say so on the call rather than promise it.
Boring, fast, yours
Nothing exotic. A stack we have run for years, chosen so a listing page loads fast on a phone and so any competent developer can take it over from you later.
What agencies ask first
The questions that come up before anyone books a call — which CRMs we can read from, what happens to the site you have now, and who owns what when it is done.
No — that is the point. The CRM stays exactly as it is and stays the source of truth. We read listings from it through its API and write leads back into it. Your negotiators change nothing about how they work.
Bring your CRM and the site you have now
Twenty minutes. We look at both, tell you what the CRM's API can and cannot give you, and quote a scoped build — not a monthly package.