Finding Where AI Fits in Your Business

Many conversations about AI start with a tool. Someone has tried a chatbot, seen a demo, or heard that a competitor is using AI, and the question becomes where the business could use it too.

That question tends to produce long lists of ideas and few results. A more useful starting point is the work itself: where it slows down, where it piles up, and where mistakes keep happening.

Some of those problems are a good fit for AI, especially work that involves reading, sorting, or interpreting information that arrives in many different forms. Others are better solved with a simple rule, an integration between two systems, an automated workflow, or a change to the process. Telling them apart before choosing a tool puts the effort where AI makes a real difference.

The following sections outline one way to find where AI fits, rule out where it does not, and choose a first task worth testing.

1. Look Where People Connect the Systems

In most businesses, the slowest and most error-prone work happens between systems rather than inside them. Information arrives by email, sits in a PDF or spreadsheet, and has to be read, interpreted, and entered somewhere else by a person. That person is doing the work of a connection that does not exist.

Common signs include:

• Staff copying information from emails, attachments, or forms into another system
• Someone reading through long documents to find a few relevant details
• Incoming requests sorted and forwarded by hand before anyone can act on them
• Reports assembled every week from several sources that do not talk to each other

These tasks are often so familiar that nobody questions them. They are simply how the work gets done.

Questions to consider include:

• Where does work wait in a queue before someone can act on it?
• Which tasks would stop or slow down if one particular person were out for a week?
• Where are the same details typed into more than one system?
• Which tasks grow in direct proportion to the number of customers, orders, or requests?
• Where do mistakes most often come from, and how are they discovered?

It helps to ask the people who do the work rather than only the people who manage it. They know where the workarounds are and how long they actually take.

2. Recognize the Tasks AI Is Suited For

Good candidates for AI are often tasks like sorting emails, pulling details from documents, matching records across systems, or drafting documents from existing material. They tend to share a few characteristics:

• A person can check the result. This matters most for a first project. AI services can sound confident and still be wrong, so start where a person reviews each suggestion before it is used. Later, the level of review can match what a mistake would cost.
• They involve reading or writing. The work centers on emails, documents, forms, notes, or other text rather than on calculations.
• They happen in volume. The task repeats often enough that saving a few minutes each time adds up.
• The input varies. The same kind of information arrives in different formats, wording, or layouts, which makes fixed rules hard to write.
• Each instance needs a little interpretation. Someone has to understand what the content means, but not apply deep expertise or make a high-stakes judgment every time.

Example. A property management company receives maintenance requests from tenants by email and through a web form. Tenants describe the problem in their own words: "water under the sink" or "something is leaking in the cabinet." A coordinator reads each one, decides whether it is plumbing, electrical, or general repair, judges how urgent it is, and assigns it to the right vendor. The requests are frequent, the wording varies, and each one needs a small amount of interpretation. AI can suggest the category and urgency, and the coordinator confirms or adjusts it. The coordinator still makes the decision, but no longer has to start from a blank screen on every request.

3. Rule Out the Poor Fits

AI is probably not the right starting point when:

• The problem is not defined. If no one can describe what is slow, wrong, or costly, there is nothing specific for AI to improve.
• The task is rare. A task done a few times a year rarely justifies the effort to build and maintain an AI feature for it.
• The information does not exist. If the knowledge needed for the task has never been written down or recorded anywhere, AI has nothing to work from.
• The result must be exact every time. Pricing, account balances, tax calculations, and compliance determinations belong in software that produces the same answer every time and can be tested and audited.
• The value is small. If the task takes a few minutes a week, even a perfect solution will not repay the effort.
• The main reason is pressure to use AI. Adopting AI because competitors are doing it, without a specific problem in mind, usually produces a feature nobody uses.

Ruling out a task is a useful result. It narrows the list to the opportunities that are worth the effort, and it often surfaces simpler fixes that can be made right away.

4. Check Whether Something Simpler Would Work

Before deciding a task needs AI, check whether a simpler fix would solve it. A simpler fix is usually cheaper to build, more predictable, and easier to maintain.

