The ESD Expectation Nobody Writes Down

Well developed SMEs can still struggle to deliver on contract. Understanding why has become one of the more consequential questions in enterprise and supplier development.

There is a moment familiar to anyone who has spent years in enterprise and supplier development. A corporate invests, in earnest and in line with its transformation commitments, in the development of an SME. The programme runs its course: governance is strengthened, compliance is achieved, financial systems are established and technical capability is certified. The SME graduates and, on the strength of that development, is awarded a supply contract into the corporate’s value chain. By every conventional measure, it is a success story.

Then, some months into the contract, the relationship begins to strain. Deliveries slip. Quality wavers under volume. The SME’s cash flow tightens against the corporate’s payment cycle. Procurement grows frustrated, the ESD function grows defensive and the SME grows quiet. What makes the situation genuinely difficult for everyone involved is that the development itself succeeded. The programme delivered what it promised. The strain originates elsewhere.

In our advisory work, this is the pattern corporates raise more often than any other, and it rests on a single expectation that is rarely examined and never written down: the assumption that an SME which has been developed is, by that fact alone, ready to deliver on a contract. These are two distinct capabilities, and the distance between them is where a significant share of ESD partnerships come under pressure.

Development is one journey. The contract is another.

Consider what each demand. Development, done well, builds the foundations of a business: governance, compliance, financial management, technical skills and market readiness. It is delivered through structured support, measured against programme outcomes and conducted, by design, within a protected environment.

A supply contract offers no such protection. Whether it takes the form of a purchase order arrangement, a fixed term supply agreement or an offtake commitment, it tests an entirely different set of capabilities: the working capital required to carry stock and production ahead of payment, the operational capacity to meet committed volumes at specification, quality consistency under sustained pressure, exposure to penalties, and the resilience to serve the contract while the business is still maturing. No certificate earned in development answers for any of these.

The corporate signs the contract expecting a supplier, because that is what the development investment was for. The SME signs it carrying the capabilities the programme built alongside the gaps the programme was never designed to close. Both parties act in good faith. Neither tests the assumption sitting between them. That is the expectation nobody writes down, and the contract will surface it whether or not anyone has planned for it.

What a partnership that holds means

The phrase deserves precision. In the context of enterprise and supplier development, a partnership that holds is one in which the development investment, funded through the corporate’s ESD budget, converts into a commercial supply relationship that performs. Four conditions must be true at the same time: the SME delivers on the contract terms it signed; the corporate secures genuine supply chain value alongside scorecard recognition that withstands verification; the relationship survives the pressures that test it, from volume increases to payment cycles to changes in personnel on either side; and the SME emerges more capable and more bankable than it entered. Where any one of these conditions fails, the partnership may continue on paper, but it has stopped holding.

The reason this gap so often goes unseen is structural rather than negligent. The implementer who delivers the development measures development outcomes. Procurement measures contract performance. Each performs its mandate well, and the bridge between the two belongs to no one. The strain lives on that bridge, and it typically announces itself at review, before precisely the audience a corporate would least choose.

The questions that close this gap

There is a set of questions that, asked early enough, closes this gap. They are worth setting out in full, together with what answering each of them properly entails. It should also be said plainly why they cannot simply be referred to the implementer running the development: most require an independent view across both the development side and the contract side of the relationship, and an implementer assessing whether its own development translated into contract performance is marking its own homework.

1. Which of the capabilities built in development are the capabilities this specific contract will actually test?Answering this requires mapping the programme’s outcomes against the contract’s demands. The two lists overlap far less often than corporates expect.
2. Can the SME carry the working capital cycle of this contract at the committed volumes? This must be verified against the actual financial position of the business rather than against programme reports. The two can tell very different stories.
3. What happens in month one when the volumes arrive: people, equipment, quality control, logistics?Operational capacity should be stress tested before the contract tests it live.
4. When the contract strains, whom does the SME call, and do the ESD function and procurement ever compare notes? The governance connecting these two sides of the corporate is often the deciding factor in whether strain becomes failure.
5. What is the SME expected to absorb in practice: price movement, payment terms, penalties? Whether the business can survive those terms should be established before they are signed, and the terms structured so that the supplier the corporate has just invested in is not undone by its first contract.
6. At review, which numbers will procurement defend and which will the ESD function defend, and are they the same numbers? A partnership should be judged on one version of the truth. Aligning the measurement before the review is considerably easier than reconciling it during one.
7. If the SME misses a delivery in month three, what is the agreed path back? Partnerships that hold have a recovery mechanism designed before it is needed, not negotiated in the middle of a failure.

Seven questions; each answerable and each actionable. What they require is sight of the whole relationship, from programme design through to contract performance, together with the independence to report what is actually there. This is the ground on which Zevoli’s advisory practice operates: between the development investment and the supply chain outcome, ensuring the first becomes the second.

Timing the conversation

The ideal moment to ask these questions is before the contract is signed. The second best moment is in the early stages of an SME’s development, while there remains ample time to strengthen the relationship before scorecard season lends every conversation a defensive edge. Tested early, contract readiness is a constructive exercise, and it usually reveals as much strength as risk. Discovered towards the end of the programme, the same gap is damage control.

For corporates with SMEs moving from development into the supply chain, or with supplier relationships straining in ways the programme reports do not explain, the question set above is the place to begin. The industry’s collective challenge is no longer whether development works. It is whether development converts, and conversion is a discipline of its own.

“The question is no longer whether development works. It is whether development converts and conversion is a discipline of its own.”