The Weekly Operator Scorecard — what to track in week one

Most Bosses install a Pack and stop watching it. Standing orders fire, some work happens. By month three the Boss can't tell you whether the Pack moved the number it was bought to move. By month six they're guessing. By month nine they're shopping for a new Pack to fix what they could have solved by tuning the one they had.

The Weekly Operator Scorecard fixes that. Six numbers, one Friday a week, fifteen minutes. Without it, the standing order flies blind and you don't notice for months.

Why six numbers, not sixty

Most ops dashboards have sixty fields and zero decisions. The operator scrolls, nods, closes the tab. Theater.

Six numbers works because each one earns a decision on Friday afternoon. Keep, tune, fire, stack. If a number doesn't earn a decision, it doesn't belong on the scorecard.

Fifteen minutes is the only cadence Bosses hold. Thirty gets skipped on busy weeks. An hour gets skipped every week. Eight Fridays of fifteen minutes is a tuning trail. Two missed reviews and the trail goes cold.

Number 1: hours saved this week

Hours you would have spent doing this work by hand, minus hours the Pack cost you to operate.

For each piece of work the Pack ran, write down what it would have taken by hand. Lead Rescue nudged 14 leads at eight minutes each, roughly 112 minutes saved. Subtract what the Pack cost: telemetry, approval queue, one nudge flagged for human eyes. Call it 25 minutes. Net saved: about 1.5 hours.

This tells you whether the Pack is paying back your time yet. Week one is usually break-even. Week three should be clearly positive. Week six should be obvious, because the volume has crossed what one person could hold by hand.

Healthy. Week one: zero to two hours. Week three: two to six. Week six and beyond: five to fifteen, depending on the Pack. Lead Rescue and Outbound Engine run higher. Day One Operator runs lower because the work was always brief.

If it's still negative at week three, the Pack doesn't fit your bleed or you haven't let it run.

Number 2: hours spent operating the Pack

Time you put in to keep the Pack running. Reviewing, approving, fixing, retraining.

Open your calendar. Count any block where you were inside the Pack: approval queue, telemetry, prompt adjustments, a call with the Co-pilot about a parameter. Don't count the Friday review. That's overhead for the system.

This tells you whether the Pack is becoming the operator's second job. If you're spending six hours a week operating one Pack, the recipe is wrong, the harness is wrong, or you're customizing before the Pack has run vanilla long enough.

Healthy. Week one: 30 to 90 minutes. Week three: 20 to 45. Week six: 10 to 25. By week eight, most Bosses are at fifteen minutes per Pack. Climbing instead of dropping means the Pack hasn't settled and you're chasing it instead of the other way around.

Number 3: revenue moved upstream of the Pack

Dollars that flowed because the Pack ran. Booked calls, qualified leads, invoices collected, contracts signed, replies on outbound.

Three buckets. Direct: Get-Paid collected an invoice, count it. Pipeline: Lead Rescue recovered a lead that converted later, count the deal size. Calendar: High-Ticket Close prepped a session that closed, count the deal. If a deal could have happened without the Pack, don't count it.

This tells you whether the Pack pays back its price. The beta self-install path now lives on packs.bossmode.ing: Outbound Engine and PM Engine are $197 beta, and Lead Rescue is free. Trust Pack runs from $14,997. If a Pack is moving five figures per quarter, the math is decided. If it's moving nothing, also decided.

Healthy ranges. Week one: usually zero. Week three: first revenue events start hitting. Week six: most Packs that fit a real bleed are moving 1× to 5× their price every quarter.

Be hard on attribution. If a referral lead came in through your existing channel and Lead Rescue nudged them, that's not Lead Rescue's revenue. Lead Rescue's revenue is the deal that died in your inbox a quarter ago, came back to life on a nudge, and closed.

Number 4: the one thing the Pack got wrong

The worst thing the Pack did this week. Not "could be slightly better." The thing that made you wince.

Find the standing order that landed badly. The Lead Rescue nudge that fired at 4am on a Sunday. The Outbound message that quoted an outdated case study. The Get-Paid follow-up on an invoice already paid. Write it down and note which standing order fired it.

This tells you where to tune next week. The Pack ships with defaults correct for most businesses most of the time. The wrong thing this week is where your buyers, your context, your offer differ from the default. That's the parameter to adjust.

Healthy. Week one will have three or four wrong things, pick the worst. Week three should be down to one a week. Week six, sometimes you go a week with nothing wrong, which means the Pack is meeting your business and you're free to watch the next bleed it's surfacing.

Number 5: the one thing the Pack got right that surprised you

The moment this week where the Pack did something better than you would have done yourself.

The reply Lead Rescue extracted from a lead you'd written off. The outbound message that landed a meeting from a list you'd given up on. The pre-prep doc High-Ticket Close handed you for a session you would have walked into cold. The thing that made you say: I wouldn't have caught that.

This tells you where to stack next. The thing that surprised you is the runway being cleared. Lead Rescue caught the warm reply, now those replies need qualifying or they hit your calendar unfit. The qualifier is the next Pack.

Healthy: most weeks should have at least one. If a Pack isn't surprising you on the upside in any given month, it isn't carrying weight. Running but not earning its slot in the chain.

Save these notes in a separate file. Eight weeks of "right" notes is case-study material for your site, your sales calls, your Case Calls. The boring Friday review writes your testimonials.

Number 6: keep, fire, or stack

A one-word decision for this Pack, this week.

Keep: the Pack is producing its expected output and hours saved are positive. The Pack stays as is, sometimes with a small tune flagged for next week.

Fire: hours saved are zero or negative for three consecutive weeks, or the Pack costs more to operate than it returns. Firing isn't failure. About one in eight first installs gets fired in the first 90 days, usually because the operator picked a Pack the Bottleneck Check would have ranked third instead of first.

Stack: the Pack is working and has cleared a runway for the next bleed. Lead Rescue stacks into Lead Qualifier. Lead Qualifier stacks into High-Ticket Close. High-Ticket Close stacks into Client Kickoff. Five Packs deep, the chain does the work a fractional COO at $7K to $7K–$15K a month would do, and the Packs run while you sleep.

Numbers one through five are the data. Number six asks: now what.

How to run the review in fifteen minutes

The whole review fits on one page. Print it, fill it, file it.

Two minutes: open the telemetry, scroll once, find the worst hit and the best hit of the week.

Three minutes: pull hours saved and hours spent from your calendar and telemetry. A reasonable estimate beats an absent measurement.

Three minutes: pull revenue moved. Cross-reference invoices, calendar, CRM. Be honest about attribution.

Four minutes: write the one wrong thing and the one surprising right thing. Two sentences each, max.

Three minutes: make the keep, fire, or stack call. If it's keep with a tune, name the parameter and the change.

Close the laptop. By week four the review takes ten minutes. By week eight most Bosses run it for two or three Packs at once and it still fits inside half an hour.

The scorecard runs as a doc, a spreadsheet, or a printed page. The Cockpit receipts surfaced in Fly AI track hours saved, hours spent, and revenue moved; pack buyers can run the scorecard manually until their Case Call scopes the next layer. The free manual version runs fine by hand. The discipline beats the dashboard.

Bosses who run this for eight weeks stop guessing. They know which Pack is carrying the chain, which one needs a parameter change, which bleed is next. That's the tune step of the Bleed-to-Build Loop. You can't compound what you haven't measured.

You don't need to become the operator again. You need to be the Boss who sets the standing order. The Pack is the standing order. The scorecard is how you watch it fly.