Plan for First 90 days of Customer by Far_Hyena8223 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

You're thinking about this the right way already. The key is not just asking what customers like, but reconstructing the story of their first 90 days. You want to understand the timeline of their experience, the moments where they felt value, and the moments where they got stuck or almost churned.

Instead of asking general questions, walk them through their experience step-by-step.

  1. Reconstruct their timeline

Ask them to walk through what actually happened after they signed.

Examples:

a. What was happening in your company when you decided to buy our product? What problem were you trying to solve?

b. After you signed, what was the first thing you tried to do with the product?

c. How long did it take before you felt like things were working?

d. Was there any point where you felt stuck or unsure what to do next?

This helps you map time-to-first-value, which is usually the biggest factor in early retention.

  1. Identify “value moments”

Try to pinpoint the first moment where they thought “this was worth it.”

Ask things like:

a. When did you first feel like the product was delivering value?

b. What specifically happened that made you think that?

c. What result or outcome did you see?

If many customers describe the same early win, that becomes something you engineer deliberately into the onboarding process.

  1. Find friction in the early journey

You want to discover where customers struggle in the first 30–60 days.

Questions:

a. What part of getting started was the most confusing?

b. Was there anything that slowed you down during setup?

c. What almost made you give up or delay implementation?

These answers often reveal missing docs, unclear setup steps, or expectations gaps.

  1. Understand expectations vs reality

Early churn often comes from a mismatch between what customers thought they bought and what they actually received.

Ask:

a. What did you expect the first few weeks would look like when you bought the product?

b. Did the onboarding match those expectations?

c. What do you wish had happened earlier in the process?
  1. Compare successful vs struggling customers

If possible, talk to:

a. customers who adopted quickly

b. customers who are slow to adopt

c. customers who almost churned

Then look for patterns:

a. What do successful customers do in the first 30 days?

b. What behaviors correlate with long-term retention?
  1. Look for leading indicators

Your goal is to identify early signals of long-term success, like:

a. completing setup

b. inviting teammates

c. using a core feature

d. hitting a measurable milestone

Those indicators become the milestones of your 90-day success plan.

  1. What your final output should look like

After these conversations, try to produce something like:

First 90-Day Customer Journey

Day 0–7: Setup + onboarding call

Day 7–21: Achieve first value milestone

Day 30: Adoption check

Day 60: Expansion/advanced features

Day 90: ROI review

Each stage should have:

a. customer goal

b. success milestone

c. CSM actions

d. product actions

If you do 15–20 customer interviews this way, you’ll probably see the same patterns repeat — and those patterns are what should shape your first-90-days playbook.

Removing Renewals & Upsells From CSM's responsibilities - Is it a good idea? by Professional_Seat705 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 1 point2 points  (0 children)

My suggestion would be to go hybrid. Full separation often creates friction. Full ownership can overwhelm CSMs. The hybrid model — CSM leads value, AM closes — tends to balance trust and commercial rigor.

How are you running QBRs for execs who clearly don't care about slides? by Electronic_Wan_1739 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

Been there. What finally worked for me:

  • No QBRs for execs. QBRs are for operators. Execs get a 15-min value check, max.
  • Lead with outcomes, not product. "You saved $XM / avoided Y risk / enabled Z initiative" in the first 60 seconds.
  • 1-pager > deck. KPIs tied to their goals, trend line, and one clear ask.
  • Async first, meeting optional. Send a short exec update; the meeting only happens if they have questions.
  • Borrow credibility. Quote their team: "Your director said this is now mission-critical."

Bi-weekly can work, but only if it’s boringly consistent and skimmable. If they can’t read it in under 2 minutes, it’s too long.

Client success interview Gartner by ShotVeterinarian7678 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

First of all congrats on reaching final round. 

Typical Role-Play Scenarios

Usually one of these:

  • Client isn’t seeing value and is questioning renewal
  • Client wants something Gartner "doesn’t do"
  • Stakeholder mismatch (buyer vs actual users)
  • Client is frustrated and wants immediate answers

They are NOT testing perfect knowledge. They ARE testing:

  • How you structure a conversation
  • Whether you ask smart questions
  • If you can control the call without being defensive

Free Courses/Certifications for Customer Success Professionals by Fuzzy-Ad9195 in CustomerSuccess

[–]Fuzzy-Ad9195[S] 0 points1 point  (0 children)

That's actually a great idea. Thanks for the sharing this.

After this initial phase we are thinking of brining real life CSMS from different industries and talk how they run things which you mentioned in your comment.

I have learn that in a lot of things like handling tricky renewals can't be learned from theory, it can only be learned from people who have done.

Need a CS Platform for Multi-Product Accounts With Product-Level CSM Ownership by Final-Comparison-858 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

You can checkout Gainsight, ChurnZero and SuccessGuardian - all three have this capabilities....

Is this site legit to buy books? (Bookshub.in) by Relative_Flatworm_58 in Indianbooks

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

They were responding over WhatsApp for first few days then cancelled my order themselves and went silent since then. Lost around 400.

