Skip to content

Case Study — Real Estate SaaS Platform

From a One-Page Lead Form to a Multi-Tenant SaaS Powering Hundreds of Real Estate Sites

A single lead-capture landing page grew into a multi-tenant platform that provisions a fully hosted MLS website — domain, SSL and CRM included — in minutes, and scales horizontally across hundreds of tenant sites.

Model
Landing page → SaaS
New site live in
Minutes
Tenancy
Multi-tenant
Scaling
Horizontal
Cover image case study 3 landing page to saas
Client
Real estate technology company (US & Canada)
Industry
PropTech / Real estate software
Year
2023
Services
SaaS productization, Multi-tenant architecture, Server infrastructure & scaling, Front-end product design

We were hired to build one thing: a lead-capture landing page for a company selling software to real estate agents across the US and Canada. That page did its job. Then the next agent needed the same thing for a different territory. Then the next. Every agent, every service area, wanted a full MLS website — property search, live listings, an admin panel where their area's leads landed — and each one was a separate build.

01 — The Challenge

A New Bespoke Site for Every Agent Doesn't Scale

After shipping several buyer and seller sites, the pattern was obvious — and so was the problem. The same features and the same structure were being rebuilt by hand for every agent, each on its own server footprint.

  1. 01

    One site per agent, per area

    Every real estate agent and every service territory required its own separate website, its own admin panel, and its own deployment.

  2. 02

    MLS features aren't trivial

    Property search, continuously updated listings, and area-scoped lead routing to the right agent's inbox is real product surface — and it was being repeated for every tenant.

  3. 03

    Growth broke the server, not the product

    As the number of sites climbed into the hundreds, disk space, cron-job load and single-server limits turned into hard bottlenecks.

  4. 04

    Non-technical users, technical system

    Agents needed to change their own site's look and content on their own — without filing a support ticket or waiting on a developer.

02 — Our Approach & the Technical Journey

Productize the Pattern, Then Make the Platform Scale

We stopped treating each site as a project and started treating the whole collection as one product. That reframing drove two builds at once: a front-end system that provisions sites in a few clicks, and a back-end one that survives hundreds of tenants on shared infrastructure.

  1. Milestone

    Spot the common structure

    Across the buyer and seller sites we'd already delivered, the feature set and information architecture were nearly identical. That was the signal to productize.

  2. Milestone

    A master admin that ships sites

    We built a control panel where the client adds a domain, picks Buyer or Seller, enters the agent's information, and draws the service area on a Google Maps interface. Custom PHP scripts and server APIs then provision the entire site — domain mapping and SSL certificate included — and it's live within minutes.

  3. Dead end

    One big server, hundreds of full copies

    Every tenant carried its own complete copy of the CakePHP framework and its own cron jobs. Disk filled up, the cron queue serialized, and a single application server couldn't keep pace with the fleet.

  4. Breakthrough

    Share what's identical, parallelise what isn't

    Symbolic links collapsed hundreds of duplicated framework trees into one shared copy, reclaiming disk across every site. Cron scripts for notification emails and site-specific tasks were refined and set to run in parallel across sites. And the application was re-architected to run across multiple application servers — true horizontal scaling.

Before — one server, N full copies

Each tenant site
a single application serverdisk, cron backlog and CPU cap out as sites multiply
Own framework copy + serial cron jobs

After — multi-tenant, horizontally scaled

Master admin provisions a tenant
domain + SSL automated in minutesload spread across multiple app serverscost per site falls as the fleet grows
Shared framework via symlinks · parallel crons

The product didn't change — the way it's hosted did. Sharing what's identical between tenants and parallelising what isn't turned a fleet that fought the server into one the server barely notices.

03 — The Solution

A Platform Agents Run Themselves

The same system that provisions a site also hands the agent the keys — no developer in the loop for day-to-day changes.

Automation

Minutes-to-live provisioning

Add a domain, choose the site type, enter the agent's details, and pick the service area on Google Maps. PHP scripts and server APIs handle domain mapping, SSL and deployment automatically.

Front-end

Themes + inline visual editor

Multiple selectable themes and an in-page visual customization editor let agents restyle and edit their own sites with no technical help.

Product

From CMS to real-estate CRM

The simple lead inbox grew into a full-featured CRM tailored to how real estate agents actually work leads, listings and clients.

Backend

Infrastructure built to divide

Shared framework files, parallel site-scoped cron jobs, and a multi-application-server architecture keep reliability high and per-site cost low as the fleet grows.

04 — Key Results & Impact

A Fleet That Gets Cheaper to Run as It Grows

Minutes

From “add domain” to live site

Domain, SSL and deployment fully automated

1

Shared framework copy, not hundreds

Symlinks reclaim disk across the whole fleet

N+

Application servers, horizontally scaled

Add nodes to add capacity

Infrastructure cost per site

Falls as the platform scales up

05 — Why This Matters

Scaling Is a Backend Problem With a Front-End Answer

Plenty of teams can build the tenth real estate site. Fewer can turn the first ten into a product — and fewer still can keep that product cheap and reliable at the hundredth tenant.

This platform works because two kinds of expertise met in one team: front-end product design that made site creation a self-serve, few-click flow, and server-infrastructure depth that re-architected the hosting so growth lowers cost instead of raising risk. If you're staring at the same scaling or productization wall, that's the conversation we're built for.

SaaS Productization · Multi-Tenant Architecture · Server Infrastructure · Front-End Product Design

Building something that has to be reliable?

Talk to a senior engineer about AI-accelerated delivery or a production RAG / agent system. We work with teams across the US, Canada and beyond.

Book a Discovery Call