Start with the partner relationship
Agree who can become a partner, which information is needed and how an application or referral is reviewed. Keep the partner relationship distinct from the referred customer so each record has a clear purpose and owner.
Define the stages that matter to the team: submitted information, review, acceptance, active collaboration and any suspended or closed relationship. The available controls should be demonstrated against the intended workflow before activation.
Make referral ownership and exceptions explicit
Decide what qualifies as a referral and how duplicate, existing-customer or disputed introductions are handled. A source label alone should not automatically establish a commercial entitlement.
Where approved integrations connect referrals to leads or sales, agree the authoritative record and the conditions for each handover. Failed or conflicting updates need a visible route for review rather than silent reassignment.
Separate activity tracking from payments
Any commission, discount or other partner benefit requires agreed eligibility, calculation, approval and settlement rules. Returns, cancellations and disputed outcomes should be addressed in that policy before automation is introduced.
This feature page does not promise automatic commission calculation or payouts in every workspace. Required capabilities, finance integrations and payment responsibilities must be confirmed in the implementation scope.
Introduce a controlled working process
Begin with one representative partner journey and test the information captured, role access, approval steps and reporting. Confirm that partners cannot see unrelated customer records or private commercial information.
Handover should identify who maintains the programme rules, resolves disputes and reviews exceptions. The aim is a dependable operating process, not a public claim that every referral is instantly approved or payable.
