'churn' 검색 결과

Design subscription retention workflows for customers who choose to cancel and those whose payments fail. The skill covers cancellation surveys, relevant offers, pauses, payment retries, reminder emails, usage-based warning signals, and metrics for evaluating retention efforts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing a cancellation flow with a reason survey
• Matching pause or plan-change offers to cancellation reasons
• Planning payment retries and reminder emails

Design SaaS cancellation flows, match retention offers to exit reasons, and prepare payment retry schedules and recovery emails. Get flow copy, survey options, email templates, and metrics for reviewing cancellations and failed payments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing a cancellation flow
• Matching retention offers to exit reasons
• Preparing failed-payment recovery emails

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Use when asked to "find at-risk accounts", "who might churn", "build a churn prevention plan", "identify churn signals", or "rescue this account".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs cancel flow UX, dunning email sequences, win-back campaigns, and retention triggers. Covers the full churn prevention lifecycle from early warning signals to 90-day win-back. Use when someone mentions 'churn', 'retention', 'cancel flow', 'dunning', 'win-back', 'users leaving', 'reducing churn', 'keep users', 'customers canceling', 'payment failed', 'failed payments', 'losing subscribers', 'customer retention', or wants to prevent customers from leaving. Even if they just say 'people keep canceling' or 'how do I keep users' — this is the skill. Handles both voluntary churn (unhappy users) and involuntary churn (failed payments). Use this whenever subscription retention is the goal.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Measure CI churn cost for a pull request: how many commits and how many CI-compute seconds were burned on avoidable "fix the CI" push rounds. Use when you want to understand the efficiency cost of a PR's iteration cycle, get actionable pre-push check suggestions, or include a churn summary in a pipeline report. Triggers: "ci churn", "how much CI did we burn", "avoidable commits", "ci efficiency", "wasted CI time", "churn report", "/ci-churn". Called automatically by /fp-drift at pipeline close.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Customer retention system — churn analysis, retention tactics, loyalty programs, and engagement scoring. Use when "retention", "reduce churn", "keep customers", "loyalty program", "customer retention", "churn prevention", "churn analysis", "engagement scoring", "win-back", "customer lifetime value", or any request to analyze, prevent, or reduce customer churn.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze SaaS customer data with three Python tools that calculate account health, rank churn risk, and prioritize expansion opportunities. Use repeatable weighted scores to plan customer outreach and prepare quarterly business reviews.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Scoring customer health across an account portfolio
• Prioritizing outreach to accounts at risk of leaving
• Ranking upgrade and additional-seat opportunities

Combine product usage, support issues, payment status, and renewal dates to rank accounts by churn risk, meaning the risk of cancellation. Produce a Slack list with specific evidence and a suggested next action for each account.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing accounts at risk of cancellation each day
• Prioritizing outreach before contract renewals
• Understanding why an account received a high risk rating

Produce a structured churn analysis that separates avoidable from unavoidable churn. Use when investigating why customers are leaving, identifying at-risk segments, calculating net revenue retention, or building a retention intervention plan. Produces a churn report with rate calculations, categorised reasons by avoidability, segment breakdown, timing analysis, early warning signals, and prioritised interventions ranked by estimated impact.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SaaS churn reduction covering cancel flow design, dynamic save offers, exit survey architecture, dunning sequences, payment recovery, win-back campaigns, and churn impact modeling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

🇺🇸 User Interview & Cold-Start Operations Playbook — Battle-tested framework from HeyGen's 937 interviews to PMF. Complete SOP for user screening, interview execution, Beta testing methodology, cold-start user operations, churn analysis, and user grading systems. 🇨🇳 用户访谈与冷启动运营实战手册 — 基于 HeyGen 937 场访谈验证的 PMF 方法论。包含用户筛选、访谈执行、Beta 测试设计、冷启动用户运营、流失分析、用户分级体系完整 SOP。 🇯🇵 ユーザーインタビュー＆コールドスタート運営プレイブック — HeyGenの937回インタビューで検証されたPMF方法論。ユーザースクリーニング、インタビュー実行、Betaテスト設計、コールドスタートユーザー運営、離脱分析、ユーザーグレーディング。 🇰🇷 사용자 인터뷰 & 콜드 스타트 운영 플레이북 — HeyGen 937회 인터뷰로 검증된 PMF 방법론. 사용자 스크리닝, 인터뷰 실행, Beta 테스트 설계, 콜드 스타트 사용자 운영, 이탈 분석, 사용자 등급 시스템. Triggers: "user interview" | "user research" | "customer discovery" | "PMF" | "product-market fit" | "beta test" | "beta testing" | "cold start users" | "cold start operations" | "churn analysis" | "user grading" | "用户访谈" | "用户调研" | "冷启动" | "冷启动运营" | "Beta测试" | "流失分析" | "用户分级"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze customer health signals, identify churn risk flags, and generate an intervention playbook. Use when user says "churn risk", "customer at risk", "red account", "at-risk customer", "health score dropped", "renewal at risk", "customer going dark", "cancel risk", or "what's wrong with this account" - even if they don't say "churn" explicitly. Applies to CSMs triaging accounts or building proactive retention workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design recurring marketing workflows for SEO checks, ad reviews, and churn monitoring. Define when an agent checks, when it acts, what requires human approval, and when it stops, using reusable workflow templates.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up a weekly SEO review
• Schedule recurring ad fatigue checks
• Monitor customer churn signals

Direct finance questions to the appropriate specialist skill: financial statement analysis or SaaS operating metrics. It helps choose the right workflow for valuation, budgets, recurring revenue, churn, and customer acquisition costs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing the right skill for a financial analysis request
• Routing budget and valuation questions
• Routing recurring revenue and churn questions

Assess a SaaS business using revenue, customer, and cost figures. Calculate recurring revenue, churn, and customer economics, compare results with relevant benchmarks, and identify priority actions plus a measurable 90-day focus.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing monthly SaaS business health
• Prioritizing churn and acquisition cost improvements
• Comparing 12-month growth scenarios

Plan revenue growth for B2B SaaS businesses by analyzing sales opportunities, pricing, customer retention, and sales capacity. Develop scenario forecasts, churn intervention plans, hiring models, and revenue reporting for board discussions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Forecast next quarter’s revenue
• Analyze churn and expansion revenue
• Review pricing and packaging

Plan customer retention and customer success staffing for a startup. Break down renewal and churn patterns, group customers by value and fit, and compare service models to guide resource allocation and hiring.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing retention metrics and reasons for churn
• Allocating support investment across customer tiers
• Estimating customer success staffing needs

Calculate and interpret SaaS subscription revenue, customer churn, and revenue retained from existing customers. Compare customer groups and revenue sources to uncover retention problems, explain growth, and prepare metrics for leadership discussions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing revenue and retention metrics for a board presentation
• Checking whether revenue growth hides customer churn
• Comparing retention by customer start date