expansion-signals
Identify upsell and cross-sell opportunities through usage patterns, growth signals, and account behavior analysis
What this skill does
# Expansion Signals > Detect opportunities for account expansion by analyzing usage patterns, growth indicators, and behavioral signals that predict readiness to buy more. ## When to Use This Skill - Monthly expansion pipeline review - Identifying upsell candidates - Prioritizing CSM expansion efforts - Building expansion playbooks - Forecasting expansion revenue ## Methodology Foundation Based on **Lincoln Murphy's Expansion Revenue Framework** and **Gainsight Expansion Playbooks**, focusing on: - Usage ceiling signals - Growth triggers - Buying intent indicators - Timing optimization ## What Claude Does vs What You Decide | Claude Does | You Decide | |-------------|------------| | Identifies expansion signals | Which opportunities to pursue | | Scores expansion readiness | Pricing and packaging | | Suggests conversation openers | Relationship approach | | Prioritizes opportunities | Resource allocation | | Calculates potential value | Discount/incentive offers | ## What This Skill Does 1. **Signal detection** - Identify expansion indicators 2. **Opportunity scoring** - Rank expansion readiness 3. **Sizing estimation** - Potential expansion value 4. **Timing recommendation** - When to engage 5. **Conversation guidance** - How to approach ## How to Use ``` Analyze expansion signals for: Account: [Company Name] Current Contract: $[ARR] Products: [What they have] Contract End: [Date] Usage Data: - Seats: [Used] / [Licensed] - Feature usage: [Which features, how much] - Usage trend: [Growing/Flat/Declining] - Power users: [How many, what they do] Account Context: - Company growth: [Hiring, funding, news] - Stakeholder changes: [New decision makers] - Requests: [Feature requests, complaints about limits] Available Expansion: - Additional seats: $[Price] - New modules: [List with prices] - Higher tier: $[Price difference] ``` ## Instructions ### Step 1: Identify Expansion Signal Categories **Usage Ceiling Signals (Strong):** | Signal | What It Means | |--------|---------------| | >90% seat utilization | Need more licenses | | Hitting API limits | Need higher tier | | Feature requests beyond plan | Ready for upgrade | | Workarounds for limitations | Pain = opportunity | | Power users maxing features | Champions for expansion | **Growth Triggers (Strong):** | Signal | What It Means | |--------|---------------| | Company hiring | More seats needed | | New office/location | Geographic expansion | | Funding announcement | Budget available | | New initiative/project | New use case | | M&A activity | Integration opportunity | **Behavioral Signals (Medium):** | Signal | What It Means | |--------|---------------| | Admin exploring pricing | Active evaluation | | Repeated feature inquiries | Interest in upgrade | | Reference/case study request | Happy, expandable | | Executive engagement increase | Strategic priority | | QBR agenda on "next steps" | Open to discussion | **Timing Signals:** | Signal | Best Timing | |--------|-------------| | Budget cycle approaching | 30-60 days before | | Contract renewal | 90 days before | | Just hit milestone | Immediately after | | Competitor mentioned | Defensively, now | ### Step 2: Score Expansion Readiness **Expansion Score (0-100):** | Factor | Weight | Scoring | |--------|--------|---------| | Usage ceiling | 25 | >90% = 25, 80-90% = 15, <80% = 5 | | Growth triggers | 20 | Strong = 20, Some = 10, None = 0 | | Feature requests | 15 | Multiple = 15, Some = 8, None = 0 | | Relationship health | 20 | Healthy = 20, OK = 10, At-risk = 0 | | Timing fit | 20 | Perfect = 20, Good = 12, Poor = 5 | **Readiness Bands:** | Score | Status | Action | |-------|--------|--------| | 75-100 | π₯ Hot | Engage this week | | 50-74 | π’ Warm | Engage this month | | 25-49 | π‘ Nurture | Build toward expansion | | 0-24 | βΈοΈ Wait | Focus on adoption/health | ### Step 3: Size the Opportunity **Expansion Sizing:** ``` Potential Value = (Additional Seats Γ Seat Price) + (Module Upgrade Value) + (Tier Upgrade Delta) Example: - 20 additional seats Γ $100/month = $24K ARR - Premium module = $12K ARR - Potential: $36K ARR (20% of base) ``` ### Step 4: Plan the Approach **Conversation Starters by Signal:** | Signal | Opening | |--------|---------| | Seat ceiling | "I noticed you're at 95% capacity. Your team must be growing!" | | Feature requests | "You've asked about X a few times. Let me show you how our [upgrade] handles that." | | Company growth | "Congrats on the Series B! How is that affecting your team structure?" | | Power users | "Sarah has become a real power user. Have you considered our advanced features?" | ## Examples ### Example 1: Expansion Analysis **Input:** ``` Analyze expansion for DataFlow Inc: Current: $48K ARR (50 seats @ $80/seat/month) Products: Core Platform only Renewal: 8 months away Usage: - Seats: 48/50 (96%) - Core features: 85% adoption - API calls: 92% of limit - Power users: 12 (doing advanced workflows) Context: - Just raised Series A ($15M) - Hiring 20 engineers this quarter - VP Data asked about analytics module 3 times - NPS: 9 Available: - Additional seats: $80/seat/month - Analytics module: $15K ARR - API tier upgrade: $6K ARR - Enterprise tier: +$20K ARR (includes above) ``` **Output:** ``` ## Expansion Analysis: DataFlow Inc ### π₯ Expansion Score: 88/100 - HOT **This account is primed for expansion.** --- ### Signal Analysis | Signal | Strength | Points | |--------|----------|--------| | 96% seat utilization | π₯ Strong | 25/25 | | Series A + hiring 20 | π₯ Strong | 20/20 | | Analytics requests (3x) | π₯ Strong | 15/15 | | NPS 9 + healthy | π₯ Strong | 18/20 | | 8 months to renewal | π‘ Medium | 10/20 | | **Total** | | **88/100** | --- ### Opportunity Sizing **Conservative Estimate:** ``` 20 new seats Γ $80 Γ 12 = $19,200 ARR Analytics module = $15,000 ARR βββββββββββββββββββββββββββββββββ Conservative Total: $34,200 ARR (71% expansion) ``` **Aggressive Estimate (Enterprise Tier):** ``` 20 new seats Γ $80 Γ 12 = $19,200 ARR Enterprise upgrade = $20,000 ARR (Includes analytics + API) Additional seats at enterprise = $24,000 ARR βββββββββββββββββββββββββββββββββ Aggressive Total: $63,200 ARR (132% expansion) ``` **Recommended Target: $40-50K expansion** --- ### Why Now? 1. **Capacity Ceiling** - 96% seat usage, hiring 20 more - They will literally run out of seats in weeks 2. **Feature Demand** - VP Data asked 3x about analytics - Not if, but when they'll need it 3. **Budget Available** - Series A just closed - Flush with cash, growth mindset 4. **Relationship Strong** - NPS 9 - Trust is high, easy conversation 5. **Power Users as Champions** - 12 heavy users - Internal advocates for expansion --- ### Recommended Approach **Timing: This week** Don't wait. Seat ceiling + hiring = urgent need. **Who to Engage:** 1. VP Data (analytics interest) - Decision Maker 2. Champion (current) - Internal advocate 3. Head of Engineering (new hires) - User expansion **Conversation Strategy:** **Opening:** "Congrats on the Series A! I saw you're hiring 20 engineersβexciting growth. I also noticed you're at 96% seat capacity, and [VP Data] has been asking about our analytics module. I'd love to get ahead of your growth and make sure you're set up for scale." **Value Framing:** "Given your expansion, I want to show you our Enterprise tier. It includes the analytics module you've been interested in, unlimited API calls, and room to grow. Many companies at your stage find it's more cost-effective than Γ la carte." **Offer:** - Enterprise tier upgrade: +$20K ARR - 30 additional seats at enterprise rate: $28.8K ARR - **Total: $48.8K expansion** (102% growth) - Incentive: Lock multi-year, 10% discount --- ### Next Steps | Action | Owner | Timeline | |--------|-------|----------| | Email VP Data re: analytics | CSM | Tomorrow | | Prep enterprise comparison | CSM | This week | | Discovery call: growth plans | CSM | Within 5 days | | Pricing approval fo
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product β visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".