菜单
When planning or refactoring an outbound motion, validating account selection before investing pipeline resources, debugging why a sequence is unde...
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/UitbreidenOS/UitKit --skill gtm-philosophy命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Guidelines and instructions for Agent execution state rollback rules
Guidelines and instructions for Agent execution step counters limits
Guidelines and instructions for Agent execution timeout limits setups
基于 SOC 职业分类
| name | gtm-philosophy |
| description | When planning or refactoring an outbound motion, validating account selection before investing pipeline resources, debugging why a sequence is unde... |
When planning or refactoring an outbound motion, validating account selection before investing pipeline resources, debugging why a sequence is underperforming, or deciding whether to pursue a prospect given your current positioning and market conditions.
When composing individual emails, personalizing a single outreach, or executing a specific tactic — this is strategic framework thinking, not tactical execution. Not for inbound contexts where demand is already created.
Before entering an account into your sequence, run it through BIPSY — a five-point disqualification framework. If the account fails any gate, reallocate resources to better targets.
B — Broken Process Does the prospect's organization have an existing, functioning process that your solution touches? If they have no formal intake, no approval hierarchy, or no budget allocation for this category, you're not filling a gap — you're creating demand from scratch. That's expensive and slow. Disqualify unless you have a champion with executive air cover.
I — Insight Gap Do you have a differentiating insight specific to this company and buyer? Not a generic pitch. Not a templated pain point. A concrete observation about their market position, internal structure, or competitive exposure that they likely haven't articulated themselves. Without it, you're one of ten identical emails in their inbox. Insight is your permission slip to cold outreach.
P — Priority Mismatch Is solving your problem in the buyer's top 3 priorities for the next 12 months? Talk to peers in similar roles at similar companies. Validate the ranking. If your issue is priority #7, you're competing for attention against 6 bigger problems. Budget dries up, deals slip. Disqualify and come back when the market shifts.
S — Skill Gap Can your team actually execute against this account profile? If you're selling upmarket but your sales team only closes SMB deals, or if you're selling to DevOps but your demo requires product context that doesn't exist, stop. Skill mismatch turns qualified pipeline into lost deals. Be honest about your team's depth.
Y — You're Not the Right Fit Is this truly your buyer? Wrong geography, wrong product-market alignment, wrong buyer persona, or timing that's 18 months too early. Sometimes the best outcome is passing on an account. It preserves credibility, frees up resources, and prevents defensive objections later when market conditions improve.
If an account clears all five gates, add it to your hit list. If it fails any, move on.
Ten hyper-targeted accounts — where you have a named insight, clear stakeholder mapping, relevant use case, and differentiated positioning — will generate more pipeline, better conversion rates, and higher deal velocity than 1,000 generic spray-and-pray outreaches.
Concentrate your effort. Research five people deeply before researching fifty casually. Quality of hypothesis beats quantity of attempts.
This means your account list is short and your personalization is deep. You know the buying committee's names. You know their recent earnings calls, hiring patterns, and funding announcements. You can predict their objections and have prepared, specific responses. You reference their actual business in your sequence, not generic vertical language.
Volume is the refuge of mediocre targeting. Abandon it.
Email alone converts at 1–2%. Phone alone (cold) converts at 2–3%. One channel creates noise. Multiple channels, sequenced with intent, create signal.
Anchor Channel: Email Email is your credibility layer. It's written, searchable, and gives the prospect time to process your insight without the friction of synchronous conversation. Your first email is short (5–7 sentences), contains a specific insight about their business, and proposes a low-friction next step. Not a demo. Not a call. A question worth answering or a data point worth exploring. You're opening a conversation, not closing a deal.
First Touch: LinkedIn Within 48 hours of your email, send a LinkedIn connection request with a short personalized note. Tie it directly to your email. "I sent you a thought on [specific thing we mentioned]. Want to continue there?" LinkedIn creates visibility and reinforces that you're a real person, not a bot. It also signals intent — you researched them enough to find their profile.
Second Touch: Phone (Warm Handoff) After email and LinkedIn have had time to land (3–5 days), you have earned permission for a call. You're not asking if they want to talk; you're assuming they read your email and offering them a specific time slot to continue the conversation. "I've sent you a note on X. I have two slots Thursday — 10 or 2:30 — to dive deeper. Which works?" This is a warm follow-up, not a cold call.
Closing Touch: Video If synchronous conversation is needed, move to video before moving to a Zoom call (if doing async review) or to the sales team. Video is higher touch than phone but lower friction than an in-person meeting. Use it to unblock decision-making, walk through a specific workflow, or build relationship after initial interest.
Spacing matters. Email → LinkedIn (48 hours) → Phone (3–5 days) → Video (as needed). Don't all-channel-at-once. Let each touch do its job.
Your targeting strategy is account-first; your execution is contact-first.
Account-First Strategy Identify the 10–50 accounts where you have the highest confidence of finding a buyer and closing a deal. Build a 12–18 month engagement narrative for each account. What's the likely buying trigger? Who will be in the committee? What's the approval path? What competitive or macro pressure might force a decision?
Contact-First Execution Within each target account, you start with one or two identified contacts. You are not flooding the account with 10 simultaneous outreaches. You find the person most likely to believe your insight (often the person with the most acute version of your problem), and you begin a conversation with them. Your goal is to move from one contact to three contacts — expanding upward and laterally as trust builds.
If your first contact doesn't respond after a thorough sequence (4–5 touches over 3 weeks), you then move to a second contact. You don't abandon the account; you change the conversation starter.
The strategic view is holistic (account value, market position, fit). The tactical view is focused (one human, one conversation at a time).
When evaluating a new account:
"Based on what I know of this account, can I articulate a specific, non-obvious business insight about why they should care about solving this problem in the next 12 months? If I can't write it in two sentences without using buzzwords, the account isn't ready for outreach."
Scenario: You're a GTM platform selling to mid-market SaaS companies. You've identified a 50-company target list and want to prioritize based on GTM Philosophy principles.
Account Evaluation:
Company: Acme APIs (a YC-backed API infrastructure company, Series A, 25 employees)
BIPSY Gate Check:
B — Broken Process: Acme has a product launch planned in Q4. They'll need coordinated sales, marketing, and customer success messaging. Currently, all three teams use Slack and a shared Google Doc. ✓ Clear broken process.
I — Insight Gap: You discover that Acme's last two product launches had inconsistent messaging across channels, leading to 30% lower-than-expected trial signups. Marketing claimed feature X did Y; sales claimed it did Z. You have a specific insight: "Your go-to-market misalignment is costing you ICP leads before they even reach your sales team." ✓ Differentiating.
P — Priority Mismatch: You speak with a peer at a similar-stage company. GTM alignment is their #2 priority for the next 6 months (after hiring). Acme is at the same growth stage, same market. ✓ High probability of priority.
S — Skill Gap: Your team has closed 12 deals with Series A SaaS. Your demo is built on an API startup's workflow. ✓ You have relevant skill.
Y — You're Not the Right Fit: Acme is US-based, English-speaking, and your platform supports their region and use case. ✓ Good fit.
Acme clears BIPSY. Add to tier-1 outreach list.
Sequencing Plan:
Email (Day 1): You send an email to the VP of Marketing. Subject: "How much did the API launch cost you in lost leads?" Body: Specific insight about their last launch (you researched their launch announcement and looked at launch day blog traffic vs. signup traffic). You reference that the signup dip happened on the same day messaging inconsistency appeared across their channels. Propose: "I have a 15-minute thought on reducing that gap for Q4. Worth a call?"
LinkedIn (Day 2): Connection request with note: "Saw your API launch piece — the product looks solid. Sent you a note on messaging consistency. Let's continue there."
Phone (Day 5): If no response, you send: "VP, I blocked 10 and 2:30 Thursday. My take on the messaging misalignment in your launch takes 10 minutes to walk through. Which slot works?"
Video (Day 12–15): If she schedules the call and there's interest, you move to a 25-minute video walkthrough showing how your platform would have caught the messaging inconsistency in real-time. You demo against her exact workflow, not a generic SaaS workflow.
Result: By the time you're on the phone, you're not selling; you're solving a problem she knows she has.
