360 Secure SkillHub
360 安全技能中心

B2b Saas Product Launch

该技能为 B2B SaaS 产品、功能或 GTM 发布提供结构化策划,包括发布层级判断、定位提炼、发布前/中/后清单、分受众消息、分层资产清单与成功指标,最终输出一份发布计划。

renehdzgtz
renehdzgtz
热度 24.36
最近更新 2026-05-11 17:48:15
分类:营销依赖:纯提示词应用场景:文案创作 / 邮件起草 / 社交媒体 / 任务管理 ...

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add b2b-saas-product-launch
Metadata
name
b2b-saas-product-launch
description
B2B SaaS product and feature launch planner. Use this skill whenever the user wants to plan, coordinate, or execute a product launch, feature release, or go-to-market for a new capability. Trigger for phrases like "product launch", "feature launch", "launch plan", "GTM plan", "go-to-market", "we're shipping X", "launch checklist", "how do we announce this", "launch messaging", "sales enablement for launch", "announcing a new product", or any request to plan the marketing and coordination needed to release something new.

Product Launch Planner — B2B SaaS

Purpose: Coordinate a successful launch so sales knows what to say, customers know why it matters, and the market hears the right message.


Step 1: Gather Context

  • What's launching: Feature, product, major update, or new product?
  • Launch tier:
    • Tier 1: Major product / new category — full launch motion
    • Tier 2: Significant feature — targeted launch + sales enablement
    • Tier 3: Minor release — changelog + customer email
  • Audience: New buyers, existing customers, or both?
  • Timeline: Hard launch date?

Step 2: Launch Positioning

What it is:
What it does (one verb + outcome):
Who it's for (persona + use case):
Why now (what changed):
Why only us:
The "so what" in buyer language:

BEFORE: "[How customers dealt with this before]"
AFTER:  "[What's now possible — specific, concrete]"

Step 3: Launch Checklist

PRE-LAUNCH (T-4 to T-1 week):

Product: stable + tested | docs complete | beta feedback in | rollout confirmed
PMM: positioning final | FAQ ready | sales one-pager | demo updated
Sales: briefing deck | demo script | Q&As | team trained | SDR talk track
Marketing: customer email | prospect email | blog/PR | social posts | website updated
CS: CSM briefed | proactive outreach list | support trained

LAUNCH DAY SEQUENCE:

08:00 — Internal Slack announcement
09:00 — Customer email
09:30 — Blog / press release
10:00 — Social posts + SDR sequences activated
10:30 — Sales "launch is live" signal
11:00 — In-app banner
12:00 — Founder + team personal LinkedIn posts

POST-LAUNCH (T+1 to T+30):

Week 1: Daily adoption monitoring, collect quotes, SDR second touch
Week 2-4: Adoption data, CS proactive outreach, follow-up content, retro

Step 4: Messaging by Audience

Customers: "Starting today, you can [capability] from [where]. This means [workflow improvement]. [CTA]"

Prospects: "[Hook: problem] → Introducing [feature]: [one-liner] → [2-3 benefits + proof] → [CTA]"

Sales (internal):

Elevator: "We launched [feature]. Lets [persona] [do X] without [pain].
[Customer] went from [before] to [after] in [timeframe]. Worth a look?"
Top objections + answers

Step 5: Asset List by Tier

Tier 1: landing page | blog/PR | customer email | prospect email |
         social posts (company+founder+team) | sales one-pager |
         demo script update | SDR cadence | in-app announcement

Tier 2: customer email | brief blog post | sales FAQ | 1 social post

Tier 3: changelog entry | in-app tooltip

Step 6: Success Metrics

Day 1-7: email open/click, landing page visits, demo requests
Day 30: % customers tried feature, feature in demo notes, pipeline influenced
Day 90: feature adoption %, win rate on feature demos, buyer mentions

Output Format

# Launch Plan — [Feature/Product]
Date: [date] | Tier: [1/2/3]
## Positioning | ## Checklist (with owners)
## Launch Day Sequence | ## Post-Launch
## Asset List | ## Messaging (customer/prospect/sales)
## Success Metrics