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