Stop SaaS CSOs From Losing Price-Sensitive Deals That Should Be Won on Value — Gemini Prompts for Building a Referral System That Expands Revenue Inside Existing Accounts (Advanced Level)

You are an expert SaaS chief revenue strategist with 16 years of experience building referral systems, account expansion playbooks, and price objection prevention frameworks for SaaS companies where the CSO is fighting a two-front war — losing new business deals on price to a cheaper competitor and leaving expansion revenue on the table inside existing accounts that do not know the full product capability. Help me build a referral request template so I can expand revenue within existing accounts and create a referral system where the expansion conversations inside existing accounts generate peer introductions that arrive at new prospect evaluations already primed to value the product at full price. My situation: - SaaS product and competitive context: [e.g., "an enterprise project intelligence platform — primary competitor charges 40% less with a feature set that covers 70% of the use cases the full product handles, winning deals where prospects do not know which 30% they will eventually need"] - Account expansion gap: [e.g., "existing accounts are using an average of 58% of the product's feature set — the 42% of unused capability represents $4.2M in potential expansion revenue across the account base, but no systematic expansion motion exists beyond annual upsell conversations"] - Referral connection to expansion: [e.g., "accounts that have expanded to 80% or more of product capability have a 94% renewal rate and refer an average of 2.3 new prospects per year — accounts using less than 60% of capability have a 71% renewal rate and refer 0.4 prospects per year, confirming that expansion is the prerequisite for referral volume"] - Price objection in new business: [e.g., "40% of new business deals lost on price — exit surveys show 60% of those prospects expected to need only the features the competitor covers and were unwilling to pay a premium for capabilities they did not plan to use"] - Referral request current state: [e.g., "no formal referral request process — the CSO sends occasional LinkedIn messages to CEOs of existing accounts asking for introductions, with a 15% reply rate and no structured follow-up"] - Expansion conversation current state: [e.g., "account managers discuss expansion at the annual renewal meeting — no mid-year expansion trigger, no usage data used to identify expansion readiness, no structured conversation for moving from 58% to 80% feature utilization"] - Revenue expansion target: [e.g., "want to increase average account feature utilization from 58% to 72% within 12 months, generating $2.1M in incremental expansion revenue and increasing referral rate from 0.4 to 1.8 new prospects per account per year"] Deliver: 1. A referral request template system anchored in account expansion — three referral request templates tied to three expansion milestones (first significant expansion from under 60% to over 70% utilization, first renewal at 80% or above utilization, and first year-over-year ROI milestone documented in a customer success review), each template under 130 words with a subject line that references the expansion outcome rather than the referral ask 2. A feature utilization expansion playbook — a mid-year expansion conversation framework triggered by usage data showing accounts between 50% and 65% utilization, covering the discovery question that surfaces the business process the unused capability would improve, the one-feature demonstration that converts feature awareness to adoption, and the expansion proposal structure that connects the new feature to a dollar-quantified outcome 3. A price objection prevention strategy using expansion evidence — a pre-evaluation social proof sequence for new prospects that uses anonymized expansion stories from existing accounts, showing the specific capability they adopted in year two and the ROI it produced, framed as the preview of a typical customer journey rather than as a sales argument 4. A referral timing decision matrix tied to expansion milestones — a specific trigger for each of the three referral template versions based on a Salesforce usage data field update, ensuring referral requests are sent at the moment of maximum account enthusiasm (immediately after an expansion win) rather than at the annual renewal meeting when the relationship is in a commercial rather than a value-delivery frame 5. A CEO-level referral conversation guide for the CSO — a five-minute structured conversation the CSO has with a CEO or CRO at an expanded account before the formal referral request is sent, covering the expansion outcome they achieved, the peer profile most likely to benefit from the same expansion, and the specific ask that makes yes easier than no without creating obligation 6. A competitive displacement brief for the 40% of deals lost on price — a three-scenario financial model showing the total cost of ownership at 18 months for the primary competitor (base price plus the cost of adopting the missing 30% of capability through alternative tools or manual processes) versus the full product, with the specific scenarios where the competitor total cost exceeds the full product cost by year two 7. A referral-to-new-business pipeline tracking system — a Salesforce configuration that tracks referral source, expansion milestone that triggered the referral, the referred prospect's evaluation stage, and the win or loss outcome, producing a monthly report that shows the CSO which expansion milestones generate the highest-converting referrals and which account profiles produce the most referral volume 8. A 12-month CSO execution calendar — a quarterly plan covering the expansion playbook rollout in Q1, the referral system launch in Q2, the price objection prevention social proof program in Q3, and the referral pipeline reporting and optimization in Q4, with the specific metric at the end of each quarter that determines whether the utilization target and referral rate target are on track **Write every referral template and expansion playbook component assuming the CSO is executing this with an account management team that is commercially cautious and relationship-protective — every expansion conversation must feel like a customer success motion rather than an upsell motion, and every referral request must feel like an opportunity for the existing account to share their success rather than a favor to the sales team.**