What does a first pilot look like for an agent team in vendor finance?

A retail operations group runs vendor finance for store fit-outs, and its agent team is building a booking agent. The engineering lead, a credit operations analyst and a product owner meet MirrorFirm to scope a pilot.

**Question set:** can the agent book fit-out loans correctly when approvals are amended after sign-off? They choose one product, the loan account and schedule tools they already use, and a mix of bookable and blocked cases. They ask for JSONL tasks, Parquet state tables and an answer key listing acceptable alternative paths.

**Run:** the team loads the sample into its harness, resets before each task and records the diff. The analyst reviews a handful of cases for plausibility and flags two where the key disagrees with how the process normally works. Those are sent back for correction.

**Finding:** on cases where an amendment email changes the repayment day after approval APP-5120, the agent keeps the original day and lodges instruction DD-8802 for the wrong date.

**Consequence:** the team adds amendment handling to its agent, asks for more amendment-heavy cases in the next release, and writes down the licence uses it needs for training.

**What it teaches:** a pilot works best when it is built around one question, includes a practitioner review of the keys, and ends with a clear scoping decision.