The practical conditions behind a service promise

The work after a project closes is frequently described as support, although it can contain several different obligations. Correcting a defect, explaining an agreed procedure and teaching a replacement employee are not interchangeable activities. I help our teams identify those differences before they price a transition. The proposal needs to specify the receiving organisation, the questions it should be able to answer and the period during which a named specialist remains available. That detail lets the client decide what it will undertake itself. It also protects colleagues from a commitment that appears small in a sales meeting but becomes an open-ended second job. My contribution is commercial and organisational: technical specialists still decide how to demonstrate the actual environment. Where a client cannot provide a permanent service owner, I would reconsider the transfer date rather than disguise the absence with more documentation.

A language capability has little operational meaning until it is attached to a time, a task and someone who can perform it. I learnt to assess bilingual service coverage through the contracted windows rather than a total number of colleagues who speak both languages. A person able to discuss a routine account query may not be prepared to handle a complex technical incident in the same language. The roster must reflect that distinction, as well as leave, training and the escalation path. I work with service managers to identify the vulnerable intervals and decide whether recruitment, paired working or a narrower promise is appropriate. We do not assume that bilingual employees should remain permanently available because their skill is scarce. The management question is whether the service can be repeated without relying on a particular colleague sacrificing personal time.

Reselling a licence can establish a useful client relationship, but its invoice value can also obscure how little resource remains to support that relationship. I examine the contribution after vendor costs, administration and the obligations attached to the sale. That is different from judging the activity by its revenue share or assuming that all resale is unattractive. Some arrangements support a service we are well placed to deliver; others tie up commercial attention without developing that capability. When we reduced a resale line, I required a separate account of client retention, purchasing terms and support workload. Otherwise a higher reported margin could conceal a damaged relationship. A chief executive needs to explain the decision in absolute amounts as well as percentages, including the loss of scale that colleagues and shareholders may reasonably value.

I ask a receiving colleague to use a record in circumstances close to the work it is meant to support. Can that person identify the current version, the authority needed for a change and the appropriate escalation when the documented answer does not fit? A successful demonstration tells us more than a count of completed documents, although it cannot prove that every unusual situation has been covered. We choose a small set of realistic requests and preserve the questions that remain unanswered. My early support experience helps me notice instructions written for their author rather than their next reader. I do not insist on one format for every client. A diagram, a short procedure and a recorded explanation can each be useful if access, ownership and maintenance are clear. The test should reveal a weakness before a departing specialist becomes unreachable.