Vendor Partnership Strategies

Vendor selection has been covered elsewhere in the Academy. This is about what happens afterwards — how a relationship develops over years, what each stage requires, and why the difference between a transactional supplier and a genuinely useful one is largely determined by the property rather than by the vendor.

The Relationship Stages

Most relationships stall between one and two, and the cause is usually structural rather than attitudinal: nothing in the scope asks for anything beyond execution.

What the Property Controls

Each transition depends more on the property than the vendor, which is the useful and slightly uncomfortable observation.

• Transactional to reliable requires the scope to specify documentation as a deliverable. A vendor not asked for photographs and condition notes will not provide them, and asking after each visit is a poor substitute for specifying once.
• Reliable to advisory requires the property to act on what is reported. A vendor whose observations are consistently ignored stops making them — rationally, since they cost time and produce nothing.
• Advisory to embedded requires sharing context the vendor otherwise lacks: the capital plan, upcoming leasing activity, tenant sensitivities, and what the property is trying to achieve. A vendor who knows a repaint is scheduled for next spring will advise differently about cleaning this autumn.

What an Embedded Relationship Actually Provides

The value is specific rather than sentimental.

1. Site knowledge that no document captures — which surfaces are sensitive, where pressure drops, which tenant opens early, where the drainage actually goes.
2. Early warning. A crew on the surfaces for hours sees things a quarterly walk does not.
3. Method judgment informed by what has and has not worked on this property before.
4. Sequencing advice that prevents work being undone by other work.
5. Continuity through the property's own personnel change, which is frequently the vendor's most underrated contribution.

That last point deserves emphasis. Property managers change more often than vendors on many assets, and an embedded vendor is sometimes the only party who remembers why the schedule is what it is.

What Partnership Does Not Mean

Two things are worth stating plainly because the language of partnership is frequently used to obscure them.

It does not mean abandoning competitive pricing. Periodically testing the market on the standard specification — a subset of properties in a portfolio, or a defined scope at a single asset — is compatible with a long relationship and protects both parties from drift. It gives the incumbent a fair reference point rather than an ultimatum.

It also does not mean tolerating declining standards out of loyalty. A relationship that has stopped delivering is not a partnership regardless of its duration.

When to Stop Developing a Relationship

Patterns rather than incidents, and specifically these: repeated schedule failures; documentation that must be chased every time; quality drift that does not correct after being raised; crew turnover severe enough that nobody arriving knows the site; or discovery that stated practices — particularly water handling — are not what happens on site.

A single missed window, an isolated quality issue corrected promptly, or a price increase tracking genuine cost movement are normal features of a long relationship and not signals of anything.

The Transition Cost Nobody Budgets

Changing vendors has a cost beyond mobilisation: the new contractor does not know the property. Substrates must be relearned, constraints rediscovered, and the first cycles will be less efficient and carry more risk. On a property with a good site file that cost is modest; on one where knowledge lived with the vendor, it is substantial.

This is an argument for maintaining the site file rather than for tolerating poor performance — a property with good documentation can change vendors cheaply, which paradoxically makes it better positioned to demand improvement from the incumbent. See vendor evaluation and maintaining consistent service quality.