Your one-page metric system this week

Everything in this piece collapses into a single page you can build this week and then hand to your CRM and your AI agents to keep current on a loop. The whole point is that it is small enough to actually run, so here is the assembly, step by step.

Write the five rates and find the constraint

Start by writing your five stage-to-stage conversion rates in order, down the page: visitor-to-lead, lead-to-MQL, MQL-to-SQL, SQL-to-opportunity, opportunity-to-closed-won. Pull the real numbers from your CRM, not the benchmarks, because the benchmarks are a reference and your funnel is the truth. Multiply them together to get your end-to-end conversion, then circle the lowest rate. That circle is your constraint, the one joint worth working this quarter, and finding it is the single most important thing on the page.

Set coverage and velocity

Next, compute the two numbers that govern pipeline and output. Set your pipeline coverage from your real win rate rather than a borrowed three-times rule, so the pipeline you carry is sized to how often you actually win. Then compute your sales velocity, qualified opportunities times deal size times win rate, divided by cycle length, and make that your weekly output number, the one figure you check every Monday to know whether the machine is generating revenue. Coverage tells you whether you have enough in the pipe, velocity tells you whether the pipe is producing.

Pick one OMTM and one experiment

Now narrow to a single focus. Pick the one constraint metric you circled and commit to it as your one metric that matters for the next two to four months, tied to the bottleneck you found. Define one experiment to move it, the single change you believe will lift that rate, and decide in advance how you will prove on the real surface that it moved. Not busy work across the whole funnel, one constraint and one experiment, run to a result you can verify.

Bin the vanity counts and automate the rest

Finally, take everything that failed the one-line test, the lead counts, the traffic totals, the activity tallies, and bin it from the decision dashboard. It can live on a report for describing the business to others, but it has no place on the board you steer by. What remains is five rates, a coverage figure, a velocity number, and one focus metric, and all of it is computable. Let your CRM and your AI agents calculate the five rates on a loop, surface the velocity each week, and flag when the constraint moves, so the page maintains itself and you spend your attention on the decisions rather than the arithmetic.

That is the system. Not a richer dashboard, a thinner one, built on rates instead of counts, pointed at the single weakest link, and run on a loop. Build the growth machine, then measure the one thing throttling it, and fix that. The constraint will migrate, and you will follow it, quarter after quarter, which is what running growth well actually looks like.