Back to Details

who-is-this-for

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Who is this for?

适用人群

"Developers" is not a market. It's a medium. If your ICP doesn't exclude anyone, it isn't one.
Use this when: you describe your user as "developers" or "engineering teams," you can't name a person who is clearly not a fit, or you're aiming your messaging at the VP of Engineering because they have the budget.
“开发者”不是一个市场，而是一种媒介。如果你的ICP不排除任何用户，那它就不是有效的ICP。
适用场景： 你将用户描述为“开发者”或“工程团队”，无法明确指出明显不适合的用户，或是因为VP of Engineering（工程副总裁）掌握预算就将营销信息对准他们。

The core idea

核心理念

A usable ICP is specific enough that some people are obviously out. "Every developer" gives you nothing to say, because a message that speaks to everyone speaks to no one. Sharpen until exclusion is possible.
And in almost every AI/dev-tool sale there is more than one person: the developer who adopts is rarely the person who pays. Market to the adopter; sell to the buyer. Confuse the two and you get great meetings and no decisions.
有效的ICP需要足够具体，能明确排除部分用户。“面向所有开发者”毫无意义，因为一款能打动所有人的产品，实际上无法真正打动任何人。要不断细化，直到能明确排除部分群体。
在几乎所有AI/开发者工具的销售场景中，涉及的角色不止一个：实际使用产品的开发者很少是付费决策者。要面向使用者做营销，面向付费者做销售。混淆两者只会让你获得大量会议机会，却无法达成任何决策。

Framework 1: The personas in the sale (Frankl)

框架1：销售中的角色（Frankl提出）

Map who plays each role. You need all of them for a complex sale; skip one and the deal stalls.
PersonaCares aboutRole in the sale
Alpha Dev"What's possible?" Lives in the future. No budget.Finds you, experiments, advocates internally, creates social proof
Empowered CTOKairos, weeks off a release cycle, competitive edge. Has budget.Approves spend and strategic fit
VP EngineeringTeam velocity, DX, quality at scale. Fears downtime/securityEvaluates feasibility, tests in staging
SRE / Platform EngReliability, less toil. Reads your code before your copy.Gatekeeps operational risk
The Alpha Dev is not your long-term customer. They chase the next shiny thing. You need them anyway: they carry new tech to the people who pay.
梳理每个角色的职责。复杂销售需要覆盖所有角色，遗漏任何一个都会导致交易停滞。
角色关注重点销售中的职责
Alpha Dev“能实现什么？”着眼未来。无预算权限发现产品、进行测试、内部推广、创造社交证明
Empowered CTO关键时机、缩短发布周期、竞争优势。拥有预算权限批准预算及确认战略契合度
VP Engineering团队交付速度、DX（开发者体验）、规模化下的质量。担忧停机/安全问题评估可行性、在预发布环境测试
SRE / Platform Eng可靠性、减少重复劳动。先读你的代码再看文案把控运营风险
Alpha Dev 不是你的长期客户。他们追逐新鲜事物。但你仍需要他们：他们会将新技术带到付费决策者面前。

Framework 2: Jobs to be done, not demographics (Czakon)

框架2：待完成工作，而非人口统计特征（Czakon提出）

A job title is not actionable; a job is. Write it as:
When [situation], I want to [motivation], so I can [expected outcome].
Example: "When I inherit a service with no tests, I want to generate a safety net fast, so I can refactor without fear." That sentence tells you the trigger, the pain, and the win. A demographic never does.
职位头衔不具备可操作性；待完成的工作才是。按照以下格式撰写：
当[场景]时，我想要[动机]，这样我就能[预期结果]。
示例：“当我接手一个没有测试用例的服务时，我想要快速生成安全保障，这样我就能毫无顾虑地重构代码。” 这句话明确了触发点、痛点和收益，而人口统计特征永远做不到这一点。

Decision tree: single-player or complex sale?

决策树：单人决策还是复杂销售？

Does the developer who adopts also control the budget?
├─ YES  → single-player / PLG motion.
│         ICP centers on the adopter. Optimize time-to-value, self-serve, transparent pricing.
└─ NO   → complex sale.
          ICP centers on the adopter FOR ADOPTION, and the buyer FOR REVENUE.
          You need a "what's in it for me" for every persona above.
