Create a new ARR expansion play: signals, proofs, and CTAs.
- User
Create a new ARR expansion play: signals, proofs, and CTAs.
Assistant
The user wants a "new ARR expansion play" involving "signals, proofs, and CTAs."
-
Deconstruct the Request:
- Context: B2B SaaS sales/customer success. "ARR" stands for Annual Recurring Revenue. "Expansion" means increasing revenue from existing customers (upsell, cross-sell).
- Framework: The user specifically asks for a structure based on "Signals, Proofs, and CTAs."
- Signals: Indicators that a customer is ready for an upgrade or expansion.
- Proofs: Evidence or value propositions that justify the expansion.
- CTAs (Call to Actions): The specific next steps or tactics to close the expansion.
- Goal: Create a new play. This implies it shouldn't just be "ask them to buy more seats." It needs a specific angle or trigger.
-
Brainstorming "New" Angles:
- Traditional: Usage limits reached (hard upsell), new feature release (product-led), contract renewal (timing-led).
- Modern/Strategic: "Value Realization," "Workflow Maturity," "Strategic Alignment."
- Trend: AI/Automation is huge. A play centered on "Efficiency/Automation" is timely.
- Trend: Consolidation. Companies want fewer tools. A "Platform Consolidation" play is strong.
Let's go with a "Workflow Maturity & Automation" play. This targets customers who have successfully adopted the core product but are hitting a "complexity ceiling" where they need advanced automation or integrations to scale. This is a high-value expansion area (often moving from Pro to Enterprise tiers).
-
Developing the Play Structure (Signals, Proofs, CTAs):
-
Play Name: "The Efficiency Scaling Play" (or something similar). Let's call it: The "Workflow Accelerator" Play.
-
Phase 1: Signals (The Trigger)
- What indicates readiness?
- Usage data: High frequency of manual tasks.
- Usage data: Usage of API/Zapier integrations (shows they are hacking together advanced workflows).
- Sentiment: CS feedback mentioning "saves time but getting harder to manage."
- Org changes: New VP hired who wants efficiency.
- Refining Signals: Let's look for "Feature Saturation" of the lower tier. Specifically, they are exporting data to CSV to manipulate it elsewhere (a classic sign they need a higher tier).
-
Phase 2: Proofs (The Argument)
- How do we prove value?
- Calculate the "Tax of Manual Work." (Time spent exporting/manipulating).
- Show benchmarks: "Customers like you who moved to [Tier X] saved Y hours."
- Case Study: A specific story of a similar company.
- ROI Calculator: Dynamic content.
-
Phase 3: CTAs (The Action)
- What do we ask?
- Not "Buy now."
- "Let's do a Workflow Audit."
- "Enable the Sandbox environment."
- "Grant access to the Integration Specialist."
-
-
Drafting the Content (Iterative refinement):
-
Title: The "Shadow Operations" Consolidation Play. (This sounds sexier. It implies they are doing work outside the tool that should be inside).
-
Concept: Identify customers using "workarounds" (spreadsheets, separate BI tools, manual notifications) and sell them the module that automates that.
-
Signals:
- The "Data Leak" Signal: High volume of CSV exports.
- The "Integration Friction" Signal: Active usage of middleware (Zapier/Make) to bridge gaps the product should handle natively.
- The "Seat Stagnation" Signal: User count is steady, but data volume is spiking (efficiency bottleneck).
-
Proofs:
- The "Shadow IT" Audit: Show them a report of where their data goes after it leaves the platform. "You spend 4 hours/week cleaning this data."
- The "Scenario Modeling" Demo: Show before/after. "Here is your current manual workflow vs. our automated engine."
- The Peer Benchmark: "Companies at your usage level typically upgrade to reduce error rates by 15%."
-
CTAs:
- The "Time-Back" Workshop: Offer a free consultation to automate one specific painful workflow.
- The "Sandbox" Trial: Give them a 14-day unrestricted trial of the automation module specifically populated with their data (if possible/legal) or a template.
- The "Executive Alignment" Meeting: Bring in an AE to talk to their VP of Ops about risk reduction.
-
-
Review against constraints:
- Is it actionable? Yes.
- Does it have Signals, Proofs, CTAs? Yes.
- Is it "New"? It focuses on consolidation and automation rather than just seat count, which is a mature expansion strategy.
-
Formatting: Use a clean, strategic layout. Use bolding and lists for readability. Add a "Why this works" section to explain the psychology.
-
Final Polish: Ensure the tone is professional, strategic, and B2B savvy. (Self-correction: Make sure the "Signals" are data points a RevOps team could actually find).
- Refining the "Shadow IT" proof: A "Data Export Report" is a strong asset.
- Refining the CTA: "Workflow Audit" is a low-friction entry point.
-
Output Generation: (Proceed to generate the response based on the above thought process). Here is a new ARR expansion play designed for B2B SaaS companies, specifically targeting the "Efficiency & Consolidation" angle.
The Play: "The Shadow Workflow Consolidation"
Objective: Move customers from "Active Usage" to "Platform Dependency" by identifying and absorbing fragmented workflows currently being managed in spreadsheets or competitor point solutions.
1. The Signals (The Trigger)
Identify the "hidden" pain. You aren’t looking for usage of your core feature; you are looking for the friction around it.
- The "Data Exfiltration" Signal:
- Trigger: A user (or a cluster of users) performs a high volume of CSV Exports or utilizes the "Send to Spreadsheet" integration (e.g., Zapier pushes to Google Sheets) immediately after completing a core task in your platform.
- Meaning: They are using your tool for data collection but performing high-value processing (reporting, forecasting, planning) elsewhere. This is "Shadow Workflow."
- The "API Endpoint Burst" Signal:
- Trigger: API calls spike, but user logins remain flat.
- Meaning: They are likely piping your data into an internal dashboard (Tableau/PowerBI) or a competitor's tool because they don't believe your native reporting is sufficient for leadership.
- The "Seasonal Ad-Hoc" Signal:
- Trigger: A sudden uptick in account creation for users with "Contractor," "Intern," or "Temp" email domains.
- Meaning: They are scaling a manual process (likely compliance or data entry) that should be automated by a premium feature (e.g., SSO, Role-Based Access, Automated Workflows).
2. The Proofs (The Evidence)
Don't tell them they have a problem; show them the receipt.
- The "Data Gravity" Audit:
- Generate a dynamic report showing the customer exactly where their data goes after it leaves your system.
- Proof Asset: An automated email stating: "In the last 30 days, [Company Name] exported 400 reports to Excel. We analyzed this volume and found that these manual uploads likely cost you ~[X] hours/month in administrative overhead."
- The "Risk & Error" Calculation:
- Highlight the risk of the manual workflow.
- Proof Asset: A one-pager comparing their current "Manual/Export" workflow vs. the "Native Integration" workflow. Focus on Data Integrity (e.g., "Human error in CSV transfers creates a 5% data discrepancy risk").
- The "Peer Benchmark" Mirror:
- Show anonymized data of similar companies.
- Proof Asset: "Companies in your industry at your current usage level have fully migrated their reporting into our platform, reducing their SaaS spend by eliminating [Competitor Tool X] and saving $50k/year."
3. The CTAs (The Action)
Low friction, high curiosity. Do not ask to "buy." Ask to "optimize."
- The "Workflow Mapping" Call:
- Instead of a "Renewal Check-in," offer a "Workflow Efficiency Audit."
- Script: "We noticed a heavy reliance on CSV exports. We'd like to map this workflow to see if our new [Premium Feature/Integration] can eliminate that manual step entirely."
- The "Sandbox" Access:
- Grant temporary, high-level access to the feature that replaces the manual export (e.g., Advanced Reporting or API Webhooks) for 14 days, pre-configured with their data.
- Action: "Click here to enable the 'Live Dashboard' that renders your nightly Excel reports obsolete."
- The "Consolidation Credit":
- If the expansion involves replacing another tool, offer a specific "Switch & Save" credit.
- Offer: "If you migrate your reporting from [Tool X] to our platform this quarter, we will apply a 20% credit toward your expansion fees."
Summary of the Play
Component Traditional Play The Shadow Workflow Play Trigger "They hit their seat limit." "They are exporting data to do the work elsewhere." Proof "Our new feature is cool." "You are losing 15 hours/week to manual errors." CTA "Buy more seats." "Let us automate this manual process for you." -
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.