About this skill

Problem Solved

Restaurant SaaS teams often track revenue, retention, and customer cost as separate reports, without a clear path from metric movement to action. saas-analyzer treats ARR, MRR, LTV, CAC, and NRR as one diagnostic frame, helping analysts define the business question, choose the right method, and rank concrete next steps.

How It Works

It follows a problem definition → framework matching → solution generation → review loop workflow:
- Problem framing: extract the key question from context and data instead of applying a generic template.
- Metric analysis: load references/ methods for core, applied, and advanced questions as needed.
- Action output: surface Top 3 priorities with owner, task, and expected timing.
- Review tracking: use assets/ templates and scripts/saas_metrics.py to calculate and follow up.

Boundaries

The source is closer to a general SaaS metrics coach. For restaurant operations, add store-level, delivery-platform, inventory, and seasonality context. When missing data is filled with industry baselines, the assumption must be explicitly labeled.

Screenshots

Use Cases

A restaurant SaaS ops lead notices MRR decline and needs to split churn, renewal, new deals, and ARPU impacts.
A BD owner prepares quarterly CAC, LTV, and NRR summaries, then ranks Top 3 investment priorities.
A product owner analyzes trial-to-paid blockers and sets 2-4 week review checkpoints.
A finance analyst uses `saas_metrics.py` to validate ARR, MRR, and NRR calculation definitions.

Best For

Restaurant SaaS ops leads who need to explain weekly MRR, renewal, and churn movements.
SaaS finance analysts who need to turn CAC, LTV, and NRR tables into decisions.
BD or sales owners who need quarterly prioritization and payback expectations.
Product owners who need trial-to-paid blockers turned into owners, actions, and review cycles.