git:20261002.46ac0a1 to git:20261002.d5668a9

25 added, 80 removed. Audit A to A.

---

name: poyar-growth-unhinged

- description: "Build evidence-based B2B software GTM and monetization playbooks using Kyle Poyar's public Growth Unhinged approach. Use for PLG and sales integration, pricing, packaging, expansion, and growth metric diagnosis."

+ description: "Build evidence-based B2B software growth and monetization playbooks using Kyle Poyar's public approach. Use to diagnose growth bottlenecks, connect PLG with sales, redesign pricing and packaging, or plan account expansion."

---

# Growth Unhinged GTM and Monetization Playbooks

Based on Kyle Poyar's public method. Not affiliated with or endorsed by Kyle Poyar.

## When to use

- Use this skill to diagnose a B2B software growth bottleneck, redesign pricing and packaging, layer sales onto product-led growth, or create an expansion plan. Its central lens is the customer's progression from discovering value to adopting more broadly, with monetization supporting adoption. [S1]

- This is an operational synthesis of public writing and interviews, including practitioner cases Poyar published. It is not a framework he published under this exact name. Subscription articles are represented only by their publicly visible excerpts. Treat historical examples as mechanisms to examine, not current market benchmarks or promised results. [S2]

- ## Procedure

- ### 1. Locate the bottleneck in the user journey

- Collect target customers, offers, activation events, usage, conversion cohorts, and expansion history. Map discovery, starting use, activation, conversion, and scaling. Record behavior, friction, and the next decision. Distinguish value realization from registration. Mark missing evidence and provisional diagnoses. [S1]

- Choose the stage limiting revenue. Acquisition needs relevant discovery; activation needs faster value realization; expansion needs deeper usage or broader adoption. Do not prescribe sales activity for every bottleneck. Include product work because it can drive acquisition, conversion, and expansion. [S1]

- ### 2. Narrow GTM to accounts worth winning

- Build an ideal customer profile from accounts where the product works well, the company can win, and customers can renew and expand. Compare candidate segments on win rate, deal size, sales cycle, retention, and expansion. Favor demonstrated fit over impressive logos or the largest addressable audience. Keep unsupported segment advantages as hypotheses. [S6]

- Create an account-level view connecting contacts, product activity, buying progress, and revenue. Ask how many best-fit accounts exist, where they stand in their journey, and which interventions move them forward. Reject MQL volume and attribution credit as sufficient proof of GTM effectiveness; they can reward low-fit activity and obscure whether target accounts are progressing. [S6]

- ### 3. Make the individual-to-team transition explicit

- Inspect whether the entry experience helps an individual discover value and colleagues join. Define the behavior that changes individual utility into team utility, such as collaborating on real work. Examine whether the current pricing discourages that transition or monetizes isolated power users neglecting business adoption. [S2]

- Propose a clear path from individual entry to team adoption and organization-wide requirements. Keep user value accessible; consider administration, security, billing, and support for monetization. Where appropriate, allow every plan to support multiple users. Do not treat low entry price as a substitute for an attractive team growth path. [S2]

- ### 4. Select a chargeable metric before debating price points

- List plausible units such as active users, transactions, contacts, or consumption. Compare how each tracks customer value, permits a small initial purchase, and expands as customers succeed. Reject seats as an automatic default when a small team can generate enormous usage or value. Choose a metric for the product's economics rather than copying a familiar competitor. [S8]

- Run illustrative bills for a new customer, an expanding customer, and a mature customer. Explain what causes spending to rise and what value accompanies it. Look for multiple expansion paths through increased usage and richer packages. Flag a model that lands customers easily but cannot grow revenue with their success. These bill scenarios operationalize Poyar's landing and expansion tests. [S8]

- ### 5. Give packaging a coherent expansion path

- Start with a good, better, best structure when no stronger reason suggests another architecture. Explain each tier's customer and graduation trigger. Reject a single inflexible bundle when it removes the upsell path; reject excessive customization when it creates decision paralysis and procurement line items. Treat the tier count as provisional. [S3]

