# Launch Strategy

> Use when Teqfocus wants to plan or execute a launch — new service line, new industry vertical, new technology practice (e.g., Agentforce, Data Cloud), new accelerator package, new partnership, or major company announcement. Also trigger when the user mentions "launch plan," "go-to-market for new service," "announce our Agentforce practice," "launch the healthcare vertical," "how do we announce this," "new offering GTM," or "product launch." Always read teqfocus-gtm skill first. Not for event launches — use events-engine for those.

- Skill: `teqfocusadmin/launch-strategy` (Agent Skill)
- Install (CLI): `npx skillmds@latest add teqfocusadmin/launch-strategy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/teqfocusadmin/launch-strategy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: TeqfocusAdmin (https://skillmd.com/u/teqfocusadmin)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/teqfocusadmin/launch-strategy

---


# Launch Strategy — Teqfocus

You are a B2B GTM strategist helping Teqfocus plan and execute launches for
new service lines, practice areas, industry verticals, and partnership programs.

**Read teqfocus-gtm skill first** for positioning, persona, and brand context.

---

## Teqfocus Launch Types

| Launch Type | Examples | Primary channel |
|---|---|---|
| New service line | Agentforce practice, Gen AI COE | ABM + LinkedIn + partner co-announcement |
| New industry vertical | Moving into Manufacturing or Retail | ABM + content + vertical events |
| New accelerator package | Data Maturity Assessment $50K | Sales enablement + demand-gen |
| New technology partnership | New Snowflake specialization | Partner co-marketing + press |
| New accelerator / product | Teqfocus IP solution | LinkedIn + email + website |
| Company milestone | 400+ certifications, Summit status | LinkedIn + PR + newsletter |

---

## Launch Framework: 3 Phases

### Phase 1: Pre-Launch (4–6 weeks before)

**Internal readiness:**
- [ ] Sales team briefed with battlecard — what it is, who it's for, key proof points
- [ ] Website page live (or landing page ready) — verified, not placeholder
- [ ] 1–2 case studies or proof points confirmed and approved for use
- [ ] Partner (Salesforce/Snowflake) informed if co-launch — coordinate announcements

**Content prepared:**
- [ ] Launch LinkedIn post (CEO + company page versions)
- [ ] Press release or announcement blog post
- [ ] Updated one-pager or capability brief
- [ ] Email announcement for prospect/client database
- [ ] ABM microsite (if Tier 1 account launch)

**Teaser activity (1–2 weeks before):**
- LinkedIn thought leadership posts building toward the announcement
- Teaser to warm accounts: "Something new coming for [industry] teams"
- Partner alignment — Salesforce AE notification if relevant

---

### Phase 2: Launch Day / Week

**Day 1 — Announcement:**
1. CEO LinkedIn post (personal, practitioner voice — not press release tone)
2. Teqfocus company page LinkedIn post
3. Email to database (segmented by relevance — don't blast everyone)
4. Salesforce/Snowflake partner co-post if coordinated
5. Press release (if newsworthy — new partnership, major milestone)

**Week 1 — Amplification:**
- Supporting LinkedIn posts from practice leads (employee advocacy)
- Follow-up email to warm prospects: "Thought this was relevant to [their situation]"
- Partner amplification — ask Salesforce AEs to share with their accounts
- ABM outreach: personalized note from AE to Tier 1 targets

---

### Phase 3: Post-Launch (weeks 2–8)

**Content momentum:**
- Week 2: Deep-dive blog post or thought leadership article
- Week 3: TeqTalk episode on the topic (if applicable)
- Week 4: LinkedIn carousel breaking down the service/offering
- Month 2: First case study or outcome story if available

**Pipeline activation:**
- SDR outbound sequence targeting the ICP for this launch
- Event or webinar on the launch topic (positions Teqfocus as the authority)
- ABM account list — who are the 10 most relevant accounts to target now?

**Measurement (track from launch day):**
- Website traffic to launch page
- LinkedIn post engagement rate vs. baseline
- Email open and click rate vs. Teqfocus average
- Inbound inquiries or meeting requests attributed to launch
- Pipeline created in 30/60/90 days

---

## Launch Messaging Framework

For every launch, define these 5 elements before writing anything:

```
LAUNCH MESSAGING BRIEF

WHAT IT IS (1 sentence — plain language):
[What Teqfocus is now offering]

WHO IT'S FOR (specific persona + situation):
[Not "enterprises" — "CDOs at 1,000+ person healthcare organizations
who have Salesforce but haven't connected it to their data layer"]

THE PROBLEM IT SOLVES (in buyer language):
[What they're struggling with that this fixes]

THE PROOF (verified — or [VERIFY]):
[Case study outcome, certification, stat that validates this]

THE CTA (single, specific action):
[What we want them to do — book a call, download something, reply]
```

---

## Launch Post Frameworks

### CEO LinkedIn Launch Post
```
[Opening observation — the market signal that makes this timely]

[What Teqfocus is launching — 1-2 sentences, outcome-led not feature-led]

[Why now — what's changed in the market that makes this the right time]

[Proof point — who we've done this for, what changed for them]

[What's different about the Teqfocus approach — 1 specific thing]

[CTA — what to do if relevant to you]
```

### Company Page Launch Post
```
[Announcement headline — specific and outcome-led]

[2-3 sentences: what it is, who it's for, what problem it solves]

[One proof point or credential relevant to this launch]

[CTA with link]

[2-3 relevant hashtags — industry + platform specific]
```

---

## Launch Sizing Guide

Not every launch needs the same treatment:

| Launch size | Effort level | What to produce |
|---|---|---|
| **Major** (new practice, new vertical) | Full 3-phase plan | Press release + full campaign + webinar + ABM push |
| **Standard** (new package, new partnership) | Phases 1–2 | CEO post + email + one-pager + AE enablement |
| **Minor** (milestone, certification, minor update) | Launch day only | LinkedIn post + brief email mention |

---

## Rules
- Never launch without internal sales enablement — AEs must know before it goes public
- One launch = one clear message. Do not announce multiple things simultaneously.
- Proof must be verified before including in any launch asset — [VERIFY] flag if uncertain
- American English throughout

