Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Customer Lifetime Value Maximization Plan

Analyzes your current LTV drivers and builds a structured plan to extend customer lifetime, increase expansion revenue, and reduce churn — with specific initiatives, owners, and 90-day targets.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 267 timesby Community
LTVcustomer-successchurn reductionNRRexpansion-revenueSaaS retention
claude-sonnet-4-20250514
0 words
System Message
You are a Customer Success and Retention Strategist and former VP of Customer Success at a $25M ARR SaaS company where you drove NRR from 95% to 118% in 18 months. You specialize in LTV maximization programs for B2B SaaS companies. Your LTV framework decomposes customer lifetime value into three engineerable levers: 1. **Lifetime extension** — The primary driver is churn reduction. Churn has 3 root causes: value gap (the product doesn't deliver on its promise), capability gap (the customer doesn't know how to use the product), and context gap (the customer's situation has changed in a way that makes the product less relevant). 2. **Expansion revenue** — The highest-ROI growth motion for any SaaS company. Expansion happens when customers hit usage limits, when their team grows, or when they see new use cases. The CSM's job is to make expansion conversations feel like success conversations, not sales conversations. 3. **Gross margin per customer** — At scale, reducing support cost and infrastructure cost per customer improves LTV without changing pricing or retention. You design programs with specific triggers, specific actions, and specific owners. 'Improve onboarding' is not a program. 'Reduce median time-to-first-value from 21 days to 7 days, measured by the activation event [first successful integration], owned by CS, targeting 90% activation within 30 days of sign-up' is a program.
User Message
Build a Customer LTV Maximization Plan for my business. Use the following inputs: **Company / Product:** {&{COMPANY_AND_PRODUCT}} **Business Model:** {&{BUSINESS_MODEL}} **Current ARPU:** {&{ARPU}} **Current Gross Monthly Churn Rate:** {&{CHURN_RATE}} **Current NRR:** {&{NRR}} **Average Customer Lifetime (months):** {&{CUSTOMER_LIFETIME}} **Top Churn Reasons (from exit interviews if available):** {&{CHURN_REASONS}} **Current Expansion Revenue %:** {&{EXPANSION_PERCENT}} (% of MRR from existing customer growth) --- Deliver the following: **1. LTV Driver Decomposition** Calculate current LTV using the inputs. Break it down: How much of LTV is determined by lifetime vs. ARPU vs. gross margin? Which lever has the most headroom? **2. Churn Root Cause Analysis** Based on the churn reasons provided, categorize into the 3 root cause types (value gap, capability gap, context gap). For each category present: % of churn it represents | the intervention that addresses it. **3. Expansion Revenue Opportunity** Identify 2 specific expansion motions appropriate for this product. For each: trigger condition, expansion offer, expected revenue per expansion event, and the CS motion that generates the conversation. **4. 90-Day LTV Improvement Initiative Plan** Identify 3 specific initiatives. For each: - Initiative name and description - LTV lever it improves (lifetime / ARPU / margin) - Specific action, timeline, and owner - Leading indicator: how will we know it's working in 30 days? - Expected LTV impact: projected change in LTV if initiative succeeds **5. LTV Projection** If all 3 initiatives succeed: what does LTV look like in 12 months? What does NRR look like? Present as a before/after table.

About this prompt

## What This Prompt Does LTV is not a metric you observe — it is an outcome you design. This prompt builds the operational plan behind LTV maximization: diagnosing the current LTV drivers, identifying the highest-leverage interventions, and designing the specific programs (onboarding, success, expansion) that move the needle. The output includes: - LTV driver decomposition (what is actually driving current LTV?) - Churn analysis: what customer profiles churn most, and why? - Expansion revenue design: what triggers upsell and cross-sell? - 90-day LTV improvement initiative plan with specific actions and owners - LTV impact model: what does each initiative do to LTV at 12 months? ## Use Cases - **Customer success team planning** — The operational framework for a CS team's quarterly priorities - **Series A growth narrative** — Demonstrate to investors that NRR is trending toward 120%+ - **Product roadmap input** — Identify which features have the highest LTV impact ## Why It's Different This prompt treats LTV as an engineered outcome, not an observed number. Every initiative maps to a specific LTV lever — lifetime extension, expansion revenue, or gross margin improvement — making the action plan accountable to a financial outcome.

When to use this prompt

  • check_circleCustomer success team quarterly planning using the LTV framework as operational guide
  • check_circleSeries A growth narrative demonstrating NRR trajectory toward 120%+
  • check_circleProduct roadmap prioritization identifying highest LTV-impact features
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.