Outreach Templates

Subject: proving your AI agents actually moved the number Hi {{FirstName}}, Most {{industry}} leadership teams I speak with now have agents running somewhere — Copilot, a custom build, a vendor pilot. Very few can show, at board level, what those agents changed. We use Plansom to connect priorities to accountable work and keep decisions, progress and supporting evidence visible across human and agent activity. We can start with a focused qualification session to agree the business problem, sponsor, success measures and next action. Worth 20 minutes to see whether your current agent estate would pass that test? Best, {{YourName}} — {{Firm}}, Plansom {{Tier}} Partner

Hi {{FirstName}} — saw {{Firm}} is doing a lot of {{transformation / agent delivery}} work. We added Plansom as the execution layer after our engagements: clients keep the accountability system and our team contributes specialist delivery within one customer journey. Happy to share how the practice economics work — want the partner one-pager?

1. EMAIL 1 — Day 0: The gap

   Subject: {{Company}} — connecting agents to a business priority

   One line on the current agent work, one line on the accountability gap. CTA: 20-minute call.

2. EMAIL 2 — Day 4: The proof path

   Subject: how we would test the fit

   Business problem, owner, evidence and a defined next decision. CTA: agree the qualification brief.

3. EMAIL 3 — Day 9: The commercial path

   Subject: choosing the right commercial route

   Direct purchase, reseller order or Marketplace/private offer only where confirmed eligible. CTA: agree the contracting roles.

Hi {{FirstName}}, We're exploring {{Account}} on agent adoption. Plansom connects a customer priority to accountable human and AI work. Please confirm the current offer’s co-sell and Marketplace status for this customer. Proposed motion: {{referral / co-sell / Marketplace private offer}}. We would like to explore role clarity and alignment on a joint account plan. Can we add it to the joint account plan for {{quarter}}?

Registering: {{Account}} — {{country}}, {{industry}}, ~{{employees}} employees. Sponsor: {{name}}, {{title}}. Use case: {{C-VI use case}}. Eligible subscription ARR: ${{arr}}. Expected close: {{date}}. Originating source: {{source}}. Influence evidence: {{evidence}}. Transaction route: {{direct / resell / Marketplace}}. Support requested: pre-sales engineering for {{connector / security review}}.