Lessons from Mitch’s development sales career
Experience behind the questions.
These anonymized accounts come from the founder’s development sales career, before the Stak72 advisory offer. They are not Stak72 client results or forecasts. They show why visibility and follow-up remain central to the review.
01 / VisibilityA lesson in See
A competitive offer needs the right audience.
In my previous role leading a development sales team, we took on a 256-unit project after another marketing firm had been selling it for a year. Sales had stalled, even though other projects in the market were still selling.
The incentives were competitive, but awareness was low. We put the offer back in front of buyers and brokers. My team went on to sell the remaining 163 suites in about 180 days.
This was a particular outcome from a full sales mandate, not a Stak72 advisory engagement or a forecast for another development. Sales pace depends on the market, product, pricing, and execution. Stak72’s role today is to help your existing team identify gaps and implement improvements.
The lesson: check who knows about the offer before changing it.
Today we look for the same visibility gaps in campaign and CRM data, then help your existing team improve how the offer reaches buyers.
02 / Follow-upA lesson in Act
Interest needs timely follow-through.
A developer ran its own campaign for the final tower in a master-planned community and registered more than 1,500 people. By the time the list reached my sales team, it had produced no sales.
Most registrants had received a few emails. We closed a dozen sales from the list. Most of the remaining registrants had already bought somewhere else.
The lesson: generating interest is only the beginning of the process.
Today we review response speed and follow-through, then build the routing, automation, and human handoffs that keep interest from going cold.
Mitch Parker · Past development sales work · Not Stak72 advisory results · Outcomes vary by project