PromptBase
PromptBase SelectGet Select
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
(claude-5-opus)
Token size
582
Example input
[Expertise or Niche]: B2B SaaS customer retention [Target Audience]: SaaS founders and customer success leaders [Authority Goal]: Become known for practical retention strategy and churn analysis [Existing Knowledge, Experience, or Proof]: Five years in customer success, onboarding projects, churn reviews, and internal retention frameworks [Preferred Channels and Additional Requirements]: LinkedIn, newsletter, and long-form articles; professional and analytical tone
Example output
## 🧠 Authority Strategy Overview **Niche:** B2B SaaS customer retention **Audience:** SaaS founders and customer success (CS) leaders **Authority Goal:** Become known for practical retention strategy and churn analysis β€” not general CS advice, but specific, actionable thinking on why customers leave and how to systematically reduce it **Verified Foundation:** Five years of hands-on customer success work, including onboarding projects, churn reviews, and internally-built retention frameworks This is a credible, specific foundation to build from. The strategy below leans on real operational experience (onboarding, churn reviews, frameworks) rather than claims of scale, industry recognition, or unverified results. Anywhere a stronger claim would help (metrics, case outcomes, before/after data), it's flagged in the Credibility Gaps section rather than assumed. --- ## 🧱 Core Content Pillars | Pillar | Focus | Why It Fits | |---|---|---| | 1. Churn Diagnosis | How to actually identify *why* customers churn (data, signals, root-cause analysis) | Directly tied to churn review experience | | 2. Onboarding as a Retention Lever | Structuring onboarding to prevent early-stage churn | Directly tied to onboarding project experience | | 3. Retention Frameworks & Systems | Repeatable internal processes for tracking and improving retention | Directly tied to internal framework-building experience | | 4. CS Team Operations | How CS teams should be structured, measured, and run to support retention | Adjacent to 5 years in CS β€” reasonable extension | | 5. Retention Metrics & Analysis | Interpreting churn/retention data without vanity metrics | Ties churn review experience to analytical positioning | | 6. (Optional) Founder–CS Alignment | Helping founders understand retention as a strategic, not just operational, issue | Bridges CS expertise to the founder audience specifically | Recommend starting with Pillars 1–4 as the primary rotation; introduce 5–6 once a content rhythm is established. --- ## ⭐ Signature Topics Recurring themes that can become "your" territory over time: - **The Churn Autopsy** β€” a repeatable method for reviewing a lost customer to extract the real cause (not just the stated reason) - **Onboarding as Insurance, Not Orientation** β€” reframing onboarding as the highest-leverage retention activity - **Leading vs. Lagging Retention Signals** β€” what to watch *before* churn happens, not after - **The Retention Framework Series** β€” periodically publishing/refining a named internal framework (even informally named) so it becomes recognizable - **CS Metrics That Lie** β€” a myth-busting angle on vanity or misleading retention metrics Signature topics work best when the same 3–5 recur across months in different formats β€” repetition builds recognition. --- ## πŸ’‘ Educational Content Ideas **Beginner** - "What is churn analysis, actually? A CS leader's plain-language guide" - "The 3 stages where SaaS customers most often disengage" - "Onboarding vs. activation: why founders confuse them" **Intermediate** - "How to run a churn review that produces real answers (not guesses)" - "Building a lightweight retention dashboard without expensive tooling" - "The onboarding checklist that catches churn risk in week one" **Advanced** - "Segmenting churn by root cause, not just by customer size or plan" - "Designing a retention framework that survives team turnover" - "When to fire a customer: retention math beyond 'keep everyone'" **Opinion** - "Most churn dashboards measure the wrong thing" - "Retention is a founder problem disguised as a CS problem" - "Onboarding should be owned by product, not just CS" **Case-Based** *(use only real, generalized experience β€” no specific client names/numbers unless verified and permitted)* - "A churn pattern I kept seeing across onboarding projects β€” and what fixed it" - "How an internal retention framework changed the way a CS team prioritized work" **Myth-Busting** - "Why 'more check-ins' doesn't reduce churn" - "NPS is not a retention metric β€” here's why" - "Churn isn't always a support problem" **Practical/Tactical** - "A simple template for structuring a churn review meeting" - "5 onboarding milestones worth tracking in any SaaS product" - "How to write a retention framework doc your team will actually use" --- ## 🎯 Thought-Leadership Angles To avoid sounding like generic CS content, anchor opinions in a distinct point of view: - **Reframe retention as a design problem, not a support problem** β€” argue that most churn is engineered in (or out) during onboarding, not fixed afterward - **Challenge metric worship** β€” take a clear stance on which popular retention metrics are misleading and why, based on direct churn-review experience - **Push founders to own retention strategically** β€” position retention as a leadership responsibility, not a delegated CS task - **Advocate for "boring" systems over reactive heroics** β€” frameworks and repeatable process over one-off save attempts These angles create a recognizable perspective without requiring unverified claims β€” they're built on interpretation of real experience, clearly framed as opinion. --- ## βœ… Credibility & Proof Strategy Ways to build credibility *without* inflating claims: 1. **Show frameworks, not just talk about them** β€” publish simplified versions of internal retention frameworks (genericized, non-confidential) 2. **Use process transparency** β€” walk through *how* a churn review is actually run, step by step 3. **Share original observations** β€” patterns noticed across onboarding/churn work, framed as "in my experience" rather than universal fact 4. **Be explicit about scope** β€” "based on 5 years running CS/onboarding/churn reviews" is a credible, specific, honest claim β€” use it directly and often 5. **Invite scrutiny** β€” ask readers whether a framework matches their experience; this builds trust more than declarative certainty Avoid: unverified statistics, invented case studies, vague appeals to "industry data," or claims of being an "expert" or "leader" β€” the specificity of real experience is more persuasive than status claims. --- ## πŸ“… Publishing Rhythm | Channel | Frequency | Purpose | |---|---|---| | LinkedIn | 3–4x/week | Short-form opinion, frameworks, myth-busting, engagement | | Newsletter | 1x/week or biweekly | Deeper synthesis, one core idea per issue, more analytical tone | | Long-form articles | 1–2x/month | Flagship pieces β€” frameworks, deep churn analysis, signature topics | Suggested cadence: one long-form article per month becomes the "core idea," which then feeds LinkedIn and newsletter content for that period (see Repurposing Plan). --- ## πŸ”„ Repurposing Plan One core idea β†’ multiple assets: 1. **Long-form article** (e.g., "How to Run a Churn Review That Produces Real Answers") 2. β†’ **Newsletter recap** with added personal commentary or a refined framework visual 3. β†’ **3–5 LinkedIn posts**, each isolating one sub-point (e.g., one post per churn-review step) 4. β†’ **1 opinion/myth-busting LinkedIn post** derived from a contrarian point buried in the article 5. β†’ **1 "template" or checklist post** extracted from the practical steps 6. β†’ Optional: a simple visual/framework graphic summarizing the article for LinkedIn This turns one piece of deep work into 2–4 weeks of content across channels. --- ## ⚠️ Credibility Gaps & Research Needs Flagged before publication β€” do not present as verified without support: - **No named metrics, percentages, or churn-reduction results** are currently available β€” avoid stating specific outcomes (e.g., "reduced churn by X%") unless real, verifiable numbers exist - **No named case studies or client references** β€” case-based content should stay generalized/anonymized unless explicit permission and verified detail exist - **No third-party validation** (press, speaking engagements, published research) β€” avoid implying external recognition - **Internal frameworks are proprietary/informal** β€” before publishing, confirm they can be shared in simplified form without confidentiality issues - **Avoid superlative language** ("leading," "top," "best-in-class") β€” none of it is currently supportable and isn't necessary for credibility here --- ## πŸš€ 90-Day Authority Roadmap **Days 1–30: Foundation** - Finalize 4 core pillars (Churn Diagnosis, Onboarding, Frameworks, CS Ops) - Publish 1 flagship long-form article (choose a signature topic) - Launch newsletter with first issue recapping the article - Begin LinkedIn rhythm: 3x/week, mixing opinion + practical posts - Draft a simplified version of one internal retention framework **Days 31–60: Signature Positioning** - Publish 2nd long-form article (churn analysis or metrics myth-busting angle) - Introduce "Churn Autopsy" or similarly named recurring format - Start repurposing each article into 4–5 LinkedIn posts + 1 newsletter issue - Begin tracking which topics/pillars get the most engagement **Days 61–90: Consistency & Refinement** - Publish 3rd–4th long-form article, doubling down on best-performing pillar - Refine and re-share the retention framework based on feedback - Introduce one clear opinion piece challenging a common industry assumption - Review 90-day content performance; identify which signature topics are gaining recognition --- ## πŸ“Œ Top Priority Actions 1. Choose the first flagship long-form article topic (recommend: a churn review framework or "Churn Autopsy" concept) 2. Simplify and prepare one internal framework for public sharing 3. Set up newsletter + posting cadence (3–4x/week LinkedIn, weekly/biweekly newsletter) 4. Draft 3–5 opinion/myth-busting posts to establish point of view early 5. Audit all draft content against the Credibility Gaps list before publishing β€” remove any unverified claims or superlatives
Claude

Authority Content Builder

Add to Cart
PromptBase Select
Get this prompt + 9 more with Select$14 your first month, then $19/mo$14 first month, then $19/mo
View Select
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
CLAUDE-5-OPUS
Tested icon
Guide icon
4 examples icon
Free credits icon
Create educational content strategies that demonstrate expertise, build trust, and strengthen authority within a specific niche. This prompt develops content pillars, signature topics, proof-backed angles, thought-leadership ideas, publishing formats, and repurposing plans. Perfect for consultants, founders, coaches, specialists, agencies, creators, and professional service brands. πŸ§ πŸ“š
...more
Added over 1 month ago
Report
Browse Marketplace