16Fold Operations — Internal Reference

Jeeves Client
Onboarding Plan

The complete step-by-step process for taking a new client from signed agreement to a fully operational Jeeves instance. Every step. Every decision point. Every handoff.

5
Phases
~4 hrs
Total Setup Time
0
Client Installs
Day 1
First Jeeves Message
⚠️
Creative Content Pipeline — Beta Notice

The automated creative content pipeline (static graphics, Reels, carousels, video ads) is in active development and produces useful starting points — not finished deliverables. AI-generated visuals and video are improving rapidly, but the highest-quality creative results today come from one of two sources:

1. Human-guided production — you or your team uses the AI tools (Claude Design, Higgsfield, CapCut) with Jeeves providing the brief, direction, copy, and specs. The human touches the creative. The AI does the heavy lifting.
2. Real-life content first — you provide actual photos, video footage, and brand assets. Jeeves remixes, formats, and publishes. Real content beats generated content every time for engagement.
During Beta: All AI-generated visual creative goes through a mandatory human approval step before any content is published. Nothing automated goes live without eyes on it. This is a feature, not a limitation — it protects your brand and your clients' brands until quality thresholds are proven.
The Five Phases
Phase 1 Pre-Onboarding

Agreement signed. Account created. Client informed what's coming. 30 min.

Phase 2 Brand Intake

30-min intake call. All client intelligence collected. Files uploaded. 90 min total.

Phase 3 System Build

SOUL.md written. Profile created. Connections wired. Jeeves tested. 90 min.

Phase 4 Go-Live

Client gets their Telegram/Slack link. First message lands. 30 min.

Phase 5 Day 30 Check-In

Confirm value delivered. Reveal next tier. Turn beta client into paying advocate.

Phase 1

Pre-Onboarding

Before the intake call. Estimated time: 30 minutes.

Step-by-Step Checklist
1. Send and collect signed client agreement
Use the 16Fold e-sign system. Agreement covers: what's provided, IP ownership (16Fold owns the engine, client owns their outputs and data), non-payment suspension, 30-day data retention on cancellation, no reverse engineering. Do not provision any profile without a signed agreement.
2. Collect payment and create Stripe record
Credit card required at signup — no exceptions, including beta. Set billing cycle. Note tier purchased. Store Stripe customer ID in their Supabase row (jeeves_clients table).
3. Create their Google Drive client vault
Create folder in 16Fold Client Vault: 16Fold Client Vault / [ClientName] / with subfolders: Brand Assets, Uploads, Content Output, Intake Documents, Ad Creative. Share the folder with the client — editor access to their folder only.
4. Send the pre-call prep email
Email the client: "Before our intake call, please drop your logo files, any brand guidelines you have, and 3-5 pieces of content that sound most like your voice into this Google Drive folder." Link to their Brand Assets subfolder. This saves 20 min on the call.
5. Book the 30-minute intake call
Schedule within 48 hours of payment. Use Calendly or direct booking. The intake call is the product — don't rush it.
Phase 2

Brand Intake

The intake call + post-call file processing. Estimated time: 90 minutes total (30 min call, 60 min processing).

On the Intake Call — Questions to Ask

Ask these in conversation, not as a form. Take notes in their Intake Documents folder. These answers become Jeeves's permanent memory about this client's world.

🏢 Their Business
  • • What do you sell and who buys it?
  • • How do you make money — one-time, recurring, both?
  • • What's your #1 problem right now operationally?
  • • Who are your top 3 competitors? Why do clients choose you over them?
  • • What does a great week look like for you?
  • • What keeps you up at night about the business?
  • • What tools do you currently use? (CRM, email, project mgmt)
👥 Key People
  • • Who are your 5 most important clients? Why?
  • • Who on your team does Jeeves need to know about?
  • • Who are your key vendors or partners?
  • • Who should Jeeves NEVER contact on your behalf?
  • • Are there personal relationships (family, close friends) you want Jeeves aware of?
  • • Any relationships that are sensitive or complicated?
🎨 Brand & Voice
  • • How would you describe your brand voice in 3 words?
  • • What's the ONE thing you never want said about your brand?
  • • Formal or casual? Technical or plain English?
  • • What do your best clients say about you?
  • • Any brands you admire whose style you'd want to channel?
  • • What content have you made that you're most proud of?
⚙️ Their Routine
  • • What time do you start your day? Check your phone?
  • • What does your ideal morning briefing look like?
  • • Telegram or Slack? (We support both.)
  • • How do you want Jeeves to handle urgent things vs. routine?
  • • Are there hours or days Jeeves should stay quiet?
  • • What's the most annoying thing you deal with every week?
