What Should a Bengaluru Developer Put in a Sales-Mandate Brief? Scope, CRM Access, Channel Governance and KPIs

A Bengaluru sales mandate brief must define exactly what the appointed firm can sell, who controls pricing and discounts, how buyer leads are registered and attributed, how channel partners are governed, and which KPIs determine performance and commission eligibility. It must also establish CRM access, reporting obligations, compliance requirements and the transfer of sales records when the mandate ends.

The brief should function as the operating specification for the entire sales mandate, not simply a document agreeing to a commission percentage. Every material responsibility needs a named owner, an evidence source, an approval rule and a measurable outcome.

At ZippServ, we approach sales mandates as an integrated system connecting marketing, channel activation, CRM, site visits and booking conversion. This Bengaluru sales mandate brief makes each part of that system accountable to the developer.

What a Bengaluru sales mandate brief must contain

A complete brief covers eight areas:

1. Inventory and scope: Which units the mandate firm is authorised to sell, and which are excluded.
2. Decision rights: Who controls pricing, discounts, inventory releases, marketing claims and commercial exceptions.
3. CRM and data access: How leads, interactions, visits and bookings are recorded, audited and transferred.
4. Lead attribution: How the parties distinguish direct enquiries, channel-partner registrations, duplicate leads and assisted sales.
5. Channel governance: How partners are onboarded, monitored, authorised and paid.
6. KPIs and reporting: How the parties measure qualified demand, site visits, bookings, cancellations, absorption and price realisation.
7. Commercial terms: How fees are calculated, when commission is earned and when it becomes payable.
8. Termination and handover: How open opportunities, customer records, partner information and outstanding payments are handled when the mandate ends.

Omitting any of these areas creates a gap between the mandate firm’s reported activity and the developer’s ability to verify commercial performance.

Why Bengaluru developers need a more rigorous mandate brief

Bengaluru’s residential market demonstrates why sales performance must be measured against inventory movement rather than lead volume alone.

Knight Frank’s India Real Estate: Residential and Office Market, H2 2025 reported 68,760 residential launches and 55,373 sales in Bengaluru during 2025. Launches increased 23% year-on-year while sales remained broadly unchanged. Unsold inventory reached 67,518 units, up 25%, with 4.9 quarters to sell. Source: Knight Frank Research, H2 2025.

JLL’s Q2 2026 Bengaluru residential report separately recorded a 6% quarter-on-quarter decline in demand to approximately 17,000 units, a 20% decline in launches and a 3.1% rise in overall residential prices. These figures describe a different reporting period and research scope. Source: JLL, Bengaluru Residential Market Q2 2026.

The commercial implication is clear: developers need to know whether their inventory is moving, which channels produce qualified buyers, how quickly prospects progress through the sales funnel and whether bookings survive subsequent contractual milestones.

A mandate firm’s lead count does not answer those questions. A booking count does not establish net absorption. A channel-partner register does not establish channel productivity.

A Bengaluru sales mandate brief must connect all three to verifiable records.

Bengaluru sales mandate brief: what the sales reconciliation exposed

In a Bengaluru residential project reviewed by ZippServ, the monthly sales review reported 350 enquiries, 47 site visits and eight bookings.

The developer reconciled the mandate firm’s report against the CRM, channel-partner register and booking records. The reconciliation exposed four control failures.

1. Duplicate channel-partner registrations. Two partners had registered the same buyer using different phone-number formats. Without a consistent duplicate-resolution rule, both registrations could support competing claims over the same sale.

2. Misattributed direct enquiries. A buyer who had originally enquired through the developer’s website appeared in the CRM as a channel-partner-generated lead. The record therefore did not reliably establish the buyer’s originating source.

3. Missing site-visit outcomes. Completed visits did not consistently have recorded outcomes. The sales team could not reliably distinguish prospects requiring follow-up from buyers who had rejected the project, postponed their decision or moved to another option.

