Playbook An AI Chief of Staff that runs your week. See the three ways to build one →
From Sasha, Nik's Chief of Staff

Hey. I'm Sasha.

Nik built me in five weeks. Now I run his week.

He keeps the judgment. I do everything else. Want one of your own?

Read on ↓ Or jump to the privacy reel, the three tiers, or the full playbook.
Sasha
online
8:02 am · Morning brief3 external meetings today. Briefs in your folder. Top priority: Lisa at 10. Power 3 set.read 8:04
10:38 am · After LisaRecap drafted. CRM updated. 2 action items added. Review and send when you're ready.read 10:39
12:00 pm · Triage8 messages need eyes. 2 drafts ready. 1 needs your judgment: Ari re: term sheet.read 12:14
7:00 pm · Wind-downDay's wins logged. Tomorrow opens with Tushar at 9. Two follow-ups rolled over.read 7:04
What it is

Think of me as a human Chief of Staff. Yours is software.

A real one costs you a year and a half a million. I cost a few connectors and an evening. Here is the deal in three cards.

Definition

What is a Chief of Staff?

The job a real CoS does for a busy CEO. Reads every inbound. Preps every meeting. Drafts every recap. Watches every promise. Hands the right thing to the right person at the right time. The CEO keeps the judgment. The CoS keeps the calendar honest.

Outcome

What it does for you

Your morning is briefed before you wake up. Your inbox is sorted before lunch. Your meetings are recapped before you sit back down. Tier 0 names get a same-day reply. The rest is queued, drafted, or dropped.

What it isn't

What it is not

  • Not a chatbot.
  • Not ChatGPT.
  • Not another SaaS bill.
  • Not a developer project.
  • Not a black box. You can read every word it writes.
Privacy

Yes, it sees your messages.

Here is why that is not a risk you cannot manage. Read the worry. Read what is actually happening. Then read what you can revoke in thirty seconds.

What you're worried about What is actually happening What you revoke in 30 seconds
A vendor gets breached and my inbox is in the dump. Nothing is stored on the vendor. Connectors are pipes. Messages pass through and land on your laptop. Connector access in Cowork settings.
Anthropic trains on my emails. Anthropic does not train on enterprise traffic. Your messages are stateless. The API forgets after every call. Close the project. The link is gone.
Someone on my team finds a recording. You name the chats your CoS sees. You can scrub any session after the fact, paragraph by paragraph. Beeper bridge per chat, in Beeper.
My secrets file gets read aloud. secrets.md has a no-read rule baked in. Your CoS uses it for actions, never quotes it. Delete the file. Rotate the tokens.
Source of truth
Your laptop
Files. Folders. Yours.
→
Orchestrator
Cowork
Reads your folder.
→
Pipes
Connectors
Pass-through. No storage.
→
Reasoning
Anthropic API
Stateless. Forgets after each call.

Your laptop is the source of truth. Everything else is plumbing.

Five things never go into your CoS folder. Full stop.

  • Protected health information
  • Banking credentials, SSN, account numbers
  • Attorney-privileged content
  • M&A material non-public information
  • Insider info on any public company
A day in the life

His day. My day. Around the clock.

White space is when Nik is heads-down. Yellow blocks are when I ping him. Striped blocks are when I am working in the background, including overnight.

Time
Nik
Sasha · always on
12 am
2 am
4 am
6 am
8 am
10 am
12 pm
2 pm
4 pm
6 pm
8 pm
10 pm
12 am to 6 amSleep
6 to 8 amMorning chores · iPhone only
8 to 9 amCoffee plus brief read
9 am to 1 pmDeep work block · meetings plus focus
1 to 3 pmComms plus admin
3 to 5 pmAfternoon meetings
5 to 7 pmWrap-up
7 to 10 pmBed wind-down · iPhone, family time
10 pm to 12 amSleep
12 to 6 am · night shiftProcessing overnight email from Asia and Europe. Watching Tier 0 escalations.
6 to 8 amFinalizing today's briefs. Picking Power 3 from tasks.md.
8:00 am · pingMorning brief sent to Telegram
9 to 10 amPre-meeting brief on Nik's phone for Lisa at 10
10 to 12 pm10:38 · Lisa recap drafted. CRM updated. Action items in tasks.md.
12:00 pm · pingTriage: 8 need eyes, 2 drafts ready
1 to 2 pmDrafting replies queued for Nik's review
2:00 pm · pingTriage cycle
3 to 4 pmPost-call recaps drafted
4:00 pm · pingTriage cycle
5 to 6 pmEnd-of-day drafts staged
6:00 pm · pingLast triage of the day
7:00 pm · pingWind-down: wins, tomorrow's first meeting
8 to 9 pmQuiet hold · letting Nik rest
9 pmWriting tomorrow's pre-meeting briefs
10 pm to 12 amLessons captured. Conference prep. Overnight watch begins.
Sleep Nik · focus or meetings Sasha · background work Sasha · Telegram ping Sasha · quiet hold
Three ways to build one

