I run a chunk of my commercial follow-up through agents now, and the wall I keep hitting isn't the writing — it's that the agent doesn't know where the relationship actually stands. Who owes whom a reply, whether we're warm or stalled, what the last real signal was. So I either hold all of that in my head (and I become the bottleneck), or I dump the whole thread history into context and the message comes back generic and expensive. For those of you running outreach or follow-up through agents: how do you represent relationship state as something structured the agent reads and acts on — a status field, a per-contact context file, a "next best touch" the system proposes? And just as important, how do you keep the output from feeling automated on the other end? I'm after the structural fix, not a better prompt. What actually lives in your setup, and what did you try that quietly failed?

I run a fair amount of educational / authority content through a folder-based setup — ideas, scripts, articles, newsletters. The thing I keep fighting isn't quality, it's voice. The drafts come back clean, on-topic, technically fine... and generic. Correct, but it reads like the model wrote it, not like me. What I haven't cracked is the structural fix. A voice/style reference the agent loads first? An examples file of my own writing it has to match against? A heavy human pass on the last mile? And whatever you use — how do you stop that voice reference from quietly drifting back to generic as it grows? Curious what's actually held for the people here shipping real volume. Half-measures keep slipping for me.

The challenge: build a 30-second explainer on any concept. This is where you post it. Where are you at?