The unglamorous workflows that compound into your team's biggest week.
For service businesses with great clients, working processes, and a 15-hour-a-week admin loop they can't get out of.
[ industry editorial photo ]
— Editorial photo: a busy but calm small-office scene — desk phone, notepad, mug. Or a service worker's hand on a tablet at a counter. Real, lived-in, warm tones. Avoid stock 'call center wearing headset smiling at screen'.
Why SMB services is a fit
This is some of the most satisfying work I do — partly because the ROI is so obvious. A four-hour-a-day manual loop is a four-figure-a-month problem dressed up as “that’s just how we do it.”
The brief is usually small, the team is usually close to the work, and the impact is usually felt in the first invoice cycle.
What I typically build for SMB services
- SMS distribution systems with reply tracking and intent classification (see ClickMeCars →)
- Call routing and tracking built on Twilio, with per-client config (see Lasting SEO →)
- Status-update automation — the “where’s my…?” emails and SMSes that don’t need a human writing them
- Custom admin UIs for ops teams who’d rather click than swivel-chair between five tools
How engagements usually shape up
Small, sharply scoped, paid back in weeks. A typical first engagement is 2–4 weeks of work. If it goes well, there’s usually a clear second engagement waiting — but I’d rather you book the second one because the first one delivered, not because we tied you into a retainer.