Internal Enablement

4.1 Internal Launch Kickoff

What you're creating: A high-energy meeting that aligns and energizes every team involved in the launch.

Schedule the kickoff (3 weeks before launch)

• Product Marketing
• Sales
• Customer Success
• Support
• Product
• Engineering
• Marketing/Content

Build the agenda (90 minutes)

• Strategic context (why this matters) - 10 min
• Product overview & demo - 15 min
• Target customers & personas - 10 min
• Go-to-market strategy - 10 min
• Timeline & milestones - 10 min
• Team roles & responsibilities - 10 min
• Q&A - 15 min

Assign clear ownership

Document who owns:

• Sales enablement: Product Marketing + Sales Ops
• Customer communications: Customer Success
• Support readiness: Support Ops
• Website updates: Marketing
• Social media: Marketing/Social
• Email campaigns: Marketing/Growth
• Analytics & reporting: Product Marketing + Growth

Set up coordination channels

• Create a dedicated Slack channel (#product-launch)
• Set up a shared folder for all assets
• Create a project in Notion/Asana for task tracking

4.2 Sales Training

What you're creating: Confident, well-prepped sales reps who can pitch, demo, and handle objections without guessing.

Run a launch training session

Walk sales through:

• The strategic narrative (why this product, why now)
• Target personas and pain points
• Key differentiators vs. competitors
• The sales deck (built in Chapter 3.2)
• The sales one-pager (built in Chapter 3.3)
• The internal FAQ and objection handling framework (built in Chapter 3.4)

Drill discovery questions

Train reps to use a discovery framework organized by:

• Current state: What do you use today?
• Pain points: What's not working?
• Decision process: Who else is involved?
• Timeline: When do you need this?
• Success criteria: What does good look like?

Run live role-plays so reps practice the questions before they hit real calls.

Practice objection handling

Take the top 5-7 objections from the internal FAQ and run scenarios using the Acknowledge → Bridge → Answer → Confirm framework. Record the practice sessions so reps can review.

Run demo walkthroughs

• Have your top performer demo the product live
• Walk through the demo flow and "gotcha" moments from Chapter 3.2
• Let each rep practice a full demo with peer feedback

4.3 CS Rollout Playbook

What you're creating: A clear plan for how Customer Success will roll the launch out to existing customers.

Segment customers by rollout priority

• Tier 1 (Week 1): Enterprise accounts, strategic customers, vocal advocates
• Tier 2 (Week 2-3): Mid-market, active users
• Tier 3 (Week 4+): Long-tail, low-engagement accounts

Define the rollout approach per segment

For each tier, document:

• Who reaches out (CSM, Account Manager, automated email)
• When and how (1:1 call, group webinar, email)
• What they share (onboarding guide, demo video, training session)
• Success metrics to track (adoption rate, support tickets, NPS shift)

Train CS on the new product

• Run a CS-specific training (different lens than sales — focus on adoption, not selling)
• Walk through the onboarding guide and adoption checklist (built in Chapter 3.5)
• Cover common customer questions and where to find answers
• Define escalation paths for product issues, feature requests, and upgrade conversations

Document the escalation path

• Product bug → Engineering on-call
• Feature request → Product Manager
• Upgrade conversation → Sales/AM
• Churn risk → CS Leadership

4.4 Support Training & Escalation Procedures

What you're creating: A support team that can resolve launch-related tickets quickly without bottlenecking the rest of the company.

Run support training

Walk the team through:

• Product overview & key features
• The technical documentation, KB articles, and troubleshooting guide (built in Chapter 3.1)
• The customer FAQ (built in Chapter 3.4)

Drill on common scenarios

• Walk through 5-7 likely tickets and have the team practice responses
• Record best-in-class responses as templates for future use
• Identify gaps in documentation and flag them back to Product Marketing

Build the escalation procedure

Define when to escalate, to whom, and how fast:

• Tier 1 (basic Qs): Resolved by support directly
• Tier 2 (config/integration): Escalate to Solutions Engineering
• Tier 3 (bugs/outages): Escalate to Engineering on-call
• Tier 4 (security/compliance): Escalate to Security/Legal

Set up real-time launch coverage

• Have extra support coverage scheduled for launch week
• Set up a dedicated launch-issues Slack channel
• Define a SLA for launch-week tickets (faster than usual)

4.5 1:1 Outreach Email Templates

What you're creating: Personalized email templates sales and CS reps can adapt for individual customer outreach. (Note: broadcast email campaigns are covered in Chapter 7.)

Sales templates

Build templates for:

• Cold outreach (new prospect, leading with the launch)
• Post-demo follow-up
• Objection response (one per top objection)
• Competitive displacement
• Pricing/contract discussion
• Re-engagement of cold leads ("Remember when we talked about [problem]? We solved it.")

CS templates

Build templates for:

• Launch announcement to existing customers
• Feature walkthrough invitation
• Check-in 7 days post-rollout
• Best practices share-out
• Success story request

Format and personalize

Each template should:

• Be under 100 words
• Have a clear single CTA
• Include 2-3 personalization fields ([Name], [Company], [specific use case])
• Be tested by 2-3 reps before going live