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

A dozen decisions, cleared in minutes

A freelance web developer describes his setup on X. One coordinator agent session reads every mail, routine report and database event across his client work. Each client has its own standing session that keeps that client's context separate. He does not read threads. Every decision the agents surface reaches him as one tappable question, with a recommended answer first. He calls it a team that does the legwork and asks the right question at the right time. It is not autonomous, on purpose.

How it wentHe says he clears a dozen decisions in the time one Slack thread used to take. He gives no money figure. The two ideas he stresses are simple: one assistant per client, so context never mixes, and decisions as one-tap questions with the recommendation first.
Try it · based on the source's workflow
Act as my coordinator across [number] client projects. Keep one separate context per client: [client list and where their files and mail live]. Read new mail, reports and [system] events for each client. Do the legwork on routine items and log what you did. Bring me each real decision as one short question with your recommended answer first and the one fact that matters. Never send, spend, post or delete without my tap. Send me one list at [times]: decisions waiting, work done, anything stuck.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
Source: smgdkngt on X · Topic: Operations · Tool: not named in the source · Other or custom cases
ShareXLinkedInForward to a friend
Cite this caseA dozen decisions, cleared in minutes. The SmallOffice Brief, Wed, Oct 28, 2026. https://smalloffice.space/case-a-dozen-decisions-cleared-in-minutes
Share this win
A dozen decisions, cleared in minutes — from The SmallOffice Brief, a daily brief of real AI cases for small businesses: https://smalloffice.space/case-a-dozen-decisions-cleared-in-minutes
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

A freelance web developer describes his setup on X. One coordinator agent session reads every mail, routine report and database event across his client work. Each client has its own standing session that keeps that client's context separate. He does not read threads. Every decision the agents surface reaches him as one tappable question, with a recommended answer first. He calls it a team that does the legwork and asks the right question at the right time. It is not autonomous, on purpose.

After · as the source reports it

He says he clears a dozen decisions in the time one Slack thread used to take. He gives no money figure. The two ideas he stresses are simple: one assistant per client, so context never mixes, and decisions as one-tap questions with the recommendation 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: smgdkngt on X
Next case: 95% solved, then failing every case. Get cases like this in your inbox each morning.
5 cases in your inbox each morningSubscribe free