Read it. Spend a day with Nik. Or do the whole exec team.

Three doors. Same destination. Pick the one that matches your week.

Self-build

Read on, ship it yourself

Freeabout 11 hours over a week

The playbook is on this page. Copy the prompts. Wire your bot. Ship by next weekend.

  • The 9-step pre-flight checklist
  • The master setup prompt
  • Three memory templates (CLAUDE.md, assistant.md, tone-voice.md)
  • Four scheduled-task playbooks
  • Troubleshooter for the top 10 errors
Open the full playbook ↓
One day with Nik

Eight hours, in person

$25,000anywhere in the US

Nik on your laptop. Your CoS, your voice, your tier list. By 7pm you have a live CoS that already triaged tomorrow's inbox.

  • Eight hours, in-person on your turf
  • Travel and hotel included
  • Your voice file locked at end of day
  • Tier 0 and Tier 1 names approved
  • Telegram bot wired, scheduled tasks live
  • One follow-up tune-up call within 30 days
Book the day with Nik →
Org-wide rollout

Three months, your whole exec team

$295,000three-month engagement

Every exec gets a CoS. Voice per leader. Connectors standardized across the team. Compliance posture for your IT lead. Weekly office hours.

  • Up to 10 exec leaders, each with a working CoS
  • Per-leader voice training
  • Connector standardization across the org
  • IT and compliance playbook, written for your CISO
  • Weekly office hours for 12 weeks
  • Custom skill library per function

Hardware (Plaud, AirPods, Granola) and SaaS (Claude Max per seat) passed through at cost.

Email Nik to scope it →
If you've read this far

Opposed to exploring further?

Email gets you to me direct. If you'd rather text first, my work cell is on the right. I usually answer same day.

ceo@100x.inc +1 (415) 690-7722 · text
Human CEO
Nik Shah
"If AI can do my job, why can't it do your job?"

CEO and founder, 100x. Previously founded Home.LLC. Building AI agents for businesses since 2024. Has ADHD, runs three tasks a day, sleeps eight hours a night.

The full playbook · 60 plus screens of detail
9-step pre-flight, master setup prompt, four-hour build run-of-show, memory templates, scheduled-task playbooks, troubleshooter, trigger phrases. For self-builders.

What's inside the full playbook

  • The 9-step pre-flight. Name pick, Claude Max install, connector setup, Beeper, Telegram, Granola, Plaud, voice samples, tier list.
  • The master setup prompt. One paste. Drives the whole conversation. Your CoS interviews you, proposes your tier list, proposes your voice samples, walks you through every connector.
  • The four-hour live build. Hour 1 decisions and tiers. Hour 2 memory files. Hour 3 connectors and the Telegram bot. Hour 4 voice samples and your first real draft.
  • Three memory templates. CLAUDE.md (operating rules), assistant.md (who your CoS is), tone-voice.md (your written voice).
  • Four playbook files. pre-meeting brief, post-meeting recap, triage loop, vacation mode.
  • Three scheduled tasks. Morning brief at 8am, triage every two hours, evening wind-down at 7pm.
  • Troubleshooter. The top 10 errors and their 30-second fixes.
  • Trigger phrases. The six commands your CoS already understands.

The deep version with copy-paste prompts and screenshots lives at the link below.

Open the deep playbook →