Read practice revenue as production per DVM and average client transaction × visits, never one alone, so a revenue problem is diagnosed correctly. Reach for this on any revenue question.
Installs into .claude/skills of the current project.
Are you the author of Instrument Production And Act?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-instrument-production-and-act)
---
name: instrument-production-and-act
description: "Read practice revenue as production per DVM and average client transaction × visits, never one alone, so a revenue problem is diagnosed correctly. Reach for this on any revenue question."
---
# Skill: Instrument production and ACT
Revenue is two engines; this reads both before prescribing.
## Step 1 — Compute production per DVM
Total production ÷ doctor-FTEs, by doctor (§3 #2).
## Step 2 — Compute ACT and visits
Average client transaction × visit volume — the other half of revenue.
## Step 3 — Decompose a revenue move
Attribute a change to doctors, production-per-doctor, ACT, or visits — each has a different fix.
## Step 4 — Baseline it
Every figure carries a window and a baseline (§3 #1).
## Output
A two-engine revenue decomposition with the driver of any move named and baselined.
