Engagement Kickoff Deck

Partner-Craft POV Engagement Series

[Field: Partner name] | [Field: Vendor name] | [Field: Date] | [Field: Engagement lead]

Slide 02 — Why We’re Here

This engagement is not a vendor briefing. It is not a training program. It is not a generic partner kit.

It is a partner methodology, built around your business, your clients, and your market.

What this is NOT

• A product pitch or vendor presentation
• A training session on vendor features
• A methodology that fits every partner equally

What this IS

• A methodology built around your business model
• A structured way to deliver and close more confidently
• A program you helped shape and that you own

Slide 03 — How This Works

Phase 01 — Partner Discovery

We learn your world before anything is built. How you sell, who your clients are, where deals stall, what the vendor has given you and how useful it actually has been.

Output: Completed Discovery Questionnaire

Phase 02 — Methodology Build

With that context, we build the engagement methodology around your motion. Sessions, worksheets, facilitation guides, and report templates shaped for your client conversations.

Output: Full methodology package, white-labeled

Phase 03 — Enablement

You go to market with a structured, repeatable methodology you helped shape. What works and what does not gets fed back in. The methodology improves with use.

Output: Partner-ready, client-facing delivery capability

Slide 04 — What We Need From You

01 — Honesty About what is working and what is not. Polished answers produce generic methodology. The more candid you are about where things break down, the more useful what we build together will be.

02 — Real Conversations Access to actual client conversations, not sanitized versions. The language your clients use, the objections they raise, the questions that kill deals. That is what the methodology gets built around.

03 — Decision Access A point of contact who can make decisions. If every output needs three layers of internal approval before we can move, the engagement stalls. We need someone in the room who can say yes.

04 — Time Realistic session commitments, kept. The methodology cannot be built in a single workshop. It takes structured sessions with preparation between them.

Slide 05 — What You Get

1. Facilitation guides — written for your style and client audience, session by session
2. Client-facing materials — slide decks and worksheets shaped around your existing conversations
3. Structured worksheets — purpose-built to capture specific, recordable outputs at each session
4. Report templates — pre-built to reflect your delivery standard, not a generic vendor template
5. Vendor reference materials — reference architectures, technical briefs, and positioning guides developed collaboratively
6. White-label packaging — partner branding throughout every client-facing document; IP ownership clearly governed

Slide 06 — The Vendor’s Role

The vendor is here as a resource. The partner’s client relationship drives the room.

The vendor provides:

• Reference architectures and technical depth on request
• Positioning support when the partner surfaces a gap
• Market intelligence when it serves the partner’s needs
• Commercial flexibility when the deal requires it

The vendor does not:

• Set the agenda or drive the session content
• Position their product before the client problem is understood
• Override the partner’s read of their own client
• Use this engagement as a channel to the client relationship

Slide 07 — Session Plan

Use the archetype-specific variant from the Archetype Variants section below

* Session count varies by archetype. See archetype variants below.

Slide 08 — Ground Rules

01 — Confidentiality What is said in these sessions shapes the methodology. It does not go back to vendor headquarters as market intelligence. Partner and client context stays in this room.

02 — IP Ownership The methodology and all client-facing materials belong to the partner. White-labeled, partner-branded, governed by the engagement agreement. Not a vendor asset.

03 — Speed of Decisions We move at the speed of decisions, not the speed of approvals. If something needs to go through three layers of sign-off before we can proceed, flag it early.

04 — No Surprises If something is not working in the engagement, say so in the room. The retrospective at engagement close exists for honest feedback. So does every session opening.

Slide 09 — Today’s Session

Slide 10 — Let’s Get Started

Agreed Next Steps

1. Complete Section 3 of the Discovery Questionnaire (archetype-specific)
2. Confirm attendees for Session 2
3. Next session date: [Field: Date]
4. Partner pre-work: [Field: Pre-work assigned]

[Field: Engagement lead name and contact] [Field: mcphail.pro]

Build it for the partner. Then make the vendor earn their place in it.

Archetype Variants

Slide 07 — Session Plan

Use the version below that matches your engagement. Replace the Session Plan table in Slide 07 with the relevant archetype variant.

A1 — Classic Enterprise Cyber

e.g. Mimic | Typical duration: 6–8 weeks

A2 — Industrial / OT / IIoT

e.g. WI-SUN Alliance, Toyota Tsusho context | Typical duration: 8–10 weeks

A3 — Emerging / Sensitive AI

e.g. WitnessAI | Typical duration: 8–10 weeks

A4 — PKI / PQC / Crypto Lifecycle

e.g. Keyfactor, OmniTrust | Typical duration: 6–8 weeks

A5 — Remediation / Hygiene at Scale

e.g. Northern Tech Mender | Typical duration: 6–8 weeks

A6 — SOC Modernization / Agentic D&R

e.g. Agentic SOC vendors | Typical duration: 8–10 weeks