How to Prioritize AI Use Cases Before You Fund a Build

Q: Which should you start with?

- Several ideas and no shared way to choose: the free 30-minute call, or AI in a Day. - A short list already, and a funding decision to make: AI Compass, whose fee is credited toward a subsequent build. - One well-defined use case, with requirements and data access agreed: go straight to a POC in 3 Weeks; how to read one is in what a proof of concept should prove. - A pilot that stalled before production: AI Rescue. The full decision guide is in which AI engagement you need, and the price ladder is in how much AI consulting costs.

Last updated: October 2026. External figures are attributed and dated in the text.

In short: To prioritize AI use cases, write each candidate as one specific use case, score it from 1 to 5 on value, effort and risk, and give its data a separate red, amber or green verdict. Fund first the candidate that ranks well on all four, and record why the others wait. Data gets its own verdict because readiness belongs to a use case, not to a company. Gartner predicts that through 2026 organizations will abandon 60% of AI projects unsupported by AI-ready data (a forecast, 2025-02-26). NewGenApps offers the ranking as AI in a Day, from $2,500 in one working day, and the ranking plus a data verdict as AI Compass, from $5,000, typically 2 to 6 weeks.

What does it mean to prioritize AI use cases?

Prioritizing AI use cases means ranking candidate uses of AI against each other, on the same scales, so budget goes to the one most likely to pay back and prove out, and the rest are deferred or declined on the record. The output is a ranked shortlist, one recommended first move and a "not yet / not this" list. It comes before a proof of concept (POC): prioritization chooses the candidate, and the POC tests it.

A use case is a task, not a technology. "AI for customer service" is a category; "draft first replies to routine support emails from the knowledge base, with an agent approving every send" is a use case. Rank only the second kind. For why a strategy should end in a working build, see AI strategy.

Why does data readiness belong in the ranking?

Because an idea can be sound and unbuildable at the same time. In a Q&A published on 2025-02-26, Gartner predicted that "through 2026, organizations will abandon 60% of AI projects unsupported by AI-ready data." That is a forecast, not a measured rate. The same page says 63% of organizations either do not have, or are unsure whether they have, the right data management practices for AI. Gartner's page description ties that figure to a third-quarter 2024 survey of 248 data management leaders; the body text names a July 2024 survey of 1,203 and gives no sample for the figure. We cite the 63% without a sample size and read it as directional.

A survey conducted by Harvard Business Review Analytic Services with Cloudera, a data-platform vendor, points the same way. Of more than 230 HBR audience members involved in their organizations' AI data decisions, surveyed in October 2025, only 7% said their data was completely ready for AI adoption (press release, 2026-03-05). The sample is small and drawn from one publication's audience: a signal, not a rate.

Gartner's definition matters most for ranking. AI-ready data must be representative of the use case, including its patterns, errors and outliers, and the first of Gartner's five steps is to align data to AI use cases. Readiness belongs to a use case on a system: the same customer export can be ready for sorting inbound email and unready for forecasting churn. So readiness gets its own verdict beside the scores. What a live system must then enforce about its data is covered by the data-integrity contract.

How do you score a use case on value, effort and risk?

Score each candidate from 1 to 5 on three scales and write one sentence of reasoning beside every score. For value, 5 is best. For effort and risk, 5 is worst. Value asks how large and certain the benefit is against a named baseline; effort, what it takes to reach production; risk, how likely a wrong or missing output is and what one costs. NIST's AI Risk Management Framework defines risk as the combination of an event's probability and the magnitude of its consequences (NIST AI 100-1, January 2023), and says the acceptable level is "highly contextual and application and use-case specific." Tolerance is yours to set, within any rules your sector already imposes.

Scoring anchors for value, effort and risk

Our working anchors, so two reviewers land in the same place:

Scale	Question it answers	1	3	5
Value (5 = best)	Size and certainty of the benefit	Marginal or speculative	Meaningful, plausible case	Large, tied to a named line item with a defensible baseline
Effort (5 = heaviest)	Work to reach production	Weeks, self-contained	About a quarter, manageable dependencies	Many months, heavy dependencies, new data or integrations
Risk (5 = highest)	Likelihood and cost of a wrong output	Low and reversible; a person reviews each output	Moderate; manageable with controls	High: customer-facing, regulated or hard to reverse

The scores are ordinal judgments, not measurements: a 4 is not twice a 2. If you combine them into one number, show the three scores beside it and treat the total as a rough guide. The decision is argued over the components. Score each candidate separately before reconciling, because the person who proposed an idea should not be its only scorer.

How do you check whether the data is ready?

