The brief
iFoundAgent is a real-estate-focused WordPress provider — a proprietary IDX system (the integration that pulls MLS listings into agent websites) wrapped in a fleet of WordPress sites for individual real estate professionals and teams. I joined as a senior WordPress developer in 2015 and stayed nearly five years. During my time there, the platform was running over 2,000 sites across multiple WordPress Multisite networks.
The constraint was the foundation: every site sat on a proprietary IDX plugin, proprietary supporting plugins, and Genesis-based parent themes. Customization happened in the margins — child themes, hooks and filters, disciplined CSS — but the foundations stayed standardized so the operations team could keep 2,000+ sites maintainable at scale.
What I built
Custom themes for the agents who needed them. The bulk of the
network ran on shared, semi-custom Genesis child themes — fast to deploy,
brand-adjustable, predictable to support. But a handful of agents and
teams wanted full custom builds. privateclientgroupagents.com and
thespaldingteam.com are two examples — pixel-perfect designs translated
into Genesis child themes that still played nicely with the proprietary
IDX and the rest of the multisite plumbing.
Features on request. The other half of the work was network-level — new functionality dropped into the shared codebase, IDX customizations when an agent’s listings needed special handling, performance fixes that mattered at the scale of thousands of sites instead of just one.
Direct client-facing support. Real estate agents aren’t WordPress developers. A lot of the day-to-day was diagnosing what “the site broke” actually meant, getting the right answer back to the agent quickly, and adding the fix to the shared codebase so the next agent with the same problem never had to encounter it.
What’s notable about it
Working across 2,000+ sites teaches a different lesson than building one site well. Every change had to be defensible in production across a fleet, every feature had to compose with the proprietary IDX, every CSS tweak had to assume someone else had overridden the variable already. It’s the kind of WordPress experience you can’t replicate by building a side project — you have to sit inside an operations team and feel the friction of supporting strangers’ sites at volume. A lot of how I think about durable-by-default code traces back to those four-and-change years.