top of page

The Weekly Scorecard for a One-Person Business (With a Free Template)

Writer: Brian Lathe
Brian Lathe
6 days ago
5 min read

Updated: 5 days ago

The Weekly Scorecard for a One-Person Business (With a Free Template)

Of all the tools in Ryan Deiss's Scalable Operating System, the one that translates to a business of one with the least surgery is the company scorecard. It also happens to be the one most solo operators get wrong — usually by building a dashboard instead.


Credit where it's due: Deiss's rules for the scorecard are good, and they're stricter than they look. In his public case study he lays out four of them. Keep it simple — his team tried expensive dashboard software and went back to a plain spreadsheet, because the fancy version didn't get used. Weekly, not real-time — real-time numbers are too noisy to act on, and monthly numbers arrive too late to fix anything. Enter the numbers by hand — in a team, that forces the owner of each number to actually know it and arrive with a plan instead of a surprise. And let the metrics mirror how value flows through the business — pick them from the actual steps a customer moves through, not from whatever a software tool happens to graph. Vanity metrics don't survive that test.


His status rule is the part worth stealing word for word, because it's the part everyone else gets wrong:

  • Green — on or ahead of target.

  • Yellow — behind target, but there is a plan to catch up.

  • Red — behind target, and there is no plan.

Read that again. In Deiss's system, a bad number is not red. A bad number with a plan is yellow — that's a business being managed. Red is reserved for the one thing that actually kills small businesses: a problem nobody has decided what to do about. Management, in his formulation, is a single job — turn reds into yellows (force a plan), and yellows into greens.


What changes when the team is you

A team scorecard can carry a metric per department. You can't, and you shouldn't try. For a one-person business, the whole scorecard is five to seven numbers, maximum, and they should cover the five jobs every solo business does whether it admits it or not:

  1. Getting known and getting leads — new contacts or inquiries this week.

  2. Sales conversations — real conversations with potential buyers, not likes.

  3. Delivery — the work you promised, shipped or completed.

  4. Content — the assets you published that keep selling while you sleep.

  5. Money — cash actually collected. Not invoiced. Collected.

One or two of those areas might earn a second metric — if follow-ups are your leak, count follow-ups. But the moment the page needs scrolling, it stops being a scorecard and becomes another dashboard you'll abandon by March. Five to seven. One page. Done.


The hand-entry rule survives the translation, too, but for a different reason. You don't have a team to surprise in a meeting. What you have is a talent for not looking. Typing last week's numbers in yourself, once a week, takes a few minutes and makes it impossible to carry a comfortable story in your head that the numbers don't support. In my own system the desks collect most of the data as the week happens — but the scorecard page is still one page, filled in weekly, and I still have to sit in front of it. The collection can be automated. The looking can't.


The template — the whole thing, right here

This is the complete template. Copy it into a spreadsheet, a notes app, a notebook — the tool doesn't matter. Nothing is held back — this exact table is the whole thing.


Example week — every number below is invented, purely to show the format:


| Metric | Target | Actual | Status | Plan | |---|---|---|---|---| | New contacts / leads | 10 | 12 | Green | — | | Sales conversations held | 5 | 3 | Yellow | Two prospects went quiet; send both a follow-up Thursday, book calls for Friday | | Deliveries completed | 4 | 4 | Green | — | | Pieces of content published | 2 | 0 | Red | (No plan yet — this row is not allowed to stay like this. See below.) | | Follow-ups sent | 8 | 8 | Green | — | | Cash collected this week | (your weekly target) | (actual) | Yellow | One invoice unpaid; reminder goes out Monday with a new due date |


The solo twist: the review ends when the reds have plans

Here's where a business of one has to be harder on itself than a team does. In Deiss's company, a red metric gets its plan in the weekly meeting, because there's a room full of people whose job includes fixing it. In your business there is no room. There's you, on a Sunday night or a Monday morning, looking at a red row — and the easiest thing in the world is to close the tab and let it ride another week.


So the rule for one is absolute: the weekly review is not over until every red metric has a written plan in its row. Not a good plan. Not an inspiring plan. A written one — a next action, small enough to actually do, with a day attached to it. The content row in the example above is red precisely because its plan cell is empty. Filling that cell — "draft the half-finished post Tuesday night, publish Wednesday" — turns it yellow on the spot, even though the number is still zero. That is the whole philosophy in one move: you will have behind weeks for the rest of your business life. Behind is weather. Behind with no plan is the disease.


And keep the review to one sitting, once a week. Don't check the numbers daily — daily checking is just anxiety with a spreadsheet, and it teaches you to react to noise. Deiss says real-time is too noisy for a company with a leadership team. It's doubly true for a person with a day job and a finite supply of evenings. The week's numbers, the week's reds, the week's plans, one honest look — then close it and go do the plans. In my system that's also when I count the number I care about most: how many times the business had to tap my shoulder that week. It sits on the same page. Watching it fall is how I know the system — not my willpower — is getting stronger.


Start this week, with last week's numbers, even if they're embarrassing. Especially if they're embarrassing. A scorecard you start ugly is worth more than a perfect one you start someday.


SuccessBrian OS is not affiliated with Scalable.co or Ryan Deiss. The scorecard rules described above are from Scalable's public case study, read in November 2026 — the translation to a one-person business, and the example numbers, are mine. If you run a $2M+ business with a team, their full system may genuinely fit you; this page is for the rest of us.


The scorecard also runs inside SuccessBrian OS — and it is free

The template above works on paper. It also works inside SuccessBrian OS, the system I run my own one-person business on. SuccessBrian OS is free.


In plain words: once a week, you type in the five numbers — new leads, sales talks, work delivered, things shipped, cash in. The system keeps them, shows you which ones hit your target and which ones fell behind, and remembers the plan and the promise you made. No spreadsheet to keep alive. No memory required. The system remembers for you.


It costs nothing. There is no form to fill out and nothing to buy. Download it and use it:



Read more from Brian Lathe on Substack


This blog is one room in a bigger house. My main writing lives on Substack - longer pieces, new posts first, always free to read: Brian Lathe on Substack.

 
 
 

Recent Posts

See All
Do You Need an Integrator If You're a Team of One?

Do You Need an Integrator If You're a Team of One?If you've read anything about EOS — Gino Wickman's Entrepreneurial Operating System, from Traction — you've met the famous pair. The Visionary is the

 
 
 

Comments


Talk to Brian

on WhatsApp

Appointment booking opens soon.

Questions about this article — or about SuccessBrian OS? Text me here.

Texting is best — please don't call. Calls are by confirmed appointment only.

Talk to Brian

Questions, or want a system like this working for your business? Message me directly.

What is SuccessBrian OS?

One system that runs a solo business while its owner lives his life: a checked second brain, a crew of AI agents, and one calendar that never forgets. The whole system is free and open.

Get new posts by email

I build this in public and post the progress. Follow along on Substack.

bottom of page