The Real Estate Project Launch Playbook (2026): Pre-Launch to Sold-Out

A residential launch in India is won or lost in about six weeks. The developer has spent 18 months on approvals, another three on the brand film and the sample flat, and then compresses the entire commercial outcome into a window where the CPs are excited, the media plan is live, and the inventory sheet is still an Excel file on somebody's laptop. When that window closes badly, the project does not fail dramatically. It just becomes another line in the unsold-inventory count: Anarock's quarterly market updates have kept unsold stock across the top seven cities in the 5-6 lakh unit range, with an inventory overhang of roughly 20 months. Most of that stock was not badly built. It was badly launched.

This playbook is the sequence we see working for Indian developers and the channel-partner networks selling for them: what to do at T-90, what to lock before the first ad goes live, how to run launch week without losing leads, and how to keep velocity after the initial rush burns off. It assumes nothing about your tech stack, though it does assume you eventually stop running a launch on WhatsApp groups and spreadsheets.

Why Indian launches leak money

Three leaks account for most of the gap between a launch's plan and its actual bookings, and none of them are about pricing.

• Demand pooled, then wasted. Pre-launch campaigns generate a large registration pool. By the time the project is RERA-registered and open for bookings, half that pool has gone cold because nobody had a nurture sequence, only a call list.
• Inventory nobody can see. Presales is quoting units the sales head has already blocked verbally for a CP. Two teams sell the same 1204. The correction costs a customer and a CP relationship.
• Attribution that arrives after the money is spent. The media budget is reallocated on day 40 of a 45-day launch because the CPL-by-source report took three weeks to assemble from four dashboards.

Each of these is a systems problem, not an effort problem. The teams working the launch are usually working very hard.

Phase 1 (T-90 to T-30): build a demand pool you can actually convert

Pre-launch exists to do one thing: assemble a qualified, contactable, tagged pool of buyers who are waiting for your price list. Volume alone is vanity.

Respect the RERA line

Under Section 3 of the Real Estate (Regulation and Development) Act, 2016, a promoter cannot advertise, market, book, sell or offer for sale any unit in a project covered by the Act without registering it with the state RERA authority. In practice this means your pre-launch communication is brand and locality building, expression-of-interest collection, and priority-list registration, not unit-and-price selling. Keep the creative, the landing page and the CP collateral inside that line, and keep a record of what went live when. Registration numbers belong on every asset the moment you have them.

Buy demand where intent is, not where volume is

A typical Indian residential pre-launch runs Meta lead forms for reach, Google Search for intent, and portals (99acres, MagicBricks, Housing) for locality-specific buyers. The CPLs are not comparable and should never be optimised against each other on cost alone: a Rs. 250 Meta lead and a Rs. 1,400 Search lead can produce the same cost per site visit. Judge sources on cost per qualified site visit and, eventually, cost per booking. We have written about that reframe in detail in the cost per lead versus cost per booking guide, and the same logic applies twice over during a launch, when a fortnight of bad allocation cannot be recovered later.

Whatever the mix, every source has to land in one place with its UTM, campaign, and CP code intact. If a lead arrives without a source tag, it is not a lead you can learn from. Our guide to paid lead generation for Indian real estate covers the UTM and tagging discipline this needs.

Collect EOIs with money attached

An expression of interest backed by a refundable Rs. 25,000 to Rs. 1 lakh cheque separates the priority list from the browsing list. Track EOI conversion as its own funnel stage from day one: EOI collected, EOI converted to booking, EOI refunded. On a well-run launch, 30-50 percent of week-one bookings come from the EOI pool. If yours converts under 20 percent, the pool was collected on discounts rather than intent.

Phase 2 (T-30 to T-0): make the inventory a system, not a spreadsheet

This is the phase most launches under-invest in, and the one that decides whether launch week is calm or chaotic. Before the first booking form is printed, the following should exist in one system that presales, sales, CP teams and post-sales all read from.

• The unit grid: every tower, floor, unit number, carpet and saleable area, facing, and configuration, loaded and verified against the approved plan.
• Availability states that mean something: available, held, blocked, booked, agreement done. A hold must carry an owner and an expiry, otherwise it is a rumour.
• Cost sheets generated from the system, with the current price ladder, floor rise, PLC, GST, stamp duty and registration handled as rules rather than as a formula a sales manager retypes at 11 pm.
• Payment plans and schemes mapped to units, so a CP quoting a subvention scheme cannot quote it on a tower it does not apply to.
• An approval chain for discounts, with a defined limit per role and a log of who approved what.

A CRM that holds leads but not units forces your team back into Excel on the highest-stakes day of the year. Running both in one platform is the point of a CRM with real estate inventory management built in rather than bolted alongside.

Sell.do's IRIS module is built for this phase specifically: tower and unit masters, hold-block with expiry, auto-generated cost sheets and scheme mapping, all visible to the same teams working the leads. If you are still choosing tooling, the 2026 buyer's guide to inventory management software sets out what to evaluate.

Phase 3 (launch week): speed is the whole strategy

Launch week produces the densest lead flow the project will ever see, often 5-15x a normal week, and the team handling it is the same size. That is why response time collapses exactly when it matters most.

The classic Harvard Business Review study on online lead response found that firms contacting a lead within an hour were about seven times more likely to have a meaningful conversation with a decision-maker than those waiting even two hours, and 60 times more likely than those waiting 24 hours. In launch conditions in India, where the same buyer has filled forms on three competing projects in the same micro-market, the practical window is minutes, not hours. Our deeper treatment of this is in the speed-to-lead breakdown.

What holds up under launch-week volume:

