War-game a pilot contract before legal, sales, and the customer treat a soft SOW as the template for every deal that follows.
Pilot contracts fail when success criteria are vague, when pricing invents a discount that becomes the floor, when data and IP terms are copy-pasted, and when exit rights appear only after the work is half done. A friendly draft is not evidence that the pilot survives a careful and hostile read.
Freeze the draft
State the pilot goal, duration, price, success criteria, data handling, IP, support level, and exit path. Attach the SOW, the pricing rationale, the internal margin note, and the customer commitments you need in writing. If sales, legal, and delivery each think they own a contested clause, stop and reconcile first.
Write the decision you will make if the war game finds nothing new, and the walk-away criteria if scope, liability, or price crosses a named line.
Who should attack it
- Legal. Liability, data, IP, and termination gaps under a realistic customer ask.
- Sales. Whether the pilot is sellable without shadow promises.
- Delivery or CS. Whether success criteria are measurable with the staffing you have.
- Customer procurement. How the draft will be quoted back as precedent.
- Skeptic. The claim that looks strongest and is least sourced.
Same pack for every seat. Hidden "we will make it up on conversion" notes for sales only create fake agreement.
Run the passes
Feed Pingpong the SOW, pricing note, and success criteria. First pass steelmans the pilot. Later passes attack from legal, sales, delivery, and customer seats. Final pass turns surviving objections into tighter criteria, clearer exits, or a hold. Delete dual-counted conversion upside and invented "customers never enforce that" reviews.
When the pilot includes free or heavily discounted seats, force finance and skeptic seats to map how that price will be quoted at renewal. A pilot that only converts if you keep the discount is a pricing change in disguise. Write the conversion price, the notice window, and the walk-away path into the package before signature.
Force a day-after narrative: what happens if the pilot expands without a change order, if success is disputed in week six, or if procurement demands the pilot price as list. If those stories are stronger than your guardrails, fix the package before signature. Separate a pilot contract from a discount policy or a partnership announcement. If the memo blurs them, run those war games as separate moves.
Related: war-game a channel partner deal, war-game a discount policy, war-game an enterprise RFP, war-game a B2B pricing negotiation, and the war-game decisions hub. See how it works.