Why projects don't sell: a diagnostic, not a marketing brief

The diagnostic sequence

Almost every developer we meet with slow inventory has already increased marketing spend, changed the creative, and often changed the agency. Occasionally that was the right response. Usually it was an expensive way of confirming that the problem was elsewhere.

The reason is that marketing addresses only one of four possible failures — insufficient top-of-funnel demand — and that is the least common of the four. If the product is mispositioned, more visitors see a product that is not for them. If the price is wrong, more visitors negotiate and leave. If the process is leaking, more leads arrive and are lost at the same rate.

The diagnostic therefore has to run in a specific order, from the bottom of the funnel upward, because a leak at a lower stage invalidates any conclusion about a higher one.

Start with the site visit conversion rate

The single most diagnostic number in a stalled project is visit-to-booking conversion. A visitor who has travelled to the site has demonstrated real intent; losing them is expensive and informative.

If visit-to-booking conversion is healthy and the problem is volume, the issue is upstream — demand generation or lead handling. If visit-to-booking conversion is poor, no amount of additional footfall will help, and the honest conclusion is that something about the product, the price or the site experience is losing people who arrived wanting to buy.

The fastest way to find out which is to listen to recorded calls and to sit in the sales gallery for a day. Both are unglamorous and both routinely produce the answer within hours — an objection nobody has addressed, a competitor comparison nobody has a response to, a show unit that disappoints, an approach road that sets the wrong expectation.

The uncomfortable possibility: the product is wrong

The hardest diagnosis to deliver is that the configuration mix is wrong for the catchment — that the project was designed for a buyer who does not exist here in sufficient numbers.

It is hard because it is largely irreversible after sanction. Carpet areas, configuration mix and efficiency are fixed. The remaining levers are price, payment structure, release sequence and repositioning to a different segment — a narrower set of options than the developer had at design stage.

It is also the diagnosis most often avoided, because accepting it means accepting that the error was made upstream by the promoter rather than downstream by the sales team. But avoiding it produces years of expensive activity aimed at a problem that is not the problem.

Where this is the conclusion, the honest remedy is usually to re-price into the segment the product actually fits, accept the realisation that segment supports, and protect velocity — rather than to defend an aspirational price into a segment that is not there.

Price is a symptom as often as a cause

Developers frequently frame the problem as price and then reject the remedy, because cutting price is painful and visible. That framing conflates two different situations.

If the product is correctly specified for its segment and simply priced above what that segment has demonstrably paid, the remedy is a price correction and it will work. If the product is specified for a segment that is not present, a price cut moves the project into a different segment's range — which can work, but it is a repositioning rather than a discount, and it needs the narrative, the channel mix and the sales pitch to change with it.

The distinction matters because the second case requires far more than a new price sheet. Cutting price without repositioning produces a cheap version of a product aimed at the wrong buyer, and the market reads it as distress.

What we do first on a stalled mandate

When we are appointed on a project that is already slow, the first two weeks are diagnosis rather than activity, and we resist pressure to launch a campaign in that window.

We instrument the funnel and establish the real conversion rates at each stage. We listen to a sample of recorded calls. We spend time in the gallery observing actual visits. We map the competitive set on the dimensions buyers compare and identify where this project loses. We pull registered transaction data for comparable inventory to establish what the catchment has actually paid. And we ask channel partners in the catchment, directly, why they are not selling it.

That last conversation is frequently the most useful and the least often had. Channel partners know exactly why a project is not moving, they will say so if asked in a way that does not require them to be diplomatic, and their answer is usually specific: the price, a competitor's better carpet, a possession-date credibility problem, or a payout that arrives too slowly to be worth the effort.