Skip to content
The GrowthCred field guide

The best AI tool list is already out of date. Use a buying test instead.

Tools change their names, prices and features faster than you can implement them. So don't start with a list. Start with one bottleneck you've measured. Then pick the smallest kind of tool that fixes it, without piling on more review, security risk or maintenance.

By Phila Ngwenya · Published

The contrarian view: don't start with the tool

A demo shows you what a tool does on its best day. It doesn't show you whether your inputs are usable. Or whether your process has settled. Or who handles the exceptions. Buy before you know that, and you've got another unfinished project.

Start with the task instead. What triggers it? What goes in? What are the steps? What comes out? Who checks it? What breaks? If the process changes every week, settle it before you automate it.

I've seen this first-hand. Macaela Oor runs Demure International. After one session with us, she wrote: “My Claude has been operating a lot better since the last session.” She didn't buy a new tool. She changed what her tool knew. That's the whole argument of this guide.

Score the bottleneck before shopping

Track a normal week. List the tasks that repeat. For each one, note how often it happens and your hands-on minutes. Note the delay it causes, how often it needs fixing and what happens when it's late or wrong.

Then ask yourself one more question. Can someone on your team judge the result consistently? If not, you're not ready for a tool.

And don't just pick your longest task. A short task that blocks every sale might matter more to you.

Choose the smallest tool category

Use an AI assistant when you supply the context and check each draft. Think proposals, summaries, research prep and first drafts.

Use workflow automation when your task moves predictable information between systems. Think routing forms, creating tasks, reminders and handoffs.

Use a system of record when your real problem is that nobody knows which customer, task or document is current. You need one reliable place for status.

Most businesses need that last one fixed before they need more AI. Automate scattered, contradictory information and you get faster confusion. Not progress.

Use this six-question buying test

Plenty of products fit more than one category. And their terms change. So check the current documentation and contract for the exact plan you'd buy. Not an old comparison article. Then ask these six questions.

  • Fit: can it handle representative examples from our actual workflow?
  • Context: can it use our approved information without mixing customers or versions?
  • Control: can one of us approve consequential output before an external action?
  • Visibility: can we see failures, usage, history and who changed what?
  • Data: where is our information processed, retained and shared, and what contract applies?
  • Exit: can we export our data and continue operating if the price, product or integration changes?

Run a ten-example pilot

Pick ten real examples from your own work. Ordinary ones, messy ones and at least one awkward exception. Record how you handle them now. Then set up the smallest workflow that could work. Measure your setup, running, fixing and review time.

It passes only if your total effort or delay goes down without losing quality or control. Fast output that creates rework, hides failures or depends on one enthusiast isn't a win. Be honest with yourself here.

And before you start, do five things. Name the owner and the reviewer. Define a good output and what the tool must never do. Log every exception and what the system did with it. Write down how to pause it and go back to the manual way. Then decide on the evidence. Keep it, change it or remove it.

Build it yourself or have it implemented

Want to map your bottleneck and build the first controlled workflow yourself? Take the workshop. You'll learn how to judge the output too. And please don't subscribe to a stack of tools before you know what the task needs.

Apply for implementation when the workflow crosses accounts, permissions or systems. Or when monitoring and exception handling need proper design. We check compatibility before we promise an integration. Third-party costs get scoped separately.

Sources behind this page

Here's where the public figures on this page come from. They aren't our client results. They don't endorse us. And they're no substitute for your own professional advice.

Frequently asked questions

Which AI tool is best for a small business?
There's no universal best tool. The right one is the smallest kind of tool that improves your most valuable repeated task, and passes a pilot on your real workflow.
Should I buy several tools at once?
Usually not. Prove one workflow first. Every extra subscription adds setup, permissions, data movement and maintenance before you know the first process works.
How many examples should I test?
Ten is a practical start. Include your ordinary cases, messy inputs and awkward exceptions. It's a pilot design, not a statistical guarantee.
When do I need implementation help?
When your workflow crosses systems, needs permissions, sends external messages or needs monitoring and exception handling. A simple drafting task you review yourself may suit the workshop.