Field Notes — AI & Automation Mini Cases

Five mini cases from production AI and automation work I have shipped. Each one is laid out the same way:

  • The case. What problem, who had it, why the obvious fix did not work.
  • The numbers. Real metrics — accuracy, latency, cost, time-saved.
  • What worked. The decisions that survived contact with production.
  • What failed. The attempts that didn’t — usually the more useful part.
  • The architecture. A diagram you could brief an engineer with.
  • Next-step checklist. How you’d start the same project on Monday.

If you subscribed via the exit-intent popup you get one of these every two weeks, in your inbox. Or just read them here.

#1 engineer

Field Note #1: 95% of SAP PII redaction does not need an LLM. The other 5% does.

Self-hosted German PII redactor for SAP prod-to-dev copies. Plugs in after TDMS/Delphix/Informatica to cover the free-text 5%. Entity F1 from .375 to .917.

Qwen2.5-1.5B + LoRA, Pydantic structured output, on-prem GPU
#2 revops

Field Note #2: HubSpot lead scoring told us who was engaged. Not who would pay.

Replacing weighted-sum lead scoring with reasoning-traced AI prioritization in HubSpot. Five custom properties, one nightly batch, reps that actually trust the score.

HubSpot workflows, Claude Sonnet, webhook + nightly batch
#3 engineer

Field Note #3: I let the AI close duplicate issues. Then I turned that off.

FixClaw GitHub issue triage with Claude tool use. Hybrid duplicate detection, three confidence bands, human-in-the-loop by default. What broke when I let it auto-close.

TypeScript backend, Claude tool use, GitHub webhooks, pgvector
#4 executive

Field Note #4: Replacing LeanIX failed. Sitting on top of it worked.

AI decision-support layer over LeanIX. Five-dimension scoring, reasoning trace as auditable property, floor rule that stops single-signal dominance. What broke when we tried to be the EAM.

LeanIX integration, Claude Sonnet, weighted-composite scoring, custom dashboard
#5 founder

Field Note #5: Cross-posting was easy. Closing the performance loop was not.

Teedian content ops engine — brief, draft, review, cross-post with canonical discipline, performance feedback. The stage everyone skips is the one that matters most.

Notion as source-of-truth, Claude as co-editor, Make.com cross-poster, Resend for performance digest

Mini cases in your inbox — one every two weeks

If you subscribe you get:

Double opt-in. Processed via Beehiiv. Privacy.