AI Engineer WF 2026
ScheduleSpeakers
Sign In
Sign In
Speakers/Dan Bjornn
Dan Bjornn

Dan Bjornn

Lease End

Dan Bjornn is a Senior Data Scientist at Lease End, where he builds AI systems behind the company's sales pipeline. He led the development of an SMS sales agent that generated over $12M in revenue last year, with work spanning fine-tuning, agent architecture, prompt engineering, and evaluations. Prior to Lease End, Dan worked at several early-stage startups. Most notably, he was an early employee at NeuroID, where he helped lay the technical foundations the company carried through to its acquisition by Experian. Dan holds a PhD in cognitive neuroscience and applies it directly to his work designing AI agents with human cognition as the reference model.

Sessions (1)

Your Fine-Tuned Model Is Tech Debt: A 50x ROI House of Cards
3:20 PM·Leadership 2 · Room 3020

We built an AI application on top of fine-tuned models that generated $12M in revenue at 50x ROI. It was fast, cheap, and impressively accurate. Then it started having problems. Small errors accumulated. The model misread intent and nuance, handling conversations wrong. But retraining was too costly to justify for each fix, so known bugs piled up until we hit critical mass. Each retraining cycle took a week end-to-end, most of it spent curating data and validating our classification pipeline. And fixes caused whack-a-mole regressions across intents that required multiple iterations per cycle. Over time, the model became increasingly rigid. Each retraining was harder than the last. Then our team started using Claude Code, and we realized context management was the real lever, not model specialization. We rebuilt on frontier models using well-crafted system prompts and progressive context management, feeding the agent only what it needs when it needs it. Adjustments that used to require a week-long retraining cycle now take a small context change. Fine-tuning should be a last resort, not a first instinct. The cases where it's the right call are far fewer than they used to be. Before you fine-tune, ask: can I solve this with better context instead?

AI Architects: Show my Workflowintermediatetalk