Everything else
ServiceTitan, Zapier, Slack, and Google Workspace get their own pages because I'm in them every day. But they're not the menu; they're examples. The real rule is simpler: if the tool your business runs on has an API, and almost everything does now, it can be wired into the rest of your setup. And for the stubborn stuff that doesn't have one, there are still ways in. The one product I've shipped on my own is a Chrome extension that automates data entry into a state portal that offers no API at all.
The kind of thing that comes up
A sample of the long tail, not a limit. If your tool isn't here, that means nothing:
Accounting tools like QuickBooks, synced with the software the work actually happens in, so nobody retypes invoices.
Form builders, website forms, and estimate-request pages, routed into your CRM instead of into an inbox.
Phone and text: missed-call texts, appointment reminders, and the follow-up messages that never get sent by hand.
Review platforms, so every finished job asks for the review and a bad one pings you immediately.
The web portals with no API at all, automated at the browser with a Chrome extension, the same way I built my own product.
And the one-off glue: the weekly report nobody wants to build, the file that has to move from here to there, the small script that replaces a recurring chore.
The honest boundary isn't which logo is on the tool. It's whether the task is repetitive enough to be worth automating, and that's exactly what the fit call sorts out.
Not sure what to automate first?
Browse the full list of what I build, or read what an automation consultant actually does. If your tool is obscure, bring it to the call anyway; the obscure ones are usually the fun part.
One 15-minute call. Bring the task that keeps stealing your hours, and I'll tell you straight whether it can run itself.