1. Choose one task, not an entire department
“We want AI in the business” does not define a testable project. “We want support colleagues to find the relevant procedure and see its source” identifies the user, information and outcome. Start with a workflow that someone on your team understands and can evaluate.
For each candidate process, record how often it happens, how long it takes today, what data it uses and what happens if the result is wrong. An infrequent task without examples, or a process with constantly changing rules, may need to be organised first.
- Is there an owner who can explain and review the work?
- Do we have typical examples, exceptions and accepted outputs?
- Can we limit the pilot to a defined user group and dataset?
- Can we stop the test and return to the current way of working?
2. Check whether AI is necessary
Choose the solution around the task. An integration or explicit rule may solve the problem more simply. Some workflows combine fixed rules with interpreting text.
Rules and integrations
Moving a field from a CRM to an ERP, fixed calculations and format checks usually have explicit rules. Check the available APIs, exports and built-in features first.
A document assistant
When people search procedures and manuals, test information retrieval, source references and recognition of questions that the documents cannot answer.
Interpretation with human review
For message classification or field extraction, agree who checks the output before it reaches a system used by the team. Exceptions need a clear route to a person.
3. Prepare the sources and access boundaries
List the sources, formats, versions and people allowed to use them. Conflicting or outdated documents do not become accurate because they are connected to an assistant. Decide who approves each source and keeps it current.
Before connecting data, we agree where it is processed, what is retained and what each user may access. Use only the information needed for the pilot. Do not send internal documents, passwords or personal data through the public enquiry form.
4. Define how you will evaluate the pilot
Keep evaluation examples separate from those used to configure the system. Include normal requests, missing information, ambiguous wording and situations where the system should decline to answer or ask for help. Reusing the same examples makes versions comparable.
Acceptance criteria belong to your workflow; no universal percentage makes every system suitable for production. Measure review effort as well as time to the first response.
- Quality: is the output correct, complete and supported by the appropriate source?
- Control: can users access only permitted information, and do consequential actions have the agreed approval?
- Effort: how long does the whole task take, including corrections and review?
- Operation: what does usage cost, what happens on failure and who handles the exception?
An example of a bounded pilot
Illustrative example, not a client project result: a team looks up instructions in an approved set of manuals. The pilot answers a small group of colleagues, references the document and section, and routes unsupported questions to the responsible person. It does not change CRM records.
Evaluation compares answers against the approved procedure and total task time against the current method. Missing sources, incorrect answers or inadequate access controls mean the next step is a fix or stopping the pilot. Additional documents and actions are a separate decision.
5. Separate delivery and running costs
The estimate covers workflow analysis, data preparation, configuration or development, integration and evaluation. Recurring costs may include model usage, document retrieval, hosting and maintenance. Request volume and document size influence the solution.
Before expansion, ask for a running-cost estimate based on your usage, spending limits and clear responsibility for updates. A successful demonstration does not replace testing the complete workflow. ESolutionMedia uses this scope to propose a pilot or a simpler alternative.
ASSESS ONE WORKFLOW
Is automation worth the cost?
Compare the time spent today with the full workflow after automation, including review and corrections. Then subtract additional running costs. Use measured pilot results when available; otherwise treat the inputs as assumptions to test.
How the estimate works
- Hours released per month = tasks × (minutes before − minutes after) ÷ 60.
- Monthly value after costs = hours released × hourly value − additional monthly costs.
- Simple payback = implementation cost ÷ positive monthly value after costs. With a zero or negative monthly value, this model has no payback.
- 12-month balance = monthly value after costs × 12 − implementation cost.
Illustrative example, not a quote or client result. 500 tasks per month, reduced from 8 to 3 minutes, release about 41.7 hours. At 60 EUR per hour and 500 EUR in extra monthly costs, the model gives 2,000 EUR per month. A 6,000 EUR implementation would have a simple payback of 3 months, if that value is realised.
Released time is capacity, not automatically a cash saving. Payback assumes you can use that capacity productively or avoid a real cost. This simple model holds monthly volume and costs constant; it excludes ramp-up, taxes, financing and changes in revenue or quality. It is not a project price or an approval to implement.
Next, test the assumptions: use a typical month, include review time and recalculate with less time saved or higher running costs. Quality and access checks still need to pass before rollout.
Discuss the assumptions for your workflowREADY FOR A CONVERSATION
Prepare a short project brief
Use these prompts to describe the project. Download the plain-text template, fill it in locally and share only the context needed for the first conversation. You can also start with a short message.
- Workflow and the person using it
- Desired outcome and what stays outside the pilot
- Available tools and sources, without confidential documents
- Approximate frequency and time spent today
- Examples of accepted results and exception types
- Who reviews results and which actions need approval
- Acceptance criteria and conditions for stopping
- Target date, available budget and acceptable running costs
The template is free and does not require an email address. Do not include passwords, confidential files or other people’s personal data.
Discuss a workflow for your pilot