Channel partners can drive a large share of a developer’s bookings, and they will leave quickly if they feel the arithmetic is unfair. Most disputes are not about the percentage. They are about who brought the buyer, when a commission becomes payable and why a statement shows a different number from the one in someone’s head.
Decide who owns a lead, and for how long
The first rule to write is lead protection. When a partner registers a buyer, how long does that registration protect them? Thirty days, sixty days, until the buyer visits? Whatever you choose, write it down and apply it to everyone.
A configurable protection period in the system, with timestamps on registration, turns an argument into a lookup. When two partners claim the same buyer, the record answers who registered first and whether the protection was still valid.
Choose a commission structure you can explain in one minute
A flat percentage per booking is simple. Tiered rates reward volume. Multi-level referrals extend reach but add complexity. Whichever structure you pick, test it with three sample bookings and check the numbers by hand before launch.
Propto CRM lets the business configure referral levels, commission types and a team incentive ladder in settings, so the structure lives in one place and changes without a software release. If a partner cannot understand their commission after reading one page, the structure is too complicated.
Define when a commission becomes payable
The trigger matters as much as the rate. Some developers pay on token, some on a percentage of the booking amount received, some on agreement or registry. State the trigger, and say what happens if the buyer cancels.
Link the trigger to something the system can see, such as the received amount on the booking. When payout depends on a data point rather than a conversation, partners can check their own position without calling you.
Give partners clear statements and a way to ask for incentives
A statement should list each booking, its date, the commission and the status. Date-range statements let you close a period and answer questions about it without reopening the whole year.
Incentive requests, where agents ask for rewards on booked property, need a visible path: request, review, accept or reject with a reason. Publishing the rules in advance, such as what qualifies and how requests are reviewed, reduces the number of requests you have to refuse.
Treat KYC and payouts as a process, not a favour
Partner KYC should be complete before money moves. Track KYC status on the partner record, and let payouts move through statuses such as pending, confirmed and released so that everyone understands where a payment stands.
A partner who sees “pending, awaiting KYC” knows what to do. A partner who sees nothing calls your accounts team. The cost of one phone call is small, but ten partners a week make a job.
Settle disputes with evidence and consistency
Eventually a dispute will arrive. Respond with the recorded registration date, the protection rule, the booking record and the commission statement. Keep exceptions rare and recorded, and communicate the decision with its reason.
Over time, partners learn that the system is the referee. That predictability is worth more than a slightly higher percentage, because partners choose to spend their time with developers whose arithmetic they trust.
A worked example: two partners, one buyer
Suppose Partner A registers a buyer on the first of the month and Partner B registers the same buyer on the twelfth. The buyer later books through a visit organised by Partner B. Without a recorded protection rule, both partners believe they earned the commission, and your team spends a week on calls.
With a protection period and recorded registration timestamps, the answer is a lookup. If your policy protects registrations for sixty days, Partner A holds the lead, and the commission statement shows it. You may still choose to share the commission as a goodwill exception, but you do so deliberately and record the reason, so it does not become a precedent.
Mistakes that damage partner trust
The biggest mistake is changing the rules after the fact. If a rate or trigger changes, announce it with an effective date and apply it only to later bookings. Another is hiding the arithmetic. A statement that shows only a total invites suspicion, while one that lists each booking, rate and status invites questions you can answer in one line.
Finally, do not forget the human side. Pay on schedule, answer queries quickly and acknowledge good performance with ranks or incentives you can afford. Partners talk to each other, and a developer known for fair, predictable payouts attracts better partners over time.
A short checklist before you publish the policy
Read the policy as a partner would. Can you tell, in one minute, how long a registered lead is protected, what rate applies, when a commission becomes payable and how to see your statement? Does the document say what happens on cancellation, and who decides exceptions? Share it with two trusted partners before it goes to everyone, and ask them what they would argue about. Their answers will point to the gaps. Publish the final version with an effective date, and keep older versions on file so you can show which rules applied to which booking.
Remember that a policy is a living document. Review it each quarter with a few partners, note what caused questions and update the wording rather than waiting for a dispute to prove the point. Every revision should carry a date, a short summary of what changed and a clear statement of which bookings it applies to, so that nobody has to guess.
What is lead protection in real estate partner programs?
A defined period during which a partner’s registered lead is theirs, which prevents ownership disputes.