3 Signs Your Project Has a Velocity Problem, Not a Demand Problem
- Kevin Wash
- Jun 15
- 3 min read
Every time a project starts slowing down, the same explanation appears:
"The market has softened."
It's convenient. If the market is the problem, nobody inside the project has to change anything. But after reviewing residential, mixed-use, and branded residence projects across multiple markets, I've noticed something interesting:
Many projects blamed on weak demand are actually suffering from something else entirely. A velocity problem.
There is a significant difference. Demand is about whether buyers exist.
Velocity is about how efficiently a project converts demand into sales.
And those are not the same thing.
Sign #1: Lead volume is healthy, but conversion remains inconsistent
When a project receives enquiries, registrations, viewings, and qualified prospects, demand clearly exists. Yet many teams continue asking for more leads.
More campaigns.
More media spend.
More exposure.
More broker appointments.
The assumption is that increasing demand will solve the problem. Often it doesn't.
Because demand is already entering the system. The issue is what happens after.
How quickly are prospects contacted?
How consistently are they qualified?
How effectively are they moved through the decision process?
How many handoffs occur before a buyer receives a meaningful answer?
At some point, adding more demand to an inefficient sales process is like pouring more water into a leaking bucket.
The problem isn't the water. It's the bucket.
Sign #2: Everyone is busy, but nobody owns the outcome
This is one of the most common patterns I see:
Marketing is generating leads.
Brokers are conducting viewings.
Sales teams are following up.
Management is reviewing reports.
Everyone appears productive.
Yet absorption remains below expectations. Why?
Because activity and accountability are not the same thing. When sales responsibility is fragmented across multiple parties, velocity slows.
Questions go unanswered > Follow-up becomes inconsistent > Buyer intelligence gets lost > Decision-making becomes reactive.
The project develops motion without momentum. Projects don't sell because people are busy. Projects sell because someone owns the commercial journey from enquiry to contract.
Sign #3: The market gets blamed before the sales system gets audited
This is probably the biggest warning sign of all. The moment sales slow down, discussions usually focus on:
Market conditions
Interest rates
Political uncertainty
Buyer sentiment
Competition
All legitimate factors. But rarely does anyone ask:
"Is our sales architecture actually designed to convert demand efficiently?"
Before concluding that demand is weak, I would always want answers to questions such as:
How fast are leads being contacted?
Where are prospects dropping out?
Which channels are converting best?
How long does the sales cycle take?
Who owns the buyer relationship?
Where is friction occurring?
Most projects can produce marketing reports. Far fewer can clearly map their conversion process, and that should concern developers.
The Real Question I will ask
The market matters.
Demand matters.
Pricing matters.
But too often, projects assume a demand problem before examining the commercial system itself. In many cases, buyers are there.
Interest is there.
Enquiries are there.
The missing piece is velocity.
Because demand creates opportunity. Velocity creates sell-out.
And the projects that consistently outperform their competitors are usually not the ones generating the most demand.
They are the ones converting it most effectively.
Question for developers and project teams:
When sales slow down, what's the first thing your team reviews?
Market demand , or the sales system itself?
Written by Kevin Wash. / VOS Consultants
Comments