30 playbooks, run from written steps
Nhan Dinh leads Seller Labs, which makes tools for Amazon sellers. He writes that he runs more than 30 playbooks this way: the weekly revenue sheet, paying recurring vendor invoices, and publishing posts like the one he wrote. Each playbook is a written set of steps, like a standard procedure for a human assistant. On October 5, 2026, he moved his AI work to a newer model by changing one model name in a config file. He rewrote no playbook to do it.
Start with one job only. Fill in the three lines. Keep the bot on that job.
The one job this bot does: ______________________________
What it may do on its own: ______________________________
What it must ask me first: ______________________________
Two lines from this case, side by side. No new figures.
Nhan Dinh leads Seller Labs, which makes tools for Amazon sellers. He writes that he runs more than 30 playbooks this way: the weekly revenue sheet, paying recurring vendor invoices, and publishing posts like the one he wrote. Each playbook is a written set of steps, like a standard procedure for a human assistant. On October 5, 2026, he moved his AI work to a newer model by changing one model name in a config file. He rewrote no playbook to do it.
The result he reports is the system itself: more than 30 repeated procedures run from written steps, and a model swap that needed no rewrite. He gives no time or money figure. His advice is plain: pick one procedure your team runs every week, not the hardest one, and write its steps down first.
The after line is the source's claim, not our measurement.
smalloffice.space · Get a case like this in your inbox each morning. Subscribe free
Read this case on your phone now, and keep it for later. Type your email. We send this case to that address, and you get the next cases each morning too.