AI in micro-businesses: what 1980s computing can really teach us

The analogy with 1980s computerisation can help a micro-business think through gradual adoption, provided it is used as a set of practical questions rather than proof that an identical AI revolution is inevitable.

• Early value often appears in a specific scope before any wider rollout.
• How work is organised matters as much as which tool is selected.
• Generative AI adds uncertainty in its outputs and data concerns that the historical comparison cannot remove.
• The sound decision may be to expand, retain human supervision or stop the use case.

1. Start with recurring, verifiable and low-risk work

The best first use case combines enough frequency to observe, reversible errors and an output that a domain owner can recognise as acceptable.

• Recurrence: the same type of request returns with comparable inputs and outputs.
• Verifiability: a competent person can quickly check accuracy, tone and omissions.
• Reversibility: an error can be corrected before a message, accounting entry or contractual commitment.
• Ownership: a named person controls the process, resolves exceptions and can stop the trial.

In a small service business, handling requests received by email is a more informative test than a vague aim to “do marketing with AI”, because it exposes a complete workflow without delegating the client relationship.

• The tool extracts the name, need, deadline and documents mentioned.
• It suggests a category, a draft reply and the next task to create.
• The owner checks the facts, supplies context and alone decides whether to send.
• Requests involving prices, contracts, disputes or sensitive data automatically leave the scope.

2. Compare the complete job, not generation speed

A trial establishes value only by comparing the original and assisted processes through to an accepted result, because seconds of generation can conceal additional preparation, review and correction.

• Human effort: preparing inputs, writing instructions, checking, reworking and handling exceptions.
• Lead time: the interval between receiving a request and having a reply ready, including queues and rework.
• Quality: factual accuracy, missing items, suitable tone, adherence to the internal template and number of corrections.
• Operating cost: subscription, integration, maintenance, training and time spent on incidents.

The comparison should use representative cases and retain failures in the record, so easy files do not create a misleading impression of improvement across the entire workload.

• Build a batch containing ordinary, incomplete and ambiguous cases.
• Process it first using the usual method to establish a baseline.
• Test the assisted workflow against the same acceptance criteria.
• Record corrections and escalations instead of counting only successful outputs.

The decision to continue requires an explicit trade-off among effort, lead time and quality, three dimensions that may move in different directions and that each business must weight according to its work.

• Expand when accepted results consistently require less effort without weakening service.
• Keep the system as an assistant when quality improves but human review remains substantial.
• Redesign when gains depend on unusually simple cases or hidden manual clean-up.
• Stop when corrections, incidents or risk outweigh the observed benefit.

3. Give the process an owner and bound its data

The tool may prepare an action, while the business must retain a clear chain of responsibility: one person answers for the result, knows which data moves through the system and can suspend it.

• The domain owner defines eligible cases, quality criteria and exceptions.
• The technical owner documents connections, access rights, logs and the rollback procedure.
• Management accepts the level of risk and decides which uses may affect company commitments.
• Users report errors in a common record instead of silently fixing them in isolation.

Before sending client data to an AI service, the business should map its complete journey and verify that each step serves an authorised purpose, following the practical questions in the CNIL guide for using an AI system.

• Identify the data genuinely required and remove the rest.
• Check processing location, retention, subprocessors and possible reuse by the supplier.
• Restrict every account and connection to the minimum access required.
• Plan for deletion, export of logs and replacement of the supplier.

Sensitive or consequential information requires a tighter scope, because a late human review cannot always undo a disclosure or an action that has already been executed.

• Exclude passwords, trade secrets and data unrelated to the task by default.
• Mask personal identifiers when the work can be completed on pseudonymised content.
• Block autonomous payments, contracts, prices, refunds and decisions about individuals.
• Escalate every ambiguous case to the owner instead of asking the model to guess the rule.

4. Pass through four gates, with an exit at every stage

Useful progression takes the form of four successive decisions, with each gate demanding stronger evidence before the scope or autonomy expands.

• Frame: name the owner, task, current baseline, permitted data and prohibited actions.
• Assist: produce drafts without external action, then measure every review and correction.
• Routinise: integrate assistance into daily work only for cases that meet the agreed criteria.
• Expand: add one action, file category or data permission at a time after a fresh review.

Stop criteria should be written before the trial so that sunk effort, enthusiasm for the tool or a few successful demonstrations do not displace evaluation of the real process.

• Quality falls below the defined threshold or varies without explanation.
• Review and rework absorb the expected time saving.
• The supplier, data processing or responsibility for an action can no longer be explained.
• Similar errors recur after the instructions or workflow have been corrected.
• No owner can resume the work manually within an acceptable time.

What the historical analogy can actually help decide

The computerisation of the 1980s shows that a tool becomes structural when it enters routines, skills and responsibilities, but it cannot predict the pace, extent or profitability of AI for a particular business.

• Conventional software generally executes defined rules; generative AI can produce plausible and false answers.
• A simple interface does not remove integration, control or process maintenance.
• Widespread adoption elsewhere does not automatically turn a use case into a priority for your business.
• The useful evidence remains local: a real process, a complete measurement, a named owner and respected limits.

For a micro-business, the strategic question is which limited piece of work deserves a controlled trial today and which observations would justify the next step.

• Choose a recurring workflow with low consequences.
• Measure effort, lead time, quality and cost through to the accepted result.
• Keep human judgement over exceptions and commitments.
• Expand only what survives difficult cases and the pre-agreed stop criteria.

---

Paul-Antoine TUAL · AI Transformation Leader · Croissance & Transitions