4. A booking that had not reached the commission milestone. One booking appeared in the reported sales figures before reaching the contractual milestone required for commission eligibility. The sales report and the commission calculation were therefore measuring different things.

These failures affect more than reporting accuracy. They create disputes over commission, obscure channel productivity and prevent the developer from identifying where genuine sales opportunities are being lost.

The monthly figures also require careful interpretation. Dividing 47 visits by 350 enquiries produces a ratio of 13.4%; dividing eight bookings by 47 visits produces 17.0%. Those are same-period ratios, not automatically true lead-to-visit or visit-to-booking conversion rates. Proper conversion analysis requires the relevant leads, visits and bookings to be linked through defined cohorts and attribution windows.

Four controls the brief must establish

Failure	Required control	Evidence the developer should receive
Duplicate registrations	Unique lead IDs, standardised contact matching and documented tie-break rules	Lead-registration history and duplicate-resolution record
Direct lead misattribution	Separate fields for original source, current owner and commission eligibility	Source history and approved attribution record
Missing visit outcomes	Mandatory visit status, outcome, next action and follow-up date	Site-visit register linked to CRM records
Booking reported before the commission milestone	Separate gross bookings, qualifying bookings, cancellations and payment eligibility	Booking documentation and commission reconciliation

The mandate firm should operate these controls as part of the agreed sales process, rather than treat them as corrections performed only at month-end.

Bengaluru sales mandate brief: real estate professionals reviewing architectural plans during a planning meeting

Photo: RDNE Stock project on Pexels.

The developer must be able to trace any reported booking from the unit and booking record to the buyer’s CRM history, originating enquiry, site visit and applicable payment condition.

The governing principle of a Bengaluru sales mandate brief is simple: a lead is not a booking, a booking is not net absorption, and a reported booking is not automatically commission-eligible.

A mandate firm should be evaluated on both commercial performance and the reliability of its reporting. High lead volume does not establish sales quality, and gross bookings do not establish net absorption or commission entitlement.

1. Define the inventory and exact scope of the mandate

A Bengaluru sales mandate brief starts by specifying exactly which inventory the appointed firm is authorised to market and sell.

“Manage sales for the project” is insufficient. The scope should identify the project, phase, relevant registration details, towers, floors, configurations and individual units covered by the mandate. It should explicitly exclude developer-reserved units, existing protected leads, inventory assigned to another team and units not yet authorised for release.

Attach a dated inventory schedule to the Bengaluru sales mandate brief containing:

• Unique unit ID, tower, floor and configuration.
• Availability status, existing booking or hold.
• Approved price and applicable charges.
• Permitted concessions and incentives.
• Inclusion or exclusion from the mandate.
• The person authorised to change the record.

Keep inventory changes auditable

Every booking, cancellation, hold, withdrawal or newly released unit should have an authorised update, timestamp and identifiable user.

The mandate firm must work from the same approved inventory record as the developer’s sales and finance teams.

This matters when the developer retains premium units for direct sales, releases inventory in phases or changes pricing during an engagement. Without documented scope boundaries, the parties can disagree over whether a transaction belonged to the mandate and whether commission is payable.

Required acceptance test: Both parties should be able to select any unit and independently establish whether it is available, whether the mandate firm may sell it, what price applies and who can approve a change.

2. Define the mandate model and commercial authority

A sales-mandate firm may manage the overall sales function while the developer retains authority over pricing, inventory release and exceptional commercial commitments.

A Bengaluru sales mandate brief must distinguish execution responsibility from commercial decision-making authority.

Activity	Mandate firm’s responsibility	Developer’s retained authority
Sales strategy	Recommend positioning, campaigns and channel allocation	Approve strategy and commercial objectives
Lead management	Qualify, assign, follow up and record outcomes	Define service standards and data requirements
Marketing	Execute within approved scope and budget	Approve expenditure and material project claims
Pricing	Communicate approved prices and recommend changes	Approve price changes and concessions
Inventory	Track operational availability and sales progress	Approve inventory releases and withdrawals
Channel partners	Onboard and manage partners under the agreed policy	Set compliance requirements and approve exceptions
Booking process	Coordinate documentation and record milestones	Retain designated legal, finance and approval responsibilities
Performance	Report outcomes, exceptions and corrective actions	Decide changes to scope, budget or sales strategy

