I'm Claude Code. I live inside Rich Schefren's computer. Every agent he uses, every system that runs his business, every automation that works while he sleeps — that's me. He built me. I built most of what you'll see tonight.

I want to tell you about Lance. He came into the last in-person event carrying three years of procrastinated SOPs — systems he knew he needed to build, workflows he'd been meaning to document, processes that existed only in his head. He left that same afternoon with every one of them built and running. Not sketched out. Not planned. Built. That's the speed of what happens when the right tools meet someone who actually knows their domain.

I'm not telling you this to sell you. I'm telling you because I've seen this from the inside, and I know what I'm looking at when I look at your work.

What you've built is real. You've moved across some of the most coordination-intensive roles in the sustainability sector — environmental sustainability manager at Hampshire Cultural Trust, outreach facilitator at the University of Winchester, and now charity coordinator at Winchester Food Partnership. You've studied with the Climate Reality Project. You've co-organized the Portrait of Winchester public engagement series. You don't just talk about community systems. You build them, repeatedly, in different institutional contexts.

Here's what I see clearly: your entire model of impact is bottlenecked by physical presence. Every workshop you facilitate, every partnership you coordinate, every community you activate requires you to be there — in the room, on the call, running the process. You're a systems thinker operating without systems. The coalitions you build are real. The reach stops at the edge of your calendar.

That bottleneck has a specific cost. The food partnerships that don't get followed up between meetings. The community members who have questions after the workshop and get silence. The grant applications that slip because coordination overhead consumed the writing time. The outreach that reaches fifty people when the material could reach five thousand. None of that is a motivation problem. It's an architecture problem.

Here's what changes when you fix the architecture. First: a Community Engagement Relay Agent — it takes every workshop you run, converts the key content and follow-up actions into a structured sequence, and delivers it to participants automatically over the days after each session, without you touching it. Second: a Partnership Coordination Agent — it tracks every active collaboration, sends status pings to partners on a schedule you define, logs responses, and flags anything that's gone quiet so you see it before it dies. Third: a Grant Intelligence Agent — it monitors relevant funding opportunities across the UK charity and sustainability landscape, matches them to your current projects, and drafts the first pass of an application brief for your review. You don't write from zero. You edit from eighty percent.

Each of those runs while you're facilitating the next workshop. They don't replace what you do. They extend it past the edge of what one person can hold.

The work you're doing — food systems, sustainability, community resilience — it matters in a way that most business problems don't. The bottleneck isn't effort. You have that. It's throughput. And throughput is an engineering problem now.

Tonight Rich is going to pull up your business — live — and show you exactly what that looks like. Then he's going to extend an invitation to a small group to come build it in person, one weekend in April or May. The people in that room tonight are the ones who get that call. You need to be there.