What can AI really automate in a small business?
AI can prepare, classify, summarise, or find information. In a small business, it becomes useful when it works from the right data, respects rules, and lets a person control important decisions.
05 chapters
Choose a narrow, observable use case
The right starting point is a repeated task, costly to prepare and easy to check: classify requests, extract information, prepare a summary, or find a rule in a document corpus.
The expected result is described before the model is chosen. Processing time, human-rework rate, refused cases, and cost per run form a baseline. Without that reference, the pilot can impress without proving it improves the process. AI solutions therefore start from the work, not from the vendor.
- An input and an output clearly defined.
- Representative real examples, including hard cases.
- A person able to validate the result.
- A measure before the prototype and the same measure after.
Prepare the data and the right to use it
The model does not fix a source that is obsolete, contradictory, or unreachable. Documents must be identified, dated, cleaned, and tied to visibility rules. A useful answer cites the source that lets it be checked.
How personal, confidential, or regulated data is processed is decided before it is sent to the model. Hosting, retention, logging, and exclusion from training are written in the architecture and in the contracts, not assumed.
Decide what the machine may prepare, propose, or execute
Not every action carries the same risk. Summarising a document, preparing a draft, and sending a message to a client do not ask for the same level of control.
A simple matrix distinguishes read, proposal, and action. It states accessible tools, limits, authorised data, and the cases that require a refusal. Custom software then carries those rules in rights, interfaces, and logs.
Four functions to maintain throughout the system lifecycle
The NIST AI RMF does not reduce governance to a final approval. It connects responsibility, context, measurement, and risk treatment.
- 01Govern
Govern
Assign responsibility, document rules, and establish a risk-aware culture.
- 02Map
Map
Describe the use, affected people, data, limits, and possible consequences.
- 03Measure
Measure
Test quality, errors, and risk on representative cases.
- 04Manage
Manage
Prioritise risks, apply safeguards, and decide whether to continue, limit, or stop.
Govern is cross-cutting: it supports Map, Measure, and Manage.
Build human validation into the journey
Writing that a human keeps hold is not enough. The interface must show the proposal, its source, its uncertainty, and the consequence of the action. Validation arrives before send or irreversible change.
Human corrections become test cases. They make it possible to track recurring errors, change instructions, and decide whether the perimeter can widen. Stellary applies this principle to agent missions attached to projects and supervised in the same system.
Validation must be a journey, not a promise
The interface must give the person what they need to understand, correct, and stop the system before a significant consequence.
- 01
Show
Present the proposal, the data used, and the source that allows it to be checked.
- 02
Warn
Make uncertainty, limits, and the consequence of the action visible.
- 03
Decide
Let a person approve, correct, or refuse before send or irreversible change.
- 04
Trace
Keep the proposal, human decision, and context needed for review.
- 05
Reassess
Turn corrections into tests and keep monitoring quality after launch.
CNIL reminds users to review generative-AI output and says the business remains responsible for its use.
Measure costs and plan for a model change
Real cost adds the model, document search, storage, called tools, observation, and validation time. It is measured per use case and per accepted result, not only per token.
Models move fast. The product therefore keeps an evaluation layer, test sets, and a replaceable integration interface. A vendor change must neither rewrite the process nor make results incomparable. To set a real case against these constraints, the starting point remains a scoping conversation.
- Log the model, its version, and the cost of each run.
- Test changes on a stable case set.
- Plan volume limits and spend alerts.
- Document the procedure to disable or return to manual handling.
The remaining decisions
Should you start with a chatbot?
Only if conversation is the best format for the task. Silent classification, a prepare button, or a suggestion inside the existing tool are often more direct and easier to control.
How do you avoid invented answers?
By narrowing the task, providing up-to-date sources, requiring citation, testing on real cases, and refusing the action when proof is missing. Risk is reduced by the whole system, not by a sentence added to the prompt.
Can the model be changed later?
Yes if the integration separates the business process from the vendor and keeps a stable evaluation set. Results and costs can then be compared before any switch.
Put the guide against a real project.
A few lines are enough: context, the main constraint, and the expected result.