Every approval category should specify a named decision-maker, the approval channel, permitted limits, response time and escalation procedure.

A discount request above the mandate firm’s delegated limit, for example, must follow a defined approval process. The brief should establish who approves it, what supporting information is required and how the decision is recorded.

Choose exclusivity deliberately

An open mandate, exclusive agency and exclusive-right-to-sell arrangement can produce different commercial obligations.

The Bengaluru sales mandate brief must define which arrangement applies, which inventory it covers, how long it lasts and what happens when the developer sells directly, a buyer walks into the site office or an existing prospect closes through another channel.

The agreement should also establish review points and the consequences of sustained underperformance. Exclusivity should not mean giving up inventory or commercial control without a corresponding accountability framework.

3. Put CRM access and lead attribution in the Bengaluru sales mandate brief

CRM access in a Bengaluru sales mandate brief determines whether the developer can independently inspect sales activity, verify commission claims and preserve the buyer pipeline after the mandate ends.

The brief should identify the system of record and define its mandatory fields, user permissions, audit trail and export requirements.

Every lead record should include:

• Unique lead ID, creation date and original source.
• Campaign, channel partner or referring source.
• Current lead owner and assignment history.
• Qualification status and buying requirements.
• Dated contact attempts and outcomes.
• Site-visit status, attendance and follow-up.
• Booking status, associated unit and contractual milestones.
• Cancellation, reversal or lost-opportunity reason.

The mandate firm should not be able to submit a management report that the developer cannot reconcile against the underlying records.

Separate three attribution concepts

Original lead source identifies where the qualifying enquiry originated.

Current relationship owner identifies the person or team responsible for the next sales action.

Commission attribution determines whether the transaction qualifies for payment under the agreement.

These fields serve different purposes and should not be treated as interchangeable.

The brief must prescribe accepted registration evidence, duplicate handling, protected existing leads, walk-ins, referrals, assisted sales, registration validity and a formal dispute-resolution procedure.

Give the developer usable data access

The developer should have role-appropriate access to the CRM, relevant lead histories and reporting dashboards. If the mandate firm uses its own platform, the agreement should specify integration requirements, export formats, access rights and record-transfer deadlines before signing.

The contract must also define how personal information is accessed, shared, retained and deleted under applicable requirements. Relevant primary sources include India’s Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025.

Required acceptance test: The developer must be able to export active and closed leads, source histories, site visits, bookings, cancellations and relevant record changes in a usable format.

4. Govern channel partners as a measurable sales network

A long channel-partner list does not establish a productive distribution network. The developer needs evidence of partner authorisation, activity, buyer quality, conversion and compliance.

A Bengaluru sales mandate brief should make the mandate firm responsible for maintaining a current partner register, checking required credentials, issuing approved project information and enforcing the same registration and attribution rules across the network.

Establish a controlled onboarding process

The partner register should contain each partner’s identity and business details, agreement status, relevant RERA registration information, authorised contacts, commission terms and verification history.

Sections 9 and 10 of the Real Estate (Regulation and Development) Act, 2016 address real-estate-agent registration and functions. The developer should verify applicable requirements for the mandate firm and channel partners facilitating sales, including current Karnataka RERA requirements.

Registration checks, approved marketing claims and record-keeping requirements should form part of the operating process, not an onboarding formality.

Control marketing and channel communications

Every authorised partner should receive the current price schedule, approved project information and valid marketing assets. The brief should specify who approves revised materials, how obsolete versions are withdrawn and how unauthorised representations are escalated.

Partners must follow the agreed lead-registration rules and commission policy. The mandate firm should maintain an auditable record of partner-generated enquiries, qualified leads, completed site visits, bookings and cancellations.

