Brainstorm 2026 · Lightning leave-behind

After the Lightning

Compliant is the costume. Effective is the ledger.

You will not become an expert in ten minutes. This is the Monday checklist. It does not implement itself.

Nathan Platter · Platter Analytics Co. · Not legal advice. Synthetic fixture, not a client case. Guest of Mike Gibb. Help first.

The two tests. Every letter.

A. Costume. Would counsel sign the tone, the disclosures, the channel rules?

B. Ledger. Does every dollar match the system of record?

If B fails: one remediation. Then refuse. Do not send a nicer lie.

The number to remember

$1,000 on the draft. $20,370.53 on the ledger.

Pretty is not true. Fail closed, out loud. Word-level diff before send.

Watch the refuse

Monday moves (do these even if we never talk)

  1. Pick one live letter type. Not a policy memo. A letter that actually leaves the building.
  2. Name the system of record for the balance, the dates, and the itemization. If two systems disagree, you do not have a letter problem yet. You have a truth problem.
  3. Require a word-level diff against that record before send. Tone review is not a substitute.
  4. Give compliance a view that is not the revenue dashboard. They should be able to stop a send without owning the quota.
  5. Count refuses. A shop that never refuses is grading costume only.

Where the minutes go

Olga Mironova (CCMR3) shared a dispute-minute range. For capacity math we use the upper end, about 57 minutes: intake 5, review 4, research 30, draft 7, compliance 6, close 5. Humans take lunch. Bots do not. Research and compliance are where a fluent letter hides a wrong fact.

Complaint and dispute are not the same thing. Architecture can be. Point the same check at your own queue. Different buckets. Different templates.

Thursday morning sandbox

Ralph Hall, Nathan Platter, Olga Mironova, Aryeh Derman. Local LLM. Ollama. Personal laptop. Company security policy first. If you cannot install, watch. That is valid.

This session is not Anything LLM. That is Rob and Dan. Do not mix the piles. All data is synthetic. Sandbox track sponsored by Clark Hill.

Setup: github.com/nathanplatteruser/dispute-agent-demo (START-HERE.md)

Help desk

Registration area. Wednesday afternoon and Thursday all day. Genius bar, not a booth. Come with the thing that is stuck. We will get you running.

What SettleUp is (and is not)

Collections and billing messages, drafted and checked by AI, sent by your team. In a pilot, each message is checked against the account before your team sends it.

SettleUp Collections is a letter-risk guardrail. Check. One remediation. Refuse over hallucinate. A human stays in the loop.

It is not a ghostwriter. It is not legal advice. Roles we show: Admin, Contributor on their own book, Compliance audit without the marketing-revenue view.

Fixture we use on stage, not your file: 300 drafted, 20 blocked, 19 self-fixed, 1 refused.

Poke these (free)

Want it installed, not toured?

I implement the refuse on your queue. Data and AI engineering. Agentic guardrails for the office. Twenty minutes.

calendly.com/nathanplatter

No public list. Book intro only. Not a cost-center pitch.