The most expensive AI mistake is not building the wrong thing — it is building the right thing in the wrong order, and skipping the assessment that would have told you the difference.
A company with 20 potential AI use cases that picks the flashiest one instead of the highest-ROI one burns budget, loses organizational confidence, and makes the second AI project harder to fund. The opportunity assessment is the step that prevents this. And most companies skip it entirely.
Three selection biases show up again and again, and each one produces a technically working AI feature that nobody can connect to revenue or cost savings.
The shiny object bias. Leadership picks the most impressive-sounding use case. “Build us an AI agent” sounds better in a board meeting than “automate the 40 hours per week our team spends categorizing inbound requests.” The second one has 10x the ROI. The first one gets funded.
The vendor-led bias. The company picks the use case their AI vendor recommends. That recommendation is shaped by what the vendor’s product is designed for, not by what has the highest business impact. The vendor sells what they have. You buy what you need. Those are rarely the same thing.
The technical-first bias. The engineering team picks the use case that is most technically interesting. Training a custom model on proprietary data is more exciting than connecting an off-the-shelf API to a manual workflow. But the off-the-shelf integration might save $200K per year. The custom model might produce a nice demo and a conference talk.
McKinsey’s 2025 State of AI report found that of 25 organizational attributes tested, fundamental workflow redesign had the single strongest correlation with EBIT impact from AI. But only 21% of organizations have redesigned even some of their workflows. The other 79% are layering AI on top of existing processes without asking whether those processes are the right place to start.
AI opportunity assessment: A structured, pre-build process that inventories business workflows, scores each on business impact and implementation feasibility, and identifies the single highest-ROI AI use case to pursue first — before any development budget is committed.
Here is the framework used at Fraction before recommending any AI build. Five steps, and the order matters.
List every business process that involves repetitive human judgment, information synthesis, or pattern recognition. Do not filter yet. Just list. Customer support triage. Invoice processing. Sales lead qualification. Report generation. Data reconciliation. Quality checks. Scheduling. Document review.
The goal is a complete inventory, not a curated shortlist. Filtering too early is how companies miss the highest-value opportunities hiding in unglamorous workflows.
For each process, estimate four things: how many hours per week it consumes, the error rate or quality issues, the cost of those errors, and the revenue impact if the process were 50% faster or more accurate. Score each on a 1 to 5 scale. The processes that score highest here are your candidates, regardless of how exciting they sound.
A mid-market company assessed last year had 14 potential AI use cases on the board. The one the CEO wanted to fund was an AI-powered customer recommendation engine. The one that scored highest on impact was automated invoice matching — a process that consumed 60 hours per week across three people, had a 12% error rate, and cost the company roughly $180K annually in corrections and delays. The invoice matching project shipped in 6 weeks and paid for itself in 4 months. The recommendation engine is still on the roadmap, properly sequenced behind the project that funded it.
For each process, evaluate: Is the data available and structured? How complex is the integration with existing systems? Are there compliance constraints? Is there an off-the-shelf solution, or does this need custom development? Score each on a 1 to 5 scale.
RAND Corporation research identified data readiness as the second most common root cause of AI project failure. If the data is not accessible, the project will stall at the data engineering phase regardless of how strong the business case is.
Plot impact versus feasibility. The top-right quadrant — high impact and high feasibility — is your starting shortlist. High impact, low feasibility goes on the roadmap for later. Low impact, high feasibility is a quick win if you need an early proof point. Low impact, low feasibility gets cut.
Not three. One.
The first AI project is a proof of the operating model, not a transformation program. It proves that AI works in your environment, with your data, for your team. It builds organizational confidence. It creates the internal case study that funds everything after it. Companies that launch three AI projects simultaneously split focus, compete for the same data engineering resources, and end up with three half-finished prototypes instead of one production feature.
| Quadrant | Impact | Feasibility | Action |
|---|---|---|---|
| Start here | High | High | First build |
| Quick win | Low | High | Optional proof point |
| Later roadmap | High | Low | Sequence after first build |
| Cut | Low | Low | Remove from list |
The output should be a prioritized list of 3 to 5 AI opportunities, each with the business process it targets, the estimated business impact in hours saved or revenue effect, the technical approach (buy, integrate, or build custom), the estimated cost and timeline, the data readiness status, and the success metric.
The deliverable should not be a 50-page report. It should be a 3 to 5 page document that a CEO can read in 15 minutes and a CTO can execute against immediately. If your assessment deliverable requires a presentation to explain it, it is too complicated.
A hands-on deep dive into your AI opportunities, gaps, and competitive blind spots. Walk away with a prioritized playbook you can act on immediately.
Book Your Audit$8K flat fee. No surprises.
A focused assessment for a mid-market company — 50 to 500 employees across 3 to 5 departments — takes 2 to 4 weeks and involves stakeholder interviews, data infrastructure review, and process mapping.
Cost varies. Typically $10K to $30K for an external assessment, or 40 to 80 hours of internal work if done in-house. The internal route is cheaper upfront but slower and prone to the same selection biases described above, because internal teams carry existing assumptions about which processes matter most.
The ROI math is straightforward. A $15K assessment that prevents a $200K investment in the wrong use case is the best money you will spend on AI. A $15K assessment that identifies a $180K annual savings opportunity pays for itself before the build is finished.
Before committing to a full build, it is worth understanding whether your company is truly ready for AI — data infrastructure, integration complexity, and organizational readiness all affect which opportunities are actually actionable in the near term.
Even when companies do an assessment, two patterns cause problems.
The assessment is done by the same team that will build. They have an incentive to recommend the project that is most interesting to build, not the one with the highest business impact. Separating assessment from build eliminates this bias. If the team doing the assessment also does the build, outcome-based pricing is the check: they only get paid for what ships and delivers value, so the incentive is to scope the right thing.
The assessment skips the data layer. The team identifies the highest-impact opportunity, scopes the build, starts development, and discovers 6 weeks in that the data they need lives in four systems, two of which have no API. The project stalls for months on data engineering. A proper assessment surfaces data readiness issues before a dollar is committed to the build.
Understanding which specific business processes are best suited to AI automation is a natural complement to the opportunity assessment — once you know your highest-impact candidate, you need to know whether automation is the right technical approach for that particular workflow.
An AI strategy tells you where AI fits in your business over the next 2 to 3 years. An AI opportunity assessment tells you what to build first and why.
Most companies that come asking for an AI strategy actually need an assessment. They do not need a roadmap for the next 3 years. They need clarity on the next 90 days. The strategy can come later, once the first project proves the model works and the organization has real production data to plan around.
The companies that succeed with AI spend 2 weeks choosing the right problem before spending 8 weeks building. The companies that fail skip the assessment and start building whatever sounded exciting in the last vendor demo.
For founders who are not sure where AI fits at all, this guide to AI strategy for non-technical founders covers how to approach the question without a technical background — which is a useful frame before undertaking a formal assessment.
Fraction’s AI audit starts with this exact framework. Before any technology is discussed, we map business processes, score them on the impact-feasibility matrix, and identify the 1 to 2 highest-ROI opportunities. The output is not a strategy deck. It is a scoped, costed plan for the first AI build. Book a free consultation to start your assessment.
An AI opportunity assessment is a structured process for identifying which business workflows are the highest-ROI candidates for AI investment before any development begins. It matters because the three most common selection biases — shiny object, vendor-led, and technical-first — consistently produce AI features that work technically but cannot be connected to revenue or cost savings. A proper assessment surfaces data readiness issues, quantifies business impact, and selects one project, not three, so that the first build actually ships to production.
Run every candidate process through two scores: business impact (hours consumed, error rate, cost of errors, revenue effect) and implementation feasibility (data availability, integration complexity, compliance constraints, build versus buy). Plot the results on an impact-feasibility matrix. The top-right quadrant — high impact, high feasibility — is your starting shortlist. Then select one, not multiple, for the first build. The first AI project is a proof of operating model, not a transformation program, and splitting focus across three simultaneous projects reliably produces three half-finished prototypes.
A focused assessment for a mid-market company — 50 to 500 employees across 3 to 5 departments — takes 2 to 4 weeks and involves stakeholder interviews, data infrastructure review, and process mapping. External assessments typically cost $10K to $30K. Internal assessments are cheaper upfront but slower and more prone to the same selection biases you are trying to eliminate, because internal teams carry existing assumptions about which processes matter most. A $15K assessment that prevents a $200K investment in the wrong use case is the best money you can spend on AI.
Two patterns cause most failures. First, the assessment is done by the same team that will build. They have an incentive to recommend the project that is most interesting to build, not the one with the highest business impact. Separating assessment from build eliminates this bias. Second, the assessment skips the data layer. Teams identify the highest-impact opportunity, scope the build, start development, and discover six weeks in that the data they need lives in four systems, two of which have no API. A proper assessment surfaces data readiness issues before a dollar is committed to development.
An AI strategy tells you where AI fits in your business over the next 2 to 3 years. An AI opportunity assessment tells you what to build first and why. Most companies that ask for an AI strategy actually need an assessment — they do not need a roadmap for the next three years, they need clarity on the next 90 days. The strategy can come later, once the first project proves the model works and the organization has real production data to plan around.
A proper assessment deliverable is a 3 to 5 page document — not a 50-page report — covering a prioritized list of 3 to 5 AI opportunities, each with: the business process targeted, the estimated business impact in hours saved or revenue effect, the technical approach (buy, integrate, or build custom), the estimated cost and timeline, the data readiness status, and the success metric. If your assessment deliverable requires a presentation to explain it, it is too complicated.
Praveen Ghanta is a five-time founder and serial entrepreneur. He is the founder of DevHawk.ai, an AI-powered engineering management platform, and Fraction.work, which connects fast-growing companies with top fractional tech and growth marketing talent. Previously, he founded HiddenLevers, a risk analytics platform for wealth management that he bootstrapped from inception to acquisition by Orion Advisor Solutions in 2021, serving thousands of advisors and $600B in assets. He earlier founded SmartWorkGroups, acquired by Intralinks in 2000.
Connect on LinkedIn →Describe your software or AI project. Get a full scope with story-point pricing, sprint estimates, and a downloadable plan in minutes. No calls, no waiting.
Scope Your Project for FreeWorking on a data strategy? Talk to a Fraction CTO. → Book an intro call
