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

Developer Uses Claude Code to Build SetForge Web App for Band Management
A developer with no professional coding experience used Claude Code to build SetForge, a React app deployed to Vercel that helps bands manage song libraries and setlists. The app includes features like Jam Set for finding overlapping songs, Excel/CSV import, flow scoring, auto-arrange modes, and real-time collaboration.

Running a 6-agent behavioral coaching pipeline on self-hosted Qwen3 235B with vLLM
A developer built a 6-agent cognitive pipeline for behavioral coaching running entirely on self-hosted Qwen3 via vLLM, using Qwen3 30B on 2x RTX 4090s for development and Qwen3 235B on RunPod A40 pods for production.

Building a Video Generation Pipeline with OpenClaw, ClawVid, and Composio
A developer built a weekend project using OpenClaw as the runtime with Claude as the LLM, integrating Composio for tool authentication and ClawVid with Remotion for video generation. The pipeline creates MP4 videos with voiceover, visuals, music, and subtitles from text prompts.

Reddit user shares Claude Code setup for portfolio projects
A developer describes their transition from a manual Claude.ai workflow to a structured Claude Code approach using file-based memory and CLAUDE.md files for planning and documentation.