Archos Labs
AI as Strategy

AI Value Levers Stop Wasted AI Spend

Rob Angeles3 min readPublished
Share
Diagram showing AI value levers tied to cost reduction and revenue per workflow metrics.

Most AI pilots never leave the lab. The problem isn’t the tech—leaders greenlight spend without tying it to a business outcome they measure. Here’s how to fix it.

You’ve approved three AI pilots this quarter. One reads loan applications faster. Another drafts customer emails. The third flags fraud in real time. None of them have a dollar sign attached to the business case. You know this because the approval forms don’t ask for one. They ask for model accuracy, latency, and vendor reputation—items engineers care about, not you.

Pilots run. Metrics appear strong. Teams celebrate. Then nothing happens.

Pilots remain pilots. Spending continues. The board asks for ROI. You don’t have an answer.

This isn’t a technology problem. It’s a decision problem.

The approval form is the bottleneck

Grant Thornton’s 2026 advisory team says leaders generate AI value by defining it as a business capability, not a technology experiment. The approval form should ask two questions before anything else: Which existing business metric will this move? and By how much? If the answer is “we don’t know yet,” the pilot doesn’t get approved. Not because the tech is bad, but because decision criteria are broken.

BCG’s 2025 work with banks shows the same pattern. The banks scaling AI didn’t start with the fanciest use cases. They started with lending operations—high-volume, repetitive workflows where cycle time reductions translate directly to cost savings. Workflow redesign came first, then AI integration. The approval form for those projects didn’t ask for model accuracy. It asked for EBITDA impact.

The Global Risk Community calls this “pilot purgatory.” Organizations post-2023 have hundreds of pilots running, but no rollout templates. Governance is absent. Connection to operating value is missing. The approval form is the missing link. If it doesn’t force a tie to a named value lever—cost reduction or revenue per workflow—the pilot fails before it starts.

The counterargument is real but wrong

Leader Talk’s webinar organizers say pilots fail because of implementation gaps—poor data quality and broken integrations. They aren’t wrong. A pilot tied to a clear value lever will still stall if data sits in silos or staff can’t interpret outputs. But pilot purgatory’s primary cause isn’t this. Global Risk Community’s data shows the real blocker is missing rollout templates and governance. BCG’s banks had the data and staff. What they created first was an approval form forcing EBITDA ties.

The counterargument treats infrastructure gaps as an alternative explanation. These gaps aren’t significant. They’re prior conditions. One can fix the approval form while data remains messy. You can’t fix data while the approval form allows pilots to launch without business cases.

The fix is simpler than you think

Stop approving AI spend based on technology promise. Start approving it based on a named, measurable impact to an existing business metric. The approval form should look like this:

  1. Which value lever will this move? (Cost reduction or revenue per workflow.)
  2. By how much? (Dollar amount or percentage.)

If the team can’t answer these questions, the pilot doesn’t get approved. Not because the tech is bad, but because decision criteria are broken. This isn’t about being conservative. It’s about clarity. Approved pilots will have built-in business cases. They scale because their design demands it.

Vendors won’t like this. They sell AI as a magic box. You’re making them sell it as a business tool. Good. Those unable to adapt don’t deserve your budget.

Share
Rob Angeles

Written by

Rob Angeles

Most consulting engagements split the thinking from the doing. Rob doesn't. Principal Consultant at Archos Labs, he owns the full stack — assessment, architecture, delivery — across retail, financial services, healthcare, and government.