In my years of CRM consulting and sales strategy work, one tension keeps coming back. Executives talk about customer-centricity while their compensation plans, metrics and processes reward something else.
The contract is signed and the salesperson moves on. The customer still has to implement, learn and achieve the result that justified buying. If the sales system ends at the signature, the customer carries a promise into a part of the company that may not know it was made.
The commercial question is how to reward acquisition without making the rest of the relationship someone else's problem. The answer starts with incentives and the handoff. A new CRM feature will not settle those responsibilities for you.
Look at what the plan rewards
A quota and commission plan creates a clear focus on new revenue. It can also encourage discounting, optimistic commitments and a rush to close if nothing in the plan makes their later consequences visible.
That is a reason to inspect the plan, not to assume every salesperson oversells. People respond to what leadership measures, what managers ask about and what they are paid to achieve. If a rep loses by slowing a deal to clarify an implementation risk, the organization has created a conflict between its stated values and its incentives.
Start with recent accounts that struggled after buying. Compare what was promised, what delivery understood and how the closing team was rewarded. Include successful accounts as a comparison. A pattern can identify a problem worth investigating; it does not by itself prove that compensation caused churn.
Assign a fair share of responsibility
Keeping acquisition central while recognizing customer outcomes is possible. The design depends on the sales motion, account value and influence each role has after the sale.
An expansion component may encourage a rep to remain interested in the customer's success. A team measure may support cooperation. A deferred component may discourage a commitment that cannot survive the first implementation period. Each option also has drawbacks: unclear credit, delayed pay or incentives to avoid difficult customers.
Do not make a salesperson personally responsible for every later failure. Product defects, a delivery shortfall or a customer's change of strategy may be outside their control. Nor should a satisfaction score become the only measure: survey response and expectations can complicate what it tells you.
Work through real situations before choosing the plan. Who gets credit when sales creates the relationship and customer success identifies the expansion? What happens if implementation is late because of the supplier? How are agreed exceptions documented? Have the appropriate employment and compensation review before introducing terms that affect pay.
The aim is a clear, fair connection between behavior and reward. A complicated plan that nobody can explain is likely to produce argument rather than cooperation.
Make the handoff a transfer of commitments
A useful handoff starts before the signature. Delivery or customer success should understand material requirements early enough to challenge a promise the organization cannot meet.
At kickoff, bring the salesperson and the continuing owner into the same conversation. Ask the customer to confirm the intended result, scope, dependencies and unresolved concerns. This creates an opportunity to correct an assumption before it becomes an implementation dispute.
Leave written notes people can use: stakeholders, decision reasons, commitments, exclusions, success criteria and what still needs clarification. A transcript or a long activity history is not automatically a transfer of understanding. Someone needs to make the relevant facts accessible.
Name the owner for the next phase and the route for bringing sales back. Strategic accounts may benefit from continued involvement in business reviews and expansion discussions. Other accounts need a clean transition with a dependable escalation path. The customer should know whom to contact, without having to resolve an internal ownership debate.
Keep the metrics honest
Net revenue retention is often useful for a recurring-revenue business, but its definition matters. ChartMogul's documentation measures revenue retained from an existing customer cohort, including expansion and losses from contraction and churn. It excludes new business. Treatment of reactivation should follow the chosen reporting policy.
For a hypothetical cohort starting with 100 units of recurring revenue, adding 10 in expansion and losing 5 to contraction and 8 to churn leaves 97: net retention of 97%. Winning 20 from new customers does not change that cohort's result.
New business still matters; measure it separately. Mixing it into retention lets acquisition conceal a deteriorating existing base. It also makes a shared target hard to interpret: a team could appear to retain customers by replacing the ones it loses.
Look beneath the aggregate. Expansion in a few large accounts can mask problems in smaller ones. Review churn, contraction, adoption and unresolved issues alongside net retention. A business without recurring revenue needs measures appropriate to its model, rather than adopting a fashionable SaaS metric unchanged.
Give every buyer the relevant commitment
A B2B purchase can involve people with different responsibilities. The economic buyer needs to understand return and risk. The technical evaluator needs fit and integration. Procurement needs terms; legal needs obligations and data handling. A champion needs an account they can explain internally.
Those are reasons to vary the discussion, not to deliver contradictory promises. Keep a shared view of what each stakeholder requires and what the company has agreed to provide. If everything depends on one contact, ask which important requirement the team has not heard directly.
Preparation also helps the handoff. Security questions, implementation dependencies and contract exceptions discovered late in a deal should not vanish after closing. They belong in the continuing team's plan.
Let the systems support the agreement
The CRM needs reliable definitions and accessible customer context. Connect the information that helps someone act: an unresolved implementation issue, an agreed success criterion or a material renewal risk. More integrations are not automatically better; irrelevant alerts create another queue people ignore.
AI can help summarize approved notes and identify missing context. Verify consequential commitments against their source. A model's summary should not turn an exploratory discussion into a contracted feature.
The organization does not have to merge sales and customer success into one department. A common leader can help, but shared records, clear authority and compatible incentives still have to work. Separate teams can cooperate well when those responsibilities are explicit.
Change one part you can observe
Review recent churned or downgraded accounts and a comparable set that stayed. Trace the promise, handoff and early experience. Choose a specific problem to address, such as missing scope notes or delayed access to a technical owner.
Pilot the change with a defined group and review both acquisition and post-sale outcomes. Listen for unintended effects: slower legitimate deals, disputes about credit or teams hiding difficult accounts. Adjust the design rather than treating the first plan as final.
When someone says “we put customers first,” I want to see what happens at the signature. Who carries the promise forward, who has the context to deliver it and what does the closing team gain from getting that right? Those answers reveal the commercial strategy more clearly than the slogan.