• Automated first response inside 60 seconds on WhatsApp, with the project deck, location pin and price band. The buyer gets an answer while the ad is still on screen.
• Round-robin or rule-based assignment with a TAT clock per lead, visible on a dashboard the presales head watches live rather than reads on Monday.
• AI qualification on the first touch (budget, configuration, timeline, funding) so human callers spend launch week on the 30 percent worth calling twice.
• Site-visit slotting that respects sample-flat capacity. Overbooking Saturday is a common and expensive launch mistake.
• Every call recorded and auto-logged against the lead, so nothing depends on a rep remembering to update a status at 9 pm.

This is where an agentic CRM earns its cost: an AI agent that responds, qualifies and books site visits without waiting for a human is the only thing that scales linearly with launch-week volume. The mechanics of AI voice and predictive scoring in presales are covered in our presales AI playbook.

Phase 4: mobilise channel partners without losing control of the lead

For most Indian residential launches, channel partners deliver somewhere between 40 and 70 percent of bookings. They are also the single largest source of disputes about lead ownership and payouts, and disputes slow a launch down.

• Give every CP a login and a subdomain rather than a WhatsApp group. Registrations, walk-in intimations and lead submissions should enter the same pipeline as your own leads, tagged with the CP code automatically.
• Publish the inventory view CPs are allowed to see, with live availability. A CP quoting a sold unit damages your brand, not theirs.
• Define the lead-ownership rule in writing before launch (first registration wins, with a validity window) and enforce it in the system rather than in arguments.
• Track payouts against verified bookings from the same records, so brokerage reconciliation does not become a two-month post-launch project.

Sell.do's channel-partner module handles the whitelabel portal, CP logins, lead tagging and payout tracking on the same data your internal teams use. For how developers evaluate and select CP networks in the first place, see our guide to picking channel partners in India.

Phase 5: from launch spike to sold-out velocity

Bookings peak in week one or two and then fall off a cliff. The projects that reach sold-out are the ones that treat weeks 3 to 26 as a managed process rather than a wait.

Work the price ladder deliberately

Publish a pre-decided ladder: an inaugural band for the first tranche of units, a step-up after a stated absorption threshold, and so on. It gives presales a real reason to call back the fence-sitters from week one, and it protects margin from ad-hoc discounting when the pipeline gets thin in month three.

Re-engage the pool you already paid for

The launch-week pool contains hundreds of buyers who were not ready in that fortnight. They are the cheapest bookings available to you. Segment them by objection (budget, configuration, possession timeline, loan) and run separate WhatsApp and calling sequences per segment rather than one generic drip. The messaging patterns that work are in our WhatsApp-first playbook.

Close the loop into post-sales on day one

A booking that stalls at agreement or first-demand collection is not revenue. Wire bookings, agreements, demand letters and collections into the same system from the launch itself, so the finance team is not reconstructing a launch's paperwork in month four. Our post-sales management guide covers the handover discipline that keeps bookings from stalling.

The launch dashboard: eight numbers, one screen

If the launch review needs more than one screen, the reporting is broken. Track these, daily during launch week and weekly after:

• Leads by source and campaign, with CPL per source
• First-response TAT: median and percentage answered inside 5 minutes
• Qualification rate, and cost per qualified lead
• Site visits scheduled, done, and no-show percentage
• Site visit to booking conversion, split by own-team versus CP
• EOI to booking conversion, and EOI refunds
• Units by state: available, held, blocked, booked, agreement done, per tower
• Cost per booking by source, which is the only number the CFO should be asked to care about

The point of putting source attribution next to unit states is that you can move budget on day 5 of the launch instead of day 40. Campaign ROI attribution that arrives after the launch is history, not management.

A 12-week launch checklist

• T-90: micro-market and competition pricing study; media plan and budget locked by source; CP shortlist agreed
• T-75: RERA registration filed; brand identity, site branding and sample flat timeline confirmed
• T-60: landing pages, lead forms and UTM taxonomy live; CRM pipeline stages, TAT rules and assignment rules configured
• T-45: pre-launch teaser campaigns live; EOI process and refund policy documented; CP onboarding and logins issued
• T-30: unit master, price ladder, cost sheet templates, schemes and approval limits loaded and tested
• T-15: presales team trained on the actual system with dummy leads; WhatsApp templates approved; site-visit slotting built
• T-7: dry run at 3x expected volume; escalation matrix, hold-expiry rules and booking-form flow tested end to end
• T-0 to T+14: daily 20-minute review on the eight metrics; reallocate media by day 5; enforce hold expiries strictly
• T+15 to T+90: price ladder step-ups; segmented re-engagement of the unconverted pool; CP payout reconciliation; post-sales handover discipline

Five mistakes that show up in almost every stalled launch

• Treating pre-launch as awareness only, so the pool arrives untagged and unqualified.
• Opening bookings before the unit master and cost sheets are in a system everyone reads from.
• Staffing presales for average volume rather than launch-week volume, then blaming conversion.
• Letting CP leads live in WhatsApp groups until a payout dispute forces reconstruction.
• Running the launch review on a report that is two weeks old.

None of these require a bigger budget to fix. They require the launch to run on one system where leads, units, calls, CP activity and money are visible at the same time.

Related reading

• Real Estate CRM with Inventory Management: One System for Leads + Units (2026)
• Speed to Lead in Real Estate: Why the First 60 Seconds Decide the Booking (2026)
• Real Estate Post-Sales Management in 2026: From Booking to Possession

Run your next launch on one system

Sell.do's IRIS module gives launch teams a live unit and tower master, hold-block with expiry, auto-generated cost sheets and scheme mapping, sitting on the same platform that captures and qualifies the leads and tracks channel-partner activity. If your last launch ended with two versions of the availability sheet and a payout dispute, that is the problem worth fixing before the next one. See how Sell.do runs launches and inventory end to end at sell.do, or ask for a walkthrough with your own tower plan loaded.