Managing and rewarding the commercial work

An industrial salesperson can be responsible for a customer relationship while depending on other people for almost every consequential promise. Engineering determines whether the application will work. Operations determines what can be delivered. Finance controls credit. Management sets the boundaries of the offer. Recognizing commercial talent means designing those relationships so capable people can get useful work done. Pay matters, but a larger commission does not resolve an unanswered engineering question or create production capacity.

Give responsibility a workable boundary

A useful management agreement begins with the decisions. Name one person to coordinate the commercial commitment, identify the technical and operational counterparts, and make their authority explicit. The salesperson should know what can be decided immediately, what requires approval, who provides that approval, and when an unresolved decision must be escalated. The allocation will vary with the business. This is a starting framework.

An exception needs an owner, a decision deadline, and the relevant evidence. A missed deadline triggers escalation, not permission to improvise. Management should also examine the queue: if routine decisions continually require senior intervention, the delegation may be too narrow. If exceptions arrive without basic information, the preparation may be inadequate. Those problems require different remedies.

Use a few measures that fit the work

The right scorecard depends on what someone is being asked to build or maintain. A person developing a new application should not be assessed solely as though they inherited a mature repeat-order account. Nor should every management indicator determine pay. Some measures explain the process; others can fairly support compensation.

Holmström and Milgrom’s analysis of multitask incentives gives this problem a useful foundation: strong rewards for easily measured work can divert effort from valuable work that is harder to measure. Applied here, a revenue target needs to be considered alongside the qualification, coordination, and follow-through required to make that revenue worthwhile. [1]

Choose only a few measures that the team understands. Define the economics before using margin in compensation: a negotiated discount and a later factory cost overrun are different events. When collections enter the scorecard, distinguish the representative’s contribution from billing errors or a disputed technical problem. Shared outcomes can support shared measures; they should not quietly become one employee’s responsibility.

Make prevention and teamwork visible

Consider a hypothetical case in which an application specialist identifies an unsuitable configuration before an order is accepted. The immediate result may be a delayed quote or a lost sale. The work may still protect the customer and the supplier. A review should examine the evidence, the alternative offered, and the decision reached. It should not automatically count a rejection as failure or attach an invented monetary value to an accident that never happened.

Use the same discipline for commercial prevention: clarifying scope, documenting a change, discovering an unrealistic deadline, or resolving conflicting customer requirements. Record the consequential decision and why it mattered. This gives managers something more reliable than either invisible effort or self-reported heroics.

Agree contribution credit before predictable disputes arise. The originator, account owner, application specialist, distributor, and service team may each help create the result. A compensation plan should make those contributions compatible. It should also allow for the time required to develop business. The case for better pay becomes stronger when it identifies the role’s actual scope, scarcity, responsibility, and economic contribution.

Preserve the knowledge behind the relationship

A contact list is an incomplete account record. Preserve the application history, customer decision roles, approved commitments, unresolved questions, and next useful action. Keep current specifications and approvals in their proper records, with links from the account. Introduce an appropriate second company contact where continuity matters. That person needs context and a credible introduction, not just access to a name and telephone number.

The purpose is better service and a more capable team. Recognition, development, and clear credit rules help make sharing knowledge worthwhile. Customer trust remains voluntary; recording a relationship does not transfer the trust that a person has earned.

Digital tools and AI deserve a bounded trial here. Test whether they can organize an inquiry, retrieve approved information, or prepare a draft handoff that a responsible person checks against its sources. Preserve document versions and ordinary access permissions. Keep decisions about suitability, price exceptions, delivery commitments, and warranty with the authorized owners. Assess time saved alongside corrections and consequential errors. Faster preparation is valuable only if the resulting commitment remains dependable.

What to change in 90 days

Begin with one product family, market segment, or small cross-functional team. Use the existing systems and select two recurring problems that the participants can influence. A focused pilot gives management a chance to learn what changes the work before expanding the program.

Long qualification cycles may leave the revenue outcome unresolved after 90 days. The immediate test is whether the company makes better decisions, reduces avoidable friction, and keeps more reliable commitments. That creates a concrete basis for recognizing commercial talent: people have a defined contribution, the authority and support to make it, and a fair way to share in the result.