Exclusive mandate vs In-house team
Exclusive sales mandate vs in-house sales team: which should a developer choose?
Developers frame this as a cost question. It is primarily an accountability and capability question, and the right answer depends on the developer's pipeline, not on the fee.
The short answer
An in-house sales team suits a developer with a continuous multi-project pipeline, strong internal sales leadership and an established channel network. An exclusive mandate suits a developer with an intermittent pipeline, a first project in a new micro-market, a stalled project, or no single internal owner of velocity and realisation. Many developers are best served by a hybrid: in-house ownership with mandate-level strategy, governance and distribution on specific projects.
Side by side
The comparison.
| Factor | In-house sales team | Exclusive mandate partner |
|---|---|---|
| Fixed cost | Permanent payroll carried between launches | Largely variable; tied to the project |
| Speed to launch-ready | Months to recruit, train and systematise | Weeks; operating stack already exists |
| Accountability for the number | Diffused across marketing, sales and promoter | Single partner owns velocity and realisation |
| Channel partner depth | Built from scratch or inherited per project | Existing tiered network across the MMR |
| Market intelligence | Limited to own projects | Cross-project, cross-micro-market evidence |
| Pricing discipline | Vulnerable to internal pressure | Documented ladder with an authority matrix |
| Control | Full, direct | Shared; promoter approves ladder and strategy |
| Institutional memory | Retained in the business | Documented, but partly held by the partner |
| Best for | Continuous multi-project pipeline | Intermittent pipeline, new markets, stalled stock |
Exclusive mandate compared with In-house team.
The cost comparison most developers get wrong
The instinct is to compare a mandate's fees against the salary cost of an equivalent team, conclude the team is cheaper, and build one. The comparison omits most of the in-house cost.
An in-house team is carried between launches. It needs a CRM, attribution infrastructure, a channel partner function, a pricing discipline and a reporting layer, which are built rather than bought. It takes months to become effective, during which a launch window may pass. And when a key closer leaves, a meaningful share of conversion capability leaves with them.
For a developer launching one or two projects a year, those costs usually exceed a mandate's. For a developer with a continuous pipeline across several simultaneous projects, the arithmetic reverses.
Accountability is the real difference
The decisive variable is rarely cost. It is whether anyone inside the business owns the combined outcome of velocity and realisation, with authority over every input that produces it.
In most in-house structures, nobody does. Marketing owns leads, sales owns bookings, finance owns collections and the promoter owns price. Each function performs against its own measure, and when absorption slows the diagnosis becomes a discussion about which function is responsible.
A mandate collapses that into one line. Whether that is better depends on whether the developer can create the same single line of accountability internally — some can, and they should.
The hybrid most developers end up with
In practice the strongest arrangement for mid-sized developers is often a hybrid: an in-house sales leadership that owns the relationship with buyers and the long-term brand, with mandate-level support on strategy, pricing governance, channel distribution and funnel instrumentation for specific projects — particularly launches in new micro-markets and recovery of slow inventory.
Choose in-house if you have a continuous multi-project pipeline and can create a single internal owner of velocity and realisation. Choose an exclusive mandate for intermittent pipelines, new micro-markets and stalled projects. Consider a hybrid if you want to retain the buyer relationship while importing strategy, governance and distribution.
The Genesis verdict
Questions
Frequently asked.
Is an exclusive mandate more expensive than an in-house team?
Not once the full in-house cost is counted — payroll carried between launches, CRM and attribution infrastructure, channel partner management, and time to become effective. For developers launching intermittently, a mandate is frequently cheaper. For those with a continuous multi-project pipeline, an in-house team usually is.
Does a mandate mean giving up control of pricing?
No. The developer approves the price ladder and every revision. What changes is that pricing becomes a documented strategy with a release sequence and an authority matrix, rather than a number that moves in individual negotiations.
Related comparisons
- Sole selling vs multiple agenciesMultiple agencies look like more reach. In practice they usually mean several parties with a rational incentive to discount the developer's own product against each other.
- Channel partners vs direct salesDevelopers often try to reduce channel partner dependence to save commission. Compared on cost per booking rather than on the commission line, channel partners are frequently the most efficient source available.
- Advisory firm vs traditional brokerBoth may be compensated on transactions. The difference is what they are accountable for before the transaction — and whether they will tell you not to proceed.
The first decision
Let's start before the building.
Send us the site, the scheme or the stalled inventory. We will tell you what we think — including when the answer is not to proceed.