◆ Real Estate Insights

Pre-Launch vs Ready Possession — You Need Different Pipelines

Pre-launch takes 2 months. Ready possession takes 2 weeks. Using the same pipeline for both means wrong stages, wrong follow-up timing, and pipeline data you can't trust.

JA

Jayesh Gadhave

Updated 29 Jul 2026 · 6 min read

A pre-launch project takes 2 months to close. A ready possession flat takes 2 weeks. You’re using the same pipeline for both. Fresh Leads → Follow Up → Site Visit → Booking. But a pre-launch buyer doesn’t do a site visit — there’s no site yet. And a ready possession buyer doesn’t need an EOI stage — they want to see the flat and book today. Same pipeline for both = wrong stages, wrong follow-up timing, wrong urgency. Your data is fiction. > Business Impact: Developers using a single pipeline for different project types report 30-40% inaccurate pipeline data. Leads sit in stages that don’t apply to them. Managers can’t tell what’s actually stuck vs what’s in a stage it shouldn’t be in. The result: bad decisions made on bad data.

Why one pipeline doesn’t work

Look at how differently these two sales cycles work:

Putting both in the same pipeline is like putting a marathon runner and a sprinter on the same track and expecting the same race.

What goes wrong with a single pipeline

Problem 1: Stages don’t match

Your generic pipeline has “Site Visit” as Stage 3. But for pre-launch:

• There’s no site to visit
• You do a sample flat tour or virtual walkthrough instead
• The real “visit” is showing the location and surroundings

So your team puts pre-launch leads in “Site Visit” even though it means something completely different. Your pipeline data is now unreliable.

Problem 2: Follow-up timing is wrong

Ready possession leads need a call every day. They’re comparing 3-4 flats this week. Miss one day and they’ve booked elsewhere.

Pre-launch leads need a call every week. They’re not in a rush. Call them daily and they’ll block your number.

One pipeline = one follow-up rhythm = wrong for at least one type.

Problem 3: Pipeline value is meaningless

Your Kanban shows “₹12 Cr in pipeline.” But:

• ₹8 Cr is pre-launch leads that won’t book for 2 months
• ₹4 Cr is ready possession leads that could book this week

Which ₹4 Cr needs your attention today? You can’t tell because they’re all mixed together.

Problem 4: Conversion data is garbage

Your “Fresh to Booking” conversion rate shows 4%. Is that good? Bad? You can’t tell because:

• Pre-launch conversion is naturally 2-3% (long cycle, high drop-off)
• Ready possession conversion is 8-10% (short cycle, higher intent)
• Blended 4% hides both — pre-launch looks better than it is, ready possession looks worse

The fix: separate pipelines for separate sales cycles

Create a pipeline for each project type. Here’s what works:

Pipeline 1: Pre-Launch Sales

Fresh Lead → Interested → Sample Flat / Virtual Tour → EOI Submitted → Token Paid → Allotment → Done

Key settings for this pipeline:

• Follow-up default: 7 days (weekly cadence)
• Transition rules: Can’t skip from Fresh Lead to EOI (must go through Interested first)
• Required fields at EOI: Budget confirmed, configuration preference, client PAN/Aadhaar
• No auto site visit (no physical site yet)

Pipeline 2: Ready Possession Sales

Fresh Lead → In Follow Up → Site Visit Scheduled → Visited → Negotiation → Booking → Done

Key settings for this pipeline:

• Follow-up default: 1-2 days (daily urgency)
• Auto site visit: ON for “Site Visit Scheduled” stage
• Transition rules: Can’t move to Done without going through Visited (must have site visit proof)
• Required fields at Negotiation: Budget, preferred unit, financing mode (loan/self)

Pipeline 3: Payment Tracking (post-booking)

Token Pending → Agreement → Home Loan → Registration → Possession

This pipeline picks up after the booking is done. Use it for both pre-launch and ready possession.

For plot and villa projects

Plots and villas have yet another cycle:

Fresh Lead → Location Visit → Legal Verification → Price Discussion → Agreement → Registration

Key differences:

• Legal verification stage — clients check title, encumbrance, NA status. This doesn’t exist in apartment pipelines.
• Location visit instead of site visit — showing the plot boundary, road access, surrounding area
• No sample flat — it’s land. The visit is about location, not interiors.
• Longer negotiation — plot rates are more negotiable than apartment rates

Create a fourth pipeline for this. Don’t force plot leads into an apartment pipeline.

How to set this up in ClosingFox

1. Open Settings → Pipeline Config
2. Click “New Pipeline”
3. Name it (e.g., “Pre-Launch Sales”)
4. Add your stages in order
5. Set transition rules (which stage can move where)
6. Set required fields per stage
7. Enable auto site visit on the right stage (ready possession only)
8. Save
9. Repeat for each pipeline type you need

Then create assignment rules per pipeline:

• “Pre-launch leads from 99acres → Pre-Launch Pipeline → Kabir, Priyanka”
• “Ready possession leads from Housing → Ready Possession Pipeline → Sonali, Namira”

Leads auto-route to the right pipeline with the right team. Zero manual sorting.

→ Step-by-step pipeline setup guide

What you see differently with separate pipelines

Kanban clarity

Switch between pipelines using the dropdown at the top. Each pipeline shows only its leads in its stages. No mixing.

• Pre-Launch Kanban: 45 leads, mostly in Interested and Sample Flat stages. Normal — it’s a long cycle.
• Ready Possession Kanban: 30 leads, mostly in Follow Up and Visit Scheduled. These need attention NOW.

Previously, all 75 leads were in one board. You couldn’t tell which needed urgent action.

Accurate conversion rates

With separate pipelines, you know 3% pre-launch conversion is healthy. Without separation, 5.1% blended tells you nothing.

Right follow-up cadence

• Pre-launch pipeline: disposal flow suggests 7-day follow-ups
• Ready possession pipeline: disposal flow suggests 1-2 day follow-ups
• Each pipeline’s Spot rules flag overdue follow-ups based on that pipeline’s rhythm

Mandate owners: one pipeline per developer

If you represent Developer X (pre-launch) and Developer Y (ready possession):

• Create “Developer X — Pre-Launch” pipeline
• Create “Developer Y — Ready Possession” pipeline
• Each developer’s leads flow into the right pipeline via assignment rules
• Report to each developer showing only their pipeline’s data

When Developer X asks “how many leads are in EOI stage?” — you filter their pipeline and answer in 5 seconds. Not 2 hours of Excel work.

→ Managing multiple projects with one team

Common questions

How many pipelines can I create?

Up to 10, depending on your plan. Most developers use 2-4. Mandate owners use 3-6.

Can one lead be in multiple pipelines?

Yes. A lead interested in both a pre-launch and ready possession project can exist in both pipelines simultaneously, at different stages in each.

Can I move a lead from one pipeline to another?

Yes. If a pre-launch buyer decides they want a ready possession flat instead, move them to the other pipeline. Their history stays intact.

Do I need separate teams for each pipeline?

Not necessarily. The same person can handle leads in multiple pipelines. Assignment rules control who gets which leads — not the pipeline itself.

What about commercial vs residential?

Same principle. Commercial sales have a completely different cycle (longer, committee decisions, multiple site visits). Create a separate pipeline with stages that match commercial sales.