Let the buyer see what the evidence establishes

An installation count can establish activity without establishing experience of the application a buyer is considering. My own campaign combined ten hot-water references with eight industrial-steam references beneath a steam-specific claim. The underlying projects were not invented within the company story; the unsupported part was the comparison we encouraged. I now ask the responsible technical colleague to explain which reference characteristics matter before marketing chooses the headline. We preserve the application, service scope and remaining questions rather than turn the largest possible count into a general capability statement. A reference is also not an assurance of the next site’s performance. Site conditions and qualified assessment retain their role. The marketing task is to make the evidence useful for a buyer’s next question, including when that requires a smaller and more relevant group of examples than the full portfolio could provide.

A shared mark on a map may suggest equivalent capability even when partner relationships have different limits. In our reviewed group of thirty-two organisations, twenty-one had completed proposition training and eleven also held a defined installation authorisation. Training and authority were not interchangeable descriptions, and the directory needed to say so at the point of selection. I work with channel and technical owners to identify what each relationship actually permits before deciding how it appears. Marketing does not grant installation approval, and a company-level label does not certify every person or every site. We also need a process for changes in status to reach the published account. A useful partner directory helps a buyer find the right conversation without letting a convenient visual system confer an authority that the underlying relationship does not contain.

A realistic rendering can explain a proposal well, but it should not be allowed to stand as evidence that the proposal has been built. Our visual library contained twenty-seven photographs and thirteen computer-generated scenes. Nine of the latter appeared without sufficiently clear status in the reviewed material. I asked the team to preserve the distinction in captions and placement, with source and permission checked separately. Labelling a rendering does not resolve copyright or customer-consent questions, just as permission to use a photograph does not establish a performance claim. The account must explain which question each check answers. I want a buyer to know whether an image records completed work, illustrates a possible arrangement or simplifies a concept, before its visual polish encourages a stronger inference than its actual provenance supports.

Commercial review becomes less useful when the only remaining question is whether a launch can proceed on time. I involve engineering and channel owners while the proposition and evidence selection can still change. Their role is not to approve the elegance of a headline; it is to explain whether the comparison, capability or depicted arrangement is supported. Marketing retains responsibility for the inference invited by the whole presentation. A technical footnote cannot automatically repair a misleading visual hierarchy. We keep the cost and delay of correction visible, including when my own earlier approval created them. That approach requires a clear decision owner and a practical route for withholding a claim. It does not make marketing an engineering function. It makes the commercial story accountable to the evidence and authority on which a customer is being asked to rely.