CERTAINCE Logo

Using AI in Your Business: What Actually Works

AI Automation · 9 min

Illustration: using AI in your business. A business as a network of recognizable processes with golden AI nodes

What can AI handle in a business? Examples include drafting a quote from a tender, producing a management report from existing data or preparing outreach to suitable new customers. Such tasks may come up every week or only once a year. It works reliably when the task is clearly bounded, the data is sound and a person reviews the right points.

Most owners we talk to do not doubt AI's potential. They want to know where it fits in their own business. Workflows in specialized companies, such as machine builders and exhibition stand contractors, look different from the generic examples in most guides. That is where those examples usually stop being useful. This article looks at which applications hold up in such businesses, what can make a first attempt fail and what AI needs to work in daily operations.

A large field study shows both the potential and the boundary of such examples. In Generative AI at Work, Erik Brynjolfsson, Danielle Li and Lindsey Raymond studied the introduction of an assistant among 5,172 support agents. Issues resolved per hour rose by 15 % on average, but less experienced workers benefited much more than the most experienced. The result holds for a clearly bounded, text-heavy workflow with many useful examples, and the average hides important differences between tasks and people. It does not simply transfer to other workflows.

How can you use AI in your business? Concrete use cases

The clearest way to make this practical is through workflows you recognize immediately. Four areas recur in specialized businesses.

  • Quote and RFQ processing. The agent reads the tender, checks it against product and pricing data, flags missing information and prepares a draft. Sales still approves the result, but no one has to gather the source material by hand.
  • Reports and analyses, such as a checked, repeatable DATEV export instead of preparing spreadsheets manually for the month-end close. Where the rules can be written down, a fixed program without AI does the job.
  • Find suitable new customers and prepare outreach, using clear sources and criteria so that sales can make an informed choice about whom to approach.
  • Handovers between systems. The agent can match purchase orders with confirmations, keep statuses current and prepare data for transfer between the shop and accounting. Your team approves the result.

An AI-assisted sales research tool for a CNC automation manufacturer shows what this looks like in practice. It checks machinery pages and job adverts against criteria for a good-fit business that were set in advance. The gain lay less in the time saved than in the order of work: sales now starts with the most technically relevant businesses instead of a long list of similar companies, and every lead includes the reason it fits.

The projects that never got started

It is also worth looking at work that never happened at all: a sales campaign for a new customer segment, a marketing series after a trade show or a recurring analysis of order data. The idea was rarely the problem. These projects stayed undone because no one had time for them alongside daily work. That calculation is now changing. Work that once required a separate project can become a recurring workflow, with your team reviewing the result instead of producing it from scratch. For many businesses, this may be more valuable than speeding up work that already happens; so far we can show it only in individual projects. Anthropic has measured inside its own company how work shifts when a company adopts AI agents early and broadly.

When the first attempt with AI fails

If a first attempt with AI on one of your own workflows was disappointing, it is tempting to conclude that AI does not work there. In our work, the cause in such cases was usually the handover: what the tool got to see and how the task was put. Four causes come up regularly:

  • The tool did not have the documents. Without the price list, earlier orders or the current template, a model fills the gaps with plausible assumptions. It needs the same documents a new employee would.
  • The workflow had not been decided. If two sources give two prices, or nobody has settled which exception applies, a new employee fails as well. The attempt shows which rule is missing; a person sets it, and then the agent applies it.
  • The task came as a question. One sentence in a chat is not yet a handover. An agent needs a goal, the material, its limits and a sign by which you can recognize a good result.
  • The first draft was taken as the verdict. What it missed belongs in the work instruction, and the next run starts from there. Only a few real cases show what an agent can do in this workflow (delegate every task to AI once).

