Customer Deck Builder

Customer Deck Builder

Use this skill when a GTM team needs a customer-facing deck for discovery, QBR, renewal, expansion, executive briefing, onboarding, or follow-up.

Workflow

• Gather the minimum context:
• company name, domain, or account ID
• call type
• meeting goal
• attendee roles
• specific topics, questions, or risks
• Resolve the account from approved CRM or account-data sources.
• Pull only the approved fields needed for the deck:
• account plan and renewal context
• usage summary
• active users or builder roles
• top apps and workflows
• feature adoption
• relevant customer notes or meeting context
• Choose the right deck shape:
• discovery or first meeting
• QBR or business review
• renewal
• expansion or upsell
• executive briefing
• onboarding kickoff
• follow-up or check-in
• Build the narrative before writing slides:
• what the customer is doing today
• what value they are already getting
• what risks, gaps, or opportunities are visible
• which use cases fit their stack, role, or goal
• what next step should come out of the meeting
• Write slide-by-slide markdown for Gamma.
• Generate the deck through Zapier MCP using Gamma actions.
• Return the Gamma URL, deck summary, and review notes.

Deck Structures

Discovery Or First Meeting

Goal: establish credibility, show useful context, and frame relevant automation opportunities.

Suggested slides:

• Cover
• Agenda
• What we know about the customer
• AI automation opportunity
• Where to start
• Relevant use cases
• Customer proof
• Next steps

QBR Or Business Review

Goal: show value delivered, identify optimization opportunities, and align on next steps.

Suggested slides:

• Cover
• Agenda
• Customer and Zapier team
• Account health overview
• Usage trend or task-limit utilization
• Feature adoption
• Top workflows and apps
• Opportunities
• Progress and next steps

Renewal

Goal: recap value, show trajectory, and connect the renewal conversation to measurable outcomes.

Suggested slides:

• Cover
• Agenda
• Year in automation
• Usage trend
• Current-period usage
• Automation stack
• Relevant product updates
• Plan fit
• Expansion opportunities

10. Next steps

Expansion Or Executive Briefing

Goal: show current value, identify where more teams or workflows can benefit, and keep the conversation outcome-focused.

Suggested slides:

• Cover
• Current impact
• Who is building
• What is working
• New use cases
• Product updates
• Proof points
• Next steps

Gamma Generation Pattern

Prepare the deck content as markdown:

# Zapier + [Company Name] - [Call Type]
*Prepared for [Company Name] | [Date]*

---

## Agenda
1. Context
2. Current impact
3. Opportunities
4. Next steps

---

## [Slide Title]
[Concise slide content]

Then use Zapier MCP to run the Gamma create-generation action with:

• format: presentation
• card dimensions: 16x9
• tone: professional
• audience: business executive
• text amount: concise

Poll the Gamma generation status action until the presentation URL is available.

Content Guidelines

• Lead with the customer outcome, not the data source.
• Use concrete numbers only when the source supports them.
• Make every slide useful in three seconds.
• Clean up technical app names before putting them on slides.
• Group workflow logic tools separately from external apps.
• Use plain language for task usage, feature adoption, renewal timing, and expansion opportunities.
• Flag any claims, product roadmap mentions, or customer references that need approval.

Zapier MCP And SDK Role

• Use Zapier MCP to read approved CRM, account, usage, meeting, and document context.
• Use Zapier MCP to call Gamma generation and status actions.
• Use Zapier SDK when the workflow becomes repeatable: deck request intake, data snapshot logging, approval routing, and handoff tracking.

Guardrails

• Do not include raw SQL, internal table names, private notes, emails, or internal IDs in customer-facing slides.
• Do not use unapproved customer names, quotes, logos, or metrics.
• Do not share a generated deck externally until a human has reviewed the content.
• Do not write back to CRM, create customer messages, or publish assets without approval.