(See sequence steps.)
Hi {{firstName}},
Welcome to the pilot. Here's what we agreed:
- Goal: {{pilotGoal}}
- Success metric: {{pilotMetric}}
- Duration: 6 weeks, decision call in week 7
- Pilot stakeholders: {{stakeholders}}
By end of this week, we need:
1. Access to {{requiredSystem}}
2. The 30-email sample we discussed
3. A 30-minute call with {{stakeholder}}
[Confirm the pilot plan]
— {{senderName}}Hi {{firstName}},
Week 1 update — kept tight on purpose.
Shipped:
- {{shipped1}}
- {{shipped2}}
Found:
- {{finding1}}
- {{finding2}}
Need from you:
- {{need1}}
Forward this to {{stakeholder}} — that's how we keep the team aligned without scheduling calls.
— {{senderName}}Hi {{firstName}},
We're halfway through the pilot. Honest read:
What's working: {{whatsWorking}}
What's not: {{whatsNot}}
What we'd need to change to hit the goal: {{whatToChange}}
Worth a 25-minute call this week to align? I have Thursday 10am and Friday 2pm open.
— {{senderName}}Hi {{firstName}},
Pilot's done. Deliverables and results:
- {{deliverable1}}: {{result1}}
- {{deliverable2}}: {{result2}}
- {{deliverable3}}: {{result3}}
Against the success metric ({{pilotMetric}}), we hit {{actualResult}}.
For the contract conversation: [proposal doc]({{proposalURL}}).
When works for the decision call?
— {{senderName}}Enterprise pilots fail at communication rhythm more often than at product. The 4-step sequence here treats the pilot like a project: explicit success criteria, named stakeholders, a milestone cadence, and a decision point. The buyer's job is to defend the pilot internally; your job is to make that defense easy.
Drop your draft into our editor. One anonymous run, no signup required.