Why the first project matters more than the first tool
Most owners who get stuck with AI picked a tool that somebody showed them, played with it for a week, and ended up with a subscription that feels like another to-do item. Instead, when AI gives you real hours back, the team stops being nervous about the whole idea, and then we can begin real AI transformation. A chatbot that takes more time from you does the opposite.
The question we ask on every first call
"Where are your people spending time where they're not visible to anyone?" Go department by department and ask two things: what are you doing internally that takes you time and nobody sees, and what's the thing you hate doing?
Write those down for your own business. You'll get a list of ten or fifteen things: re-keying data from one system into another, chasing documents, assembling the same report every month, answering the same questions, scheduling, sending the invoice and then the reminder, and so on.
Three checks before anything gets built
For each task on your list, ask whether it happens every week, whether you could write the steps down for a new hire, and whether the information it needs is in software, like your inbox, a CRM or a spreadsheet. A task that passes all three is ready for automation. A task that needs judgment every single time still needs a "human in the loop", and that's fine, because we can automate all the preparation and follow-up around it.
Before you automate it, try to delete it
This is the step most people skip, and it's the one I'd fight for. Automating a bad process just gives you a faster bad process. We work through a short sequence on every build: Challenge whether the task is really required, Remove every step you can, Improve what's left, Speed it up, and only then Program it. We call it CRISP.
When I took over operations at an importer in New York, the project tracking system was printed paper taped to a board and marked up with a Sharpie. Nobody automated anything. We moved the whole thing to a digital board, and compliance and visibility into every job improved from that change alone. The process had to be right before the software could be, and systems should be designed to evolve over time.
Pick one, build it, and let it pay for the next one
Resist starting three things at once. One task running on its own is worth more than three half-built ones, and you can build on the first success. A recent example: a firearms training academy was taking class bookings by text, then the owner typed each student into a spreadsheet and sent the invoice by hand. Now the form fills the sheet and the confirmation and reminder emails send themselves, and the owner's next question was: what else could work that way?
What if it seems like we can't automate anything?
Sometimes the honest answer is that every task depends on judgment, or the information lives in two people's heads. Then the first project is writing the steps down for the two or three processes the business depends on. This step is unglamorous but necessary, and it can enable us to build some amazing things on top - while increasing the value of your business.
If it sounds tricky, don't worry. We have some tricks of the trade to speed up the process.
What we'd do about it
This is the exercise we run in the free consultation. You show us where your week goes, we score the tasks with you, and you leave with a prioritized list of what to automate first, whether you hire us or not. If the right first step is a simple fix you can do yourself, we'll say so. If you'd rather see it than read about it, our case studies show what a first build looked like for other owners.