- Evaluate an add-on when a capability is valuable to a minority, belongs to another buyer or budget, replaces another vendor, becomes relevant later, or carries substantial delivery cost. Otherwise consider including it in a tier. More than two initial add-ons is a warning. Specify adoption timing and buyer. [S3]

- ### 6. Add sales at a useful moment in adoption

- For each proposed sales touchpoint, specify the customer's problem, product signal, assistance offered, and expected incremental outcome. Preserve a credible self-service path. Test whether assistance improves conversion or expansion beyond what would happen without it, rather than counting every assisted purchase as a sales-created win. Define a suitable comparison group when the task's data allows it. [S4]

- Avoid calling every free signup, hiding prices to force conversations, or weakening free and self-service offers to protect enterprise deals. Avoid pressing for a company-wide purchase before users have value and internal support. These moves shrink future pipeline. Match the ask to readiness. [S4]

- ### 7. Connect product champions to economic buyers

- Define activation from the product's actual value mechanism. In Poyar's Figma interview, collaboration during the first week is the activation event; that timing is a case example, not a universal threshold. Use active accounts with the right profile to prioritize outreach, then connect each product signal to relevant assistance and messaging. [S5]

- Separate a product-qualified user from a product-qualified account. Aggregate adoption across the account and identify the buyer who controls broader deployment. Equip the champion with a buyer-facing value proposition and target decision makers with material about organizational value. Do not assume the person using the product controls the budget; combine bottom-up adoption with top-down engagement. [S5]

- ### 8. Resolve flexibility and predictability together

- For usage pricing, investigate enterprise bill uncertainty. Consider annual commitments, volume discounts, annual allowances, and explicit overages. Explain customer control and vendor commitment economics. Contracting can resolve procurement objections while preserving usage-linked expansion. [S7]

- Check seasonality and adoption pace. State consequences of underuse and overuse. Avoid requiring large upfront commitments when customers cannot estimate volume. Connect entry and mature-account offers. [S7]

- ### 9. Gather pricing evidence before a broad change

+ Use this skill when a B2B software team needs a decision about growth, pricing, packaging, product-led sales, or expansion. Produce a practical decision memo that connects customer value, account progression, payment, and business economics. Begin with the customer journey rather than choosing a sales tactic or pricing model in advance. Product can drive acquisition, conversion, and expansion. [S1]

- Start with independent win-loss research. Ask what drove decisions, how alternatives compared, and whether price conveyed value or cheapness. Frequent price-driven wins can indicate wrong customers. Assign an evidence owner. [S7]

+ This package synthesizes public writing and interviews, including practitioner cases published by Poyar. He did not publish this exact combined framework. Only public previews of subscription articles informed the method. Historical company examples illustrate mechanisms, not current benchmarks. Distinguish direct advice, interviewee practices, and this package's operational suggestions using [references/method.md](references/method.md) and [references/sources.md](references/sources.md).

- Use package-choice research or a limited sales pilot to examine a proposed change. Do not treat arbitrary website price variation as the default experiment. Recruit willing, value-oriented reps for unpublished pricing pilots and acknowledge selection bias. Specify the cohort, duration, deal outcomes, and learning needed before rollout; a pilot builds evidence, not certainty. [S7]

+ For a narrow request, complete the relevant analysis and mark other memo fields as outside scope. Do not expand a pricing-page review into an unsolicited company-wide redesign. When evidence is thin, deliver a provisional diagnosis and the next learning action. Recommend live experiments or changes within the user's scope; the skill itself does not authorize publishing prices or contacting customers.

- ### 10. Judge the economics and deliver a decision

+ ## Procedure

- For usage models, connect finance to granular account usage, adoption forecasts, metering, and billing. Evaluate acquisition payback with recognized revenue and the costs of acquiring and serving customers, including infrastructure and implementation. Annual cash collected upfront does not by itself mean acquisition costs have economically paid back. [S9]

