1. Choose a task with a verifiable result
Start with a repeated task that a person can easily review. Describe how it is done today, what information goes in and what result you need. “Prepare a reply to an inquiry” is more specific than “use AI to sell more.”
The best first-test candidate combines available information, a clear result and simple review. If the task requires sensitive decisions, has poorly defined conditions or depends on data you do not have, address those questions first.
| Task | Test input | What to check |
|---|---|---|
| Reply draft | Fictional question and confirmed service information | Preserves prices, scope and tone |
| Inquiry classification | Ten invented messages and defined categories | Uses the categories and flags uncertainty |
| Meeting summary | Fictional notes with agreements and pending actions | Distinguishes decisions from proposals and preserves owners |
Choose just one to start. For sales work, you can combine this test with the WhatsApp follow-up guide. The record helps identify which information the draft must include.
2. Prepare data and rules before choosing the tool
Create a short worksheet with valid information: what your service includes, what you need to ask and which details are not confirmed yet. Update it if a condition changes. Organized text helps both manual work and an AI test.
For the first trial, use invented or anonymized data. Before using real information, review permissions, team access and the tool's data-processing terms. Define who can use it and who approves the final replies.
A convincing output can be incorrect. The generative AI profile from NIST describes risks such as fabricated information and data privacy. Review must check the content against your sources.
When comparing tools, check whether they support your required format, who has access, what data options the account offers and the cost of expected usage. Confirm current availability for your country and plan before subscribing.
3. Write an instruction you can evaluate
Include the task, data, output format and rules. This example is a fictional reply-writing exercise; you can copy it into an AI tool you already have access to.
Task: prepare a draft reply to a business inquiry. Confirmed sample information: - Service A: initial review of an administrative process. - Deliverable: list of steps and improvement opportunities. - Price and timeline: not confirmed yet. Fictional inquiry: "Can you help with my quotes? How much does it cost?" Rules: - Reply in English using no more than 80 words. - Explain only confirmed information. - Do not invent a price, timeline or results. - Ask which part of the quoting process needs improvement. - Do not present the draft as a confirmed contract. Output: 1. Draft for human review. 2. Missing information needed for a complete answer.
Check whether the text preserves the scope, acknowledges the missing price and asks a useful question. A reply that invents “delivery in 24 hours” fails even if it is well written. Note the error, adjust the instruction and test that case again alongside different ones.
4. Compare the complete process
Prepare ten different fictional cases: some simple, some ambiguous and some with missing information. First solve them as you would today. Then test with AI and keep the results for review.
- Total time: count preparation, generation, review and correction. Include updating the information the tool uses.
- Quality: check facts, scope, format and next action. Define which errors require rejecting the output.
- Corrections: record which each result needed and whether they repeat.
- Cost: consider tools, usage, setup and review time. Use current provider prices.
Set your criteria before seeing the results. For example: “The reply must not invent conditions and must acknowledge all missing information. Total time must be acceptable for our team.” This is a test criterion you can adapt to your process, not a performance guarantee.
If review takes more time than you save, reconsider the task, available information or how you use the tool. Sometimes a template or simple rule addresses part of the work better.
5. Expand only what you can control
When the test is consistent, document the instruction, data source, known errors and reviewer. Keep a manual alternative for inquiries that do not fit the process.
If the next step requires connecting forms, documents or systems, request a proposal with inputs, outputs, permissions and acceptance criteria. Administrative automation and AI assistants require this scope to be defined before implementation.
When asking for help: share the task, a fictional example, approximate workload and how you will know the result is correct. You do not need to send private conversations in the first contact.
Sources and review
Official references consulted on October 13, 2026: NIST AI Risk Management Framework and NIST AI 600-1 Generative AI Profile, published in 2024. The examples and test method are a practical ArepaDev proposal. These references are not presented as new announcements or a certification of the service.