The blog
Short, useful, and written like we're talking across the table. Cash flow, AI agents, the $100K Challenge, and the patterns we see in every audit we run.
We moved our agents off the platform we started on, partway through real client work. The reasons — and the one principle that made it a re-point instead of a rewrite.
Everyone wants an AI that improves over time. Almost nobody wants one that quietly rewrites its own instructions overnight.
More context sounds like a smarter agent. Past a certain line it costs you twice — once on the invoice, and once on the pause before it speaks.
The texting feature takes an afternoon to build. Getting permission to actually send it takes about a week. Here's how not to get caught by that.
It sounds like the obvious first question for a dispatch line. It's also the fastest way to make your priority queue meaningless.
An eighteen-minute call once produced nothing, because the agent tried to hand off the whole job at once. Fixing that changed how we build every agent that has to write something down.
Speech-to-text guesses at names, and it guesses confidently. The small rule that keeps a misheard name from becoming a bad record, a bounced email, and a duplicate customer.
A client asked us to build a system that would work out when his customers were due for service. We started designing it — then found his software had been doing it for two years.
It isn't a wrong answer. It's the half-second of silence before the agent starts talking — and here's how we design around it.
Yes — but there's a right way and an illegal way. Here's the line we hold on every agent.
Give an AI create-only access and it "fixes" problems by making duplicates. The three guardrails that keep it clean.
We tried adding filler words to make an agent feel natural. It sounded worse. Here's what actually moves the needle.