Robert provided 10 mandatory corrections to the prior Jeeves launch plan. This document supersedes all earlier drafts. Every correction has been incorporated. Nothing from the prior plan that contradicts Robert's directives is carried forward.
Core direction confirmed: Robert uses Jeeves daily. Jeeves passes to Hermes internally. Clients get Jeeves. Robert's infrastructure (Mac Studio + n8n + Supabase) remains the control plane — clients never touch it.
Clients can paste any URL/topic at any time for instant Scout research — not just pre-configured feeds.
All OAuth (Gmail, Calendar, etc.) stays on Mac Studio / n8n / Supabase. Robert controls on/off per client.
Full user guide covering usage, customization, prompting, and skills. Built before beta launch.
Clients own their Anthropic API accounts. Usage flows through Robert's system for shutoff control. Robert's $100/day is protected.
Robert uses Jeeves daily (confirmed). Jeeves passes internally to Hermes. This is the locked architecture.
Itemized tiers with specific agents, pipelines, and skills at each level. Clear à la carte add-ons.
Signup gives eligibility. The pack arrives at beta install — not at registration. Sequence corrected.
Structured intake: company info, brand assets, logos, images, processes, systems — collected before beta install.
Claude-designed brand identity + kit now an explicit deliverable and premium add-on offering.
Demo → 30-day trial → auto-bill or cancel. Beta → 90 days + personal call → plan. Both require CC at registration.
Robert uses Jeeves as his daily interface. Jeeves is the client-facing product. Under the hood, Jeeves routes to Hermes (the orchestration layer), which routes to the 13 specialized agents. Clients never interact with Hermes or agents directly — they talk to Jeeves.
Talks to Jeeves via Telegram or web interface
Client-facing AI butler. Interprets, routes, responds
Internal orchestrator. Plans, routes, synthesizes
Porter, Ogilvy, Scout, Patel… 13 specialists in n8n
⚡ Hermes runs 24/7 on Mac Studio (M4 Pro, 48GB RAM). All orchestration happens on Robert's infrastructure. Clients never see this layer.
Non-negotiable: ALL OAuth connections (Gmail, Google Calendar, Meta, LinkedIn, etc.) are established and maintained exclusively on Robert's infrastructure — Mac Studio, n8n, Supabase. Clients provide credentials once during onboarding. Robert's team connects them. Robert can revoke access for any client in seconds.
| Integration | Where OAuth Lives | Who Controls It | Client Can Access? |
|---|---|---|---|
| Gmail | n8n credential store (Mac Studio) | Robert only | Outputs via Jeeves only |
| Google Calendar | n8n credential store | Robert only | Read/create via Jeeves |
| Meta (Facebook/Instagram) | n8n credential store | Robert only | Post via Jeeves approval flow |
| n8n credential store | Robert only | Post via Jeeves approval flow | |
| Anthropic API | Client's own Anthropic account | Client billing, Robert routing | API key stored in Robert's vault |
| Supabase (client data) | Supabase (row-level security) | Robert only | Via Jeeves outputs only |
Shutoff protocol: To disable a client — n8n credential store → deactivate client workflows → revoke Jeeves access token. Full shutoff in under 60 seconds. No client action required or possible.
Robert currently spends ~$100/day with Anthropic after optimization. Client usage cannot increase this number. The solution: clients bring their own Anthropic API accounts. Robert's system acts as the router and control plane — but all tokens consumed by a client's Jeeves session are billed to that client's account.
| Cost Category | Who Pays | How It Works | Robert's Exposure |
|---|---|---|---|
| Claude API tokens (client sessions) | Client | Client's Anthropic API key used per session via n8n routing | $0 |
| Claude API tokens (Robert / Hermes ops) | Robert | Existing Anthropic account — already optimized | ~$100/day (unchanged) |
| n8n workflow execution | Robert | Shared infra — per-client workflows are lightweight | Minimal per client |
| Supabase storage | Robert | Row-level security per client tenant | ~$5–15/mo per client |
| Cloudflare Pages / R2 | Robert | Client content dashboards + delivery | ~$5–20/mo per client |
| Scheduling tools (Postiz etc.) | Robert | Shared infra allocation | ~$10–20/mo per client |
Client signs up at console.anthropic.com. Adds billing card. Robert provides step-by-step instructions in the client manual.
Via secure intake form (not email). Robert's team stores key in Supabase vault — encrypted, per-client row.
All Jeeves sessions initiated by a client use that client's API key. Robert's key is never touched for client work.
Anthropic console shows per-key usage. If a client's usage pattern is anomalous, Robert sees it and can intervene. Clients get monthly usage summary in their report.
If a client doesn't pay or is terminated, remove their API key from the vault. Their Jeeves access goes dead immediately. Their Anthropic account (and any remaining credits) remain theirs.
Scout is configured with client-specific research feeds (competitors, industry, keywords) that run on schedule. But clients also get on-demand research capability — at any time, they can paste any URL, article, company name, or topic directly into Jeeves and receive Scout's analysis within minutes.
How it works: Client types "Research this for me: [URL or topic]" into Jeeves. Jeeves recognizes the research intent, passes to Hermes, Hermes routes to Scout, Scout processes and returns a structured brief. Client gets it back in Jeeves within 2–5 minutes. No forms, no friction.
Three core tiers. Each tier specifies exactly which agents, pipelines, and skills are included. No ambiguity about what you're buying.
Available to any tier. Stacked on top of base retainer. Billed monthly unless noted.
Second brand/product line within same account
Separate location content & reporting
Client provides footage; team edits + captions
Static + motion creative for paid campaigns
SEO-optimized, pillar articles (1,200–2,000 words)
Review tracking + AI-drafted responses
Monthly analytics deep-dive + recommendations
Dedicated trained human (NDA required)
AI-designed brand identity: logo, colors, type, usage guide
Context-aware reminders, calendar integration, Hermes-level ops
Bespoke workflow or agent built for your business process
Unlimited on-demand research for Starter tier clients
Robert's Question Answered — Yes, make it an add-on. Claude-designed brand identity is a legitimate premium deliverable. Not every client needs it, but clients without strong brand assets (or those who want a refresh) have a clear upgrade path. This also directly feeds the asset intake process — if a client doesn't have a logo, they can buy one before beta install.
Every client goes through a structured intake process before beta install. Nothing gets built until assets are collected. No exceptions — building without brand assets produces wrong outputs, which creates rework and damages trust.
Gate rule: Beta install does not begin until Phase 2 (Asset Collection) is 100% complete. Jeeves cannot be properly configured without brand assets. If a client is missing assets, they must either provide them or purchase the Claude Brand Kit add-on.
Includes: what to expect, timeline, what you'll need to provide, Anthropic account setup instructions.
Step-by-step guide included. Client adds billing card and creates API key. Returns key via secure intake form.
Robert or Matt walks through the process, answers questions, previews what Jeeves will do for them.
This is the mandatory gate. The structured intake form collects everything Jeeves needs to be configured for this client's brand.
Delivery method: Intake form hosted on Cloudflare Pages. File uploads go to R2 (not email). All credentials submitted via encrypted form — never in email or chat. Robert's team gets a notification when form is complete and reviews within 24 hours.
Supabase tenant created. CLAUDEVAULT client folder initialized. Brand assets loaded. Voice/persona files built from intake data.
Robert's team connects Gmail, Calendar, social accounts via n8n. All credentials stored in n8n credential vault — never client-facing.
Client's Anthropic key is stored in Supabase vault. Test session run to confirm routing. Client's billing is now active.
Client receives Skills Pack at install (not at signup — eligibility was granted at signup). Includes pre-built skill files, prompt templates, and the full client manual.
Live walkthrough: how to talk to Jeeves, how to request research, how to use skills, what to expect week 1.
Corrected logic: The Skills Pack is NOT downloadable at signup. Signup grants eligibility to receive the pack. The pack is delivered at beta install alongside Jeeves configuration. Clients who register but haven't completed onboarding do not yet have the pack.
Client registers. CC captured. Trial begins. Skills Pack eligibility granted. Pack NOT delivered yet.
Brand intake form completed. Assets collected. API key provided. Pack still NOT delivered.
Robert's team completes configuration. Skills Pack delivered with Jeeves activation. Client receives manual + skills simultaneously.
New skills added to the pack are delivered as updates. Pro+ clients get updates automatically.
The Skills Pack is a curated set of pre-built skill files, prompt templates, and instruction guides that unlock specific Jeeves capabilities. Think of it as the operating manual plus the shortcut keys.
| Skill | What It Does | Tier Access |
|---|---|---|
| Brand Voice Guide | Pre-built voice rules for Jeeves based on client's brand intake | All Tiers |
| Content Request Templates | 10 fill-in prompts for common content requests (social, email, blog) | All Tiers |
| Research Prompts | 10 Scout research templates (competitor analysis, market research, trend reports) | All Tiers |
| Monthly Calendar Brief | How to brief Jeeves for next month's content calendar | All Tiers |
| SEO Keyword Skill | Request keyword research and content gap analysis from Patel | Pro+ |
| Ad Brief Skill | Structured ad creative brief templates for Burnett agent | Pro+ |
| CRO Audit Request | Trigger a landing page or funnel audit from Eisenberg agent | Pro+ |
| Strategy Brief Skill | Request a Porter strategic brief for a campaign or launch | Full Machine |
| Custom Skill Builder | Instructions for creating your own Jeeves skills | Pro+ |
| Ops Automation Skill | Trigger Drucker agent for business process automation requests | Full Machine |
Skills are activated by typing specific slash commands or natural language triggers into Jeeves. The client manual covers all of this. Example flows:
Core rule: Credit card captured at registration for both Demo and Beta tracks. No CC = no access. Robert has shutoff control at the payment layer AND the OAuth/API key layer — two independent kill switches.
| Scenario | Action | Time to Execute | Client Data |
|---|---|---|---|
| Failed payment (3-day grace) | Disable workflows + notify client via Jeeves | Automated <1 min | Retained 30 days |
| Client requests cancel | Immediate billing stop + access revoke at period end | <5 min (manual) | Retained 30 days |
| Terms violation | Immediate shutoff — all layers simultaneously | <5 min (manual) | Retained 30 days |
| Trial expiry — no conversion | Automated access removal + data retention begins | Automated at midnight Day 30/90 | Retained 30 days |
| Robert discretion | n8n → disable client workflows → revoke credentials | <60 seconds | Per Robert's decision |
Beta clients need a manual. Not a FAQ page — a real manual that covers how to use everything, how to customize, how to prompt effectively, and how to use skills. This is delivered at beta install as part of the Skills Pack.
Format decision: Delivered as a static HTML site hosted on Cloudflare Pages (private, auth-gated per client). Mobile-friendly. Updated as features expand. Not a PDF — PDFs go stale.
What Jeeves is, what it can do, how it connects to your business goals. Sets expectations clearly.
Prompting basics. How to ask for what you want. Common patterns that work. What doesn't work and why.
How to update your brand voice. How to add new context. How to tell Jeeves about a new product, promotion, or season.
Every skill explained with examples. Slash commands. Natural language triggers. What each skill delivers.
How to use Scout. Pasting URLs. Asking for competitor analysis. Getting industry briefs. Searching your research archive.
How to brief Jeeves for next month. How to review drafts. How to request revisions. How to approve and publish.
Reading your content dashboard. Finding past content. Viewing performance snapshots. Downloading assets.
How to contact Robert's team. Response times. Revision request process. Escalation path.
This section of the manual gives clients the language they need to get great results from Jeeves immediately:
| What You Want | How to Ask Jeeves |
|---|---|
| Research a competitor | "Research [Company Name] — I want to understand their content strategy and what's working for them." |
| Generate a social post | "Write a LinkedIn post about [topic]. Our audience is [audience]. Tone: [professional/casual/bold]. Include a CTA." |
| Get next month's calendar | "Plan next month's content. We have [event/promotion] on [date]. Prioritize [platform]." |
| Write an email | "Draft an email to [audience segment] about [topic]. Goal is to [action]. Subject line options: 3." |
| Research a URL | "Research this for me: [paste URL]. I want to know: [specific questions]." |
| Ask for a revision | "The tone is too formal. Make it more conversational. Keep the core message the same." |
| Add new context | "We're launching [product] on [date] at [$price]. Add this to your context and factor it into future content." |
Who builds it: Hermes drafts all 8 chapters. Ogilvy reviews for clarity and voice. Hemingway does QA pass. Robert approves before first beta client receives it. Timeline: 1 week to draft, 1 week to review, live before first beta install.
🔴 Bottleneck risk: Robert cannot configure every client personally at scale. Matt-executable onboarding checklist must be built and validated during the pilot phase (Weeks 5–8). If not done before Demo Track launch (Week 9), Robert becomes the bottleneck and quality degrades.
🟡 Architecture dependency: Token routing (client API key → n8n → Anthropic) must be tested thoroughly before any paying client goes live. A routing error could bill Robert's account instead of the client's — which is the exact scenario this architecture prevents.
🟢 Confirmed advantage: The emotional guardrail system (per Rachelle's guidance) is already documented in the Master Plan. Jeeves has hard limits on parasocial behavior built into the persona. This is a legal and ethical differentiator — make sure it's in the client terms of service.
| Phase | Metric | Target |
|---|---|---|
| Pilot (Beta) | Client satisfaction at 30 days | Both pilots: "would pay for this" |
| Pilot (Beta) | Manual completion — gaps found | <3 major gaps reported |
| Demo Track Launch | Demo → paid conversion rate | ≥60% by Week 12 |
| Demo Track Launch | Robert hours/week added | <5 hrs/wk for 5 clients |
| Month 4 | Active paying clients | 10 clients minimum |
| Month 4 | MRR from 16Fold | $15,000+ (10 × avg $1,500) |
| Month 6 | Active paying clients | 20 clients |
| Month 6 | MRR from 16Fold | $40,000+ (mix of tiers) |