The SmallOffice Brief Subscribe
Operations
Thu, Nov 12, 2026
Operations

Nothing goes out without approval

Travis Pugh, a Texas real estate broker, built an operations assistant for the busywork of his practice. It checks his advertising against Texas license rules, so the right name and required notices land where they belong. It keeps his buyer list up to date, sends a morning brief, and tracks deadlines. It drafts marketing, from flyers to outreach scripts. Outreach follows do-not-call rules and calling hours, and drafts get a fair-housing language check.

How it wentHe reports no hours, revenue, or deal figures. The result he states is the setup itself: the busywork runs under one rule, that nothing is sent, posted, spent, or filed without his approval.
Try it · based on the source's workflow
Act as the operations assistant for [brokerage name]. Check each new ad draft against [state license rules]: the brokerage name, license numbers, and required notices must appear as the rules state. Flag any draft that fails, with the exact line and the rule it breaks. Keep the buyer list in [CRM] current from [inbox and forms]. Each morning, send me a brief: deadlines in the next [7] days, new buyers, and drafts that wait on me. Draft marketing in my voice from these examples: [paste]. Screen every draft for fair-housing risk before you show it to me. Never send, post, spend, or file anything without my approval.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
Source: Travis Pugh on X · Topic: Operations · Tool: not named in the source · Other or custom cases
ShareXLinkedInForward to a friend
Cite this caseNothing goes out without approval. The SmallOffice Brief, Thu, Nov 12, 2026. https://smalloffice.space/case-nothing-goes-out-without-approval
Share this win
Nothing goes out without approval — from The SmallOffice Brief, a daily brief of real AI cases for small businesses: https://smalloffice.space/case-nothing-goes-out-without-approval
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

Travis Pugh, a Texas real estate broker, built an operations assistant for the busywork of his practice. It checks his advertising against Texas license rules, so the right name and required notices land where they belong. It keeps his buyer list up to date, sends a morning brief, and tracks deadlines. It drafts marketing, from flyers to outreach scripts. Outreach follows do-not-call rules and calling hours, and drafts get a fair-housing language check.

After · as the source reports it

He reports no hours, revenue, or deal figures. The result he states is the setup itself: the busywork runs under one rule, that nothing is sent, posted, spent, or filed without his approval.

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: Thu, Nov 12, 2026 · Updated: Thu, Nov 12, 2026 · Topic: Operations · Tool: not named in the source · Other or custom cases · Source: Travis Pugh on X
Next case: 12 scheduled tasks, moved to cloud. Get cases like this in your inbox each morning.
5 cases in your inbox each morningSubscribe free