Enterprise pilots

Enterprise buyers sound serious fast. "Let's put you in the innovation lab," "we'll run a 90-day proof of concept," and "can you do a free evaluation for our digital transformation office" feel like pipeline. A convertible enterprise pilot names a LOB owner, EVP, or CFO as the economic buyer, one BU, region, or plant as scope, exec-readable success criteria, InfoSec / legal / procurement on a parallel track, and a date for the commercial ask.

Keep unpaid innovation slots, open-ended sandboxes, and free POCs separate from customer pilots. They can create evidence later. They seldom close this fiscal year unless you put a paid commercial clock on them.

Hunt for compelling events: a board or audit mandate, a peer competitor win at a similar enterprise, a fiscal-year or annual-ops-plan gate, a new EVP mandate to cut cost or grow output without headcount, a plant or region that underperforms peers, or a vendor consolidation that opens budget.

Map the committee early: VP or senior director champion, LOB owner / EVP / CFO (economic buyer), finance partner who will read the ROI, InfoSec / GRC for questionnaire and access, legal for MSA and DPA, procurement for the order path, and the day-to-day operator on the floor. A VP alone won't get you to a PO.

Enterprise deals die when you single-thread a VP who loves the product and never puts the economic buyer, InfoSec, or procurement in the room. Get the LOB owner, EVP, or CFO on a call by week two. Ask who signs annual software above your ACV, when the next budget gate is, and what proof they will accept.

InfoSec, legal, and procurement are heavier than mid-market. Start the security questionnaire, data-access plan, DPA, and MSA redline path in week one of serious interest so they do not land in the final week.

Budget reality matters. Work backwards from phase-two ACV the LOB can fund this fiscal year. If the full rollout needs a number that only corporate can approve after a longer cycle, say so and cut scope to one BU or region before you waste the pilot.

Write criteria a LOB owner or CFO will sign, and instrument them on one BU, region, or plant inside an 8 to 12 week window: cost per unit, throughput, cycle time, error or rework rate, OTIF, risk-event detect time, overtime hours, or a named conversion metric finance already tracks.

"Team likes it," login counts, and NPS-only lines won't pass an enterprise finance or risk review. Price the pilot when you can, and put phase-two commercial terms (BUs, regions, plants, seats, modules, annual ACV or MSA intent) in writing so the pilot cannot become a permanent evaluation.

Land a week-2 quick win the economic buyer can see without living in the product. A one-page KPI memo with baseline, target, and current beats another feature demo.

Hold midpoint against the written scorecard with the champion and the LOB owner, CFO, or finance partner present. Adjust only against the criteria. Do not expand to every BU or every region without saying so.

Keep access, InfoSec questionnaire, legal redlines, procurement path, and the commercial ask date moving each week. Enterprise pilots die after everyone said yes informally when the team learns in the final week that "we still need security, legal, and a vendor form."

Restate the criteria, the evidence, and the commercial path, then ask for the MSA schedule or annual PO. "Loved it" without a signature is a stall. Enterprise teams give verbal yeses often; paper seldom arrives until you ask on a set date with InfoSec and procurement already briefed.

If budget or attention wobbles, cut to one BU, one region, fewer seats, or fewer modules. Don't teach procurement that a successful pilot earns a permanent deep discount.

Name the enterprise stall mode before you improvise.

Treat the pilot scope (one BU, region, or plant) as a proof sample. Expand from the phase-two price and MSA terms in the agreement.

Add adjacent BUs, regions, or modules after production is live. A short champion-to-peer intro inside the account helps you win the next BU. If you keep "pilot pricing" going across the company, each expansion starts at a discount the business can't sustain.

Use this as a pattern drill. It is not a claimed case study, and the numbers are illustrative. Company-size overlay: enterprise (procurement-led), separate from SME and mid-market.

Use the enterprise pilot scorecard template for the blank worksheet, a filled example, the InfoSec / legal / procurement parallel-path checklist, and a copy-ready AI prompt.