The SmallOffice Brief Subscribe
Operations
Mon, Nov 16, 2026
Claude

One phone tap, fix live in 40 minutes

Kevin Champlin runs a software firm with an always-on Mac mini agent built on Claude. Every client request becomes a written proposal first, with scope, estimated hours, and risk. It waits for his approval. There is no path for the agent to approve its own work. Approved code changes ship only as pull requests with required checks. Deploy scripts check that the server matches the merged commit, with a snapshot for rollback. Finished work is booked as tracked time, ready as invoice lines.

How it wentIn the worked example, a client mailed at 7:40 AM about a contact form that had stopped sending. He tapped Approve from a coffee-shop queue. Forty minutes later the fix was live, with checks, merge, and gated deploy done, and the hours booked. The agent works across more than 20 production systems. No total time or money figure is given.
Try it · based on the source's workflow
Turn every client request from [email or text] into a written proposal with [scope, estimated hours, risk] and wait for my approval. Ship approved changes only by [pull request with checks]. Book the time to [client] with a line breakdown, and draft, never send, the client update.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
Source: Kevin Champlin blog · Topic: Operations · Tool: Claude
ShareXLinkedInForward to a friend
Cite this caseOne phone tap, fix live in 40 minutes. The SmallOffice Brief, Mon, Nov 16, 2026. https://smalloffice.space/case-one-phone-tap-fix-live-in-40-minutes
Share this win
One phone tap, fix live in 40 minutes — from The SmallOffice Brief, a daily brief of real AI cases for small businesses: https://smalloffice.space/case-one-phone-tap-fix-live-in-40-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

Kevin Champlin runs a software firm with an always-on Mac mini agent built on Claude. Every client request becomes a written proposal first, with scope, estimated hours, and risk. It waits for his approval. There is no path for the agent to approve its own work. Approved code changes ship only as pull requests with required checks. Deploy scripts check that the server matches the merged commit, with a snapshot for rollback. Finished work is booked as tracked time, ready as invoice lines.

After · as the source reports it

In the worked example, a client mailed at 7:40 AM about a contact form that had stopped sending. He tapped Approve from a coffee-shop queue. Forty minutes later the fix was live, with checks, merge, and gated deploy done, and the hours booked. The agent works across more than 20 production systems. No total time or money figure is given.

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: Mon, Nov 16, 2026 · Updated: Mon, Nov 16, 2026 · Topic: Operations · Tool: Claude · Source: Kevin Champlin blog
Next case: 361 hours a month, €464 a month. Get cases like this in your inbox each morning.
5 cases in your inbox each morningSubscribe free