[DHARM/SY]
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.

Visit Live ProjectAll Projects
Upcoming Projects homepage — a Bangalore property listing platform showing unit configurations, pricing and sold-out status per project
Cover image for the Upcoming Projects case study.

About this project

Upcoming Projects is a Bangalore-wide listing platform for residential developments that have not been completed yet — new launches, pre-launches and under-construction projects across twelve developers. I worked on the website as a full-stack developer. It is the third portal I built on this platform, and the one with the deepest data model. Its sister sites, Chikkajala Realty and Hebbal Realty, list projects. This one lists projects and the units inside them: each development carries its individual configurations — 2 BHK 2T, 3 BHK 3T, 4 BHK 4T — with a carpet-area range, a starting price and an availability state per configuration. That sounds like a small addition and it changes almost everything downstream. The budget filter is the clearest example. A buyer with a two-and-a-half crore budget is not filtering projects, they are filtering configurations: a development whose headline price is ₹2.26 crore may have nothing available at that number because the smallest unit is sold out. Filtering on the project's starting price would return results the buyer cannot actually buy. So the filter reasons over configurations and the card surfaces the whole matrix, sold-out rows included, rather than a single from-price. Showing "Sold Out" at all was a decision worth defending. The instinct is to hide unavailable inventory because it looks like a dead end. In practice it is the most useful signal on the card: it tells a buyer the development is selling, which configurations have gone, and where the remaining demand sits. Concealing it produces enquiries that waste both sides' time and cost trust at the point the buyer finds out. The harder problem is that the entire premise is unbuilt property. Pre-launch pricing moves, possession years slip, configurations get revised before a single unit is poured. Every price on the site carries an asterisk for that reason, and the build separates inventory data from templates so it can be corrected quickly. A listing platform for things that do not exist yet is a data-freshness problem wearing a front-end's clothes, and treating it as anything else is how these sites quietly become wrong.

Tech Stack

Next.jsReactTailwind CSSNode.jsnginxJSON-LD Structured DataResponsive Design

Frequently Asked Questions

Upcoming Projects is a Bangalore-wide listing platform for residential developments that are new launches, pre-launches or under construction — apartments, villas, plots and townships from twelve developers including Century Real Estate, Sobha, Embassy, Brigade, Puravankara, Lodha, L&T Realty, Sattva, Total Environment, TVS Emerald, Maia Estates and White Lotus Group. The site is at upcomingprojects.org.
I worked on the website as a full-stack developer — the Next.js build, the unit-level inventory model, the budget and builder filtering, the listing card and project detail templates, the callback capture flow, and the structured data each page type emits.
Same platform, deeper data. Those two cover single micro-markets and list projects; this one covers Bangalore as a whole and goes a level below the project, modelling each unit configuration with its own area range, price and availability. That extra level is what makes budget filtering meaningful and what the listing card is built around.
Because a single from-price is often not purchasable. A development advertised from ₹2.26 crore may have sold out at that size, so the real entry point is a crore higher. Showing the full matrix — configuration, area range, price, availability — lets a buyer see in one glance what is actually available in their range rather than discovering it on a call.
Because it is genuinely useful information. It tells a buyer the project is selling, which sizes have gone, and therefore where demand is concentrated — all of which helps them decide. Hiding it produces enquiries about units that do not exist, which wastes the buyer's time and costs trust the moment they find out. Transparency about what you cannot sell makes what you can sell more credible.
It filters configurations, not projects. Filtering on a project's starting price would surface developments where nothing is available at that number. Matching against individual configurations means a budget query returns places the buyer could actually transact in, which is the only version of the feature worth shipping.
By accepting that you cannot fully — and building for correction rather than permanence. Pre-launch prices move, possession dates slip and configurations get revised before construction starts. Prices carry an asterisk for exactly that reason, and inventory data is kept separate from the templates so it can be updated without a code change. A listing platform for unbuilt property is a data-freshness problem more than a front-end one.
New launch, pre-launch and possession year are the axes buyers in this segment actually use, because they are buying a timeline as much as a home. Someone who needs to move in two years and someone investing on a 2031 possession are looking at different inventory, so the stage and possession year sit on the card rather than buried on a detail page.
Next.js with React, served behind nginx, with pages statically generated and incrementally regenerated so listings stay fast while remaining editable. Every page type emits JSON-LD — RealEstateAgent, Organization, Product and Offer per listing, OfferCatalog, BreadcrumbList and a WebSite SearchAction.
Yes. The front end is the straightforward half; the decisions that matter are in the model — how far below the top-level item your data needs to go, which of those attributes users actually filter on, and who updates it once you are live. Model too shallow and your filters lie; too deep and nobody maintains it. Use the form on this page with your inventory shape and I will give you an honest read.

Details

Organization
Upcoming Projects
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

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.

Saturn Realcon homepage — a WordPress luxury real-estate services site with property search and city-based navigation

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.

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.