“Design a customer onboarding sequence for my product. My product: [describe]. My ICP: [describe]. Time-to-first-value (when a new customer typically experiences their first meaningful outcome): [describe]. The most common reasons new customers fail to activate: [list what you’ve observed]. Design: (1) A day-by-day onboarding sequence for the first 14 days — what communication goes out, when, with what goal, (2) The activation milestone that I should track to know onboarding is succeeding, (3) The moment in the sequence where I should offer a live check-in call — and what that call should cover, (4) The email I send at day 7 to customers who haven’t reached the activation milestone. Focus on getting customers to first value as fast as possible, not on showing them every feature.”

“Write a 30-day check-in email for a customer who signed up a month ago. What I know about them: [describe their role, company, use case, and any usage data you have — are they active, partly active, or dormant?]. My goal: understand if they’ve achieved value, identify any friction, and strengthen the relationship. The email should: come from the founder (not automated-sounding), ask one specific question about their experience (not a survey), reference something specific about their use case or onboarding, and make it easy to reply. Under 100 words. Include 2 subject line options.”

“Help me reach out to a customer who shows at-risk signals. What I’m seeing: [describe — login frequency dropping, feature usage declining, support tickets increasing, stopped responding to emails, etc.]. What I know about them: [describe their use case, tenure, and contract value]. Write: (1) The outreach message — direct, no fluff, genuinely curious rather than alarming, (2) The subject line that gets opened (not ‘checking in’), (3) What I should be trying to learn from their response — the 2 things that would tell me whether this is recoverable, (4) The follow-up action if they don’t respond within 5 days. The tone should be personal and human — this is a relationship, not a retention campaign.”

“Help me respond to a frustrated customer. Their complaint: [describe exactly what they said or wrote]. The context: [describe what actually happened, what’s true in their complaint, and what may be mischaracterised]. My goal: de-escalate, acknowledge what’s valid, and rebuild the relationship — without making false promises or accepting blame for things outside our control. Write: (1) The response email — acknowledges the frustration specifically, owns what we got wrong, describes what we’re doing about it, and asks what would make this right, (2) The internal note on what actually needs to change to prevent this complaint from recurring, (3) The follow-up I should send in 5 days to close the loop. Tone: direct, warm, no corporate language.”

“Build a QBR (Quarterly Business Review) agenda for a customer meeting. Customer: [describe — company, role of attendees, contract size, tenure]. Their key goals when they signed up: [describe]. What I know about their usage and results this quarter: [describe — what they’ve achieved, what they haven’t, any areas of friction]. The QBR should: demonstrate the value delivered, not just the activity logged, surface any gaps between their goals and current usage, and set clear direction for next quarter. Design a 45-minute agenda with: specific talking points for each section, the data I should prepare for each section, and the 1 question I should ask that creates the most useful conversation. Also: what’s the one thing I should make sure this customer walks away knowing?”

“Help me design the expansion conversation for a customer I believe is ready to grow their account. Customer context: [describe — current plan, tenure, usage signals that suggest they’re getting value and could benefit from more]. Expansion options: [describe — additional seats, higher tier, add-on features]. The conversation should: feel like a logical next step in their success, not a sales pitch, be grounded in their specific usage and outcomes, and make it easy for them to say yes. Write: (1) The opening that transitions from a value conversation to an expansion conversation naturally, (2) The 2 questions that help me understand whether expansion is right for them right now, (3) The framing of the expansion option in terms of their outcome, not our product features, (4) How to handle ‘let me think about it’ — the follow-up that keeps momentum without pressure.”

“Write a renewal email for a customer whose contract expires in 45 days. Customer context: [describe — tenure, usage level, any known concerns or successes]. My goal: prompt the renewal conversation without making it feel like a collections notice. The email should: reference specific value they’ve received (not generic claims), make the renewal process easy, and open a conversation rather than close one. Include: (1) The email — under 150 words, from the founder, referencing something specific, (2) The subject line, (3) What I should be prepared to discuss if they raise a concern or ask for a discount, (4) The follow-up sequence if they don’t respond — what to send at day 7, day 21, and day 35 from this first email.”

“Help me design a customer health score for my product. My product: [describe]. The data I currently have about each customer: [list — login frequency, feature usage, support tickets, NPS, contract size, tenure, etc.]. What I know from experience about which signals predict churn vs retention: [describe any patterns you’ve observed]. Design: (1) A health score framework using 4–5 of my available data points, with a weighting rationale for each, (2) The threshold that triggers an ‘at-risk’ flag and what action it should prompt, (3) The threshold that signals ‘healthy and expansion-ready’ and what action that should prompt, (4) How to implement this as a simple weekly review process without a dedicated CS tool. Make it simple enough that I can run it in 30 minutes per week.”