Three limits remain. Where a stable rule is enough, a fixed program is cheaper and gives the same result every time, as with the DATEV export above. Where good off-the-shelf software covers a workflow, such as accounting, it stays there; an agent can still file incoming invoices from the mailbox. Prices, commitments and anything with legal effect are decided by a person, even when the agent writes the draft. A task that comes up only twice a year needs no setup of its own; the existing tool is enough.

You can also build some things yourself. For a small tool that stays internal and does not affect critical decisions, a technically minded employee may be able to make a useful start with an AI coding tool. Outside support becomes more important once the software is business-critical, several people use it or sensitive data and integrations are involved. At that point, someone must maintain the result for years.

The calculation is simple. AI lowers the cost of building but does not remove the cost of responsibility. Operation, maintenance, edge cases and review remain real work. Those costs ultimately determine whether an initiative is worthwhile.

That second cost rarely appears in a quote.

What AI needs to hold up in daily operations

AI adoption in an SMB rarely fails because of the language model itself. What matters is whether the task, data, access and human review are clearly defined. An existing AI tool may already cover those needs for a well-bounded task. When several systems, company-specific rules or sensitive data come together, the workflow also needs reliable interfaces, permissions and defined error paths. Context management for business determines what information the AI should see for each task.

First check whether an existing tool can solve the task reliably. If it cannot, the next step might be a configured way of working, a connection between existing systems, a small automation, a bounded AI agent or custom software. If the rule for the normal case fits in three sentences, a fixed automation is cheaper and easier to check than an agent; an agent belongs where every case looks different. The use case determines which option fits. What matters is whether the solution improves the workflow in daily use, not what it is called.

The boundary is part of the picture. Agents take on whole tasks autonomously, in steps, within their tools, permissions and tests. Binding steps are approved by a person; small, reversible steps run automatically with spot checks once they have proven themselves in live operation. For agreed tasks, we can run and improve the agents for you, billed by the hour; binding steps are still approved by a person in your company.

The project management software we built for an exhibition stand builder shows what such a foundation looks like. It is a business app for exhibition stand teams that brings inventory, reservations and project status into one shared data model and logs every movement as a transaction. Automation can build safely on that foundation because the authoritative data and permissions are explicit.

Adopting AI: the first step

Adopting AI can sound like a large program with a roadmap. The start is smaller: your team gives a real task to a tool that can reach your documents, and checks the result. A one-page AI policy sets out what may go into that tool. Which workflow suits it often only becomes clear from your last normal working week: what came up again and what was transferred, compared or rewritten by hand.

For smaller companies, this is a realistic path. A first attempt with the existing tool on the real workflow shows whether the case holds before you invest more. Afterwards, you know what AI can do in your business rather than what it can do in general. A free AI assessment is for walking through that workflow and assessing which approach fits it.

How can you use AI in a business?

AI is most reliable on clearly bounded tasks, one-off and recurring alike. Examples include evaluating inquiries and RFQs, preparing quote drafts, producing reports and preparing outreach to suitable new customers. It needs sound data, clear rules and human review at the right points.

What are examples of AI in a business?

One example from our projects is an AI-powered sales research solution that evaluates manufacturing companies' websites for CNC buying signals and delivers prioritized leads with talking points. The checked, repeatable DATEV export that replaces manual spreadsheet preparation at month-end close, by contrast, is deliberately a fixed program without AI, because its rules can be written down.

Where is AI not worth it in a business?

Less often than a failed first attempt suggests. In our work, the tool then usually lacked documents, a decided rule or a clearly framed task. We work without AI where a stable rule is enough or good off-the-shelf software covers the workflow, and a person decides prices, commitments and anything legally binding. AI lowers the cost of building, not the cost of responsibility; operation, maintenance and review remain real work.

The first step should be small and reviewable. If it fails, first find out what it was missing; if off-the-shelf software or a fixed rule is enough, stay with that. The AI services overview shows which paths are open after that. Getting started with AI describes how we support that first step. With quote preparation or the monthly report as the example, let us discuss a concrete workflow.

Inquiries