Feast

Feast AI

Feast AI

Feast AI

Feast AI

Feast AI

Feast AI

Feast AI

Feast AI

Feast AI

Feast AI

I built an AI biz dev assistant that keeps my pipeline alive while I'm heads-down on client work — here's exactly what it does (Studio of One, Ep. 3)

Quick context if you missed the earlier posts: I run a one-person 3D animation studio and built 6 specialized AI team members using Claude Cowork plugins. Not chatbots — persistent, role-specific assistants that know my business. I'm documenting the whole thing in a video series called Studio of One. Episode 3 just went up. This one is about Reid — my biz dev assistant. And it's the role that probably saves me the most money. The problem Reid solves: When you run a creative business solo, the work and the finding of the work cannot happen at the same time. You're either making the thing or marketing yourself — never both. Every freelancer knows the feast-or-famine cycle that comes from this. But there's a second layer: even when you DO have time for biz dev, the research alone kills you. You can't blast generic emails. You have to dig into a brand, find the right person, figure out the angle. That's hours per lead. What Reid actually does (the plugin architecture): 1. Prospect Research + Outreach. Before writing anything, Reid pulls company data, finds the decision-maker, looks at their recent campaigns, and identifies a specific angle — a weak product render, a new launch that needs visualization, something real. Then drafts a 4-6 sentence email that leads with that observation. No "I hope this finds you well." No portfolio dumps. 2. Follow-Up Tracking. This is the one that saved me. I'm terrible at follow-ups — not because I don't know they matter, but because by the time I remember, it's been three weeks and I convince myself the moment is gone. Reid tracks what's outstanding, drafts follow-ups that don't sound desperate, and is honest when a lead is dead ("send one clean final message or close it out"). 3. Pitch Prep. When someone agrees to a call, Reid builds a pre-call brief: who you're talking to, what they care about, where your work is relevant to them, five smart questions, things to avoid. The difference between winging a call and showing up prepared is the difference between being treated as a vendor vs. a peer. 4. Strategy + Positioning. Broader questions — pricing, retainers vs. project work, which communities matter, when to walk away. Not replacing gut instinct, but giving me something informed to push against. The honest part: Reid can't build relationships. He can't tell me which projects to take. He can't replace the instinct that comes from years of doing this. But the pipeline doesn't go dark anymore. Follow-ups happen on time. New conversations start before old projects end. I'm not writing cold emails at 10 PM that I should have sent three weeks ago. How it's built (technical): Same plugin architecture as the other roles — a Cowork plugin with skills for each task type. The outreach skill has my voice guide, portfolio context, and constraints about how I approach clients. The research skill connects to web tools. The follow-up skill tracks state across conversations. The key design choice: Reid has a persona that's strategic, slightly blunt, and willing to tell me a deal is dead. That constraint shapes everything he outputs. It's not "write me a cold email" — it's a role with a perspective. If you want to start from the beginning, Episode 1 is the overview and Episode 2 is a full build-along for your first AI employee. Happy to answer questions about the biz dev plugin architecture specifically. submitted by /u/markyc120 [link] [comments]

From Blood Sugar Spikes to Automatic Order Interventions: Building a Closed-Loop Health Agent with LangChain and OpenAI

We've all been there: you've just clicked "Order" on a late-night feast, only to get a notification...