+ 1. **Frame the decision and evidence.** Read the evidence boundaries in [references/method.md](references/method.md#evidence-and-attribution). Capture the product, target customer, existing motion, requested decision, constraints, and available data. Separate observed facts, customer statements, calculated results, and assumptions. Start the decision memo in [templates/output-template.md](templates/output-template.md).

- Interpret net dollar retention alongside acquisition payback and customer type. A motion with quick payback can tolerate different retention economics from one requiring a long recovery period. Separate margin profiles where services or other revenue streams differ from software. Do not import a celebrated company's retention number as a target without matching the business model. [S9]

+ 2. **Locate the limiting journey stage.** Follow [references/method.md](references/method.md#1-diagnose-the-customer-journey). Map discover, start, activate, convert, and scale with cohort denominators and time windows. Identify where customers fail to realize or extend value. Choose one primary bottleneck and explain competing explanations rather than treating every low conversion rate as a sales problem. [S1]

- The finished output must contain a journey diagnosis, the limiting stage, evidence gaps, and the intervention advancing value and payment. [S1]

+ 3. **Select accounts worth winning.** Use [references/method.md](references/method.md#2-focus-on-best-fit-accounts) to compare segments on product fit, win probability, deal size, sales cycle, retention, and expansion. Connect contacts, usage, buying progress, and revenue at account level. Measure progression among best-fit accounts; lead counts and attribution credit are insufficient evidence of effectiveness. [S6]

- It must also contain a best-fit account definition, account progress measures, and the reason those measures reveal more than lead counts. [S6]

+ 4. **Define the adoption bridge.** Apply [references/method.md](references/method.md#3-move-from-individual-value-to-team-value). State the meaningful activation behavior and how an individual becomes a team champion. Check whether collaboration, invitations, or billing gates block wider adoption. Treat Figma's first-week collaboration example as a case, not a universal threshold. [S2] [S5]

- Include the proposed chargeable metric, illustrative bills, landing offer, expansion triggers, and a check for the five recurring pricing failures: undercharging, a poor metric, difficult entry, missing expansion, and static pricing. [S8]

+ 5. **Choose the chargeable metric.** Use [references/method.md](references/method.md#4-select-the-pricing-unit). Compare plausible units against customer value, easy entry, expansion, predictability, and measurement feasibility. Calculate illustrative new, expanding, and mature customer bills. Keep seats when they fit; do not select consumption merely because usage pricing is fashionable. [S7] [S8]

- Include the package and add-on rationale, sales trigger and buyer path, a bounded validation plan with an owner, and the economics that determine whether to proceed. Label proposed thresholds as task-specific choices and unresolved assumptions as unresolved. [S3] [S4] [S7] [S9]

+ 6. **Design packages and graduation triggers.** Follow [references/method.md](references/method.md#5-build-packages-with-jobs). Start with good, better, best unless context supports another structure. Give each package a customer, buying reason, and expansion trigger. Test candidate add-ons against separate demand, buyer, timing, alternatives, and delivery cost. [S3]

- ## Worked example

+ 7. **Place sales where it helps.** Apply [references/method.md](references/method.md#6-make-sales-incremental-and-reach-the-buyer). Specify the account signal, customer problem, assistance, champion, economic buyer, and intended incremental result. Preserve useful self-service. Plan a comparison that distinguishes sales contribution from purchases that would happen anyway. [S4] [S5]

- Illustration only. RelayBoard is an invented workflow product. Its hypothetical data shows many individual signups but weak team adoption. The agent identifies the individual-to-team transition as the first constraint and proposes measuring shared workflows used by colleagues, rather than completed onboarding screens. That event is an illustrative hypothesis to validate, not a Poyar benchmark. [S1] [S2]

+ 8. **Resolve purchasing and billing friction.** Use [references/method.md](references/method.md#7-balance-flexibility-and-predictability). Explain the landing offer and pricing page in customer language. For consumption models, state allowances, commitments, overages, underuse, seasonality, and spend controls. Match predictability to customer needs without forcing an oversized initial purchase. [S7] [S8] [S9]

- The proposed packages are entry, team, and organization tiers. A specialist audit export becomes a candidate add-on because a separate compliance buyer needs it later. Sales assistance starts after useful team adoption in best-fit accounts, with help mapping deployment needs and identifying the budget holder. Signup alone does not trigger a pitch. [S3] [S4] [S5]

+ 9. **Build a bounded learning plan.** Follow [references/method.md](references/method.md#8-research-and-pilot-before-rollout). Begin with independent win-loss evidence, then choose package research, usability testing, or a limited pricing pilot. Record owner, cohort, duration, comparison, success criteria, stop criteria, and bias. Proposed thresholds are local decisions, not expert benchmarks. [S7] [S8]

- The first deliverable is a decision memo with the journey bottleneck, competing pricing-unit hypotheses, package rationale, and a limited pilot. It measures target-account progress, incremental assisted conversion, expansion, and margin-adjusted payback. No rollout is declared successful merely because more leads were scored or annual cash arrived. [S6] [S9]

+ 10. **Check economics and incentives.** Apply [references/method.md](references/method.md#9-evaluate-economics-and-incentives). Link usage forecasts, retention, recognized revenue, acquisition costs, and service costs. Distinguish cash collection from economic payback. Check whether seller incentives reward customer success or simply discounted commitments. [S9]

- ## Sources

+ 11. **Review and deliver the decision.** Complete [checklists/review-checklist.md](checklists/review-checklist.md), using [examples/worked-examples.md](examples/worked-examples.md) to calibrate specificity. Revise failed checks, label unresolved evidence, and deliver the memo with the recommended next action. Revisit pricing as the product and customers evolve; one successful pilot does not establish a permanent optimum. [S8]

- All URLs below were fetched with curl. For Growth Unhinged subscription posts, only visible public excerpts informed this skill.

+ ## Files in this skill

- 1. [S1] Your guide to SaaS metrics 2.0. https://kylepoyar.substack.com/p/your-guide-to-saas-metrics-20

- 2. [S2] Your guide to PLG pricing 201. https://kylepoyar.substack.com/p/your-guide-to-plg-pricing-201

- 3. [S3] Your guide to SaaS packaging 201. https://kylepoyar.substack.com/p/your-guide-to-saas-packaging-201

- 4. [S4] PLG and sales in 2023. https://kylepoyar.substack.com/p/plg-and-sales-in-2023

- 5. [S5] Your guide to product-led sales. Interview with Jesus Requena. https://kylepoyar.substack.com/p/your-guide-to-product-led-sales

- 6. [S6] Your guide to GTM metrics 2.0. https://kylepoyar.substack.com/p/your-guide-to-gtm-metrics-20

- 7. [S7] Usage-Based Pricing with Kyle Poyar of OpenView. RevOps interview. https://www.revops.io/blog/usage-based-pricing-with-kyle-poyar-of-openview

- 8. [S8] 5 Pricing Strategy Mistakes Costing SaaS Companies Growth. SaaS Club podcast and transcript. https://saasclub.io/podcast/saas-pricing-strategy-mistakes-kyle-poyar/

- 9. [S9] What does usage-based pricing mean for your B2B SaaS finance team? A conversation with Kyle Poyar. Subscript interview and transcript. https://www.subscript.com/the-dive/what-does-usage-based-pricing-mean-for-your-b2b-saas-finance-team-a-conversation-with-kyle-poyar

+ - [SKILL.md](SKILL.md): Entry point, use cases, evidence boundaries, and the agent's main loop.

+ - [references/method.md](references/method.md): Detailed principles, decision rules, warnings, and edge cases.

+ - [references/sources.md](references/sources.md): Nine fetched public sources and their contributions.

+ - [examples/worked-examples.md](examples/worked-examples.md): Two invented before-and-after decision memos with rule notes.

+ - [templates/output-template.md](templates/output-template.md): Fill-in decision memo with field-by-field guidance.

+ - [checklists/review-checklist.md](checklists/review-checklist.md): Pass/fail review criteria and common failure repairs.