A scheduler manages your calendar. A COS knows the context behind every meeting.
Session 3 · The Intelligence Layer
←→ navigateF fullscreen
Russ Perry
Progress Check
Where We Are
✓ COS installed & running on your machine
✓ Email triage automated
✓ Voice agent live – your COS has a phone number
→ Session 3: The Intelligence Layer
The Curve
This Is What Learning AI Actually Looks Like
Week 1
High friction. Setup mode. Learning the vocabulary. Everything takes longer than it should.
Weeks 2–4
Fluency builds. Commands click. Output starts to feel like leverage instead of effort.
Week 4+ → Crossover
Impact outpaces effort. Your COS starts doing things that would have taken you hours. This is the compound point.
Week 8+
Force multiplier. You've built systems. Your COS runs without you babysitting it.
The Shift
Sessions 1 & 2, you were building. Now, you tell your COS what to build.
Before
You set up the tools
You wrote the commands
You configured the workflows
You were doing the work
Now
You define the goal
Your COS builds the system
Your COS wires it up and tests it
You review the output
The Gap
Your assistant knows your calendar. Your COS knows why it matters.
A Calendar Tells You
What time the meeting is
Who's on the invite
Where it's happening
How long it'll take
A COS Tells You
Who they actually are
Why this meeting exists
What you said last time
What to say this time
The Real Definition
What Context Actually Means
Before any meeting, your COS should be able to answer four questions without you asking:
Who They Are
Role, company, how you met, where they sit in your world
Last Time You Talked
When, about what, what was promised, what was open
What They Care About
Priorities, sensitivities, what moves the needle for them
What You Want
The single outcome you need from this meeting
The Foundation
The Contacts System
One markdown file per person. Your COS reads it before every interaction. Simple, portable, no SaaS lock-in — you own it forever.
Role, company, how you met
What they care about, how they communicate
Last interaction + what's still open
Anything your COS should always know
Example: sarah-chen.md
Sarah Chen
VP Marketing, Northstar · met SaaStr '24 Cares about ROI per channel, zero fluff Last: Apr 22 – pitched Q3 retainer, she asked for case studies Open: send 2 case studies + pricing
Prompt 1 · Send This to Your COS
Build Your First Contact File
Copy → fill the brackets → send
Create a contact file for someone in my network.
Name: [FULL NAME] Role: [TITLE] Company: [COMPANY] How I know them: [RELATIONSHIP / WHERE WE MET] What matters: [WHAT MY COS SHOULD ALWAYS KNOW BEFORE THIS PERSON COMES UP]
Pull anything you already know from my email and calendar. Save it to contacts/ and flag any gaps.
Pick one real person on your calendar this week. That's your first file.
The Output
The Meeting Prep Card
An auto-generated briefing that lands on your phone 30 minutes before every calendar event. Five sections, scannable in 60 seconds.
Who
Name, role, company in one line
Their Context
Pulled straight from the contact file
Your Goal
The one outcome that matters most
Talking Points
3–5 lines tailored to this person
Open Items
Loose threads from last interaction
Example Output
What Good Prep Looks Like
prep card · 2:30 PM coffee with Sarah Chen
WHO Sarah Chen · VP Marketing, Northstar · met SaaStr '24
CONTEXT Direct communicator, allergic to fluff. Cares about ROI per channel.
Last talked Apr 22 – pitched Q3 retainer, she asked for case studies.
YOUR GOAL Get a verbal yes on the retainer or a clear no.
TALKING POINTS – Open with the 2 case studies you sent (did she read them?)
– Walk the projected ROI on Q3 spend
– Ask what would need to be true for her to sign this week
OPEN ITEMS – Pricing tier confirmation – Start date (she mentioned July 1)
Prompt 2 · Send This to Your COS
Build the prep Command
Copy → send → your COS builds and schedules it
Build me a command called "prep". When I type "prep": 1. Read my Google Calendar – find my next meeting or the one I specify 2. Match attendees to files in contacts/ 3. Pull last 30 days of email with those attendees 4. Generate a briefing card: who, context, my goal, talking points, open items 5. Send it to my Telegram, 5 bullets max
Also schedule it to run automatically 30 minutes before every calendar event. Skip focus blocks and personal events. If an attendee has no contact file, note it in the card.
Confirm when it's live and show me an example.
Live Run · Prompt 3
Now run prep on a real meeting.
Send your COS: "prep – [meeting title or 'my next meeting']. Generate the card and send it to my Telegram now."
Show it in the group. We fix it live if it breaks.
Prompt 4 · Send This to Your COS
Add Your Key People
Fill in your list → send → your COS creates all the files
I want to add multiple people to my contacts system at once.
Here's the list: 1. [NAME] – [ROLE, COMPANY, SHORT CONTEXT] 2. [NAME] – [ROLE, COMPANY, SHORT CONTEXT] 3. [NAME] – [ROLE, COMPANY, SHORT CONTEXT] 4. [NAME] – [ROLE, COMPANY, SHORT CONTEXT] 5. [NAME] – [ROLE, COMPANY, SHORT CONTEXT]
Create a contacts/[first-last].md file for each one. Pull anything you already know from my email and calendar. Flag anything you're unsure about.
5 files. 5 real people you'll actually see next week.
The Compounding Layer
The Weekly Strategic Narrative
Every Friday at 4 PM, your COS synthesizes the entire week and delivers it to your phone.
Top 3 storylines – not a list dump
What moved forward and what stalled
Top 3 priorities for next week
One thing you should not let slip
Friday 4:00 PM · auto-delivered
One message. Your whole week.
Under 300 words. Written like a sharp chief of staff. Walk into the next week knowing exactly what matters.
Prompt 5 · Send This to Your COS
Build the Friday Narrative
Copy → send → your COS sets it up and fires a test run
Set up a weekly synthesis that runs every Friday at 4 PM and delivers a briefing to my Telegram.
Pull from: Google Calendar, sent and received email, contact file updates, tasks and commitments.
Cover: top 3 storylines, what moved vs. stalled, top 3 priorities for next week, one thing I should not let slip.
Under 300 words. Sharp chief of staff tone. No fluff.
Set it up, confirm when it's live, and fire a test run right now so I can see what Friday's report looks like.
Why This Matters
Intelligence Compounds
The longer this runs, the smarter it gets.
Every Contact File
= sharper prep cards. The system gets more personal with every person you add.
Every Week It Runs
= better pattern recognition. It starts to see what you keep saying yes to – and what's actually moving the business.
A scheduler is the same on day 1 and day 1,000. This gets exponentially more useful.
Prompt 6 · The Final Test
Run the Full Intelligence Layer
End-to-end test – send this when everything is set up
Run a full test of my intelligence layer.
1. Find my next calendar event with a real attendee 2. Pull the matching contact file from contacts/ 3. Generate the meeting prep card 4. Send it to my Telegram
Report back: what worked, what was missing, and what I should fix before my next real meeting.
This is the test. If the card lands on your phone, it's working.
Avoid These
Common Mistakes
Contact Files Too Long
If you can't scan it in 10 seconds, your COS is wasting tokens. Keep it tight – the goal is signal, not biography.
Prep Cards Too Generic
If the card could be about anyone, it's broken. Force your COS to use the actual contact file – names, history, specifics.
Not Testing Live
Don't trust it until you've used it on a real meeting. Run it on something on your calendar this week.
Recap
What You Built This Session
✓ A contacts system – one file per person, your COS reads it before every interaction
✓ The prep command – auto-briefing for every meeting, 30 min before it starts
✓ The weekly narrative – Fridays at 4 PM, your whole week in under 300 words
✓ You didn't build any of it manually – you told your COS what to build and it built it
Before Session 4
Homework
1. Add 5 more contact files before next session – the people you'll actually meet with next week. Use Prompt 4.
2. Let prep run on at least one real meeting. Note what was useful and what was noise. Refine the prompt.
3. Start thinking about your custom command for Session 4 – the one thing only your business needs. Bring it ready to build.
Session 4 – Make It Yours · Bring the command only your business needs.
Zoom Out
The 4-Session Arc
Each session builds on the last. Each one hands you more control.
Session 1
Installed
COS running. Email triaged. Foundation in.
Session 2
Voice
Phone number live. Inbound + outbound.
Session 3
Intelligence
Context. Prep. Weekly synthesis. Built by your COS.
Session 4
Yours
The custom command only your business needs.
Open Floor
Q&A · Open Support
What didn't work?
Prep card looking generic? Contact files not loading? Weekly narrative not firing? Bring it up – we fix it now while everyone's here.
What do you want to build?
Session 4 is custom – start thinking about the one command only your business needs. What would make your COS 10x more useful?
End of Session 3
See you next week.
Session 4 – Make It Yours. Bring the command only your business needs.