Does the developer who adopts also control the budget?
├─ YES  → single-player / PLG motion.
│         ICP centers on the adopter. Optimize time-to-value, self-serve, transparent pricing.
└─ NO   → complex sale.
          ICP centers on the adopter FOR ADOPTION, and the buyer FOR REVENUE.
          You need a "what's in it for me" for every persona above.

Sharpen it: the 5-attribute ICP

细化ICP：5要素模型

Fill every line with something a stranger couldn't guess:
  1. Company shape: stage, size, team structure (e.g. "50-500-engineer companies with a platform team")
  2. Technical context: stack / recent change (e.g. "just adopted Kubernetes")
  3. The trigger: what just happened that makes this urgent now
  4. The pain, in their words: the exact phrase they'd use (get this from 
    talk-to-users
    )
  5. Who says no: the segment you are deliberately not for
每一项都要填写陌生人无法凭空猜测的具体信息：
  1. 企业形态：发展阶段、规模、团队结构（例如：“拥有平台团队的50-500人规模的技术公司”）
  2. 技术背景：技术栈/近期变更（例如：“刚采用Kubernetes”）
  3. 触发事件：刚刚发生的、让需求变得迫切的事件
  4. 用户原话描述的痛点：用户会使用的准确表述（通过
    talk-to-users
    获取）
  5. 排除群体：你明确不面向的用户群体

Mistakes that look reasonable

看似合理的错误做法

  • TAM theater: "there are 30M developers." True and useless. Nobody sells to 30M anyone.
  • Budget-chasing: writing everything for the CTO/VP because they pay. They don't visit your homepage; the developer does.
  • Persona = job title: "backend engineers." That's a hat, not a human. Use the job.
  • One persona, complex sale: nailing the Alpha Dev and forgetting the buyer → adoption with no revenue.
  • TAM空谈：“全球有3000万开发者。”这句话没错但毫无用处。没有人能面向3000万用户销售产品。
  • 追逐预算：所有内容都针对CTO/VP，因为他们掌握预算。但他们不会访问你的官网——开发者才会。
  • 角色=职位头衔：“后端工程师”。这只是一个身份标签，而非具体用户。要关注他们的待完成工作。
  • 复杂销售只关注单一角色：精准定位Alpha Dev却忽略付费决策者→获得产品使用量但没有收入。

Example

示例

❌ "For developers who want to ship faster." ✅ "For platform engineers at 50-500-eng companies who just standardized on Kubernetes and are drowning in hand-written YAML, the ones who'd say 'I spend a day a week on manifests I shouldn't have to touch.' Not for solo devs on Heroku."
❌ “面向想要更快交付的开发者。” ✅ “面向刚统一采用Kubernetes、被手写YAML淹没的50-500人规模公司的平台工程师，这些人会说‘我每周要花一天时间处理本不该我做的配置清单。’不面向使用Heroku的独立开发者。”

Your next 30 minutes

接下来30分钟的行动

  • Write your ICP with all 5 attributes filled in, including who says no.
  • List every persona in your sale and mark: who finds it, who evaluates it, who pays.
  • Rewrite your one-line pitch as a Job To Be Done (
    When… I want… so I can…
    ).
  • If you couldn't fill attribute #4 in their real words → you owe yourself 
    talk-to-users
    before anything else.
Built from real dev-tool GTM experience, with frameworks from Adam Frankl (The Developer-Facing Startup) and Jakub Czakon (markepear.dev). When a framework can't make the call, that's what a human is for: The DevTool GTM Company.
  • 填写包含全部5项要素的ICP，包括排除群体。
  • 列出销售中的所有角色，并标记：谁发现产品、谁评估产品、谁付费。
  • 将你的一句话宣传语重写为待完成工作格式（
    当…我想要…这样我就能…
    ）。
  • 如果你无法用用户的原话填写第4项→你需要先完成
    talk-to-users
    （与用户沟通），再做其他事情。
基于真实的开发者工具GTM（上市策略）经验构建，整合了Adam Frankl（《面向开发者的创业公司》）和Jakub Czakon（markepear.dev）提出的框架。 当框架无法做出决策时，就需要专业人士的帮助：The DevTool GTM Company。