The SmallOffice Brief Subscribe
Operations
Wed, Oct 28, 2026
Operations

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.

How it wentThe 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.
Try it · based on the source's workflow
Turn this weekly procedure into a playbook an AI can run: [procedure name]. Write the steps in plain language, in order, with the exact source for each input: [files, tools, accounts]. Mark every step that sends, pays or deletes as stop-and-ask: show me the finished work first and wait for my approval. Run it once on last week's data and show me the output next to the result I did by hand, so I can check it step by step.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
Source: Nhan Dinh on X · Topic: Operations · Tool: not named in the source · Other or custom cases
ShareXLinkedInForward to a friend
Cite this case30 playbooks, run from written steps. The SmallOffice Brief, Wed, Oct 28, 2026. https://smalloffice.space/case-30-playbooks-run-from-written-steps
Share this win
30 playbooks, run from written steps — from The SmallOffice Brief, a daily brief of real AI cases for small businesses: https://smalloffice.space/case-30-playbooks-run-from-written-steps
One bot, one job

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: ______________________________

Before and after

Two lines from this case, side by side. No new figures.

Before · as the case describes it

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.

After · as the source reports 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

Send this case to my inbox

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.

Additional Details

Published: Wed, Oct 28, 2026 · Updated: Wed, Oct 28, 2026 · Topic: Operations · Tool: not named in the source · Other or custom cases · Source: Nhan Dinh on X
Next case: 412 calls answered, every one. Get cases like this in your inbox each morning.
5 cases in your inbox each morningSubscribe free