Use Cases by Team
Each use case is one job an agent does better with a route: the next step, who signs off and what tends to go wrong, measured by a number the team already tracks.
Engineering
Briefed coding sessions
Each session starts with the files to read first and the likely next step, from sessions that did the same kind of work.
Measure Tokens per finished sessionChecks before a merge
Before merging, the agent asks. It learns which tests caught problems in changes like this one.
Measure Reverted changesTickets handed to a service
The agent for a service reproduces the bug, fixes it and opens the pull request for review.
Measure First-try rateProduct & Design
Customer signal to the roadmap
Feature requests and bugs from tickets, calls and usage, linked to the product area that owns them.
Measure Requests linked to the roadmapSpecs and designs grounded in the past
What similar features needed, the components and services they touched, and where users struggled after they shipped.
Measure Rework after reviewRelease readiness
The steps a release takes here, from flags to docs to the support briefing, and what went wrong last time.
Measure Issues after releaseIT & Security
Access to sensitive data
The data owner signs off, then a read-only grant. Requests that skip the sign-off are the ones reversed later.
Measure Requests reversedChange approvals
The approvals a change needs, in order, and what broke the last time a change like it went out.
Measure Approvals skippedOnboarding and offboarding
Every system in the order that worked before, with the owner of each step named.
Measure Time to completeSupport & Success
Escalation routing
An issue goes to the team that owns it the first time, with what that team will ask for attached.
Measure Tickets handed backContext on every ticket
Past fixes, open incidents and the account’s history, limited to what the person asking may read.
Measure Time to resolutionBugs handed to engineering
A confirmed bug goes to the agent for the service that owns it, with the reproduction attached.
Measure Reopened ticketsSales & Marketing
Account research before a call
Open tickets, usage, recent conversations and who decides, limited to what the rep may read.
Measure Prep time per meetingDeal approvals
The approvers a discount or non-standard term needs, in order, and which deals stalled waiting for them.
Measure Days in approvalCampaign and launch reviews
The legal, brand and product reviews a launch has to pass, and what slipped the last time.
Measure Launches on scheduleOperations & Finance
Refunds
The approvals a refund needs for its amount and reason, and the exceptions that tend to come back.
Measure ExceptionsQuote to cash
Each step from quote to invoice with its owner, and where deals usually wait.
Measure Cycle timeRenewals
What has to happen before a renewal date, and which accounts drift when a step is late.
Measure Work handed backHR
Hiring pipeline
The steps a hire takes here, from requisition to offer, with who approves each and where candidates wait.
Measure Days at each hiring stageOnboarding
Accounts, equipment, training and the first-week plan, in the order that worked, with the owner of each step.
Measure Ready on day onePolicy questions
Answers from the current policy, with its owner named, limited to what the asker may read.
Measure Requests resolved without a ticketLegal
Contract review routing
An agreement goes to the reviewers its type, value and terms need, with the clauses that drew comments before.
Measure Days in reviewNDAs and standard paper
Agreements the playbook already allows go out on the approved template; anything off it goes to counsel.
Measure Standard paper ratePolicy and compliance questions
Answers from current policies and past guidance, limited to what the asker may read, with the owner named.
Measure Escalations to counselLeadership
Where to place agents
The steps where work waits, loops or gets handed back, ranked by how much time they cost.
Measure Time back each weekGoverning autonomy
Each kind of move with the level it has earned, and the switch to hold any of them.
Measure Moves made without askingWhy a metric moved
A metric traced back through the work, systems and agents that produced it.
Measure Decisions traced to the work