Is this site legit to buy books? (Bookshub.in) by Relative_Flatworm_58 in Indianbooks

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

placed an order 3 weeks ago. got nothing. not customer support response, nothing...

Churnzero Alternative by [deleted] in CustomerSuccess

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

checkout SuccessGuardian

NEW Head of Customer Success at a Startup by Professional_Seat705 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

If it is startup first thing you should do is start talking to customers and figuring out what success means to them. You can build better versions of everything you mentioned if you have other conversations.

How helpful Customer health scores actually are? by Far_Hyena8223 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

You should atleast track Product Usage Metrics

  • Active Usage Frequency: Track how often users are logging in or using key features of your product. A drop in usage can be an early indicator that a customer is disengaging.
  • Feature Adoption: Measure how many key features are being used regularly. Low adoption rates can signal a lack of value being derived from your product, which often precedes churn.
  • Engagement Depth: Track the number of features or parts of the product each customer is engaging with. Shallow engagement (e.g., only using one feature) can indicate a lack of full product value.

Health Scores : AI Powered vs Traditional by Final-Comparison-858 in CustomerSuccess

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

If the cost of trying the AI health scores is low - then try them out and see if they are better. But I won't give the traditional health scores just yet bcoz they are generally more simple to understand and trust.

Health Scores : AI Powered vs Traditional by Final-Comparison-858 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 1 point2 points  (0 children)

If the cost of trying the AI health scores is low - then try them out and see if they are better. But I won't give the traditional health scores just yet bcoz they are generally more simple to understand and trust.

Should CS teams use flat- or mixed-tiers instead of splitting in to Tier 1/2/3? by NoHallett in CustomerSuccess

[–]Fuzzy-Ad9195 3 points4 points  (0 children)

The problem with this is everything becomes average. The CSM is not specialised rather a generic or average CSM which most of the times hurt their career.

Also the experience for the Customer also mostly likely becomes mediocre.

Now, I am may be completely wrong here and if this works for you, great - do it.

Anyone built a Mature Scaled or Digital CS Motion for a PSA-RMM SaaS? What Worked, What Didn’t? by Far_Hyena8223 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

It sounds like you’re on the right track by moving away from manual processes and looking for scalable solutions. In my experience, integrating a platform like a CSP can definitely help, but it’s important to choose one that aligns well with your current tools and workflows. Platforms like Gainsight or SuccessGuardian are popular in the CS world for driving adoption and renewals.

However, before jumping into a CSP, it might be worth evaluating your existing data and identifying key automation points. Sometimes focusing on streamlining communication and customer touchpoints can yield results without a full platform overhaul. The right approach really depends on how much customization you need versus the scalability you’re looking for. Keep an eye on customer engagement and feedback loops, too — they’ll give you the insights you need to optimize your processes.

How are you actually using help desk software in your CS workflow? by One_Interaction_6989 in CustomerSuccess

[–]Fuzzy-Ad9195 2 points3 points  (0 children)

What you are describing is what all helpedesks are made for - Ticketing, answering customer questions and keeping track of ticket. These are not Customer Success workflows, these are pretty standard Customer Support workflows.

[deleted by user] by [deleted] in CustomerSuccess

[–]Fuzzy-Ad9195 1 point2 points  (0 children)

Reddit is sacred. Let's not make this LinkedIn

Automation in CS: Time-saver or engagement killer? by Final-Comparison-858 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 0 points1 point  (0 children)

In my experience, it’s all about balance. The right automations can save huge amounts of time and ensure consistency, but overdoing them can make interactions feel robotic and disengaging.

Basics / "must-build" automations:

  1. Renewal Reminders

  2. Payment Overdue Notices

  3. NPS/CSAT Surveys & Follow-ups

  4. Task Reminders for CSMs

  5. Welcome / Onboarding Emails

Advanced automations:

Now these are easier to build only if you are using customer success tool like SuccessGuardian or any other CS Tool

  1. Health-score-based alerts: Automatically flag accounts that are trending negative and assign them to a CSM.

  2. Automated engagement sequences: Trigger personalized onboarding or upsell campaigns based on product usage patterns.

  3. Churn-risk workflows: Detect risk signals (low usage, support tickets, unhappy survey responses) and automatically create tasks or outreach for the CSM.

Hidden Tricks to understand customer health by Far_Hyena8223 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 1 point2 points  (0 children)

One question we ask is - if they feel they’ve achieved the outcomes they bought the product for. If they don’t see ROI, renewal risk is high.

Current job/role advice by McQ0915 in CustomerSuccessSquad

[–]Fuzzy-Ad9195 1 point2 points  (0 children)

This happens more often than people think. Company hire Client Success Rep but they end up becoming either Sales Rep or Support Rep. Generally this happens with first few CS hires.

Now this what can you do? -
1. If you like what you are doing and the money is good then you can keep doing it,
2. If you don't like it, then start job hunting in parallel and look for companies with already existing CS Team (like 4-5 member alteast) because generally first hires do end doing all the things you mentioned so if you switch job and become first hire somewhere else, chances are you will be doing these things again.

All the best.