Back to Details

founder-led-sales

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Founder-led sales (close your first customers yourself)

创始人主导销售（亲自签下你的第一批客户）

Nobody can sell it before you can. The first ten deals are not a hire, they are how you learn what you are actually selling and to whom. Do them yourself, badly at first, until the motion repeats.
Use this when: developers love it and live in the free tier but nobody pays, you have never sold anything and freeze on the actual conversation, every deal dies on "let me think about it," or you are tempted to hire a salesperson to do the part you have not figured out yet.
在你能卖出产品之前，没人能做到。前10笔交易不是靠招聘销售完成的，而是让你了解自己实际在卖什么、卖给谁的过程。亲自去做，哪怕一开始做得很差，直到这个流程可以重复。
适用场景： 开发者喜爱你的产品、一直使用免费版但无人付费；你从未做过销售，实际沟通时不知所措；每笔交易都卡在“我再想想”这一步；或者你想招聘销售人员来完成你自己还没搞懂的环节。

The core idea

核心理念

market-to-devs-sell-to-buyers
told you who to sell to (the dev adopts, the boss pays). 
pricing
set the number. This is the part nobody warns technical founders about: actually doing it. And it is not slimy. Selling a dev tool well is discovery plus helping a champion get budget. You are not convincing anyone of anything false, you are finding the people who already have the pain and making it easy for them to say yes.
One rule under all of it: do this yourself until it repeats. You cannot outsource a motion you have not cracked. Founders who hire a rep at deal one hire someone to fail at a job that does not exist yet.
market-to-devs-sell-to-buyers
告诉你要卖给谁（开发者试用，老板付费），
pricing
确定了价格。而这部分是技术创始人很少被提醒的：实际去做销售。而且这并不虚伪。做好开发者工具的销售，关键在于挖掘需求，同时帮助支持者争取预算。你不是在说服别人相信虚假的东西，而是找到那些已经有痛点的人，让他们更容易说“是”。
所有环节的一条准则：亲自做这件事，直到流程可以重复。 你无法外包一个自己还没搞通的流程。在第一笔交易就招聘销售的创始人，相当于雇人去做一份还不存在的工作，结果必然是失败。

Every real deal has four things

每一笔真实交易都具备四个要素

If any one is missing, it is not a deal, it is a conversation. Your job is to find out which is missing.
  • A champion. Someone who uses it, loves it, and will fight for it inside their company. Usually the developer who adopted you.
  • A buyer. Someone with budget. Often not the champion.
  • A pain with a cost. Not "this is nice." A problem costing them money, time, or risk right now.
  • A trigger. A reason to act now, not next quarter. An incident, an audit, a deadline, a scaling wall.
如果缺少任何一个，那只是一场对话，不是交易。你的任务就是找出缺失的要素。
  • 支持者（Champion）：使用你的产品、喜爱它，并且会在公司内部为它争取资源的人。通常是试用你产品的开发者。
  • 付费决策者（Buyer）：拥有预算的人。通常不是支持者。
  • 有成本的痛点：不是“这个东西不错”，而是当前正在耗费他们资金、时间或带来风险的问题。
  • 行动触发点：现在就行动的理由，而不是等到下个季度。比如一起事故、一次审计、一个截止日期、一道增长瓶颈。

The motion

销售流程

1. Start with who is already engaged. Do not cold-blast strangers. Your first customers are hiding in your own usage data: the team with three seats on the free tier, the person who filed four issues, the account that hit a limit. They have already shown you the pain.
2. Reach out like a founder, not a sequence. One short, human message to a real person about a specific thing you noticed. If it could have gone to a thousand people, do not send it.
3. The first call is discovery, not a pitch. Talk 30 percent, listen 70. Learn: what are they using it for, what did they do before, what is the pain costing them, who else feels it, who owns the budget. Founders pitch too early and too much. The person asking the best questions controls the conversation.
4. Demo their use case, not your feature list. Show the product doing their job with their kind of data, and get them to the win (see 
time-to-first-value
). A feature tour is not a demo. "Here is your exact problem, solved" is.
5. Frame value for the buyer, not the dev. The developer feels the hours saved (Chronos). The buyer approves budget for the outcome: a release cycle back, an incident avoided, a compliance box checked, a competitor not winning (Kairos). Translate the dev's love into a business result the boss can defend.
6. Arm the champion to sell internally. You are rarely in the room when the yes happens. Give your champion the one-paragraph business case, the number, and the answer to "why now," so they can walk it to their boss. This is the middle-out motion: an excited dev plus a buyer who sees the ROI.
7. Always leave with a specific next step and a date. This is how you kill the stall before it starts.
1. 从已参与的用户入手：不要给陌生人群发消息。你的第一批客户就藏在自己的使用数据里：使用免费版3个席位的团队、提交过4个问题的用户、达到使用限制的账户。他们已经向你展示了痛点。
2. 以创始人的身份联系，而非套用模板：给真实的人发一条简短、人性化的消息，内容要针对你观察到的具体情况。如果这条消息可以发给上千人，那就不要发。
3. 首次沟通是挖掘需求，而非推销：你说30%，听70%。了解这些信息：他们用产品做什么、之前用什么、痛点带来的成本是什么、还有谁受这个痛点影响、谁掌握预算。创始人往往过早且过多地推销。提出最佳问题的人才能掌控对话。
4. 演示他们的使用场景，而非你的功能列表：展示产品如何用他们的数据完成他们的工作，让他们快速看到价值（参考 
time-to-first-value
）。功能展示不是演示。“这就是你的具体问题，我们帮你解决了”才是。
5. 站在付费决策者的角度阐述价值，而非开发者：开发者感受到的是节省的时间（Chronos）。付费决策者批准预算是为了结果：缩短发布周期、避免事故、满足合规要求、不被竞争对手超越（Kairos）。把开发者的喜爱转化为老板能认可的业务成果。
6. 帮助支持者在内部推进销售：最终拍板的场合你很少在场。给你的支持者准备一段简短的业务案例、价格，以及“为什么现在就要行动”的理由，让他们可以向老板汇报。这就是“中间驱动”的流程：一个兴奋的开发者加上一个能看到ROI的付费决策者。
7. 每次沟通都要确定具体的下一步和日期：这是从一开始就避免交易停滞的方法。

