Field Notes - Jan 09, '26

Executive Signals

State before action: automation follows reliable status reads, not optimism
Emails are the API: historical corpora deliver safer tests than brittle sandboxes
Batch is the moat: session-aware adapters shrink logins and scrape risk
Confirm or it didn’t happen: capture references now, sweep later when blind
CRM over CSVs: programmatic CC truth prevents drift and compliance misses

Resubmission automation is downstream of reliable status intake. Establish a single status model and instrument SLOs before any auto-resubmit. Keep manual resubmits until adapters have broad coverage and status accuracy sustains >99% on a seven-day rolling basis.

Publish SLO: 95% machine-read status within 24 hours; alert on misses
Stage Phase 2 for status intake, then layer adapters per OEM
Hold auto-resubmit behind a >99% accuracy gate for seven days

Customer Success

Preflight Guards for New-Dealer Onboarding

Most first-run failures are missing CRM contacts or absent compliance recipients in OEM portals. Add preflight checks that fail fast with clear next steps and auto-retry on state change.

Before submit, assert CRM contact and portal compliance recipient; set Needs-Onboarding if absent
Auto-generate OEM add-request email when recipient is missing
Escalate after two failed retries with explicit reason codes

CRM Is The Source Of Truth For Contacts

Compliance CC lists drift in spreadsheets. Move them into CRM with explicit roles and programmatic pulls, then reconcile weekly to stamp out manual edits.

Add a Compliance Contact role with required fields; enforce on account creation
Reconcile CRM vs last 30 days of CC traffic weekly, alert on mismatches
Target zero manual CC edits per week after cutover

Product

Post-Submit Confirmation Gate

Capture an in-session confirmation when portals echo reference numbers or pending entries. Where they do not, schedule delayed sweeps to avoid wasted logins while ensuring every submission has a confirmation artifact within 24 hours.

Require a reference ID or equivalent artifact on every submit
Enqueue a T+24h check when blind; escalate at T+48h if still absent
Track >98% of submissions with confirmation within 24 hours

Pipeline Hygiene: Close Zombies, Sort Newest-First

Ops surfaced stale open requests and default-oldest sorting that hide real work. Clean the queue, enforce one-open-per-dealer, and default to newest-first with tests.

One-time cleanse: close or merge requests predating the current month
Default newest-first across views; unit-test sort behavior
Nightly auto-close idle >30 days with a reason code

Engineering

Build The Status Intake Pipeline

Stand up status pollers and parsers across email and portal sources, unifying to a single model: New, Submitted, Approved, Denied, Needs-Onboarding, Error. Instrument SLOs and alerting so misses are visible.

Reach 95% machine-read status within 24 hours; alert on gaps
Keep manual resubmits until adapter coverage is proven
Defer auto-resubmit until status accuracy sustains >99% on seven days

Batched Portal Access With Adapters

OEM portals fall into repeatable patterns: dealer login, brand account with pending table, or per-reference lookup. Build adapters per pattern and batch reads by brand and session to minimize logins and scrape risk.

Map OEMs to 3–4 adapter types with documented happy and denial paths
Batch reads by session; target 60–70% reduction in logins per record
If items hide until state changes, skip same-session checks and schedule sweeps

Email-First Test Harness

Status emails are abundant and structured enough to parse. Use historical corpora to build fixtures and fuzz tests, and replay synthetic load to validate throughput and idempotency before portal environments exist.

Ingest a year of emails; build fixtures for Approved, Denied, Partial, Missing-Ref
Hit >99% field extraction on known corpus; add spacing and casing fuzz tests
Replay 1k mixed emails per hour to validate throughput and idempotency