Most property builders in India have two bad options for a web presence. They can rent leads from the listing portals (99acres, MagicBricks) for ₹30-45k a month and get a generic listing page that looks identical to every competitor on the same portal. Or they can commission a custom agency site that is slow to build, expensive, and stale the day it ships, with no way to keep it current as inventory sells.
And every builder needs the same things said completely differently. A luxury apartment tower, a plotted layout, a township, and an off-plan launch all need pricing, RERA proof, live availability, and an EMI story, but a layout that converts one would look wrong on the others. A one-off build can't scale across thousands of builders; a generic template farm can't deliver the craft that actually converts a buyer.
An engine that gives any property builder an agency-grade website in minutes, not months. A developer needs a website to sell flats, but the options are bad: rent a generic page on a listings portal that looks identical to every competitor, or pay an agency a fortune for a custom site that's outdated the day flats start selling. This spins up a premium, phone-first website for any builder almost instantly: pick a layout, pick a look, point it at the project, and a conversion-tuned site renders. Every builder also gets a simple dashboard to manage sales leads and show which flats are still available. The clever part: one shared engine powers every builder's site, so making the next one is basically typing in their details, not building from scratch. I built all of it solo, and it runs on the same property-data brain as my TN Property tool.
Templates are data, skins are tokens
A template is an ordered array of {module, config} plus a default skin; a skin is a set of CSS design tokens. Adding a new builder's site is data entry; adding a new template is one file. The engine renders any template-and-skin combination server-side, so SEO (the thing the builder is actually paying for) is real.
Modules that compose, not pages that repeat
Each module is a React component plus a Zod config schema plus a fromData() mapper, registered once. Modules read skin tokens and never hardcode color or type, so the same module looks native in Editorial Luxury or Dark Cinematic. Each declares a tier (core, addon, optional) so optional modules, like location-intelligence, drop out cleanly when their data or flag is absent.
The conversion codex, baked into the engine
The 22 rules that make a property page convert are structural, not suggestions: aspiration before data, price shown as a monthly EMI first, one call-to-action per screen, RERA proof one tap away, scarcity drawn only from live inventory, a sticky mobile CTA bar, and a sub-five-minute WhatsApp lead handoff. Because they live in the engine, every site gets them for free.
Grounded, not generative
The on-site AI chatbot answers strictly from the project record (Anthropic Haiku when a key is set, a deterministic scripted fallback otherwise). It logs every turn and captures phone numbers as leads, and it never invents a price or a possession date. The builder's dashboard then turns those leads, views, and sources into a retention loop.
Mobile is the real product
Indian property buyers are on phones, so the site is designed at 375px first, not as an afterthought to a desktop layout. Pages are server-rendered with schema.org JSON-LD, because the builder's value is being found, not just being seen.
Build the engine, integrate the commodities
The platform builds the parts where craft compounds: the engine, the modules, the dashboard, the chatbot orchestration. It integrates the commoditized parts (maps, 3D tours, payments, WhatsApp, auth) rather than rebuilding them. Never rebuild a CRM you can buy; spend the effort where the product is differentiated.
Optional intelligence as the moat
A feature-flagged location-intelligence module plugs the sites into a proprietary infrastructure-catalyst dataset (metro, highway, airport, and industrial pipelines), so a builder's page can show what is coming to the neighborhood and why it matters. It is the same data asset behind the TN Property Intelligence terminal, and it drops out cleanly when a builder isn't on the plan.
Recurring, not project
Priced against the monthly portal-lead spend it replaces, the product is a subscription with a retention layer (the dashboard) rather than a one-off agency invoice. The engine is what makes that economically possible: the marginal cost of the next builder's site is data, not a rebuild.