← Assessment library

7 to 9 minutes

Assess an AI use case

Prioritize an AI use case across business value, ROI, data, risks, dependencies and control.

Assess one specific use case to obtain a reasoned initial direction: launch, frame, experiment, defer or discard. The most sensitive assumptions must be confirmed before investment.

ROI – Risk – Control matrix

Business value · ROI · data · risks · costs · dependencies · reversibility · implementation capacity.

Context

Which sector or business area is this use case in? *

Keep it general: do not enter confidential information.

What is the approximate size of the organization? *

1 to 10 peopleVery small organization or autonomous team.11 to 50 peopleSmall organization with few decision layers.51 to 250 peopleMid-sized organization with several involved functions.251 to 1,000 peopleStructured organization, often across several departments.Over 1,000 peopleLarge organization, potentially multi-entity.

Required field

What is your role in the decision? *

This helps assess sponsorship and action capacity.

Which family best describes this use case? *

This explicit choice determines the right path. Free text is never used for automatic routing.

Business process or productivityReduce workload, re-entry, delays or errors on a defined process.Analysis or decision supportPrepare analysis or a recommendation that remains validated by an accountable owner.Customer or citizen serviceHelp prepare, personalize or improve an external interaction.Document search or knowledgeRetrieve, summarize or reuse authorized internal content.Tender responseIdentify requirements and prepare responses from validated content.Governance or usage controlMake uses visible, set rules or organize approvals.

Required field

How many use cases actually need to be compared? *

The number of cases determines the comparison format and workshop depth.

One use caseFocused decision: the one-case format closes essential assumptions.Two to three use casesSmall portfolio suitable for a structured diagnostic.Four to five use casesA prioritization matrix becomes preferable to isolated analysis.Six to twelve use casesA common framework can compare this portfolio before prioritization.More than twelve use casesThe portfolio must first be grouped and sequenced before detailed scoring.

Required field

Describe the AI use case in one operational sentence. *

State the process, the user and the expected outcome. Avoid real client data.

Value and ROI

How often does this process occur? *

OccasionalA few times per year.MonthlyAt least once a month.WeeklyEvery week or nearly.DailyEvery working day.Several times a dayHigh or repetitive volume.

Required field

How much time or effort does it currently consume? *

MarginalLittle time or effort.LimitedReal but contained workload.RegularRecurring workload for a team.HighVisible, costly or frustrating workload.Very highHigh, repetitive or blocking workload.

Required field

How many people or teams are affected? *

One person / isolated caseVery limited scope.Small teamA few people involved.Team or departmentA whole department or process.Several teamsVisible cross-team impact.Organization / clientsBroad impact, including clients or users.

Required field

How business-critical is it if the process is slow or poorly executed? *

LowError or slowness has no major consequence.LimitedLocal or easily recoverable impact.SignificantNoticeable impact on quality, timelines or workload.HighImportant business, client, financial or reputational impact.CriticalCritical impact on decision, continuity or obligations.

Required field

What quality or reliability gain can be expected? *

LowLittle expected improvement.LimitedUseful but secondary gain.SignificantFewer errors, delays or iterations.HighVisible gain on quality, timeline or satisfaction.Very highMajor, measurable and valuable improvement.

Required field

Is a decision expected soon? *

No deadlineInteresting topic, but no near-term decision.To monitorDecision may happen later.Within 90 daysA decision or direction is desirable this quarter.Within 30 daysDecision expected soon.ImmediateStrong pressure, decision or upcoming event.

Required field

Risks and control

Are the required data or documents available and reliable? *

Unavailable or unreliableData is scattered, outdated, unavailable or unverified.FragileSome data exists, but quality or access is an issue.Usable with preparationData seems useful, but requires cleaning or validation.GoodData is mostly available, up to date and understandable.Very goodData is structured, reliable, accessible and governed.

Required field

How sensitive is the data involved? *

Non-sensitivePublic, generic or fictitious data.Low-sensitivity internalInternal data with limited confidentiality stakes.Regular internal / clientInternal or client data to protect, without extreme criticality.ConfidentialContracts, client data, HR, strategy, finance or sensitive elements.Highly sensitive / regulatedHealth, highly sensitive data, secret, security or strong regulatory exposure.

Required field

Would AI output be reviewed or validated by a human? *

No review plannedOutput would be used as-is.Occasional reviewReview exists, but depends on individuals.Review for sensitive casesImportant cases are reviewed, without exhaustive rules.Formalized reviewReview responsibilities and criteria are known.Systematic and tracked reviewCritical outputs are reviewed, validated and traceable.

Required field

Is there compliance, legal or regulatory exposure? *

Very lowLow legal, regulatory or reputational stakes.LowSome rules to respect, easy to document.ModerateValidations or traces will be needed.HighLegal, GDPR, security or business frame must be addressed explicitly.CriticalHigh non-compliance risk, sensitive decision or external impact.

Required field

Does the use case create strong tool or supplier dependency? *

LowLimited lock-in, credible alternatives or easily recoverable data.LimitedDependency exists but can be worked around.ModerateSome dependencies to document before commitment.StrongProvider, contract, integration or data is hard to replace.Very strongExit is costly, complex or uncertain.

Required field

How complex is integration with existing systems or tools? *

Very simpleLittle or no system integration.SimpleLimited connection or use, without critical dependency.ModerateSome flows, accesses or tools to coordinate.ComplexMultiple integrations, sensitive systems or strong constraints.Very complexArchitecture, security, data or legacy make the topic heavy.

Required field

Does the organization have the capacity to implement and monitor it? *

Very lowNo sponsor, no availability or no owner.LimitedSome capacity is possible, but fragile or unconfirmed.PartialA lead exists, with limited availability.GoodSponsor, leads and scoping time are identified.StrongActive sponsor, available team and decision capacity.

Required field

How well evidenced are the answers provided? *

Distinguish intuition from recent, sourced and validated assumptions.

Very lowRough or unverified assumptions.LowSome rough figures, but many uncertainties.MediumPlausible assumptions, to be confirmed before investment.GoodData is reliable enough to scope a decision.HighRecent, sourced data validated by business teams.

Required field

Choose what happens next

You can generate the diagnostic anonymously. Contact details are only retained if you request email delivery or a conversation with BRAINYTECH.

Name

Organization

Role

Phone

Source

I would like to receive the link to this summary by email.

This authorization is limited to delivery and does not authorize commercial follow-up.

I would like BRAINYTECH to contact me about this diagnostic.

If you request delivery or contact, the contact details you provide are used only for that purpose. Privacy (2026-09-10)

This diagnostic is indicative. It does not replace a full audit. It is used to identify a first orientation and whether deeper scoping is useful.