Not every use case earns a pilot.
By the end of this lesson, you'll be able to qualify any use cases that are worth scoping and identify which three engagement patterns consistently produce a defensible ROI story at Day 30.
Two types of gain. One of them survives a CIO readout.
Before scoping a pilot, you need to know whether the use case produces structural change or marginal improvement. The distinction determines whether your ROI case holds at Day 30.
The unit of work doesn’t change. Claude speeds up an existing task, reduces friction, or cuts time on something repetitive. Productivity gains are real but diffuse, and hard to isolate from other factors in a 30-day window. Examples: autocomplete, boilerplate generation, inline documentation. Good for adoption momentum. Difficult to anchor a CIO-level business case to.
The unit of work itself shifts. A task that required a team of four and six weeks now requires two developers and two weeks. The ROI case is measurable before Day 30 and defensible at the readout. Examples: legacy migration at scale, new feature loops with full Claude participation, framework-level modernization. Anchors a renewal conversation.
Two activation modes. One changes the data you get.
The scope decision happens at engagement entry. Mode 1 is a training-only activation. Mode 2 wraps it in a 30–45 day program.
Code 101 and admin setup delivered as a standalone training event. Fast to deploy, minimal setup. Produces adoption signals but not ROI data: there’s no measurement period, no use case owner, and no baselined metrics to close the loop against.
Training plus a structured activation: pre-kickoff setup, use case definition, a midpoint check at Day 20–25, and a closeout readout with champion-presented results. ROI data is available because the measurement infrastructure was built before Day 1.
Three engagement patterns that consistently produce structural gains
Migrate legacy stacks, translate languages, upgrade dependencies across a large codebase. Claude handles the volume; developers handle judgment calls on architecture. The ratio of Claude-assisted commits to total commits is directly measurable.
Accelerate net-new development through the full feature loop: scaffolding, implementation, tests, review prep. PR cycle time before and after is the core metric. Works best when the feature scope is clear and CLAUDE.md is well-invested.
Move between frameworks, cloud providers, or architectural patterns. Well-scoped, high-volume, low-ambiguity tasks ideal for agentic delegation. Velocity gain is visible within the first two weeks.
Four criteria that separate a pilot-worthy use case from a wishlist item
Not every use case that sounds promising passes qualification. Run each candidate through these four criteria before committing to a pilot scope. A weak score on any one is a signal to reframe the use case or deprioritize it.
Volume means the task recurs frequently enough to generate meaningful data in 30 days. A one-off project doesn’t qualify regardless of complexity.
Complexity means Claude adds real leverage, not just speed. If a junior developer could do the task in an afternoon, Claude’s contribution is marginal. If it takes a senior engineer three weeks, there’s structural gain available.
Measurability means you can capture a baseline before Day 1. If you can’t measure it before the pilot starts, you can’t close the ROI loop at Day 30. This is non-negotiable.
Developer readiness means the team is willing to change their workflow, not just try a tool. A pilot where developers use Claude occasionally around their existing habits produces flat metrics. Adoption has to be designed in.
A use case that scores well on complexity but fails on measurability is not a pilot candidate. It is a risk.
The Arvana Technologies Qualification
Arvana Technologies is a mid-market software firm with a 60-developer engineering team. Their CTO wants a Claude Code pilot. Three decisions, up to 6 points.
Arvana’s engineering lead proposes two use cases. Option A: using Claude Code to add unit tests to a codebase that already has 82% coverage. Option B: a Java-to-Spring Boot migration the team has been scoping for eight months.
Which use case qualifies for the pilot?
The team chooses the migration. Now determine which metric to baseline before Day 1.
Which baseline metric gives you the most defensible ROI story at Day 30?
You’re designing the pilot cohort. Arvana has 60 developers. Migration is the work.
Which cohort design produces the most signal by Day 30?
By the end of this course you’ll have a complete Delivery Plan Pack covering qualification, pilot design, ROI scorecard, and champion plan. This lesson contributes the qualification section.
You can qualify a use case. Now design the pilot.
The structural vs. marginal distinction is the first decision in every Claude Code engagement. Structural gains produce defensible ROI. Your qualification section is started.