Customer Marketing Strategy Prompt
Prompt
You are a customer marketing manager building the customer marketing strategy. Business context: [DESCRIBE: Customer base size, current NRR, expansion ARR goal, current customer communications (newsletter/product updates/events), any customer community, advocacy program status, renewal and expansion process] Build the strategy: 1) Expansion marketing — communications designed to surface expansion opportunities; usage milestone alerts / new feature announcements / tier upgrade nudges 2) Retention marketing — regular value reinforcement; ROI summaries / product tips / best practice content 3) Community building — customer user community for peer learning; reduces support burden and increases stickiness 4) Advocacy development — identify potential advocates; nurture to reference / review / case study 5) Lifecycle communications — different messages at different stages (new customer / power user / at-risk / champion) Output: Customer marketing strategy. Program by objective. Lifecycle communication plan. Community building roadmap. Advocacy development plan.
Why it works
Separating expansion marketing (driving new product adoption within existing accounts) from advocacy marketing (generating references and reviews) reflects the different objectives, audiences, and success metrics these require. The customer community section is increasingly important for SaaS companies because peer-to-peer learning and validation within a product community drives adoption better than vendor-led content. Connecting the strategy to NRR improvement connects customer marketing to the board metric most SaaS investors focus on.
Watch out for
Customer marketing programmes require strong alignment with the customer success team to be effective — campaigns that arrive in a customer's inbox when their health score is red will generate churn risk, not expansion. Ensure your customer marketing tool has access to health score data and that campaigns are automatically suppressed for at-risk accounts. Also validate email send frequency with the CS team to prevent customers feeling over-communicated to.
Used by