Map
Embed with a team, map the current-state workflow, and score the opportunity backlog by adoption risk — not projected impact.
Current-state workflow — bill-exception triage
Representative workflow — assumptions stated, not client data- 1Intake
Bills arrive from utilities and vendors in mixed formats and are normalized into the system of record.
- 2Validation failure
Automated checks flag exceptions — rate mismatches, demand spikes, missing fields. Volume concentrates here; many flags are benign.
◆ errors concentrates here - 3skill targetsAnalyst tariff lookup
An analyst pulls the account’s tariff and finds the applicable schedule and version. Manual, and version ambiguity is common.
◆ time concentrates here - 4skill targetsManual comparison
The analyst recomputes expected charges against billed, line by line. Seasonal and time-of-use schedules are easy to misread.
◆ time concentrates here◆ errors concentrates here - 5Resolution / escalation
Internal correction, or escalation for a payment or vendor action. Escalation criteria vary between analysts.
◆ errors concentrates here
Time concentrates in the manual tariff lookup and line-by-line comparison (stages 3–4); errors concentrate wherever a human reads a seasonal or time-of-use schedule by hand. Those two stages are what the skill automates — the analyst keeps the resolution and escalation calls.
Assumptions: a mid-to-large commercial account portfolio; exceptions already flagged by upstream validation; analysts working from tariff references rather than a single authoritative rate service. No client-specific volumes or durations are claimed — the map shows where work concentrates, not how much.
Opportunity backlog — ranked by adoption risk
Five candidate workflows, each scored on five dimensions from 1 (low adoption risk) to 5 (high). The axis is adoption risk — whether a team will actually keep using the thing — not projected impact. Lower total ranks earlier. A higher-impact workflow with a bigger blast radius or no clear owner still waits.
| # | Workflow | Workflow | Data | Judgment | Champion | Failure | Total |
|---|---|---|---|---|---|---|---|
| 1 | Bill-exception triagegoes first Bounded taxonomy; public tariff + structural bill data; a human gate on any payment action; analysts who do it daily are natural champions. | 2 | 2 | 3 | 2 | 2 | 11 |
| 2 | Procurement RFP intakenext Advisory pre-decision step with an available owner, but inputs are less structured and it sits closer to sourcing decisions. The designated next instance. | 3 | 2 | 3 | 2 | 2 | 12 |
| 3 | Tariff-change monitoring Useful, but ownership is diffuse and a missed change propagates quietly. | 3 | 2 | 3 | 3 | 3 | 14 |
| 4 | Usage-anomaly detection Judgment-heavy; false alerts erode trust and missed anomalies are costly. | 3 | 3 | 4 | 3 | 4 | 17 |
| 5 | Vendor-dispute drafting Drafts go to an external party — the largest blast radius. Waits regardless of impact. | 4 | 4 | 4 | 3 | 5 | 20 |
Why bill-exception triage goes first. It scores lowest on every dimension that predicts abandonment: a bounded classification taxonomy (low variance), public tariff data plus structural bill fields with no PII or payment credentials (low sensitivity), and a hard human gate on anything touching a payment (small blast radius). The analysts who triage today become the champions — the tool removes their most tedious step rather than replacing their judgment.
Why procurement RFP intake waits. It is the designated next instance and close behind, but its inputs are less structured and it sits nearer a sourcing decision. Proving the operating model on the safest workflow first earns the right to take on the messier one — with the template, controls, and gate already in place.
Scoring note: scores are the builder’s structured judgment for this representative setting, stated so they can be argued with — not a measured index. “Champion availability” is scored risk-first: 1 means a ready, embedded owner; 5 means no clear one.