Ask four plain questions about each system the use case depends on, answer them with evidence, and give the system a red, amber or green verdict.

Freshness. How old is the data when the use case uses it, how old can it be before the output is wrong, and would anyone notice if the feed stopped?
Ownership. Who owns it, who can approve its use, and who fixes it when it is wrong?
Access. Can the team reach it, how long does approval take, and do privacy, residency or contract terms limit its use?
Quality. Is it complete, consistent and representative of the cases the use case will meet, including the awkward ones, and labeled where the use case needs labels?

What "the data" means shifts with the use case. For drafting or search over documents, it is the documents: who maintains them, whether they contradict each other, who may see each one. For prediction, it is labeled history: enough examples of each outcome, and labels you trust. Evidence means a sample pulled, a person named, a timestamp seen.

Red, amber and green verdicts

Verdict	Meaning	Effect on the ranking
Green	Reachable, owned, fresh enough and good enough to start on now	Eligible to be the first build
Amber	Usable with named fixes, each with an owner and a rough effort	Eligible once the fixes are scheduled; their effort counts in the effort score
Red	A blocker: no access, no owner, or not usable for this task	Moves down the order; the fix becomes its own work, or the candidate waits

How do you turn the scores into a ranking?

Run the same seven steps for every candidate and keep the working visible.

Write each candidate as a use case. One sentence naming the task, who does it today, the decision it informs and the system it touches.
Screen out the wrong tool. Set aside anything a written rule, a report or a process change would handle better.
Name the value. The line item it should move, today's baseline and the person who owns that number. A benefit with no baseline cannot score 5.
Score value, effort and risk, each 1 to 5 with a sentence of reasoning, separately by at least two people, then reconcile.
Ask the four data questions for each system and record a red, amber or green verdict with its evidence.
Rank. High value with low effort, low risk and green or amber data goes first. High value with high effort is a staged bet, usually proven by a POC first. Low value with high effort is declined, in writing.
Name the first move and write the defer list. Say what the first build must prove, and give each deferred candidate a reason and a condition for revisiting it.

When is AI the wrong tool for a candidate?

When a simpler tool does the job, or when success cannot be shown. Five signs:

A rule can be written down. If an expert can state the logic and the inputs are structured, ordinary software is usually cheaper to build, test and audit than a model.
Nobody can score the output. With no agreed way to judge an output, whether against known answers or a reviewer's written rubric, you cannot show the system works; see the evaluation harness.
Volume is too low. A task done a few times a month is unlikely to repay the build and run cost.
A wrong answer is costly and unreviewed. Either design the review in, or do not automate the step.
The data is out of reach. That is a red verdict, not a modeling problem, and a better model will not fix it.

Each is a result, not a failure: a shortlist can include candidates that need no AI.

What do AI in a Day and AI Compass deliver?

Both rank candidates with a senior practitioner, and neither builds anything. AI in a Day scores value, effort and risk from what the people in the room know. It does not connect to your systems, so it gives no data verdict. AI in a Day delivers the ranked shortlist, a one-page "where to start" and a "not yet / not this" list in one working day. AI Compass goes deeper for leaders who need a costed roadmap and a data-readiness verdict before funding a build: initiatives are scored on value, feasibility, time to value and risk with their ROI assumptions exposed, and each system is rated red, amber or green.

AI in a Day and AI Compass compared

	AI in a Day	AI Compass
Good fit when	Several ideas compete, an earlier effort stalled, or a board wants a plan	You need a costed, ranked roadmap and a data verdict before funding a build
You get	Ranked shortlist, one-page "where to start," "not yet / not this" list	Prioritized, costed roadmap; red, amber or green data-readiness scorecard; recommended first POC; executive readout
Duration	One working day	Typically 2 to 6 weeks
Starting price	from $2,500	from $5,000, credited toward a subsequent build

Which should you start with?

Several ideas and no shared way to choose: the free 30-minute call, or AI in a Day.
A short list already, and a funding decision to make: AI Compass, whose fee is credited toward a subsequent build.
One well-defined use case, with requirements and data access agreed: go straight to a POC in 3 Weeks; how to read one is in what a proof of concept should prove.
A pilot that stalled before production: AI Rescue.

The full decision guide is in which AI engagement you need, and the price ladder is in how much AI consulting costs.

What happens after the ranking?

The first move is funded as the smallest valuable thing the evidence supports, usually a proof of concept with its pass/fail bar written first, then a production build. Decide at the same time how payback will be measured against a baseline taken before launch; measuring AI ROI in production covers the method. Deferred candidates return when their condition is met: the data fixed, the review designed in, the volume proven. Re-score when the data or the business changes.