[DHARM/SY]
Project

Saturn Realcon — Luxury Real Estate Services Website

WordPress build for a luxury real-estate services company across four cities — Elementor Pro templates over a JetEngine content model, JetSearch property search, and a handover the client's own team could operate.

Visit Live ProjectAll Projects
Saturn Realcon homepage — a WordPress luxury real-estate services site with property search and city-based navigation
Cover image for the Saturn Realcon case study.

About this project

Saturn Realcon is a luxury real-estate services company operating across Gurgaon, Delhi, Bangalore and Kasauli. I worked on the website as a full-stack developer. It is the only build in this portfolio that is not JavaScript, and that was the decision worth defending. Everything else here is Next.js; this one is WordPress with Elementor Pro on the Hello Elementor theme, with JetEngine driving the property post types and JetSearch powering the search. The reason is not budget or speed of delivery — it is who owns the site afterwards. A marketing team that publishes several times a week and edits city and service pages without asking a developer is better served by a page builder they can actually use than by a codebase where every copy change is a pull request. Choosing the boring tool because the handover matters more than the stack is a judgement call, not a compromise. The site is service-led rather than listing-led, which shapes the whole architecture. The proposition is end-to-end — research-based buying, home loan facilitation, rental and repair, furnishing, high-end construction and property management, sold on a zero-brokerage model. So services are the primary axis and properties support them, the reverse of a portal. Cities form the second axis, which is where JetEngine earns its place: property types are modelled as custom post types with taxonomies, and the city and category pages are dynamic listings over those, not hand-built pages that drift apart as inventory changes. The parts that needed real care were the ones a page builder does not solve for you. Elementor will happily produce a page that looks right and loads slowly, so the work was in disciplining it — controlling how many widgets a template carries, keeping image weight down on a site whose whole subject is large interior photography, and making sure the search returns something useful rather than a raw keyword match. A visual builder removes the barrier to building pages; it does not remove the responsibility for what those pages cost to load. Alongside the nine core pages there is an editorial layer of around thirty posts, which is what a service business in this market actually competes on.

Tech Stack

WordPressPHPElementor ProJetEngineJetSearchMySQLCustom Post TypesResponsive Design

Frequently Asked Questions

Saturn Realcon Pvt Ltd is a luxury real-estate services company working across Gurgaon, Delhi, Bangalore and Kasauli. Rather than acting purely as a broker, it offers end-to-end services — research-based buying, home loan facilitation, rental and repair, furnishing, high-end construction and property management — on a zero-brokerage model. The site is at saturnrealcon.com.
I worked on the website as a full-stack developer — the WordPress build, the Elementor Pro templates, the JetEngine content model behind the property types and city taxonomies, the JetSearch-driven search, the performance work, and the handover to the client's own team.
Same business, same phone number, same zero-brokerage positioning — two sites on two stacks. Saturn Realcon is the broader services site on WordPress; LuxPropServ is the luxury property arm on Next.js. Both are in this portfolio deliberately: the point is not that I built two property sites, it is that the same client got two different technical answers to two different jobs.
WordPress on PHP 8.3, using Elementor Pro on the Hello Elementor theme, with JetEngine for custom post types and dynamic listings, JetSearch for the property search, and Dynamic Content for Elementor for the conditional pieces. Nine core pages plus an editorial layer of around thirty posts.
Because the question is not which stack is better, it is who maintains the site after handover. This client's team publishes and edits regularly and needed to do that without a developer in the loop. A Next.js build would have been faster to load and more satisfying to write, and would have made every copy change a deployment. Picking the tool the client can actually operate is part of doing the job properly, not a compromise on it.
When the site has real application state — authentication, a user account area, billing, anything transactional. Also when performance is the product rather than a constraint, or when the content model is unusual enough that fighting a page builder costs more than writing components. WordPress with a good content model is excellent for a content and marketing site; it is the wrong answer for a SaaS product, which is why nothing else in this portfolio uses it.
It provides the content model. Property types are custom post types with taxonomies for city and category, and the city and service listing pages are dynamic queries over that model rather than pages built by hand. That matters for maintenance: hand-built listing pages drift out of sync with inventory within months, while a dynamic listing simply reflects whatever the team has published.
It makes slow sites easy to build, which is not the same thing. A visual builder removes the barrier to adding widgets and every widget carries CSS and often JavaScript. The discipline is in the templates — limiting how much each one loads, being ruthless about image weight on a site whose subject is large interior photography, and checking what a page actually costs rather than only how it looks. Left unmanaged it will absolutely produce a slow site.
The company's proposition is end-to-end service, not brokerage, so services are the primary navigation axis and properties support them — the reverse of a property portal. Cities form the second axis. That ordering follows the business: someone arriving because they want help buying, furnishing or managing a property is answering a different question from someone browsing inventory, and the site is arranged around the first.
Yes, and that was a stated goal from the start rather than an afterthought. The client's team publishes and edits without needing a developer, which is the outcome the stack was chosen for. A site the client cannot maintain is a site that quietly rots, however well it was built.
Yes — this project is the evidence. Most of my work is Next.js, React, Node and MongoDB, but the right answer depends on who operates the thing afterwards. I would rather recommend the platform that fits the team than the one that is more interesting to build. If you want an honest read on which suits your case, use the form on this page.

Details

Organization
Saturn Realcon Pvt. Ltd
Role
Full-Stack Developer
Timeline
Client engagement

Questions about this project?

Tell me what you're building — I'll reply within 24 hours.

Email me insteadOr use the full contact page

Related work

Upcoming Projects homepage — a Bangalore property listing platform showing unit configurations, pricing and sold-out status per project

Upcoming Projects — Bangalore Property Listing Platform

Next.js listing platform for pre-launch and under-construction Bangalore developments — unit-level inventory with per-configuration pricing and availability, and budget filtering that reasons across configurations rather than projects.

LuxPropServ homepage — a Next.js luxury property services site with a unified search across property, location, city and builder

LuxPropServ — Luxury Property Services Platform

Next.js site for a curated luxury property advisory — a single search across property, location, city and builder, and a schema model that describes a consultative service rather than a listings catalogue.

Hebbal Realty homepage — a North Bangalore luxury property portal with builder pages and head-to-head project comparison articles

Hebbal Realty — North Bangalore Luxury Property Portal

Next.js property portal for the Hebbal luxury corridor — eleven builder pages, faceted browse, and an editorial layer of head-to-head project comparisons aimed at buyers who already have a shortlist.

Chikkajala Realty homepage — a North Bangalore airport-corridor property portal listing projects by builder, type and construction status

Chikkajala Realty — North Bangalore Property Portal

Next.js property portal for the Chikkajala–Devanahalli airport corridor — faceted browse by builder, type and status, keyword-first project URLs, and Product/Offer schema describing real inventory.