A process to understand
Repetitive tasks, dispersed documents or manual steps between systems: we reconstruct the current work before attributing a solution to AI.
AI OPPORTUNITY ASSESSMENT
We review your processes, data and tools to compare practical opportunities. The aim is a reasoned decision: buy, integrate, develop or wait.
An initial discussion helps us understand your needs, with no commitment to a project.
It is useful when there are many ideas, but priorities, available data and responsibilities are not yet clear.
Repetitive tasks, dispersed documents or manual steps between systems: we reconstruct the current work before attributing a solution to AI.
We evaluate commercial products, configurations, integrations and development alongside the alternative of improving the process without AI.
We transform an idea into testable hypotheses, with constraints, responsibilities and criteria for deciding whether to continue.
Perimeter and depth are agreed based on the context; it is not an indistinct audit of the entire company.
Discussion with decision maker, people who carry out the work and IT contact person. We identify objectives, exceptions and constraints.
Map of activities, inputs, outputs, tools, data and authorizations. Minimized or synthetic samples when possible.
Opportunity cards with buy, integrate, develop and wait alternatives; dependencies and common criteria.
Comparison between expected utility, feasibility, risk and effort. We highlight what is not yet estimable.
Shared and proposed return of the first experiment, or reasons for stopping or postponing.
Output and level of detail are defined in the assignment proposal: we do not promise an economic result before having measured the starting point.
Summary of the processes examined and the opportunities compared.
Criteria and motivations readable by the decision maker, with open questions.
Proposed steps for a limited and verifiable project.
An interesting opportunity is not automatically ready to be realized. We separate observed data, estimates and conditions to verify.
We agree on the criteria with the client: frequency of activity, expected value, data availability, impact of an error and dependencies. Every score has a reason.
Estimates are prepared after the survey and indicate assumptions and uncertainty: licensing and consumption, integration, data preparation, training, controls and maintenance. They do not constitute a published price or an already approved quote.
We define baseline, sample, manager and measurement method. Examples of indicators, without promised results: time per task, errors detected, human review requests, cost per execution and actual usage.
The return does not commit you to develop with Tredipi. If you decide to continue, the pilot project requires a separate assignment: objectives, access, activities, responsibilities, acceptance criteria and budget are agreed before starting. Any commercial relationships with proposed suppliers are declared.
Methodological sample, DEMO version 1. The context and evaluations are constructed to illustrate a possible output: they do not describe an assignment, a client or results obtained by Tredipi.
Organization Alpha is fictional. An internal support group wants to understand whether to improve the search in a collection of procedures. We hypothesize inconsistent documents and permits yet to be verified: these are teaching conditions, not observations on a real company.
Inventory of synthetic or authorized documents, information search, citation of sources and human verification before use.
Unauthorized confidential data, decisions about people, automatic messages to customers and autonomous actions on systems.
| Opportunity | Proposed priority | Condition |
|---|---|---|
| Organize sources and permissions | First | Identify versions, owners, and allowed users. |
| Research with reference to sources | To compare | Evaluate traditional and AI research on the same sample. |
| Draft internal responses | After a test | Human verification, traceability and the possibility of not responding. |
| Autonomous actions on systems | Excluded | Not necessary for the hypothesized problem. |
Evaluate a product if it covers the essential requirements. Check data processing, permissions, export, limits and overall cost. A fee does not alone demonstrate adequacy.
Consider development if there are distinctive requirements not covered. Clarify maintenance, skills, continuous assessment and operational responsibilities.
Connecting existing tools can preserve workflow. Check APIs, identities, permissions and dependencies: integration does not eliminate checks.
Delay adoption if sources, permissions, or utility are not demonstrated. Define preparatory activities and a concrete condition for re-examining the choice.
In the proposed scenario the first decision is Wait on the purchase: prepare sources and access, then compare traditional research and possible AI integration. This is not a recommendation for all businesses.
| Criterion | Hypothetical evaluation | Evidence required |
|---|---|---|
| Utilities for the process | Possible, not proven | Observed activity and research baseline. |
| Quality of sources | To prepare | Inventory, versions and document manager. |
| Permissions | Blocking condition | Access test with admitted users and documents. |
| Quality of responses | To measure | Shared sample, cited sources and recorded errors. |
| Cost and reversibility | To be estimated | Licensing, consumption, integrations, human verification, maintenance and exit. |
An unresolved critical condition prevents the test from being extended. This grid does not replace technical or privacy reviews and does not certify compliance.
Illustrative scenario: An SME wants to find instructions in its internal documents. It is not a customer case, does not contain measured results and does not define contractual times or prices.
Delimit the admitted documents, check permissions and quality, assign a contact person. If these prerequisites are missing, the priority becomes data preparation.
Test a configurable commercial product and integration option on an authorized sample. Record limitations, costs to estimate, and human control burden.
Run a limited pilot with test questions, expected answers and verification of sources. Measure the agreed indicators against the baseline.
Extend only if criteria are met; otherwise correct, change solution or stop. No automatic production.
| Proposed liability | Role to be confirmed | Outputs |
|---|---|---|
| Process and utility criteria | Process manager | Scope and advancement decision. |
| Sources and accesses | Documentation / IT manager | Verifiable inventory and authorizations. |
| Test and check | Technical contact and users | I record trials, errors and comparison of alternatives. |
| Data processing | Competent privacy contact | Evaluation before using real data. |
| Proposed indicator | How to measure it | Baseline / goal |
|---|---|---|
| Search time | Median on the same sample, before and during the test. | Not detected / to be agreed. |
| Answers to be corrected | Cases with errors or insufficient sources out of the total sample. | Not detected / threshold to be agreed. |
| Unauthorized access | Negative tests on separate users and documents. | Not executed / any violation blocks the extension. |
| Cost per verified activity | Use of the service, human control and maintenance included. | Not estimated / budget to be approved. |
The illustrative choice is to postpone the purchase and prepare the test conditions. Only after an inventory, access and shared criteria would it make sense to compare the alternatives. The next decision could be to buy, integrate, develop, improve search without AI, or stop.
Limits: no real interviews, no data audits, no product tests, no quotes and no measured results. The roadmap is not a time or performance commitment. The indications must be redefined for each actual context.
No. Reconnaissance and roadmap help decide. Configurations, integrations and development require a separate assignment, with scope and verification criteria.
No. The comparison includes commercial alternatives, integrations and development, but also postponement or intervention without AI when they are more suitable.
No. Describe the process in general terms. Any samples are requested only after having agreed on the purpose, authorizations and management methods.
Tell us about your work and the questions you want to start from.