Answer
How can a small business use AI without hiring an AI specialist?
By keeping every arrangement simple enough for the person who owns the process to change it. The constraint is maintenance, not building.
By building only what the person who owns the process could change themselves. Building is cheap and getting cheaper; maintaining something nobody in the business understands is the cost that ends these projects.
The specialist question is usually asked about construction and belongs to maintenance. Building a workflow has become cheap enough that a capable non-specialist can do it, often with the assistance of the tools themselves. What has not changed is that the thing then has to keep working while the business changes around it, and that requires somebody who can open it, understand what it does and alter it. If nobody in the business can, the workflow has an expiry date set by the first upstream change.
That gives a design rule with an unusual shape: build the version the process owner could maintain, even where a better version exists. A rules table someone can edit beats a clever inference nobody can adjust. A scheduled job beats an event-driven architecture. Three simple automations beat one sophisticated one, because each can be understood, switched off and replaced independently.
Buying reduces the maintenance burden and does not remove it. A purchased product is maintained by its vendor, which is a real advantage, and it still needs somebody who knows how it is configured, what it connects to and what to do when it behaves unexpectedly. The saving is in the difficult technology rather than in the operational knowledge, and the operational knowledge is the part a small business most often lacks.
Where outside help is used, the deliverable that matters is not the working system. It is the working system plus a person inside the business who can operate it: a short document, a walkthrough where somebody else ran it, and the credentials and code in the business's own accounts. An arrangement that leaves the knowledge with the contractor has bought a dependency rather than a capability, and the invoice looks the same either way.
The most under-rated route is the one that involves no building at all. A great deal of value is available from using these tools directly and well — supplying material rather than describing it, using them on work you can judge, building the habit of checking specifics. That requires no integration, no permission surface and no maintenance, and most businesses have not exhausted it before they start commissioning systems.
Finally, be realistic about the scale that works. A business with a handful of people can operate a small number of simple automations well and cannot operate a portfolio. Choosing the two or three that matter and running them properly produces more value than a broader programme that nobody has time to observe, and it is a decision rather than a limitation.
The question is not who can build it, it is who will still be able to change it in March.
Siddharth Sharma, Context Theory
Related questions
Is it worth learning to build these things yourself?
For the person who owns the process, yes, more than for anyone else in a small business. The barrier is lower than it was and the relevant skill is specifying clearly and testing rather than programming. Someone who understands the process and can adjust the workflow is worth more here than a technical person who understands neither.
How do you tell whether an outside supplier is leaving you with a dependency?
Ask where the code and credentials will live, who else could change it, and what happens if they are unavailable for a month. The answers are usually clear and rarely volunteered, and asking before the work starts is the difference between a capability and an arrangement you cannot leave.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Sub-15-minute compliance — automated routing vs manual only | 62.5% vs 39.1% | Category-wide |
| US SMB retainer, focused one-to-two-service engagement | $1,500–$4,000 | Category-wide |
2026 speed-to-lead benchmark · verified
2026 agency pricing survey · per month · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Procurement | Construction has become cheap enough for a capable non-specialist while maintenance has not, so a workflow nobody in the business can open and alter has an expiry date set by the first upstream change. | Naming, for each existing workflow, the person in the business who could modify it. |
| Buying behaviour | Purchasing shifts maintenance of the difficult technology to a vendor and leaves the operational knowledge — configuration, connections, unexpected behaviour — with the business, which is the part a small business most often lacks. | Identifying who in the business knows how each purchased tool is configured and what it connects to. |
| Constraint | An engagement that delivers a working system without transferring operating knowledge, credentials and code into the business's own accounts has produced a dependency rather than a capability. | Checking whose accounts hold the credentials and code for work delivered by an outside supplier. |
| Workflow | Substantial value is available from direct use of these tools without any integration, permission surface or maintenance, and most businesses have not exhausted it before commissioning systems. | Listing the tasks in the business currently done manually that could be assisted without any connection being made. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one