A business development commission structure should reflect what the role actually owns. Some teams identify accounts and arrange conversations; others qualify opportunities, develop partnerships or carry a revenue target. The job title alone does not define a suitable payment rule.
Map the work and handoffs before selecting a measure. A person should be able to explain what earns credit, what evidence is required and when a result is reviewed.
Define the role’s contribution
Write down where business development’s responsibility begins and ends. Identify who accepts its work and who controls the later decisions. Avoid treating a booked meeting, an accepted opportunity and a closed sale as equivalent outcomes.
For a role focused on early qualification, examine the quality of the handoff. For a role responsible for a commercial agreement, examine the relevant revenue or other agreed result. Mixed responsibilities may need separate rules that remain understandable together.
Make acceptance criteria usable
Specify what the receiving owner needs to see before accepting an opportunity. This may include account fit, the customer’s stated need and a reason for the next conversation. Decide who reviews exceptions.
Consider a fictional representative who books ten meetings, of which six satisfy the written acceptance criteria. Under a fictional plan paying 100 per accepted opportunity, those six produce 600. Counting all ten bookings would apply a different rule.
The numbers illustrate the calculation, not a recommended rate or target. The important question is whether both teams can apply the acceptance rule consistently.
Resolve shared credit before it becomes a dispute
Decide how to handle an existing account, several contributors and an enquiry that arrives through more than one channel. Keep the source and ownership history with the record.
Also define what happens when the receiving team does not review a handoff promptly. The representative needs a route to resolve the record rather than wait indefinitely for an unexplained status.
Test a business development commission structure
Prepare examples covering an ordinary accepted opportunity, a duplicate, a rescheduled meeting and a disputed rejection. Calculate the expected result independently of the tracking system.
If the plan uses thresholds or accelerators, explain which results count towards them and how a correction affects the total. The incentive examples show how a rate change can produce different payouts depending on the rule.
Examine delayed revenue measures
A later revenue result may depend on work outside the business-development role. Review the time between the original contribution and the payment event, along with the person’s influence over what happens in between.
If later outcomes form part of the plan, explain the crediting period, evidence and treatment of account transfers. Do not assume that adding a renewal or margin measure will automatically improve customer quality.
Make records and statements traceable
Agree where eligibility and acceptance are recorded, who may change them and how corrections are approved. A CRM status can support the process, but it is not proof that the underlying criteria were met.
Check that a representative can follow a payment back to the accepted result and applicable rule. Use the SDR compensation guide for related questions about targets, acceptance and plan administration.
Review the plan with both sides of the handoff
Ask business development and the receiving team where the rules create confusion or unintended incentives. Inspect examples of accepted and rejected work rather than relying only on the total pipeline amount.
Have the responsible compensation and payroll reviewers check the proposed plan. Explain changes and their effective dates clearly. Review the behaviour and quality of the work after rollout before attributing a movement in revenue to the incentive alone.
