What is the scoreboard in InstinctGTM?

Part 3 · Operate

The scoreboard

What you did today, what it produced, and whether the lane is worth another week.

01What it is

One screen, opened at the end of the day. It shows progress against the targets you set, what those actions produced, and a running total since you started. Half of what it counts comes from the product; the other half you log yourself in one tap.

02Why it exists

Outbound is a lagging-indicator game. The work happens for weeks before the first result arrives, and that gap is where most founders stop — not because the approach was wrong, but because nothing visible happened for long enough that continuing felt irrational.

The scoreboard closes the gap by making the leading indicators visible today. Those are the part fully inside your control: how many people you contacted, how many posts went out, how many calls you took. They can be true on a day when nothing has closed, and seeing them true is what makes the next day happen.

The risk in building this is the obvious one. A screen designed to make daily work feel worth doing can make an unproductive month feel productive, which is worse than no screen at all: it spends your weeks and tells you it was fine. So outcomes sit directly beneath activity rather than on another page, and a lane that hits its target repeatedly and produces nothing is named as one.

03How to use it

01Choose the lanes that match your week and set a daily number for each. We suggest a starting point from how far along the venture is; change any of it.
02Set your working days. Days outside the pattern are skipped rather than scored, so a Sunday never shows as a failure.
03Work the day. Anything the product can see is counted for you; log the rest with the Log button, which is on this screen and on Today.
04Open it in the evening. Read the outcomes row next to the activity row, not instead of it.
05When a lane has hit target for three weeks and produced nothing, change it or stop it. The screen will say so, but stopping is your decision.

04What good looks like

You give it: A founder with LinkedIn and cold email switched on, targets of 15 touches and 20 emails a day, working Monday to Friday.
You get: Four full columns in the week strip, a run of four days, 140 actions in the ledger, and two positive replies against 60 emails.
Why: Both lanes are counted from tables the product already writes: LinkedIn touches from outbound touchpoints, emails from sends that actually left the mailbox. Nothing had to be logged by hand for those two, and the reply rate is computed from the same rows rather than estimated.

Derived from the rules in the code

05What weak looks like, and what it costs

You give it: A founder who set a target for calls taken and audits recorded, and logged nothing for two weeks.
You get: Both lanes read zero, and the screen says nothing measures them rather than showing a bare zero next to a target.
Why: Neither lane has a source in the product. A zero there means no entries, not no work, and printing one without saying so would make the founder look worse to themselves than they are.