Owners who want to see the actual output before buying, click here
https://nathanplatteruser.github.io/dispute-agent-demo/DEMO-OUTPUT.html
Opens an HTML page showing the finished demo output — what a synthetic dispute-resolution run actually produced. Skip the pitch deck and look at the real artifact your team would be handing a client.
Operations leads who want to read the code, click here
https://github.com/nathanplatteruser/dispute-agent-demo
Opens the GitHub source repository for the demo. Browse the Python code, prompts, and data files so your technical staff can vet the approach before any procurement conversation.
IT managers who need a 10-minute local setup, click here
https://github.com/nathanplatteruser/dispute-agent-demo/blob/demo/both-sides/00-START-HERE-Setup-Guide.docx
Downloads a Word setup guide (00-START-HERE) your IT lead can follow to run the demo on a local laptop in under 15 minutes — no cloud account, no shared credentials, no vendor access required.
Team leads running the session themselves, click here
https://github.com/nathanplatteruser/dispute-agent-demo/blob/demo/both-sides/handout/START-HERE.md
Opens the markdown handout entry point used to run the session from the front of the room. Use it as a script so a junior associate can facilitate the walkthrough without you standing over their shoulder.
Owners mapping the session to a training plan, click here
https://github.com/nathanplatteruser/dispute-agent-demo/blob/demo/both-sides/SESSION-RUN-OF-SHOW.md#the-four-levels
Opens the four-level run-of-show — the sequenced teaching agenda from intro to advanced. Drop it into a training calendar so staff know exactly which level they are expected to complete each week.
Counsel who want to read the exact prompts, click here
https://github.com/nathanplatteruser/dispute-agent-demo/blob/demo/both-sides/handout/prompts.txt
Opens the plain-text prompts.txt file fed to the model during the session. Read the literal instructions your system would send before you sign off on using it for live claim work.
Office managers who need a Monday-morning checklist, click here
https://github.com/nathanplatteruser/dispute-agent-demo/blob/demo/both-sides/handout/WHAT-TO-DO-MONDAY.md
Opens a markdown Monday follow-up checklist — the concrete next steps to take after the session. Print it, assign owners, and track which items land on which desk the week after piloting.
Compliance staff who need to verify the data is synthetic, click here
https://github.com/nathanplatteruser/dispute-agent-demo/blob/demo/both-sides/data/synth/DATA.md
Opens the DATA.md notes documenting how the synthetic dataset was generated. Hand this to compliance so they can confirm no real consumer PII is in the demo before any internal review.