• A rule. If the task follows the same logic every time, such as routing every request from a certain customer to a certain team, a fixed rule in the existing system will be faster and more reliable than AI.
• An integration. If the same information is typed into two systems, connecting the systems so the data moves automatically removes the task entirely.
• A simple automation. If a task is the same sequence of steps every time, such as sending a reminder two days before each appointment or building the same weekly report, a scheduled workflow can run it without anyone touching it.
• A better form. If staff spend time interpreting free-text requests, a form with the right fields may collect the information in a structured way from the start.
• A process change. Some steps exist only to work around an old limitation and can be removed rather than automated.

None of these require AI. Some are ordinary automation, and some need no new software at all.

Example. An office manager copies every new order from the online store into the accounting system. The orders already arrive as structured data, with the same fields every time. Nothing about the task requires interpretation. This is an integration problem, not an AI problem, and connecting the two systems would remove the work rather than speed it up.

Compare that with a distributor that receives price updates from dozens of suppliers, each in its own spreadsheet layout with its own column names and product codes. Someone has to work out which column is which and match each product to the distributor's catalog. The inconsistency is the problem, and that is where AI can help, with a person reviewing the matches before the prices are updated.

The two tasks look similar from a distance. Both involve copying information from one place to another. The difference is whether the work requires interpretation.

5. Describe the Opportunity Before Choosing a Tool

Once a task looks like a good candidate, describe it clearly before comparing AI products or vendors. A short written description makes it easier to judge whether the opportunity is real and to explain it to the people who will approve it.

The description should cover:

• The task: what is done today, step by step, and what is slow or error-prone about it
• The people: who does the work, who depends on the result, and who would review the AI's output
• The information: what the task reads, where that information is stored, and whether it includes customer, financial, or otherwise confidential data
• The systems: which applications the task touches and where the result needs to end up
• The review point: where a person checks the result before it is acted on
• The measure of success: how anyone will know it worked, such as time saved, fewer errors, or faster responses

If any of these cannot be filled in, the opportunity is not ready yet. The information is especially worth settling early, since whether it includes confidential data often determines which AI services and setups can be used.

6. Estimate What It Is Worth

A rough estimate of value helps compare opportunities against each other and against the cost of building them.

Start with the time the task takes today. Multiply the hours per week by the cost of the people doing the work, and project it across a year. For example, a task that takes eight hours a week, at a staff cost of $35 an hour including taxes and benefits, adds up to about $14,560 a year.

AI rarely removes a task entirely, especially when a person still reviews the result. A more realistic estimate assumes part of the time is saved. If the AI suggestion cuts the time in half, the value in this example is closer to $7,280 a year.

Time is not the only measure. Some opportunities are worth more for what they prevent or enable:

• Errors that currently reach customers or cost money to fix
• Requests that wait too long and cost the business work
• Growth that would otherwise require hiring someone just to keep up with the volume
• Work that stops when one experienced person is unavailable

Keep in mind that time saved gives staff room for other work. It does not necessarily reduce payroll, so treat it as added capacity unless the business actually plans to reduce hours.

7. Pick One Task to Test

With a few candidates described and estimated, choose one to test first.

The best one to start with has measurable value, a point where a person reviews the result, and information the business is comfortable sending to an AI service. It also:

• Is contained to one workflow or one team
• Has someone who does the work and is available to help test it

It is tempting to start with the largest opportunity. A smaller one with a clear measure of success is often the better first choice, because it shows whether AI works with the information and people the business already has before a larger commitment is made.

The next step is usually a small proof of concept that tests the task on real examples against agreed success criteria. That process, and how to add the result to an application the business already runs, is covered in Adding AI to an Existing Application Without Rebuilding It.

Start With the Work, Not the Pressure to Use AI

The most useful AI projects begin with a specific task that is slow, repetitive, or error-prone, not with the question of where to use AI. The goal is to choose the simplest approach that fixes that task. For work that involves reading and interpreting varied information, that approach is often AI.