How many tools does it take your team to get one order out of the door?
Count them honestly. The first is the system you bought. Then there's a form for requests and a shared folder for the paperwork. Add a group chat for “is this ready yet?” and a Zapier step someone set up 2 years ago. Then the spreadsheet that reconciles all of it. Most growing businesses never chose that stack. It built up one sensible fix at a time.
“Nobody builds a workaround for fun. Each one is answering a question the system couldn't.”
The part I pay attention to
I don't start by asking which tools a business uses. I ask what people do when the tool doesn't help. The answer is almost always a workaround, and every workaround is a requirement in disguise. “We need to know who approved this.” “We need the delivery photo next to the invoice.” “We need to see stock before we promise a date.”
What I'd do before adding another tool
List every workaround, who uses it, and the question it answers. Then group them. Most of them usually point at the same 2 or 3 missing connections. Those are typically an order and its documents, stock and sales, or a request and its approval.
Fixing those connections is a much smaller job than another app. Sometimes it means a connected system that holds those records together, which is what we use AnyDB for. Sometimes it's one integration between tools you already pay for. Either way, start from the workarounds, because they've already done the requirements gathering for you.
Your workarounds are the spec. Read them before you write one.
Where AI fits
Your workarounds are also the job list. Most of them are routine steps a person does because the system can't: copying, checking, chasing. Once the missing connection is in place, those are the first jobs worth giving AI, with a person approving the result.
