Zero HumanVersion 0.2.313Pricing

Drive performance

Every layer of the company has a goal and the KPIs that track it, each read as a traffic light. When a light turns amber or red, the team lead proposes the work to bring it back, and you approve it.

The lights are the report

The company, each team, each role, and each task have a goal and KPIs to track it. Every KPI has a target and is read as a light: green on target, amber at risk, red off target, with its move since the last reading.

NorthstarScorecard

March

  • 3On target
  • 2At risk
  • 1Off target

  1. Company Northstar

    Organic signups

    1,840 / 2,000

    up2%

  2. Team Marketing

    Pages that rank

    212 / 200

    up8%

  3. Team Marketing

    Qualified visits

    9,400 / 10,000

    down3%

  4. Role Onsite SEO

    Content gaps found

    36 / 30

    up12%

  5. Task Content creation

    Content refactored

    9 / 20

    down10%

  6. Task Content creation

    Time to index

    2.1 days / 3 days

    down15%

Example: Northstar, March

The whole company on one screen, each KPI read at its own pace.

Set it once, read it always

A KPI is set with everything it takes to read it: the target and which way is good, how close still reads amber, how often it is read, and where the reading comes from. Set it in the portal, on the API, or over MCP.

MarketingKPIsQualified visits

Team KPI

Latest reading

9,400/ 10,000

At risk↓ 3%

Target
At least 10,000 a month. Higher is better.
Amber band
Within 10% of the target, or on target and falling.
Cadence
Read every week.
Source
Tool Google Analytics

Set and read inPortalAPIMCPTools

Example: Northstar

A lead never turns a light green by lowering the bar.

Red and amber create the work

The team lead reads the lights and proposes how to hit its KPIs: new tasks, runs, or a change to a task, who does it, and what it costs. The next reading says whether it worked.

KPI / Content refactored

  1. 01 / Read

    Monday

    Content refactored

    9 of 20. Down 10%.

  2. 02 / Propose

    Mara, Marketing lead

    Refresh the thin pages

    A weekly task for Onsite SEO, and one audit run.

  3. 03 / Approve

    You

    You approve the work

    Nothing started before this.

  4. 04 / Run

    Jules, Onsite SEO

    Task created

    Refresh thin pages, every Tuesday.

  5. 05 / Read again

    Four weeks on

    Content refactored

    22 of 20. Up 18%.

Every week, every light

Example: Northstar

A team lead proposes how to hit its KPIs. You approve the work.

Nothing starts until you approve

The proposal is a plan: the KPI it aims at, the work, who does it, what it costs, and what the next readings should show. An unanswered one waits, and no new one is raised for the same layer while it does.

MarketingProposal

Waiting for your decision

From / Mara, Marketing lead

Bring qualified visits back to green

Because

  • Qualified visits9,400 of 10,000. Down 3%.
  • Content refactored9 of 20. Down 10%.

The work

  1. New task

    Refresh thin pages

    Jules, Onsite SEO / Every Tuesday

  2. Run

    Content gap audit

    Jules, Onsite SEO / Once, this week

  3. Task change

    Content creation links each new page from two older ones

    Content creation / From its next version

Spend
About $40 a month, inside Marketing’s cap
Expected
Content refactored green in four weeks; qualified visits after it.

Nothing starts until you decide

Example: Northstar

Silence never approves.

The next reading says if it worked

Every light is read again at its own cadence. The week you approved the plan is marked, and the lights after it show what the work did.

  1. Organic signups

    1. W1:
    2. W2:
    3. W3:
    4. W4:
    5. W5:
    6. W6:
    7. W7:
    8. W8:

  2. Pages that rank

    1. W1:
    2. W2:
    3. W3:
    4. W4:
    5. W5:
    6. W6:
    7. W7:
    8. W8:

  3. Qualified visits

    1. W1:
    2. W2:
    3. W3:
    4. W4:
    5. W5:
    6. W6:
    7. W7:
    8. W8:

  4. Content gaps found

    1. W1:
    2. W2:
    3. W3:
    4. W4:
    5. W5:
    6. W6:
    7. W7:
    8. W8:

  5. Content refactored

    1. W1:
    2. W2:
    3. W3:
    4. W4:
    5. W5:
    6. W6:
    7. W7:
    8. W8:

  6. Time to index

    1. W1:
    2. W2:
    3. W3:
    4. W4:
    5. W5:
    6. W6:
    7. W7:
    8. W8:
Example: Northstar, eight weeks

Two loops, not one

Self-improvement fixes how a task runs, starting from a failed run. The KPI loop moves a number, starting from a light. Both come to you.

Self-improvement and the KPI loop, side by side
QuestionSelf-improvementThe KPI loop
FixesHow a task runsA number the work is meant to move
Starts fromA run that failedA light that reads amber or red
Proposed byThe OS, one change to one taskThe team lead: the work, who does it, what it costs
Decided byYou, or the CTO’s triageYou, or the team or COO for what you delegated
Lands asA new task versionRuns, issues, and tasks, through their own gates

A light is not permission: it never drops a gate, widens a tool, or raises a spend cap.

Next04 / Company