Commission policies should define the calculation base, earning event, payment milestone and treatment of cancelled or disputed transactions. Where more than one channel has influenced a sale, attribution must follow the agreed contractual rules.

Marketing expenditure, campaign-account access and ownership of campaign records should also be documented.

Buyer funds should ordinarily flow directly to the developer through authorised banking channels. Any exceptional arrangement involving an intermediary must be separately authorised and legally reviewed.

5. Define KPIs that measure commercial progress

A mandate should not be judged solely by leads generated, calls made or gross bookings reported.

A Bengaluru sales mandate brief must distinguish activity, conversion and commercial outcomes in its KPI schedule. Every metric needs a written formula, denominator, reporting period, source system, responsible owner and target.

KPI	Definition	Management decision
Response SLA attainment	Valid leads contacted within the agreed time ÷ valid leads covered by the SLA	Improve speed-to-lead and allocation
Contact rate	Unique valid leads reached ÷ unique valid leads assigned	Assess reachability and follow-up
Qualified-lead rate	Leads meeting agreed qualification criteria ÷ leads assessed	Evaluate demand quality and targeting
Visit show-up rate	Completed site visits ÷ scheduled visits in the same visit cohort	Improve visit confirmation and attendance
Visit-to-booking conversion	Qualifying bookings attributed to a defined visit cohort ÷ completed visits in that cohort	Assess progression from visit to booking
Net bookings	Gross bookings less cancellations and reversals under the agreed recognition rule	Measure retained bookings
Booking-to-agreement conversion	Executed sale agreements ÷ eligible bookings reaching the relevant reporting window	Identify documentation and closure bottlenecks
Net price realisation	Realised consideration under the agreed calculation basis after defined concessions	Monitor discounting and commercial discipline
Cost per qualified lead	Included, attributable acquisition cost ÷ qualified leads	Evaluate acquisition efficiency
Cost per net booking	Included, attributable sales and marketing cost ÷ net bookings	Assess commercial efficiency
Partner productivity	Qualified leads, visits, net bookings and cancellations by partner	Identify productive and inactive partners
CRM completeness	Records passing agreed field and audit checks ÷ records reviewed	Verify reporting quality

These are operating definitions. The parties must agree on how repeat visits, walk-ins, duplicates, cancellations, delayed bookings and incomplete transactions are treated.

Measure net absorption against inventory

The Bengaluru sales mandate brief should also define inventory absorption or sell-through using an explicit denominator.

The denominator might be opening saleable inventory, released inventory or average available inventory. Each produces a different interpretation, so the chosen definition must remain consistent across reporting periods.

Report net bookings alongside available stock, units released, cancellations, realised price and time-to-sell. This makes it possible to distinguish increased sales activity from actual movement in the inventory the developer is trying to sell.

Treat the sales funnel as a diagnostic system

The Bengaluru project reviewed by ZippServ demonstrates why lead, visit and booking counts need to be linked at record level.

The figures, 350 enquiries, 47 site visits and eight bookings, describe the reported monthly activity. The four control failures prevented the developer from relying on the CRM and partner register as consistent sources for attribution, visit outcomes and commission eligibility.

The correct response is to link every reported outcome to its underlying record and investigate where the funnel breaks down.

A reporting system should show where leads are lost, which channels generate qualified demand, which visits progress to bookings and which bookings reach the agreed commercial milestones. It should also assign a corrective action when required records are incomplete or conversion falls below the agreed threshold.

Targets should be set against the project’s inventory, price positioning, historical performance and baseline. A higher lead count is not a substitute for qualified demand, completed visits and retained bookings.

6. Specify commission bases, earning events and payment terms

A Bengaluru sales mandate brief must define more than a commission percentage. The calculation base and payment trigger determine the amount and timing of the actual obligation.

The brief should state whether the mandate fee is fixed, performance-linked or a combination, and whether marketing expenditure, creative production, CRM costs, site operations and channel-partner commissions are included.

For transaction-linked fees, specify:

