The Pilot-to-Production Bridge

Most enterprise AI relationships do not start with a $150K annual commitment. They start with a pilot. The vendor sends a short-form pilot agreement — a purchase order, a lightweight evaluation license, a click-through trial. It has none of the AI-specific hooks: no derivative definition, no training prohibition, no exit provisions for model changes. The pilot goes well. Procurement moves to the full MSA. Forty-seven redlines appear.

The deal that worked in practice cannot survive the paper it needs for production. Four to six weeks of legal negotiation follow. The champion inside the enterprise loses momentum and the pilot's goodwill evaporates.

The fix is negotiating the production MSA now and attaching a Pilot Schedule that carves out production-level obligations during the evaluation period. The production MSA is the base and both sides negotiate it in full ahead of the pilot — definitions, IP, training restrictions, liability caps, exit provisions. Once aligned, a Pilot Schedule is attached that specifies certain provisions are modified during the evaluation period only. When the pilot graduates to production, the carve-outs expire and the underlying MSA activates in full.

The incentives align. The vendor gets the production MSA negotiated while the relationship is new and goodwill is high. The buyer gets binding commitments on the things that matter — derivatives, no-training, sub-processor flowdown, exit — without having to renegotiate them when the pilot succeeds.

The Pilot Schedule defers four operational carve-outs: (1) SLA credits — no credits during pilot, though production terms are agreed and activate at graduation; (2) data in scope — pilot-eligible data only, non-sensitive, non-personal unless anonymized; (3) liability caps — modified to a pilot-period floor bridging the gap between pilot fees and enterprise-data risk; and (4) warranties — scoped to pilot documentation only, with the production warranty package negotiated and held in reserve.

Graduation triggers define what 'graduation' means: auto-graduation when the pilot period expires and the customer continues; a usage threshold such as 1,000 API calls per month or 50 users; or express written notice from either party. At graduation, the Pilot Schedule terminates and the full MSA activates. The transition is a single sentence in an email, not six weeks of redlines.

Red Flags

• A click-through pilot agreement with no AI-specific definitions or training restrictions
• No path from pilot to production MSA defined in the initial agreement
• Pilot scope includes production data or personally identifiable information
• No graduation triggers or timeline defined — the pilot can run indefinitely without activating production protections