Zero HumanVersion 0.2.313Pricing

You’re in full control

The team runs the day inside lines you draw: which calls come to you, how much it may spend, and how fast you hand the routine on. What you approve is exactly what runs, and nothing approves itself.

Two different questions

A tool’s permission is what its connection can do. A gate is whether this output may happen. A member whose GitHub connection can merge still waits at the gate before a merge goes out.

Tool permissionWhat the connection can do

ToolsGitHub

Bound for Engineering

  • Read the repositoryGranted
  • Open pull requestsGranted
  • Merge pull requestsGranted
  • Change repository settingsNot granted

GateWhether this output may happen

GatesWaiting on you

github.merge_pull_request

Waits on: You

Merge “Fix page titles” to production

4 files, every check green

Waiting for your decision
Example: Northstar

You choose the gates

Each kind of action runs freely, or waits on the team lead, the COO, or you, and every one of them is yours to move. When nobody answers, the work is nudged, handed on, or cancelled.

ControlGates

Northstar

  1. Research, drafts, and notes

    Waits on: Runs freely

  2. Reply to a support tickethelpdesk.reply

    Waits on: Team lead

  3. Email customersUnder 100 peopleemail.send

    Waits on: COO

  4. Email customers100 people or moreemail.send

    Waits on: Ask me

  5. Publish to the websitecms.publish

    Waits on: Ask me

  6. Merge to productiongithub.merge_pull_request

    Waits on: Ask me

  7. Spend in one runOver $50

    Waits on: Ask me

If nobody answers

  • Nudge me, then cancel after 72 hours (chosen)
  • Hand it to Casey, the COO, after 24 hours
  • Approve on silenceNot an option
Example: Northstar

Silence never approves.

Approve the payload, not a summary

A gate stores exactly what would go out before it asks: the post, the email, the payment, the screen about to submit. You read that, you decide on that, and that is what runs.

GatesWaiting on you

Marketing / Ava, Content editorWaiting 2 hours

Publish “What changed in March pricing”

Leaves the building: goes live on northstar.com

Waiting for your decision

The stored payloadStored at 09:05

cms.publish

title
What changed in March pricing
slug
/blog/march-pricing
body
In March every plan moved to one price per seat. Here is what changes for you, and what does not.
length
1,240 words, 3 images, alt text on each
menu
Replaces /blog/february-pricing
status
published

Approve sends this payload as stored. Reject sends nothing.

Example: Northstar

What you approve is exactly what runs.

The tightest cap wins

Runs use your own model key, under caps you set on the enterprise, a team, a member, a role, or a task: by the day, the month, or the run. The tightest cap in the chain wins, and a run pauses before its next paid call. A member operating a system stops the same way.

Spend

Today

Check search rankingsJules / Onsite SEO

Spend paused

Paused at 06:14, before its next paid call

The caps on this run

  1. EnterpriseNorthstar

    $50 a day

    $31.20 spent

    $18.80 left

  2. TeamMarketingTightest

    $15 a day

    $15.00 spent

    $0.00 left

  3. MemberJules

    $20 a day

    $11.40 spent

    $8.60 left

  4. RoleOnsite SEO

    No cap set

  5. TaskCheck search rankings

    $0.50 a run

    $0.21 spent

    $0.29 left

Your model key / caps reset at midnight

Example: Northstar

Raise the cap, and the paused run carries on.

Loosen the loop at your pace

Start with every decision coming to you. As the team earns it, hand calls to a lead or the COO, and keep the ones you want. Anything you hand on, you can take back.

  1. Week 1

    6 ask you

    Everything that leaves the building asks you

    Asks you

    • Support replies
    • Customer emails
    • Social posts
    • Publishing
    • Merging
    • Spend over the cap

  2. Month 1

    5 ask you

    Support replies go to the team lead

    Asks you

    • Customer emails
    • Social posts
    • Publishing
    • Merging
    • Spend over the cap

    Handed on

    • Support replies to Sam

  3. Month 3

    4 ask you

    Small emails and social posts go to the COO

    Asks you

    • Big emails
    • Publishing
    • Merging
    • Spend over the cap

    Handed on

    • Support replies to Sam
    • Small emails to Casey
    • Social posts to Casey

  4. Month 6

    3 ask you

    What is left is what you chose to keep

    Asks you

    • Publishing
    • Merging
    • Spend over the cap

    Handed on

    • Support replies to Sam
    • Emails under 100 to Casey
    • Social posts to Casey
Illustration: Northstar’s first six months

You set the pace. Nothing changes until you do.

Change comes to you

Self-improvement proposes one change to how a task runs, and you approve or decline it. A retro asks whether a team should still exist. Memory is how the company learns, and it replaces neither decision.

  • Self-improvementA task

    How should this task run?

    Keyword research, v4 to v5

    From run 207, which failed: Search Console timed out

    One change: wait, and retry the call once

    Who decidesYou approve or decline

  • RetroA team

    Should this team still exist?

    Marketing, quarterly

    The charter is still true, and 3 of 4 KPIs are green

    Grow: a second content editor

    Who decidesA new charter, a hire, or a close waits for you

  • MemoryThe company

    What have we learned?

    “Lead with the price”

    From your correction on 12 March

    Used by Marketing and Support

    Who decidesEvidence, never permission

    Memory
Example: Northstar

Memory is evidence, never permission.

Yours to close

Closing an enterprise deletes all its resources and memory. That cannot be undone.

Next Pricing