After the Call — File Processing Checklist
Confirm all files are in their Google Drive vault
Logo (SVG + PNG minimum), brand colors (hex codes), fonts if they have them, sample content. If they haven't uploaded — send a reminder. You cannot build their SOUL without this.
Populate their Supabase brand_context JSONB field
Everything from the intake call goes in here: competitors, key people, tone, off-limits topics, business model, pain points. This is what Jeeves pulls when building their briefings and content.
Collect their Anthropic API key
Clients provide their own key (BYOK). Walk them through creating one at console.anthropic.com if needed — takes 5 minutes. Store securely in their isolated profile .env — never in Supabase, never in shared systems.
Walk them through connection authorizations (screen share)
Based on their tier: Google Calendar OAuth (one click), Gmail OAuth (one click), Meta Business partner access request (2 min), Google Ads manager link (2 min). You handle everything. They just click Approve. Document which connections are live in Supabase features_enabled.
Save their Telegram user ID or Slack workspace details
For Telegram: they need to search @jeeves_[name]_bot and tap START before their ID is visible. For Slack: collect workspace ID and confirm bot has been added to their workspace.
Phase 3

System Build

Building and testing their Jeeves instance. Estimated time: 90 minutes. Robert never needs to be involved after initial setup.

Technical Build Steps
1
Create their Telegram bot
Open Telegram → search @BotFather → /newbot → name it "Jeeves for [First Name]" → save the token. Rename display name to match their chosen persona (Jeeves, Kate, Winston, Leora, or Ben).
2
Create their Hermes profile
Clone from the jeeves-template profile. Copy skills directory manually (template cloning does not include skills). Assign the next available gateway port. Hermes profiles sync automatically to Google Drive via the existing CLAUDEVAULT symlink.
hermes profile create jeeves-[name] --clone-from jeeves-template
cp -r ~/.hermes/profiles/jeeves-template/skills ~/.hermes/profiles/jeeves-[name]/
3
Write their SOUL.md
Generate from intake notes using the SOUL template at CLAUDEVAULT/clients/16fold/product-specs/jeeves-soul-template.md. Fill in: client name, business context, persona voice, key people, off-limits topics, communication style, feature flags. This is what Jeeves reads on every session. Treat it as the intelligence layer — the more specific, the better Jeeves performs.
4
Configure profile .env
Set TELEGRAM_BOT_TOKEN, TELEGRAM_HOME_CHANNEL (their user ID), and ANTHROPIC_API_KEY (their key — not Robert's). Profile .env does NOT inherit from root — every key must be explicitly written. OAuth tokens for Google/Meta go in the profile's secrets/ directory.
5
Set feature flags in Supabase
Update their jeeves_clients.features_enabled JSONB to match their tier. Base tier: chief of staff only (morning_briefing, follow_up_tracker, meeting_brief, scout). Content tiers add marketing agents. Jeeves checks this before routing any request — a client cannot access features outside their tier.
6
Create and start the LaunchAgent
Create the plist file with HERMES_HOME pointing to their profile directory. Without HERMES_HOME set, the gateway defaults to Robert's profile — a silent failure that looks like everything is working but isn't. Load and start the LaunchAgent.
7
Test before going live
Send 5 test messages: (1) a simple greeting — Jeeves should respond in the right persona voice; (2) "what's on my calendar today" — should pull their Google Calendar; (3) a brain dump — Jeeves should process and respond; (4) "morning briefing" — should deliver properly formatted; (5) a file (a logo or PDF) — should acknowledge and confirm receipt. All five pass = ready to go live.
8
Update Supabase registry
Set onboarding_complete=true, gateway_port=[port], profile_name, persona. This is the source of truth for every client's status. Never rely on memory for port assignments or profile names.
⚠️ If Client Purchased a Content Tier — Creative Pipeline Setup

For clients on Content Essentials, Content Growth, or Content Performance — the creative pipeline requires additional setup and a clear expectation conversation.

Set the expectation in writing: Jeeves produces briefs, copy, and strategy immediately. Visual creative (graphics, Reels, video ads) is AI-assisted but requires human approval before publishing — every single time during beta.
Upload their real brand assets (logo, product photos, videos) to Google Drive Ad Creative folder. Better input = dramatically better output. A client who provides zero real-life content will get generic AI output.
Wire the approval gate in Warhol's pipeline. No creative goes to scheduler without human sign-off. This is non-negotiable until automated quality is proven at the client's brand standards.
Phase 4

Go-Live

Handing the client their Jeeves. The buyer's remorse window is 24–48 hours. Get them a win immediately. Estimated time: 30 minutes.

Go-Live Checklist
Send the client their access link
For Telegram: t.me/[their_bot_username] — one link, that's it. For Slack: confirm the bot is in their workspace and send a direct message introducing Jeeves. They install nothing. This link IS their Jeeves.
Confirm they've sent the first message
The gateway cannot send proactive messages until the client initiates. Make sure they've tapped START (Telegram) or sent a message (Slack). Jeeves should respond within seconds.
Deliver the welcome message and quick-start guide
Send their personalized PDF guide: what Jeeves knows about their business, how to use each feature, example prompts that work well for their tier, how to send files, and a "try this first" list of 5 things to ask Jeeves in their first session.
Verify first morning briefing scheduled
Confirm cron job is active for their timezone and their preferred briefing time from the intake call. The morning briefing is the highest-impact daily touchpoint — it must land correctly on Day 1.
Robert gets a Telegram notification
The onboarding completion webhook fires a Telegram message to Robert: "[Client Name] is live. Profile: jeeves-[name]. Port: [port]. Tier: [tier]. First message received." This is how Robert knows the system worked without checking anything manually.
Eisenberg Rule — Day 1 Client View

On Day 1, show the client only their active features. No locked cards, no "upgrade to unlock," no greyed-out anything. A client who sees features they can't use on Day 1 feels like they bought the small version. A client who sees a complete, polished tool that does exactly what they signed up for feels like they got a great deal. The expansion conversation happens at the 30-day check-in — after value is proven, not before.

Phase 5

Day 30 Check-In

The expansion conversation. Confirm value. Unlock next tier. Turn a client into an advocate. 30 minutes.

The Check-In Script

"You've had Jeeves for 30 days now. Before I tell you what's next, I want to hear from you — what's actually working? What does Jeeves do every day that you'd miss if it stopped?"

Let them answer fully. Their words are your testimonial. Their answer tells you exactly which features to expand on.

Review their usage data from Supabase
How many sessions per week? Which features got used? Which didn't? If they're not using Scout, ask why — might be a setup issue, might be they don't know how to use it. Fix it before the check-in call.
Introduce the next tier personally
"You've been getting value from X and Y. I've been holding back one more capability because I wanted you to have a rhythm first — want to hear about it?" This is the reveal moment. The locked feature becomes a gift, not a paywall.
Ask for a referral or testimonial
If they're happy — and they should be by now — ask: "Is there one other business owner in your circle who runs into the same problems you had 30 days ago?" One referral per client is the growth engine for the first 20 clients.
Feature Flags by Tier — Quick Reference
Feature Base $500 Content $2,500 Growth $4,500 Performance $6,500
Morning Briefing ✓ ✓ ✓ ✓
Scout (Competitive Intel) ✓ ✓ ✓ ✓
Follow-Up Tracker ✓ ✓ ✓ ✓
Meeting Brief ✓ ✓ ✓ ✓
Content Pipeline (1 platform) — ✓ ✓ ✓
Email Campaigns (Schwartz) — ✓ ✓ ✓
Paid Ads (Burnett) — — ✓ ✓
SEO Engine (Patel) — — ✓ ✓
Creative Pipeline (Warhol) — — ✓ ✓
All 14 Agents + Private Monthly Session with Robert — — — ✓
IP & Legal — Quick Reference
✓ Client Owns
  • • All content created on their behalf
  • • Their business data and uploaded files
  • • Email drafts, social posts, reports, copy
  • • Their brand assets they provided
  • • Everything Jeeves produced for them
🔒 16Fold Owns
  • • The system that produced it (SOUL, agents, skills)
  • • V4 agent fleet and all workflows
  • • Jeeves platform configuration
  • • All 16Fold infrastructure and code
  • • Intelligence layer — never on client devices
⚠️ On Cancellation
  • • Gateway stops immediately
  • • Their data retained 30 days
  • • Data exported to them on request
  • • Full deletion within 14 business days
  • • Their brand assets returned to them
📋 Required Before Go-Live
  • • Signed client agreement (e-sign system)
  • • Credit card captured in Stripe
  • • Anthropic API key provided (BYOK)
  • • Data processing acknowledgment
  • • Supabase row created and confirmed
16FOLD™

Internal Operations Document · Not for client distribution · v1.0 May 2026