How a Solo 3D Animator Built a Persistent AI Biz Dev Assistant with Claude Cowork Plugins

A solo 3D animation studio operator built an AI sales development representative (named Reid) using Claude Cowork plugins. Unlike generic chatbots, Reid is a persistent, role-specific assistant with knowledge of the business. The architecture consists of four core skills:
Prospect Research + Outreach
Before writing anything, Reid pulls company data, finds the decision-maker, reviews recent campaigns, and identifies a specific angle — e.g., a weak product render or a new launch needing visualization. Then drafts a 4-6 sentence email leading with that observation. No 'I hope this finds you well' or portfolio dumps.
Follow-Up Tracking
Tracks outstanding follow-ups and drafts messages that don't sound desperate. When a lead is dead, Reid advises: 'send one clean final message or close it out.' This prevents the common solo freelancer trap of forgetting follow-ups for weeks.
Pitch Prep
When a prospect agrees to a call, Reid builds a pre-call brief: who they are, what they care about, where your work is relevant, five smart questions, and topics to avoid. The difference between winging a call and preparing is the difference between being treated as a vendor vs. a peer.
Strategy + Positioning
Reid addresses broader questions — pricing, retainers vs. project work, which communities matter, when to walk away. It doesn't replace gut instinct but provides informed input to push against.
Technical Implementation
Same plugin architecture as the other AI team members: a Cowork plugin with skills defined per task type. The outreach skill includes a voice guide, portfolio context, and constraints about client approach. The research skill connects to web tools. The follow-up skill tracks state across conversations.
The key design choice: Reid has a persona that is strategic, slightly blunt, and willing to declare a deal dead. That constraint shapes everything it outputs — it's not just 'write me a cold email,' but a role with a perspective.
Limitations acknowledged: Reid cannot build relationships, tell which projects to take, or replace years of instinct. But the pipeline no longer goes dark, follow-ups happen on time, and new conversations start before old projects end. The creator documents the full process in a video series called Studio of One — Episode 3 covers Reid in detail, Episodes 1-2 cover the overall architecture and build-along.
📖 Read the full source: r/ClaudeAI
👀 See Also

Claude Managed Agents Released: Multi-Agent Orchestration and 70 Days of Practical Lessons
Anthropic launched Managed Agents for multi-agent orchestration and enhanced toolchains. A developer shares 70 days of experience using role-split agents (Opus decision layer, OpenCode engineer, research agents) and the critical shift from 'execute this' briefs to 'you can question my premise' briefs.

Practical OpenClaw Use Cases from the LocalLLaMA Community
A Reddit post details specific ways developers are using OpenClaw for tasks like automated cold outreach, SEO content updates, social media captioning, server monitoring, and receipt processing.

Non-Developer Builds Three Production Apps with Claude AI Assistance
A user with no coding experience created three functional web applications using Claude AI, including a fuel price finder, MTG proxy printer, and budgeting tool, all deployed via GitHub, Cloudflare Workers, Cloudflare D1, and Vercel.

Built a Daily YouTube → LinkedIn Pipeline with OpenClaw: Architecture, Gotchas, and Lessons Learned
A developer shares the architecture of an OpenClaw skill that scrapes 30 YouTube channels daily, analyzes transcripts via LLM, and writes to Google Sheets. Details key gotchas like Apify async vs sync, Codex idle-turn watchdog, and ARG_MAX limits.