A regional brokerage group · $8K → $52K platform MRR.

The archetype represents a pattern we ship into reliably in residential real estate: a regional brokerage group with nine offices and roughly 140 agents across a mixed sales-and-lettings book, run by a second-generation managing broker who knows the group's technology is the thing capping it. Pre-engagement state: every listing hand-entered twice — once into the regional MLS, once into a decade-old WordPress site — viewing requests arriving by phone and inbox, agent follow-up living in spreadsheets, and a thin internal "platform" the group half-licensed to two friendly partner brokerages for $8K MRR combined, held together by one overworked in-house developer.

The group's ambition was specific: stop being a brokerage with a website and become the brokerage whose platform other regional offices license. The raw material was there. The MLS membership gave them clean, authoritative listing data they were ignoring in favour of manual re-entry. The nine offices gave them a built-in first tenant cohort for anything multi-office. And the two partner brokerages already paying for the old platform proved regional operators would pay for shared listing infrastructure — if it stopped embarrassing the agents using it.

What they didn't have was software. The old platform pre-dated the RESO standards era, so listing data flowed in by hand. Search was a paginated filter list with no map. Viewing scheduling was a phone number. And there was no CRM at all — a viewing request that arrived on a Friday evening had a coin-flip chance of ever being answered. The in-house developer knew all of this; what the group lacked wasn't diagnosis but delivery capacity, which is the honest shape of most brokerage-platform engagements we take on.

Three structural problems compounded the ceiling. First, the double-entry tax: getting a property live took an average of 45 minutes of manual work per listing — re-typing MLS fields, resizing photos, fixing whatever the WordPress editor mangled — multiplied across roughly 90 new listings a month. Agents did the maths and simply stopped bothering; a third of the group's inventory never made it to their own site at all, which meant the group was paying to send its own buyers to national portals.

Second, the demand side leaked. Listing pages converted views to viewing requests at 2.1 percent. Buyers and tenants couldn't search by area on a map, couldn't see what was near a school or a station, and when they did want a viewing, the call-to-action was a phone number answered during office hours. Every viewing that did get booked cost two to four phone calls of back-and-forth between applicant, agent, and — for tenanted properties — the current occupier.

Third, the licensing story had no product under it. The two partner brokerages paying into the $8K MRR were buying goodwill, not software; churn was a renewal-dinner conversation away. Charging real money to real third-party offices meant multi-tenancy, per-office billing, and an onboarding path that didn't require the in-house developer to hand-configure every new office. None of that existed. The engagement brief we scoped against was blunt: kill the re-keying, fix the funnel, and make the platform licensable — in that order, because the feed is what makes everything downstream trustworthy.

Workstream 1 · RESO Web API feed sync. Manual entry was replaced with a scheduled replication service against the regional MLS's RESO Web API — Data Dictionary field mapping, delta polling on modification timestamps every 15 minutes, media replication with responsive image derivatives, and a nightly reconciliation job that flags drift between MLS truth and platform state. A listing now lands on the platform pre-populated; the agent's remaining 6 minutes are enrichment — photo ordering, a description pass in the group's voice, and viewing-slot rules. Average time-to-list fell from 45 minutes to 6, and the third of inventory that never used to reach the site now ships automatically.

Workstream 2 · Map-first search UX. Search was rebuilt around the map instead of the filter list, on Google Maps Platform: clustered markers that resolve to price pins on zoom, draw-your-own-boundary search, school and transit layers, and saved-search alerts keyed to map areas rather than postcode strings. Listing pages went server-rendered and Core Web Vitals-clean — LCP under 2 seconds on mid-tier mobile, layout shift pinned at zero with explicit media dimensions — because a search experience that stutters on a phone loses the applicant before the viewing button exists.

Workstream 3 · Automated viewing scheduling. The phone number was replaced with self-serve booking: viewing slots derived from agent calendars and per-property rules (tenant-notice windows for occupied lets, open-house blocks for launches), instant confirmation with calendar invites, reminder sequences at 24 hours and 2 hours, and a no-show recovery flow that offers the next available slot. Combined with the map-first rebuild, listing-view to viewing-request conversion moved from 2.1 percent to 6.8 percent — and each booked viewing stopped costing the front desk three phone calls.

Workstream 4 · Lightweight brokerage CRM. Every viewing request now auto-creates a lead — source, listing, applicant details, stage — in a purpose-built brokerage CRM deliberately smaller than the enterprise suites agents refuse to open: pipeline per office, follow-up nudges when a lead sits untouched for 48 hours, viewing-feedback capture on the agent's phone in the car outside the property, and a weekly digest to each managing broker. Friday-evening enquiries stopped dying in inboxes; the group's own measure of "leads with a first response inside 4 hours" went from roughly half to 96 percent.

Workstream 5 · Multi-tenant licensing. The internal build became a licensable product: tenant-isolated data with per-office theming, seat-and-office billing on Stripe, a self-serve onboarding path that connects a new office's MLS credentials and branding without engineering time, and an admin plane for the group to manage tenants. This is the SaaS-development half of the engagement — the two goodwill licensees were migrated first, then the platform sold on its own terms. Platform MRR climbed from $8K to $52K across 18 months (6.5x), with month-12 logo retention at 88 percent.

The pattern this archetype represents (a regional brokerage group with 5 to 15 offices, mixed sales and lettings, MLS membership it under-uses, a listings workflow held together by re-keying, and an ambition to license its platform to peer offices) is one of the most repeatable engagement shapes in our real-estate software development practice. The 22-week timeline holds steady; the workstreams compress or expand in the same proportions; the metrics typically land within plus or minus 20 percent of the archetype numbers.

Five capabilities transfer directly: RESO Web API feed sync with reconciliation (the feed is the foundation — nothing downstream is trustworthy without it), map-first search UX with Core Web Vitals discipline, automated viewing scheduling with occupier-aware slot rules, a lightweight brokerage CRM that agents actually open, and multi-tenant licensing infrastructure with per-office billing. The same sequence — feed first, funnel second, licensing last — also transfers to lettings-only operators, commercial brokerages on RESO-adjacent data sources, and new-build developers syndicating inventory.

The five headline numbers on this page — $8K to $52K platform MRR, 6.5x, viewing-request conversion 2.1% to 6.8%, month-12 logo retention 88%, and time-to-list cut from 45 minutes to 6 — are the archetype's canonical pillars; you'll find the same five on our real-estate industry page, deliberately identical, because a case study and its industry page quoting different numbers is how trust dies. Every proptech engagement starts with a 30-minute discovery call. Scope, timeline, and budget come back in writing within 48 hours.