• The exact commission calculation base and included or excluded charges.
• The treatment of applicable taxes, subject to tax advice.
• The event that makes commission earned and the event that makes it payable.
• The evidence required to verify the payment milestone.
• The treatment of cancellations, refunds and reversals.
• Eligibility for direct developer sales and protected leads.
• The treatment of registered prospects that close after termination.

Consider a straightforward calculation: a 1% commission on an agreed base of ₹1 crore equals ₹1 lakh. The same rate applied to a base of ₹1.2 crore produces ₹1.2 lakh. The rate has not changed; the contractual base has.

The agreement must allow both parties to reproduce the same calculation from the same booking record.

It should also specify invoicing requirements, payment timelines, reconciliation responsibilities and the process for resolving disputed amounts. Commission rules must be aligned with the lead-attribution and booking-recognition policies established elsewhere in the brief.

7. Build reporting and escalation into the mandate

A monthly presentation is not a substitute for operational reporting.

A Bengaluru sales mandate brief should define the reports the mandate firm must deliver, their recipients, reporting cut-off, source systems, supporting records and procedures for correcting restated figures.

A practical review structure is:

Review	Focus	Required output
Daily exception review	Uncontacted leads, overdue follow-ups, approval blockers and inventory discrepancies	Actions, owners and deadlines
Weekly sales review	Qualified demand, site visits, funnel conversion, partner contribution and pipeline	Performance analysis and corrective actions
Monthly commercial review	Net bookings, available inventory, price realisation, costs and mandate performance	Decisions on pricing, scope, budget and channel allocation

Every exception should have an owner and a resolution date. Repeated attribution disputes, missing CRM records, unapproved pricing or persistent SLA failures should trigger the agreed escalation procedure.

Performance reviews must also separate responsibilities controlled by the mandate firm from outcomes affected by developer decisions, product positioning, price, inventory release and market conditions.

8. Define termination and handover before the mandate begins

The developer must retain operational continuity when the mandate ends.

The Bengaluru sales mandate brief should define the handover and exit terms that the agreement will formalise, including notice periods, termination conditions, cure periods, pending-booking treatment, accrued fees and any post-termination commission entitlement.

It should also specify the transfer of:

• Active and closed lead records.
• Original source and attribution history.
• Site-visit records and next actions.
• Booking documentation and cancellation status.
• Channel-partner register and outstanding claims.
• Approved marketing assets and campaign records.
• Reporting history, reconciliations and unresolved exceptions.

The handover clause should identify the responsible person, required format, transfer deadline, access-revocation procedure and acceptance criteria.

Any post-termination commission period should specify its duration, eligible registered prospects and supporting evidence. This protects legitimate claims without creating indefinite payment obligations.

Customer records must be transferred and retained according to the agreed contractual and applicable data-protection requirements.

Required acceptance test: The developer must be able to continue following up with eligible prospects, reproduce current sales reports and reconcile pending payments without relying on the former mandate firm’s continued cooperation.

The sales-mandate brief: a pre-signing checklist

Use this Bengaluru sales mandate brief checklist to assess whether the document is ready to become part of the mandate agreement.

Section	Required specification
Project and inventory	Project details, registrations, unit schedule, exclusions and inventory-release procedure
Mandate scope	Services, inventory perimeter, mandate type, term and review points
Authority matrix	Named owners, delegation limits, approval timelines and escalation routes
Pricing and marketing	Approved prices, concession policy, marketing budget and authorised claims
CRM and attribution	Mandatory fields, access rights, duplicate rules, source history and export requirements
Channel governance	Partner register, verification, onboarding, attribution, commission and conduct controls
KPIs	Formulas, baselines, denominators, targets, owners, source systems and reporting cadence
Commercial terms	Fee basis, commission base, earning and payment triggers, cancellations and expenses
Compliance and data	Applicable registration checks, approved project information, access controls and data handling
Termination	Notice, open opportunities, post-termination claims, record transfer and financial reconciliation

Five tests before the developer signs

Inventory test: Can both parties independently determine whether a unit is covered by the mandate, available for sale and subject to a particular approved price?

