Back to Demo Lab
Interactive systems demo · 04Financial operations
From spreadsheet chaos to one operational workflow.
Merchant dispute data was bouncing around in spreadsheets over email, Slack, and Drive. We migrated the old records into a structured system — and made sure new disputes never needed a spreadsheet at all.
Why this mattered
Every spreadsheet copy was another chance to overwrite something, lose a change, or work from the wrong version. And because this was financial dispute data, “looks right” was not good enough — the records had to be checked for both format and factual accuracy.
What came from the real project
The underlying problem and approach are real: CS shared merchant-dispute spreadsheets across multiple channels; we ingested the legacy data, normalized, deduped, and verified it in multiple passes, built structured intake for new disputes, and created onboarding materials for the new workflow. The tool reached operational use in roughly 2–3 weeks and eliminated about 295 hours of manual entry each month.
What is illustrative
The fictional system name “ResolveIQ,” merchant names, case numbers, sample files, values, field mappings, conflicts, and review outcomes in this demo are invented. No proprietary records, internal product names, or client data are shown.
Run it · inspect it · try to break it
Watch the records move.
How to use this demo
Legacy migration is the messy version: find the copies, map the fields, clean them up, dedupe, review, verify, publish.
Clean run shows the same idea when the source data is not a disaster.
New dispute shows what replaced the spreadsheet for new work.
Use Brenda whenever you would like to publish something that absolutely should not be published yet. 😈
Data Operations Workbench
Legacy dispute migration
Keep the originals. Fix what is safe. Publish only what we can verify.
PIPELINEIDLE
- 01SOURCES
- 02MAP
- 03NORMALIZE
- 04DEDUPE
- 05VALIDATE
- 06REVIEW
- 07VERIFY
- 08READY
- 09PUBLISHED
WORKING SET
Three copies. No single version we can trust yet.
The files loaded. That does not make them correct.
Before these become application records, we have to reconcile what changed and what is actually true.
| Source | Case # | Merchant | Received | Amount | Status |
|---|
LEGACY COLUMNTRANSFORMATIONNEW RECORD
Legacy spreadsheetsmigration translator→
ONE SHARED RECORD SHAPEResolveIQ record
New structured formvalidated intake→
NEW DATA PATH
CS specialistcreates a dispute directly
The spreadsheet stops being the workflow.
New disputes are entered once, checked immediately, and written into the same record shape ResolveIQ already uses. No spreadsheet in the middle.
Required fieldsControlled status valuesValidated formatsConsistent structure
RECORD PREVIEW
{
"externalReference": "DSP-3008",
"merchantName": "Northstar Auto",
"receivedAt": "2026-06-18",
"amount": 2481.17,
"workflowStatus": "OPEN"
}Same record shape ResolveIQ uses. No spreadsheet in between.
✋
RELEASE GATEAbsolutely not, Brenda.
Looking valid is not the same as being correct.
One more thing
Shipping the tool was not enough.
We also created onboarding and training materials so CS could get out of the shared spreadsheets and into the new workflow quickly.