HomeSellers: A real estate brokerage site with a self-serve content and lead engine
A full brokerage website with lead capture on every page, a blog the team publishes themselves, and a role-based admin panel, all on Cloudflare Pages and D1, owned outright by the business.
- HomeSellers
- Real Estate
- Aug 2025
- shipped

The problem
A brokerage website usually fails in one of two ways. Either it's a generic template that looks fine but can't capture or route a lead, or the business leans entirely on listing portals and has no presence it actually controls. In both cases the same things break: the team can't publish anything without calling a developer, inquiries land in a shared inbox with no structure, and nobody can tell which page produced which lead.
HomeSellers needed a site that did three things at once: present the brokerage properly across its different audiences (residential, commercial, investors, wholesale), capture and organize every lead, and let the team manage content and follow-ups without a developer in the loop.
What we built
A full marketing site. Dedicated pages for each audience the brokerage serves, plus a blog and the usual legal pages, all on one fast, mobile-first front end.
Lead capture on every page. Five separate forms, each tagged with the page it came from, writing straight to a database the brokerage owns. Every inquiry is attributed to its source instead of disappearing into an inbox.
A blog the team runs themselves. Posts are written and published from the admin panel and served at clean URLs. No developer, no deploy, no CMS subscription.
A role-based admin panel. Admins manage leads, blog posts, and users. Editors are scoped to the blog only. Leads move through a simple pipeline: new, contacted, closed.
Hardened auth and intake. Passwords are hashed (PBKDF2), sessions expire on a fixed schedule, forms are rate-limited with an optional bot check, and the team gets an email the moment a new lead comes in.
How it's built
The front end is a static site on Cloudflare Pages, so it loads instantly on mobile, where almost every real estate search starts. The API runs as Cloudflare Pages Functions against a D1 (SQLite) database holding leads, blog posts, users, and sessions. Lead notifications go out through a transactional email provider.
No WordPress plugin stack, no website-builder subscription, no monthly platform fee beyond the domain. The brokerage owns the code, the data, and the publishing workflow.
What changed
The brokerage went from a presence it couldn't control to one it owns end to end: a fast site, forms that record and route every inquiry by source, and a blog the team updates on its own. Because every lead is attributed to the page that produced it, the team can see which parts of the site actually bring in business instead of guessing.
The stack
- Front end: static site on Cloudflare Pages
- API: Cloudflare Pages Functions
- Database: Cloudflare D1 (SQLite): leads, posts, users, sessions
- Auth: PBKDF2 password hashing, session tokens, role-based access (admin / editor)
- Hardening: rate limiting, optional bot check, server-side validation
- Email: transactional lead notifications
A brokerage doesn't need a website builder with a monthly bill and a publishing process it can't touch. It needs a fast site that captures every lead and a content workflow the team controls.