Joy Santos · Systems architectureCase study · client data removed
Sit Write Here · Path to Publication

Nine months per author, running on triggers, not on memory.

The backend behind a nine-month author program, rebuilt inside the tools the business already paid for. Every client is one row in a registry, every stage moves on an event, and the team steps in only where judgment is the job.

80%
Manual tasks automated
~65%
Less admin workload
6 → 40
Clients, same team
0
Recurring errors after rollout
01 · The client journey

Watch one author travel nine months

Select any stage to see what runs inside it, what moves it forward, and what it writes to the record.

PEOPLESTAGESSYSTEMSRECORDSEEP2P REGISTRY · ONE ROW PER CLIENTstage · advisor · program dates · word allowance · meeting date · submissions · send log · daily snapshotDaily snapshot · 6amone row per client per day, history keptDashboards count every client by stageleadership reads the state · nobody compiles a reportC-27
Handoff on an eventHuman gateWrite to the recordVisibility loop

Runs
Moves on
Gate
Writes
Stack
The pipeline · read-only

Every author, every stage

Sample rows with client details removed. The board is the Asana pipeline and the registry, not a separate tracker.

Waiting on a person
Completed
0
Client records retyped

Sample rows. In production the counts come straight from Asana dashboards and the registry snapshot.

01 / 11