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.