Definition

The condition where a vendor pitch arrives before the operator has diagnosed the problem the vendor claims to solve. The solution defines the problem instead of the other way around.

Explanation

This is the inverted diagnostic sequence, and it’s worth naming because it’s the default state for most operators rather than an occasional mistake. A vendor shows up with a polished pitch for a tool, and the operator backfills a problem the tool happens to solve, rather than starting from an actual diagnosed gap and shopping for a tool that fits it.

[Vendor Capture] compounds with [Stack Drift] — a stack built from captured pitches rather than diagnosed needs is a stack that grows in whatever direction the sales calendar points it, not in the direction the operation actually needs.

[Vendor Capture] manifests in specific market-facing patterns worth naming as their own IP. [Table-Stakes Repricing] is the manifestation in which the vendor sells baseline restaurant infrastructure — direct ordering, mobile reservation, integrated loyalty, modern payment, owned digital storefront — as a “growth product” or “foundation layer,” thereby extracting subscription fees for capabilities that fulfill the operator’s baseline obligation to the Guest rather than delivering growth above baseline. The manifestation is worth its own IP handle because the pricing itself is not the failure — the framing is. When a vendor calls direct ordering a “growth strategy,” the operator hears growth instead of hearing baseline obligation, and the misread funds the vendor’s business model. Recognizing [Table-Stakes Repricing] as a specific manifestation of [Vendor Capture] gives the operator a diagnostic to run at the point of the pitch: is this vendor offering growth infrastructure, or baseline infrastructure priced as growth?

[ROAS Lock] is a secondary manifestation of [Vendor Capture] — specifically, when the vendor arrives with ROAS as part of the initial pitch and the operator adopts the metric because the vendor introduced it rather than because the operator diagnosed a measurement gap that ROAS would fill. Not every instance of [ROAS Lock] is also [Vendor Capture] — an operator can run [ROAS Lock] with an in-house team — but when the metric arrived with the vendor, both mechanisms are operating simultaneously, and the intervention has to address both.

The pattern to teach the operator is that [Vendor Capture] is the default direction of vendor relationships in the restaurant industry. The vendor’s job is to have a solution ready; the operator’s job is to have a diagnosed problem first. When those two arrive in the wrong order — solution first, problem backfilled — the operator is running [Vendor Capture] whether or not they buy the tool, because the diagnostic sequence has already been inverted. Buying the tool locks the inversion into the operating architecture; declining the tool leaves the inversion at the level of habit, which the next vendor pitch will exploit again.

Pairs with: [Stack Drift], [Table-Stakes Repricing] (baseline-infrastructure manifestation), [ROAS Lock] (measurement-instrument manifestation), [3P Arbitrage] (the delivery vehicle Vendor Capture usually rides in on).