TAM Expertise
Parent: TAM Operating Reference · researched 2026-05-25· 0 sources · 3 concepts · skill tam-expertise
Reference skill compiled from 120+ authoritative sources. Full context in tam-expertise-context.md.
TAM Expertise — BI, Reporting, Writing, Risk, Churn, Sentiment & Account Management
- Reference skill compiled from 120+ authoritative sources. Full context in tam-expertise-context.md. [source]
When NOT to use
- MongoDB Premium Services operating procedures → use tam-reference [source]
- Active case management and TS Tools API → use case-tracker [source]
- Atlas cluster diagnostics and troubleshooting → use atlas-diagnostics-expert [source]
- Code review, frontend design, or implementation tasks → use domain-specific skills [source]
When to use
- Writing or reviewing account deliverables (EBRs, QBRs, architecture reviews, post-mortems, runbooks, migration guides, case notes) [source]
- Assessing account health, churn risk, or customer sentiment [source]
- Building KPI frameworks, dashboards, ROI analyses, or adoption reports [source]
- Applying communication frameworks (BLUF, STAR, Pyramid, SCQA, Diataxis) [source]
- Onboarding accounts (30-60-90), managing escalations, navigating stakeholder dynamics [source]
- Benchmarking SaaS metrics, calculating NRR, or scoring customer health [source]
Skill guidance
- Treat tam-expertise-context.md in this directory as the source of truth for frameworks, templates, and benchmarks. [source]
- Prefer the frameworks, checklists, templates, and benchmarks in the context before improvising. [source]
- Cross-reference with tam-reference for MongoDB Premium Services specifics. [source]
- Cross-reference with case-tracker for case management specifics. [source]
- Apply the Diataxis framework for document structure and BLUF/Pyramid/STAR for communication. [source]
- SaaS benchmarks are 2025-2026 vintage; verify current figures for customer-facing deliverables. [source]
Common mistakes
- Mixing Diataxis types: a runbook (how-to) that drifts into explanation, or a reference doc that tries to teach via tutorial. [source]
- Unoperationalized RYG scores: every score state needs a mandatory action, not just a color. [source]
- Benchmarks without recommendations: presenting a number without a prescriptive next step. [source]
- Score inflation: defaulting accounts to Green without data-backed justification. [source]
- Single-audience framing: writing for engineers when the deliverable serves both engineers and executives. Use layered structure: exec summary → findings → technical appendix. [source]
Children
- Account Health Assessment (frontier)
- EBR and QBR Preparation (frontier)
- Churn Risk Analysis (frontier)
- Customer Success Frameworks (frontier)
- MEDDPICC and NRR Metrics (frontier)
Frontier under this node: Account Health Assessment, Churn Risk Analysis, Customer Success Frameworks, EBR and QBR Preparation, MEDDPICC and NRR Metrics