Evaluate CS Tech Stacks
Requirements
Company stage (early, growth, enterprise) for relevant tool recommendations
3
Gather context from the user:
- What stage is your company? (Early/Seed, Growth/Series B-C, Enterprise/Series D+)
- What tools do you currently use? (CRM, success platform, analytics)
- Any specific category you're evaluating? (success platform, analytics, CS ops)
- Budget constraints?
Check Customer Success Context Profile for existing context.
4
First, check CS Benchmarks Reference — it has tools by stage and a
platform comparison matrix (Gainsight, ChurnZero, Totango, Vitally, Planhat, Catalyst).
Search only if the user needs:
- Head-to-head comparison of specific tools not in cache
- Recent reviews or pricing changes
- Niche tools for specific use cases
If searching, run 1-2 targeted queries:
- "[Tool A] vs [Tool B] review 2024"
- "best [specific category] tool for [stage] startup"
For platform comparisons, G2 head-to-head pages are most useful.
5
Synthesize findings into the CS Tooling Stack Evaluation format:
- Recommended stack by company stage
- Tool comparisons for relevant categories
- Pricing ranges and value assessment
- Integration considerations
- Stage-appropriate recommendations
Include sources and note recency of reviews.
6
Provide specific recommendations:
- Tools to prioritize based on their stage and needs
- Build vs buy considerations
- Migration path if switching tools
Ask if they want deeper comparison on any specific tool category.
To run this task you must have the following required information:
> Company stage (early, growth, enterprise) for relevant tool recommendations
If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.
---
You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).
Add all steps to your todo list now and begin executing.
## Steps
1. [Read CS Benchmarks Reference]: Read the documentation in: `./skills/sauna/[skill_id]/references/success.benchmarks.cache.md` (Start with tooling by stage and platform comparisons)
2. [Read Customer Success Research Guide]: Read the documentation in: `./skills/sauna/[skill_id]/references/success.research.guide.md` (Get the tooling evaluation output format)
3. Gather context from the user:
- What stage is your company? (Early/Seed, Growth/Series B-C, Enterprise/Series D+)
- What tools do you currently use? (CRM, success platform, analytics)
- Any specific category you're evaluating? (success platform, analytics, CS ops)
- Budget constraints?
Check `./documents/customer-success/profile.yaml` for existing context.
4. **First, check `./skills/sauna/[skill_id]/references/success.benchmarks.cache.md`** — it has tools by stage and a
platform comparison matrix (Gainsight, ChurnZero, Totango, Vitally, Planhat, Catalyst).
**Search only if** the user needs:
- Head-to-head comparison of specific tools not in cache
- Recent reviews or pricing changes
- Niche tools for specific use cases
If searching, run 1-2 targeted queries:
1. "[Tool A] vs [Tool B] review 2024"
2. "best [specific category] tool for [stage] startup"
For platform comparisons, G2 head-to-head pages are most useful.
5. Synthesize findings into the CS Tooling Stack Evaluation format:
1. Recommended stack by company stage
2. Tool comparisons for relevant categories
3. Pricing ranges and value assessment
4. Integration considerations
5. Stage-appropriate recommendations
Include sources and note recency of reviews.
6. Provide specific recommendations:
- Tools to prioritize based on their stage and needs
- Build vs buy considerations
- Migration path if switching tools
Ask if they want deeper comparison on any specific tool category.