In industrial automation, the signing of the purchase order is habitually treated as closure of the operation. For the commercial team it is the end of the sales cycle. For the client, it is usually the beginning of risk. The distance between what has been signed and what the client can effectively operate with their own internal team defines, with greater force than product quality, the actual outcome of the project.
A significant fraction of closed automation projects suffers delay, rescoping or paralysis during the deployment phase. The cause identified by the majority of industrial executives is not the technical quality of the supplier. It is the difficulty of the client themselves in assimilating the delivered solution: configuration, operator training, calibration with live processes, adjustment of internal capabilities.
The problem is not with the first sale. It is with the second. A correctly delivered project that the client fails to operate sustainably leaves a silent residue of dissatisfaction. When the moment arrives for the next project, the client does not attribute the problem to their internal team. They attribute it to the supplier who signed and did not accompany.
A substantial portion of the medium-sized industrial fabric operates with a growing debt of internal technical talent. Automation is purchased to resolve operational problems, but the capability to configure, maintain and optimise what has been automated requires internal engineering that many plants do not possess. The supplier who implicitly assumes that the client is prepared to receive their solution transfers a risk that the client cannot always absorb.
The reverse of the pattern is viable. Industrial companies that close successive projects with the same account have an explicit post-PO accompaniment system. It is not reactive technical service. It is consultative presence during the months following delivery, with defined responsibilities, indicators shared with the client and periodic reviews of the operational state of the installation.
Three components define an accompaniment system that yields measurably. A formal operational training programme with defined cadence, not merely delivery of manuals. A post-deployment review protocol with planned visits during the first twelve months, with metrics of actual use versus expected use. And an application support channel accessible to the client's technical team, distinct from the reactive technical service channel.
The frequent error consists in delegating accompaniment to the technical service team, which operates with metrics of efficiency and incident resolution, not account relationship. The consequence is that the post-PO conversation is reduced to fault attention. What the client needs is the opposite conversation: help to use what they already have better, before faults appear.
The consequences for the management committee are three. The allocation of application engineering must be extended to the post-PO period, with protected time and associated metrics. The commercial system must distinguish between accounts in active deployment and accounts in stable operation, with different proposals for each state. And the remuneration of the commercial representative responsible for the account must incorporate indicators of client operational health, not only closure of the initial project.
The habitual objection is that post-PO accompaniment is unrecoverable cost and must be minimised. The aggregate arithmetic contradicts that logic. The account whose first project operates correctly closes the second with substantially higher probability. Accompaniment is not commercial cost: it is investment in the next sale, with measurable return.
The post-PO phase in automation is not a courteous extension of commercial service. It is the phase where it is decided whether the account returns or not. The industrial company that treats it as such opens the difference between client of one project and client of a decade.