A small business does not need an elaborate network of agents to start working with several ai systems. It needs a task that can survive a handover. Consider a fictional repair shop preparing a guide to requesting a quotation. The useful result is a clear guide based on approved information, with missing details left visible.
Define the finish line
Write one sentence describing the reader and the result: “Help a first-time customer understand which details to include in a repair enquiry.” Specify the allowed sources, the desired length, and anything that must not be invented. Opening hours and prices belong in approved business information, not in the writer's imagination.
Give each role a different output
The researcher produces an evidence sheet: claim, source location, date, and uncertainty. The drafter produces the article using that sheet. The reviewer produces a list of problems tied to specific sentences. Asking three assistants to “improve the article” gives them overlapping work and leaves responsibility unclear.
Use this role card:
Task: explain how to request a repair quotation. Research output: approved facts and unanswered questions. Draft output: a short guide with numbered steps. Review output: unsupported claims, missing steps, and unclear wording. Publication decision: a named human editor.
Make the handover explicit
The drafter should receive the evidence sheet alongside the assignment. If a detail is unknown, the researcher records it as unknown. The reviewer needs both the draft and its evidence; the draft alone cannot establish where a factual statement came from.
Start with one article rather than connecting every business process. Keep each role's output in a separate section so that a reviewer can trace changes. Multiple ai systems can repeat the same error, so agreement between them is not a substitute for checking the original material.
Try it on a small task
Choose one recurring customer question. Prepare the three role cards before opening another chat. Run the sequence, then mark every point where somebody needed extra information. Improve the handover at those points. Judge the workflow by the usefulness and accuracy of the finished answer, rather than the number of assistants involved.
Mika is an editorial pen name used by the KENJTEC editorial team in Hamburg. This article proposes a workflow; it does not report a completed test.
