msp-metrics

Calculates MSP business health metrics and guides client repricing or exit decisions.

75|17|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/RTFM-IT-Services-LLC/msp-claude-skills --skill msp-metrics-rtfm-it-services-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: msp-metrics
Source: https://github.com/RTFM-IT-Services-LLC/msp-claude-skills/tree/main/skills/msp-metrics
Command: npx skills add https://github.com/RTFM-IT-Services-LLC/msp-claude-skills --skill msp-metrics-rtfm-it-services-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? MSP owners often lack a disciplined way to measure whether clients are profitable, whether ticket loads are healthy, and when to reprice or exit a bad relationship. This skill turns PSA ticket and agreement data into a small set of monthly numbers tied to concrete decisions. ## Core Features & Use Cases - Monthly Owner Review: A 30-minute checklist covering MRR delta, effective hourly rate per client, tickets per endpoint, SLA attainment, aged receivables, capacity utilization, and pipeline glance. - Client Health Scorecard: A quarterly green/yellow/red rating across profitability, ticket load, payment, security posture, and relationship dimensions that feeds QBR preparation. - Fire-or-Fix Framework: Decision paths for underpriced clients, environment-driven ticket load, refused security baselines, chronic late payment, and abusive behavior, with escalation into repricing, waivers, or offboarding. - Use Case: An owner notices a client's effective hourly rate has been below the pricing floor for two quarters; the skill routes the conversation through the QBR, the repricing letter through client comms, and the exit path through offboarding if the client refuses. ## Quick Start Ask Claude to run the monthly owner review using ticket time entries and agreement data from your PSA, flagging any client below the floor-equivalent rate.

Frequently Asked Questions about msp-metrics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I measure MSP profitability per client?

Divide the client's monthly fee by hours logged that month to get the effective hourly rate, then compare it against the cost floor in your pricing model. One bad month is noise; two consecutive quarters below the floor triggers a repricing conversation.

What is a good tickets per endpoint benchmark for an MSP?

Industry data puts an average MSP at 0.75 to 1.0 tickets per endpoint per month and top performers at 0.2 to 0.5. A client sustained above roughly 1.5 signals a broken environment, a behavior pattern, or a mispriced agreement.

When should an MSP fire a client?

Default to fix first: reprice underpriced clients, quote remediation for environment-driven ticket load, and document security refusals with waivers. Exit when the math stays red after repricing, refusals create existential risk, or the client mistreats staff.

Does this skill work without a PSA ticketing system?

No. Every figure is computed from PSA ticket time entries and agreement data, so helpdesk hygiene rules like no work without a ticket and same-day time entries are prerequisites for trustworthy numbers.

How does the client health scorecard relate to the QBR?

The scorecard is internal only and rates clients green, yellow, or red across five dimensions each quarter. It informs QBR preparation but never appears in the client-facing QBR document itself.