"Let me think about it" is not an objection

“我再想想”不是反对意见

It is a missing next step, or a concern you did not surface. Do not accept it and leave. Ask, gently: "Totally fair. What would you need to be sure of to move forward?" Then you learn the real blocker (budget, a stakeholder, a missing feature, timing) and can actually address it. A vague yes-later is a no you have not diagnosed.
它意味着缺少明确的下一步，或者你没有发现潜在顾虑。不要接受这个托词就结束沟通。温和地问：“完全理解。你需要确认哪些事情才能推进？”然后你就能了解真正的障碍（预算、利益相关者、缺失的功能、时间安排），并实际解决它。模糊的“以后再说”其实是你还没诊断出来的拒绝。

Thresholds worth knowing

需要了解的关键阈值

  • Do it yourself through roughly your first 10 to 20 paying customers, or until you can write down what works and repeat it. Only then does hiring make sense.
  • Multithread. A deal with only the champion is fragile. If you have not spoken to the person with budget, you do not have a deal, you have a fan.
  • No next step, no deal. Never end a sales conversation without a specific action and a date.
  • Do not discount out of fear. Price pushback is a conversation about value, not a reason to cave (see 
    pricing
    ).
  • Talk less. If you are talking more than the customer in discovery, you are pitching, not selling.
  • 亲自完成大约前10到20个付费客户的销售，或者直到你能写下有效的流程并重复它。只有这时招聘销售才有意义。
  • 多方沟通：只和支持者对接的交易很脆弱。如果你还没和掌握预算的人谈过，那你没有交易，只有一个粉丝。
  • 没有下一步，就不算交易：永远不要在没有明确行动和日期的情况下结束销售沟通。
  • 不要因恐惧而打折：对价格的异议是关于价值的对话，不是让步的理由（参考 
    pricing
    ）。
  • 少说多听：如果在挖掘需求时你说的比客户多，那你是在推销，不是在销售。

Mistakes that look reasonable

看似合理的错误做法

  • Hiring a salesperson too early. You cannot delegate a motion you have not figured out. The first deals teach you what you are selling.
  • Pitching instead of asking. Founders lead with the product. The best sellers lead with questions and let the customer talk themselves into it.
  • Selling to the champion and stopping there. They love it and cannot sign. You have to reach the buyer.
  • Feature-touring the demo. Showing everything shows nothing. Show their problem solved.
  • Treating "think about it" as a yes. It is an undiagnosed no. Surface the real blocker before you leave.
  • Confusing usage with revenue. Ten thousand free users and zero conversations with a buyer is not traction, it is a popular free tier.
  • Apologizing for charging. If it delivers value, the price is fair. A founder who flinches on price trains the buyer to flinch back.
  • 过早招聘销售人员：你无法委托一个自己还没搞通的流程。前几笔交易能让你明白自己到底在卖什么。
  • 推销而非提问：创始人往往先讲产品。最优秀的销售会先提问，让客户自己说服自己。
  • 只卖给支持者就停止：他们喜爱产品但没有签字权。你必须接触到付费决策者。
  • 演示时只做功能展示：展示所有功能等于什么都没展示。要展示他们的问题如何被解决。
  • 把“我再想想”当成同意：这是未被诊断的拒绝。结束沟通前要找出真正的障碍。
  • 把用户量等同于收入：一万个免费用户，却没有和任何付费决策者沟通，这不叫增长，只是受欢迎的免费版。
  • 为收费道歉：如果产品能带来价值，价格就是合理的。在价格上退缩的创始人，会让客户也学会退缩。

Your next 30 minutes

接下来30分钟你可以做这些

  • Open your usage data. List the 5 most engaged accounts (most seats, most usage, most issues filed). Those are your first sales calls.
  • For your best one, fill in the four: champion, buyer, pain-with-a-cost, trigger. Note which is missing.
  • Write one short, human outreach message to that champion about a specific thing you noticed. No template.
  • Draft five discovery questions you will ask before you show anything.
  • Decide the one business outcome the buyer would pay for, and say it in a single sentence.
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个参与度最高的账户（使用席位最多、使用频率最高、提交问题最多）。这些就是你第一批要沟通的对象。
  • 针对最优质的那个账户，填写四个要素：支持者、付费决策者、有成本的痛点、行动触发点。标注缺失的要素。
  • 给那个支持者写一条简短、人性化的消息，内容要针对你观察到的具体情况。不要用模板。
  • 草拟5个挖掘需求的问题，在展示产品前先提问。
  • 确定付费决策者愿意为之付费的一个业务成果，并用一句话表述。
基于真实的开发者工具GTM经验构建，参考了Adam Frankl（《面向开发者的初创企业》）和Jakub Czakon（markepear.dev）的框架。 当框架无法做出决策时，就需要人的参与：The DevTool GTM Company。