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.
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.
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.
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
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.