ホーム / Skills / ブランド・マーケティング / プロダクト主導の成長(Product-Led Growth)
ブランド・マーケティング

プロダクト主導の成長(Product-Led Growth)

Smit PatelMITSkill の言語: 英語
ライセンス確認済みスクリプトなし低リスク
デモ実行記録 · claude-sonnet-5-5 · 2026年10月
We sell a developer API with a free tier. Self-serve signups are growing but revenue is flat, and our biggest accounts come from sales calls. Using the gtm-product-led-growth skill, tell me whether to go product-led or sales-led, and how to review the economics of our three channels: SEO blog, paid search and community events.
Skill: gtm-product-led-growth

Recommendation: go hybrid, with PLG as the top of the funnel and sales-assist on top of it. Don't choose one motion over the other.

Your data already points this way. Signups are growing while revenue is flat, so self-serve is producing volume but not dollars. Your biggest accounts come from sales calls, so the buyers who matter aren't converting through the product alone. This matches the skill's PLG-vs-sales finding: self-serve brings volume at low ACV (~$5K), and sales-led brings high ACV (~$50K). In the skill's parallel test, sales won about 10x on revenue despite about 10x less volume. That test isn't your data, so treat it as a hypothesis for you to check.

Run the decision tree on your product

  1. Can a user get value in under 10 minutes without docs? For an API this is often yes, so measure time to first API call.
  2. Can they self-serve implementation? Small projects usually can. Production integrations at larger companies usually can't.
  3. Is the buyer the user? Your developers are the users. The budget owner at a large account usually isn't a developer.

If the answers are yes, yes, no, the tree gives hybrid. Check each answer against your own activation data.

What to do

  • Keep the free tier and self-serve checkout for accounts under about $10K.
  • Add sales-assist for $10K–$50K accounts. Trigger it on product-qualified signals:
    • several users from one company
    • usage near the free-tier limits
    • questions about SSO, SLAs, security or team pricing
  • Make outreach specific. For example: "Your team is calling endpoint X from 12 services. Want 15 minutes on rate limits?" Don't send "I saw you signed up."
  • Leave sub-$5K accounts alone. Early sales contact on small deals hurts the self-serve motion.
  • Look at your closed-won accounts first. Did they start as free signups and then get a call, or did they come in through sales without ever using the product? If most started in the free tier, the PQL triggers will work. If not, the free tier is mostly serving hobbyists.
  • Run a 4–6 week test. Compare PQL-triggered outreach against a no-contact control group on conversion and ACV.
  • Fix activation. If time to first value is over 10 minutes, shorten it with sample data, a working quickstart and less setup before the first call.

Reviewing channel economics (SEO blog, paid search, community events)

Report every metric by channel and by acquisition source, not as a blended number. The weakness in most reviews is that they stop at signups.

Metric Why it matters
CAC (spend ÷ new users) Include content production and staff time for SEO and events, not just ad spend.
Signup → activated (first successful API call) Shows whether a channel brings real developers or just clicks.
Signup → paid, and → $10K+ Your revenue comes from large accounts, so measure this too.
30- and 90-day retention Cheap users who churn cost more than expensive users who stay.
LTV and payback period Use revenue, and revenue by account size, not signup counts.

Then apply the rule:

  • CAC below LTV × margin: scale. Check 90-day retention first. If it's above 60%, put about 3x the budget there. If it's below, fix activation first.
  • CAC about equal to LTV × margin: optimize, but don't scale.
  • CAC above LTV × margin: give it 4 weeks to improve, then kill it.

Build a growth equation for each channel before you scale it. Examples are 1 post → N visits → X% signup, $1K → clicks → signups, and 1 event → attendees → users. Validate with 4 weeks of data, then scale on that basis.

Channel-specific notes (my expectations, to be checked against your numbers)

  • SEO blog: often the cheapest per user and the best retained. Segment by post type, because tutorials and integration guides probably bring developers who build, while top-of-funnel posts bring browsers.
  • Paid search: probably the highest CAC and the lowest retention of the three, but test that. Look at which keywords bring activated accounts, and cut the ones that only bring signups.
  • Community events: small volume, but attendees may be the most likely to become sales-assisted accounts. Track attendee → account → pipeline through CRM, not signups alone. Events are the channel most likely to look bad on a self-serve-only view and good on a pipeline view.
  • Sales-sourced accounts: put your sales calls in the same table as a fourth channel, with fully loaded CAC. That's how you compare them fairly with the other three.

Cadence

  • Review monthly. Reallocate quarterly. Test two new channels a month.
  • Forecast baseline, upside and downside, and update the forecast monthly.
  • Write a one-page playbook for each channel that works.

What I need from you to turn this into numbers

  • spend and new users by channel
  • activation, paid conversion and retention by source
  • ACV and LTV by source
  • the origin story of your top 20 accounts

I haven't seen any of your data, so everything above about your channels is a framework or a hypothesis, not a finding. If you share even a rough export, I can build the channel table.

Real run in an isolated folder with only this skill installed. Only the Skill and Read tools were enabled, so nothing was fetched from the web and no file was written. The example is fictional. The model answered from SKILL.md alone and said it had no real channel data.

できること

セルフサーブ型の成長を「常にうまくいく」と決めつけず、きちんと検討する手助けをします。PLG の現実チェック(作者が 6 か月間並行して試し、売上では営業主導が勝った例)、チャネルごとに投入量と成果を結びつける成長方程式、チャネルの採算(CAC、転換率、継続率、LTV、回収期間)、初回価値までの時間、セルフサーブが限界を迎えて営業支援が必要になる地点、3 つのシナリオによる成長予測、1 ページのプレイブックを残す習慣を扱います。

動き方

  1. モデルが、価値が数分で伝わるか、導入が簡単か、買い手と利用者が同じかを確認します。
  2. チャネルごとに成長方程式と「維持・拡大・停止」のルールを作ります。
  3. 利用の深さ、チーム内の広がり、購買シグナルをもとに営業支援のきっかけを提案します。

向いている場面

開発者ツールや B2B SaaS が PLG と営業のどちらにするか決める、フリーミアムの転換を改善する、チャネルの優先順位をつける。

補足とリスク

指示のみのパッケージです。スクリプトはなく、ネットワーク接続、ファイルの書き込み、アカウントは不要です。5K から 50K ドルの転換点や 4 週間で停止するルールなどの数字は作者の経験に基づくもので、ベンチマークではありません。この Skill はお使いの分析データを見られないため、数字はご提供いただいた内容次第です。出力は予測ではなく、検証すべき計画として扱ってください。