AI opportunity selection

How to prioritize AI opportunities by revenue, margin, and capacity

Start with business pressure and a repeatable unit of work. The best first project has meaningful value, enough volume, usable data, a stable process, an accountable owner, and consequences you can control.

Short answer: score each candidate from 1–5 on business value, frequency, feasibility, data readiness, change burden, and risk. Favor high-value, high-frequency work with an owner and measurable baseline. Penalize unstable processes, inaccessible data, and high-consequence decisions even when the theoretical upside is large.

Value determines why. Feasibility and risk determine whether now.

DimensionAsk5 looks like1 looks like
Business valueWould this materially affect revenue, margin, capacity, quality, or risk?Leadership KPI with a clear economic mechanismConvenience with no owned outcome
Frequency and volumeHow often does the unit repeat?Daily, high-volume, similar casesRare, bespoke work
Process stabilityCan operators describe the normal path and exceptions?Documented, observable, bounded exceptionsChanges constantly or depends on heroics
Data readinessAre required inputs accessible and trustworthy?Structured, permissioned, representativeMissing, inaccessible, or contradictory
Change burdenHow many roles, systems, approvals, and habits must change?One owner, few systems, reversible rolloutEnterprise-wide behavior change
Risk and judgmentWhat happens when the system is wrong?Low consequence, easy review and reversalMaterial legal, financial, safety, or customer harm

Do not simply add the six scores. Business value and frequency increase priority. Change burden and risk should be subtracted or treated as gates. A high-value workflow with no owner, no baseline, or uncontrolled consequences is an audit candidate—not an autonomous implementation candidate.

Three plausible projects; one better first move.

Customer health report

High weekly effort, stable sources, one operating owner, reversible drafts. Strong first candidate: measure time-to-report and decision latency, then automate preparation with human approval.

Contract negotiation

High value but low frequency and high judgment. Use AI for research and clause comparison, not autonomous decisions. Keep legal approval explicit.

Company-wide knowledge bot

Broad appeal but vague owner, permissions, success metric, and source quality. Narrow it to one decision and one audience before funding a build.

A practical first-week decision process

1. List workflows, not tools

Name the unit of work, owner, volume, handoffs, and failure cost. “Use an agent” is not an opportunity definition.

2. Quantify the current state

Measure touch time, wait time, rework, loaded cost, quality, and downstream capacity or revenue effect.

3. Fund a bounded proof

Pick one baseline, one owner, one review window, one human-control policy, and one stop rule.