AI for Life

Blog

Should you keep the maintenance contract or hand over a runbook?

Featuring From the Weekly Meeting. Published July 30, 2026.

The build decision at handoff: keep maintenance as a revenue stream, or one-and-done with a runbook. Frank’s requirements for the interview-driven build: private enough that people talk honestly, full enough that the system learns what they really need, not just what they think they need.

Watch the clip

More from the Weekly Meeting

What changes when your onboarding interview actually listens?

  • Matthew Sutherland

Onboarding interviews with dynamic follow-up questions and Fable-level reasoning behind them. The script probes based on what the person actually said, not a fixed question list.

What does a working content engine look like from the inside?

  • Gina Wang

Screen-share walkthrough of Gina's content engine: her own transcripts as the idea source, rubric gates on quality, and one human approval point in Slack. She named the AI staff Birdie and Lanny. One of them rejects her ideas.

What happens when you ask an autonomous workflow when to publish?

  • Matthew Sutherland

Matthew asked when he could publish the LinkedIn post his Fable workflow drafted. The answer: it's already published. Audit, red-team, image, approval, publish, all in one autonomous run.

Community

Keep going with AI for Life

This clip comes from the AI for Life Weekly Meeting, live Wednesdays at 11 a.m. Eastern. Join the community to be in the room for the next one.

Join the AI for Life community (opens in a new tab, leaves this site) Request a custom lesson