What does a useful first pilot look like for a team building a utility onboarding agent?

The product lead of a team building an agent for utility connection requests asks MirrorFirm for a sample. The agent handles new-connection applications for a retail energy provider, and the customer team says it asks for more documents than needed.

They scope a pilot around two case types: residential connection and tenant transfer. They ask for requirement sets for each, a spread of cases from clearly sufficient to clearly insufficient, and a smaller group of borderline cases where a substitute document is arguable.

The sample arrives as case records, document records, requirement sets and gap labels, with a held-out portion kept for evaluation. The team's reviewer opens several cases. In CONN-0731, the proof of occupancy is a lease extract rather than a signed lease; the requirement set lists extracts as acceptable, and the gap label is empty. The reviewer notes their own agent would have asked for the full lease.

They also find that no case includes a policy version change, though their process revises requirements each quarter. They add that to the scope as a second round, with mid-case version changes in the environment.

**What it teaches:** a first step is a narrow sample that exposes mismatches in scope, not a broad purchase. Check labels against your own policy, record defects, and decide what the next release should add.