Site Visits but No Bookings? It’s Probably the Project

Your floor did its job. The visits are happening. The bookings are not. Past the site visit, roughly half the outcome belongs to a product you do not own — and what you actually control is which developers you carry.

This is the hardest place in the funnel to be, because everything upstream is working. Leads are coming. Calls are real. Visits are happening on Saturday and Sunday. And the booking sheet stays empty.

The instinct is to push the team harder. That is usually the wrong move here, and it can be an expensive one.

The one number that splits the diagnosis

It is the site closing ratio: of the visits that actually happened, how many became bookings.

The working floor is 10% — about ten completed visits to one booking. Above it, your floor and the product are both doing their part. Persistently below it, the problem is usually the project rather than the people, and no amount of extra calling fixes it. The full chain is in our funnel benchmark.

Measure it per project, never blended. A single strong project can hide two weak ones for months, and the blended average tells you nothing you can act on.

One condition before you trust the number: the visits must genuinely be completed, not scheduled. If your visit records are unreliable, fix that first — you cannot diagnose a ratio built on a count you do not trust.

How many visits before you judge a project?

This matters more than people expect, and getting it wrong is expensive in both directions.

Ten completed visits with no booking feels like proof. It is not. If a project genuinely converts at 10%, then across ten visits you would expect one booking — and pure chance alone produces zero surprisingly often.

So use two marks instead of one:

• At 10 completed visits with no booking — stop and review. Not stop selling. Grade the project on the checklist below, talk to the developer, and fix what is fixable.
• At 20 to 30 visits still under 10% — now you can decide. At that point the evidence is real, and continuing is a choice rather than an accident.

The review at ten is the discipline that matters. Most desks never review at all — they keep sending visits into a project for two quarters because it is already in the plan.

If the project is the problem: grade it honestly

When the ratio is genuinely low, go through these one at a time. Score each out of five and total it. The exercise is more useful than the score, because it forces a specific conversation with the developer instead of a vague complaint.

Take the two lowest scores to the developer as specific asks. “Your project is not converting” gets you nothing. “Your closing manager is not at site on Sundays and the 2BHK stock is gone” gets you a conversation.

Notice how much of this list you do not control. That is the point. As a channel partner the end product is not yours, and pretending otherwise turns a product problem into a morale problem on your floor.

What is still yours after the visit

Half of it is still your half, so be equally honest here before blaming the developer.

• Conviction. A rep who does not believe the project cannot transfer belief to a buyer. Buyers read hesitation quickly.
• Who came to the visit. If the person who signs the cheque was not there, the visit was information gathering, not a closing opportunity.
• The follow-up after the visit. This is the most commonly dropped step in the entire funnel. The buyer visited on Sunday, and nobody called on Monday with a reason to move.
• The second visit. In most markets a family visits more than once before booking. If your process ends at visit one, you are measuring an incomplete funnel.
• Objection handling. Price, loan eligibility, possession date, spouse or parent approval — these repeat. They should be answered the same strong way by every rep, not improvised.

A quick way to separate the two halves: if every rep is failing on one project but the same reps convert on another, it is the project. If one rep is failing across all projects, it is the rep. Our guide on finding where the funnel breaks covers the upstream version of the same test.

The real fix: choose your developers, quarter by quarter

Diagnosing one bad project is useful once. Choosing better projects is what compounds.

Plan your developer list one quarter at a time. Rank projects P1, P2 and P3 by their actual site closing ratio, plus inventory depth, price position and the support you get. Then commit your floor to the P1 list for the quarter, and review at the end of it.

The reason to concentrate is not efficiency. It is conviction.

A rep carrying eight projects knows a brochure’s worth about each one. A rep carrying two knows the layouts, the view from the eleventh floor, which bank clears the file fastest, what the neighbouring project charges, and what the last three buyers objected to. That rep does not sound like a broker. They sound like someone who works there — and buyers can hear the difference on a site visit.

Focus is also what makes coaching possible. You cannot build a strong objection-handling playbook across eight projects at once. You can across two.

Two practical rules for the quarterly plan:

• Do not add a project mid-quarter unless something in the P1 list is being dropped. Otherwise focus quietly erodes back to eight.
• Judge a new project on its own sample, using the 10-review and 20-to-30-decide marks above. Do not let a bad first month kill something that never got a fair count.

If you are carrying too many projects at once, that is its own problem — we covered it in managing multiple projects.

The circuit breaker

There is a point where continuing to send visits actively damages you, and it is worth naming because most desks blow through it.

Every completed visit into a project that cannot close costs you a Sunday slot, a rep’s best hours, the transport, and a buyer who now associates you with a project they rejected. It also corrupts your own numbers. A floor judged on a booking ratio it cannot reach stops trusting the targets, and then stops trusting the reporting.

So when a project is under review, cap the visits going into it rather than continuing at full volume. Move those slots to a P1 project while the developer conversation happens. Resume when something has actually changed — new inventory released, a price correction, a closing manager posted at site, a real offer.

Nothing changed and the ratio is still under 10% after twenty to thirty visits? Then it is not a sales problem you can solve, and the honest move is to reallocate the floor. The unit economics of a channel partner make this concrete: every visit has a cost, and visits into a dead project are simply spend with no return.

If you are the developer, this is your half

The same diagnosis read from the other side. When channel partners are producing visits and not bookings, the fixable items are usually yours:

• Put a real closing person at site on weekends, when the visits actually happen.
• Keep sellable inventory available in the configurations partners are being asked for.
• Give a reason to decide now — a genuine, time-bound offer or payment plan.
• Make the site experience match the pitch. The show flat is your conversion tool.
• Train the partners’ reps like your own. Their conviction is your revenue.

A partner whose floor cannot convert your project will quietly reallocate to someone else’s next quarter. Usually without telling you.

What to track

All of this needs the ratio to exist per project, which is the part most desks are missing.

• Completed visits by project — separate from scheduled, so the ratio uses a real denominator.
• Bookings by project, on the same period, so the closing ratio is comparable across your P1 list.
• Visit outcomes and ratings against each visit, so a pattern of weak site experience shows up before the quarter ends.
• Booking prospect scores to see whether visits are producing genuinely warm buyers or just footfall.

In ClosingFox these sit in the site visit records and the report builder, and location proof on completed visits is available on the Growth plan. If you are still unsure whether the visits themselves are real, site visit tracking covers that separately.

Quick answers

About these numbers: The 10% site closing ratio, the roughly 50/50 split between floor effort and developer product, and the P1/P2/P3 quarterly project planning approach are indicative benchmarks from the ClosingFox funnel model and our own operating experience — not a published industry standard, and not current market data. They move with city, price band, project type, lead source and season, so build your own baseline from three months of real data and compare against yourself.

The probabilities in the chart are a straight binomial calculation assuming each completed visit converts independently at a true 10% rate: zero bookings occurs with probability 0.9 raised to the number of visits, giving about 35% at ten visits, 12% at twenty and 4% at thirty. Real visits are not fully independent — they cluster by rep, season and buyer profile — so treat these as an argument for waiting longer before judging, not as an exact forecast. We deliberately do not publish a measured site-visit-to-booking rate from our own customer data, because visit-stage and booking-stage modelling varies too much between organisations for a reliable cross-org figure.

About ClosingFox: ClosingFox is a real estate CRM built for brokers, channel partners, mandate teams, developers and sales managers, with a focus on lead assignment, call tracking, follow-ups, site visits and sales accountability.