AI Marketing Team Blueprint
A complete multi-agent AI system for the in-house marketing function. Includes agent configurations, execution scripts, and a setup guide - the same architecture behind Ravenopus, configured for in-house operating teams. Choose your tool: Claude Code or Google Antigravity.
What you get
Choose your tier
Choose your tool
Built on Claude Code (Anthropic's agentic terminal, paid). Ships with a complete CLAUDE.md directive layer, 31 specialist subagents (.claude/agents/) that double as auto-activating skills, a 9-workflow ops library, 12 execution scripts for major ad platforms and analytics, and an env.template where you add your own ad-platform, analytics, and CRM keys when ready. Plus an optional .mcp.json for power-ups like Google Drive and image generation.
Blueprint
Download and deploy it yourself.
- All template files: directive layer, 31 subagents, 9 workflow protocols, 12 execution scripts
- Brand voice + positioning calibration with multi-brand support
- Operator-architect setup walkthrough
- Ready-to-connect MCP connector slots (bring your own API keys)
- LICENSE for internal company use, modification, and rebranding
Blueprint Pro
Guided setup with onboarding support.
- Everything in Blueprint
- 60-minute 1:1 onboarding call with the founder
- Private Telegram/WhatsApp group for 30 days
- Priority email support during setup
Blueprint Enterprise
We install and customize it for you.
Starts with a $497 scoping session - credited toward the full package if you proceed within 14 days.
- 60-minute scoping session ($497, credited toward full package if you proceed within 14 days)
- Founder-led installation in your environment
- 5 hours of customization for your specific workflows
- Agent tuning for your brand voice and industry
- Direct working-sessions access during installation period
- Priority email support for 90 days post-install
The structural problem in-house marketing has not solved
Marketing inside a company is the function most disfigured by coordination overhead. A VP of Marketing is hired to set positioning, allocate budget, decide what the brand stands for, and arbitrate between conflicting growth bets. In practice, the VP spends the week running standups, reviewing copy decks, chasing the agency for ad accounts the company should own, reconciling dashboards, and translating the same brief between four contractors who do not talk to each other. The decisions get made in the cracks. The execution is uneven because no one holds the whole picture. Headcount grows because every gap looks like a hiring problem, and every new hire adds another seam.
The Blueprint is the architecture that resolves this. One accountable operator holds the VP-level function - positioning, allocation, prioritization, brand judgment - and a structured ecosystem of specialist subagents holds the execution underneath. Strategy briefs are written once and routed cleanly. Campaigns are launched without translation loss. Analytics flow back to the same operator who set the brief. The coordination cost collapses because the seams between functions are no longer human handoffs; they are directive routing inside a system designed for it.
This is what an in-house marketing function looks like when it stops scaling by headcount and starts scaling by architecture.
Who this Blueprint is built for
This Blueprint is built for in-house operators and founders who own the marketing function for their own company. Heads of marketing carrying the VP-level mandate without a VP-level team underneath. Founders running marketing as one of several hats and refusing to scale headcount before the architecture is right. Operating leaders building marketing capability inside a company that does not have it yet, and does not want a six-person team to get it.
This Blueprint is not for you if you are running a marketing agency that sells services to clients. If your buyer is an external company paying you to handle their marketing, the architecture you need is the AI Marketing Agency Blueprint. Same underlying stack, different productization, written for the agency operating model.
Frequently Asked Questions
How is this different from the AI Marketing Agency Blueprint?
The underlying architecture is the same Ravenopus Claude stack. What differs is the productization layer wrapped around it. The Agency Blueprint is written for operators selling marketing as a service to external clients - the README, the setup walkthrough, and the onboarding documentation assume a client-delivery operating model with intake, scoping, project management, and reporting flowing outward. The Team Blueprint is written for operators holding the marketing function inside their own company - the same documentation assumes an internal stakeholder map, a single brand and positioning, an integrated analytics surface, and the in-house operator's accountability model. Same engine. Two structurally different buyer situations.
How do I know which Blueprint I should buy?
If your buyer is an external company that pays you to do their marketing, you are running an agency. Buy the AI Marketing Agency Blueprint. If your buyer is your own company - if you are the head of marketing, the founder, or the operating leader building the marketing function in-house - the Team Blueprint is the one written for your situation.
What is in the zip?
The complete Ravenopus Claude stack productized for in-house operating teams: the CLAUDE.md directive layer, the 31-subagent specialist ecosystem inside .claude/agents/, the 40-skill library inside .claude/skills/ (every specialist as an auto-activating skill, plus 9 workflow protocols), 12 execution scripts inside execution/ (Google / Meta / TikTok / LinkedIn Ads, CRM, analytics, deck and doc generators, competitor and Reddit scrapers), 4 reusable directives inside directives/, TEAM_DNA.md for brand voice and positioning, the brands/ folder for multi-brand support, env.template for credential management, a .mcp.json connector scaffold you populate with your own API keys, SETUP.md + START_HERE.md walkthroughs, and the LICENSE.
Do I need to be a software engineer to install this?
No. The Blueprint is designed for the operator-architect - someone fluent in SQL, comfortable with light Python, and at home in a terminal. Production engineering is not the working assumption. The judgment lives in the directives, the routing, and the boundaries; the execution is delegated to specialist subagents that know their domain.
Why does this cost the same as the Agency Blueprint?
Because the underlying architecture is the same architecture, and the value of the architecture does not change based on who the buyer's company is. The productization layer is rewritten for two different operating models. The engine, the subagent ecosystem, the skills library, and the directive layer are identical work, priced identically.
My team uses a variant that is not live yet. What should I do?
If your team runs on Claude Code, the variant is live today and ready to install. If your team runs on Antigravity, the Team Blueprint Antigravity variant ships later in the launch sequence; the "Soon" pill on the toggle marks it. Email Linara directly if you want to be notified the day it goes live, or if you want to discuss a custom installation under the Enterprise tier in the meantime.
What if I get stuck during setup?
Blueprint Pro is self-installation with a guided onboarding call and an asynchronous follow-up review. Enterprise is the $4,997 full installation package - it starts with a $497 paid scoping session where Linara maps the Blueprint to your stack and quotes the installation scope. Your $497 credits in full if you proceed within 14 days; otherwise it stays as the scoping fee.
Is this a subscription?
No. One-time purchase. You own the files. Lifetime access to the version you purchase; major revisions ship as upgrade paths; minor revisions ship as in-place improvements you can pull at your discretion.