Practical AI for small teams: where to start (and where not to)
Skip the moonshots. The fastest ROI from AI for most businesses is unglamorous, narrow, and close to a workflow you already run.
Every team we talk to wants to "use AI." Almost none of them need the thing they first ask for. The wins aren't moonshots — they're narrow, boring automations sitting next to a workflow you already run every day.
Start where the pain is repetitive
The best first project has three traits:
- High frequency — it happens many times a day or week.
- Low stakes per instance — a mistake is annoying, not catastrophic.
- A human still in the loop — AI drafts, a person approves.
Think: summarizing inbound requests, drafting first-pass replies, extracting fields from documents, tagging and routing. Unsexy, and exactly where the ROI is.
Where not to start
Avoid anything that's customer-facing, irreversible, or judged on being right every time as your first build. That's how pilots become cautionary tales. Earn trust on the low-stakes stuff first.
Build the boring plumbing
The model is rarely the hard part. The durable value is in the plumbing around it: clean data in, a review step, logging, and a way to measure whether it's actually saving time. That's the part we obsess over — because it's the part that decides whether the thing survives past the demo.
Curious where AI would actually pay off in your operation? Tell us what you're trying to do and we'll point you at the straightest line.