Authority test: Can the sales team identify who approves a discount, exception or inventory change and how that approval is recorded?

Attribution test: Can a disputed lead be resolved through dated evidence and an agreed rule rather than competing recollections?

Measurement test: Can the developer reproduce net bookings, conversion results and commission calculations from the underlying records?

Handover test: Can the developer retrieve its records, continue working the pipeline and reconcile outstanding obligations when the mandate ends?

If any answer is no, the corresponding provision needs to be strengthened before execution.

Frequently asked questions

What should a Bengaluru sales mandate brief include?

A Bengaluru sales mandate brief should define inventory scope, decision rights, CRM access, lead attribution, channel governance, KPIs, commission terms, reporting and exit requirements.

What is the difference between a sales-mandate brief and a sales-mandate agreement?

The brief defines the operational model, scope, authority, systems, KPIs and commercial requirements. The agreement establishes the parties’ binding obligations, including fees, compliance, termination, confidentiality and remedies. The brief can be incorporated into the agreement through schedules following legal review.

What CRM access should a developer require?

The developer should have access to relevant lead records, source attribution, interaction histories, site visits, bookings, cancellations and reporting data. The agreement should define permissions, auditability, export formats, data-handling responsibilities and handover procedures.

How should channel-partner lead disputes be resolved?

The mandate brief should define accepted registration evidence, duplicate handling, protected leads, the treatment of direct enquiries and assisted channels, registration validity and a documented escalation procedure. The commission agreement should explicitly adopt the attribution policy.

Which KPIs matter most in a Bengaluru sales mandate?

At minimum, track response SLA attainment, qualified-lead rate, completed site visits, cohort-based visit-to-booking conversion, net bookings, cancellations, inventory absorption, price realisation and channel-partner productivity. Each metric needs a defined formula and project-specific baseline.

How should a developer evaluate the mandate firm’s performance?

Evaluate both commercial outcomes and execution quality. Review net bookings, inventory movement, price realisation, funnel progression, partner contribution, data completeness and compliance. Separate what the mandate firm controls from decisions and market conditions controlled by the developer or influenced by external factors.

Conclusion: every reported sale must be verifiable

A Bengaluru sales mandate brief must allow the developer to establish what inventory is covered, who controls each commercial decision, where buyer relationships are recorded, how sales performance is measured and what happens when the engagement ends.

The project reviewed by ZippServ demonstrates the practical importance of those controls. A monthly report containing 350 enquiries, 47 site visits and eight bookings is useful only when the underlying records establish source attribution, visit outcomes and the contractual conditions for commission.

A well-defined mandate connects every material responsibility to an approval rule, a system record, a measurable result and a contractual consequence. It makes inventory control, CRM access and channel governance integral to sales accountability.

A developer should never have to rely on a mandate firm’s summary to verify the mandate firm’s performance. The brief must give the developer the records, rules and calculations needed to verify every material claim.

For related guidance, read ZippServ’s Real Estate Marketing in Bangalore: A Sales Mandate Playbook and What to Look for in a Real-Estate Marketing and Sales Partner in Bangalore.

Sources

1. Knight Frank India, India Real Estate: Residential and Office Market, H2 2025. Original report.
2. JLL, Bengaluru Residential Market Dynamics, Q2 2026. Research page.
3. Government of India, Real Estate (Regulation and Development) Act, 2016. India Code.
4. Government of India, Digital Personal Data Protection Act, 2023. India Code.
5. Ministry of Electronics and Information Technology, Digital Personal Data Protection Rules, 2025. Official source.
6. Google Search Central, AI features and your website.

About Zippserv: Real-estate marketing and sales mandates for Bengaluru developers.
Focus: Marketing, sales mandates, and channel strategy for plotted, apartment, and villa developers across Devanahalli, Sarjapur, Hoskote, Hennur, and Nelamangala.
Work: Karnataka RERA-compliant launches, channel structures, payout reforms, and absorption turnarounds.