Separating relationship development from technical delivery in family businesses
Built on Rainmaker by Richard C. Wilson.
The employee who wins a major customer should know who will deliver the promise. A billionaire founder can attract opportunities that stretch a family business beyond its normal work. When relationship development and technical delivery are left undefined, the customer's first real experience may be an argument inside the company.
Rainmaker's sales-team chapter asks managers to understand individual strengths and make expectations clear. I would apply that advice by assigning commercial and technical responsibilities separately, then defining how they meet. A smaller enterprise may give one person both responsibilities, but the decisions still need to be distinguished.
Identify the promise being made
List the statements that affect the customer's expectations. These may concern product suitability or the timing of delivery. Some statements can be made from established service information. Others need confirmation from the employee responsible for the technical work.
Name who can approve an exception. A relationship manager may understand the customer very well and still lack the information needed to promise a special specification. Give that employee an accessible path to an answer.
Apply the same rule when the founder is involved. The founder can authorize a commercial priority, but the operating team needs to confirm what execution requires. A casual assurance at a dinner should lead to a clear internal decision before it becomes a delivery commitment.
Give technical employees an early role
Bring the relevant specialist into a discussion when the customer's requirements move beyond the standard offering. Explain the commercial context before the meeting. A specialist cannot assess a request accurately when they hear only that an important family friend needs help.
Let the specialist ask about actual use and constraints. The customer may be requesting a feature because they misunderstand how the existing product works. A direct technical discussion can uncover a simpler answer.
Keep the relationship manager involved. The customer should not have to repeat its business objective to every department. The commercial contact can preserve that context while the specialist establishes what can be delivered.
Use a handoff the receiving team can accept
Before work begins, record the agreed scope and any exclusions that affect delivery. Include the assumptions the customer must satisfy. A team asked to implement a proposal needs more than the salesperson's recollection that the conversation went well.
Ask the receiving manager to confirm acceptance. If an item is unclear, resolve it while the customer can still consider alternatives. Passing incomplete work into operations makes the problem more expensive and may force the enterprise into concessions later.
For a hypothetical custom service, the handoff might include the required input from the customer and the event that starts delivery. That detail prevents a disagreement about timing when the customer's information arrives late.
Examine what the business rewards. An employee paid only for signed business may be encouraged to push unresolved questions into operations. A technical team measured only on avoiding rework may resist reasonable custom work. Both groups need expectations consistent with the enterprise's commercial approach.
The compensation design needs its own assessment by the responsible people. At the operating level, I would make accepted scope and customer outcomes visible alongside the sale. That makes it easier to identify whether a relationship is producing good work for the business.
Avoid treating every disagreement as a personality problem. A salesperson and a specialist may be acting rationally under conflicting instructions. Clarify the instruction before deciding that either person is unwilling to cooperate.
Preserve one accountable customer contact
The customer needs to know where to bring a question after the sale. Identify the ordinary service contact and the route for a serious unresolved issue. The commercial manager may remain involved without being responsible for every technical answer.
When scope changes, have the authorized employees confirm the new commitment. A customer request can look minor in a conversation while changing the cost or delivery sequence. Record the decision where both teams can find it.
After completion, examine any promise that required repair. Use the finding to improve the relevant approval or handoff. Repeated rescue work by the founder usually signals that the ordinary process needs a specific correction.
Questions and answers
Can one employee handle both responsibilities? Yes, if the person has the capability and authority. The business should still distinguish selling a scope from accepting responsibility for delivery.
When should specialists join a customer discussion? When requirements exceed the standard offering or an answer could materially change the commitment.
Related
This page is general information, not legal advice. Family governance documents and dispute processes should be reviewed by a qualified attorney.