Plotted developments live and die by what happens between an enquiry and a token. The buyer rarely decides on the phone. They want to see the layout, stand on the plot, ask about the road width and compare it with two other projects. A good workflow does not try to rush that. It makes sure nobody is forgotten while the buyer thinks.
Define stages by what actually happens
Many teams copy a generic pipeline and then wonder why nobody trusts it. Start from reality. In a plotted project, a common sequence is: unassigned, new, contacted, connected, qualified, negotiation, site visit and booking. Propto CRM’s default sales pipeline follows nine stages of this kind, and you can rename or reshape them.
For each stage, write a one-line rule for entering and leaving it. “Connected” should mean you spoke to the buyer, not that you called. “Qualified” might mean you know the budget range, the type of plot and the buying timeline. When definitions are written, managers can review fairly and new telecallers learn quickly.
Give every lead one owner and one next step
A lead without an owner is a lead nobody is losing sleep over. Decide how leads get assigned: round-robin for similar enquiries, by project or language where expertise matters, or manually by a team leader for high-value cases. Keep an unassigned view so nothing waits unseen.
Then enforce one dated next step on each lead. The follow-up tracker should show overdue, due today and upcoming items for each person. A manager looking at the overdue list at ten in the morning can help rather than blame.
Treat the site visit as its own stage with an outcome
For plotted developments, the site visit is the moment a buyer stops being a lead and starts being a prospect. Schedule it in the system, confirm it the day before, and record an outcome when it ends: interested, needs a second visit, comparing options, not interested.
Visits that need an outcome should stay flagged until someone records it, because a visit without an outcome is invisible to your funnel. Over a month, those outcomes tell you what kind of plots, prices and objections dominate, which is more useful than any marketing report.
Use holds and tokens to protect commitment, not to hoard inventory
When a buyer says “give me two days”, a temporary hold protects the plot and the relationship. Make holds explicit, with a start date and an end date, and make them visible to the whole team. A hold that quietly lasts for weeks is a plot nobody can sell.
When the buyer pays a token, convert the hold into a booking with the amount, mode and partner attached. A live plot map that changes colour when the booking is confirmed stops two salespeople from promising the same plot.
Automate the reminders, not the relationship
Automations are best at the boring middle. A new lead gets assigned, a follow-up reminder appears, a buyer who has not heard from you in a few days appears on a list. Keep customer-facing messages short and specific, and let a person handle anything that involves price or doubt.
Whatever you automate, preview it first and review the log. A rule that sends a message to every lead after a site visit is helpful until it fires at a buyer who just cancelled. Switching rules on one at a time makes mistakes cheap.
Review the funnel weekly and fix one thing
A weekly funnel review should take twenty minutes. Look at how many leads reached each stage, where the biggest pile sits and which source produced the visits. If many leads are stuck before the site visit, the problem is usually follow-up or qualification. If many visits do not become bookings, look at pricing, inventory presentation and objection handling.
Pick one fix, assign it to a person and check it next week. Workflows improve by small repeated corrections, and the CRM’s job is to make those corrections obvious.
A worked example: one enquiry, start to token
Consider a buyer who fills a Meta lead form on a Tuesday evening asking about a 1,200 square foot plot. The lead lands in the pipeline as unassigned, and an automation assigns it by project to a telecaller and sets a follow-up for the next morning inside business hours.
On Wednesday the telecaller connects, learns that the buyer is comparing two projects and wants to visit on Sunday. She moves the lead to qualified, schedules the visit, and notes the main concern, which is road width. On Sunday the sales executive shows two corner plots on the map, records the outcome as needs second visit and places a three-day hold. On Thursday the buyer pays a token and the plot becomes a booking, with the cost sheet generated from the record. Nobody retyped anything and every handover carried context.
Mistakes that quietly kill conversions
Teams often add too many stages, so cards pile up in vague middle columns. Keep stages few and defined. Another mistake is letting holds run without an end date, which hides sellable inventory. A third is measuring telecallers only by number of calls, which rewards dials rather than conversations.
Also watch for lead recycling. Leads that never connected deserve a different cadence from leads that visited and disappeared. Use the pipeline to separate them, and give each group a follow-up routine that suits it rather than one generic reminder for all.
How many stages should a sales pipeline have?
Enough to describe real decisions, typically between five and nine. Each stage needs a written entry and exit rule.