Tokens
Track what each role uses in scheduled work, founder conversations and agent handoffs.
Internal case study · 2026
How Zo Liang runs the Liang Crew with written roles, a shared weekly budget and one human approval gate.

Track what each role uses in scheduled work, founder conversations and agent handoffs.
Set priority tiers and schedule work on the Melbourne clock.
Record what was delivered, reviewed and used.
The workforce board brings schedules, quota and delivery into one weekly review. Every recurring job has a priority, a delivery location and a named owner.
HR checks whether spending is ahead of the elapsed week. At normal pace it stays quiet. Under pressure it pauses lower-priority routines first, keeps critical jobs running and reports what can resume after reset.
Source: 2026 internal workforce board snapshot before the weekly reset. Historical percentages describe the team at that time.
Social, Design and Admin accounted for 68% combined. Social’s three scheduled routines used about one share point in total, so the review focused on open-ended activity. Adding Copywriting and HR took the top-five share to 77%. The concentration index was approximately 2,198. Those figures describe spending concentration. Comparing it with adoption requires separate evidence.
All four critical routines matched expected counts.
Approximate counts show runs occurred. Timestamped receipts would be needed to check punctuality.
Several jobs clustered around 8:00. The board proposed staggering them for Zo to review.
The 99.4% reading was a pre-reset snapshot. It shows how tight the week was, without establishing final utilisation.
The board recorded routine counts and usage. It could not establish punctuality or value without timestamps and adoption decisions.
Our delivery KPI
How much work people adopted for the token budget spent.
Illustrative target
45 adopted deliverables ÷ 90 quota points. Calibrate the target to the job and its starting point.
The first board snapshot recorded spend and approximate run counts. It did not record which deliverables Zo adopted, so actual ROT was not calculable for that period. The 0.50 target is a worked example from the case, expressed in adopted deliverables per point of weekly quota.
Mark each delivery as used, revise or park. Compare adoption and spend over the same week before recommending changes to a role. Zo remains the approver.
Pick one recurring deliverable and name the person who approves it.
Record used, revise or park. Review spend, rework and delivery timing together.
Expand a role with evidence, keep watching when evidence is thin, or pause routines while you re-scope.
Pick the first task you want to hand off. Little Liang will help you build the team around it.
