Pay for outcomes
Hourly billing rewards effort. AI should be paid for outcomes.
Read the full dispatchField Notes · live series
Notes from the front lines of enterprise AI — why production, not prototypes, is the real finish line. Each dispatch is archived here as it goes out on LinkedIn.
Hourly billing rewards effort. AI should be paid for outcomes.
Read the full dispatchThe most in-demand engineer of 2026 doesn't have the job title you'd guess.
Read the full dispatchHere's something you might not expect from someone at AWS: not every organization should bring in forward deployed engineers.
Read the full dispatchBefore AWS embedded engineers with customers, it ran the experiment on itself.
Read the full dispatchA 30-developer project, scoped at 12–18 months. Delivered in 76 days.
Read the full dispatchThe best measure of an AI engagement isn't what you ship. It's what happens after you leave.
Read the full dispatchThree years ago, AWS ran an experiment: what happens if you put applied scientists and strategists directly in the room with customers, instead of shipping them a deck?
Read the full dispatchForward Deployed Engineering is not consulting with a cooler name. If it doesn't leave the customer more capable than it found them, it isn't FDE.
Read the full dispatchAn MIT study found ~95% of enterprise AI pilots never produce measurable P&L impact. The models were rarely the problem. The last mile was.
Read the full dispatch