You Can Learn AI Chief Of Staff With Claude Code In 29 Min | Founders, PMs, Skills — Transcript

Full transcript

1. 0:00Everyone's Sean. So, today I want to
2. 0:01show you how we can use Claude code as
3. 0:03your AI Chief of Staff. Previously, I
4. 0:05made a lot of videos about how you can
5. 0:06break down, you know, agent harnesses
6. 0:08and memory systems in a very technical
7. 0:09way. But, I realized that a lot of my
8. 0:11audience are also running their own
9. 0:12business, owning their own agency, or
10. 0:14they're a product leader who's leading a
11. 0:15technical team. So, I'd like to show you
12. 0:17exactly how a startup founder or an AI
13. 0:21developer would use Claude code to run
14. 0:23their day-to-day as if it's your Chief
15. 0:25of Staff. And, I'm not only going to
16. 0:26show you a system design chart where I'm
17. 0:28going to show you how you can set up a
18. 0:30company brain for your Claude and how
19. 0:32exactly it should be working using some
20. 0:33of the skills and some of the tools that
21. 0:36you should be connected to using the
22. 0:37connectors or MCPs. And, eventually, how
23. 0:39you will be able to trust the decisions
24. 0:41they made. But, also, I will walk
25. 0:43through five top use cases that I think
26. 0:46are going to be really helpful for your
27. 0:48day-to-day tasks. And, they include, you
28. 0:50know, how you can plan for your day, for
29. 0:52tomorrow especially, using some of the
30. 0:54connectors. How you can triage your
31. 0:56inbox if you're a client-heavy person.
32. 0:58And, how you can prepare for your
33. 1:00meetings for tomorrow using some of the
34. 1:02tools such as, you know, these Google
35. 1:03Suite, Waku Memories, and Meeting Notes.
36. 1:06To how you can align the rest of the
37. 1:08team with your agents by sharing some
38. 1:11context together and making decisions
39. 1:12together. And, last but not least,
40. 1:14closing the deals by, you know, creating
41. 1:16a quote to instant it to your CRM. So, I
42. 1:19think this should be something that's
43. 1:20going to be helpful for you if you are
44. 1:22just getting started using Claude code.
45. 1:24But, also, if you are someone who's
46. 1:26collaborating with the rest of your team
47. 1:28using agents together, this should be
48. 1:30very helpful for you, too. So, without
49. 1:32further ado, let's get started. Based on
50. 1:34these five items I'm going to show you
51. 1:36for the rest of the video, I prepared
52. 1:38five possible tasks that we need, right?
53. 1:41Maybe you want to set up a 7:00 a.m.
54. 1:43morning brief every day for your team.
55. 1:45And, maybe there's a client email that
56. 1:46just arrived. Or, maybe you want to
57. 1:48prepare some meeting notes or take some
58. 1:49voice notes. All the way to there's a
59. 1:51team checking you want to do with the
60. 1:53decisions that are made by agents or by
61. 1:55human. And, eventually, maybe you have
62. 1:57got a request for a quote from your
63. 1:59clients. Okay? And all of these things
64. 2:00will firstly hit Agent harnesses, which
65. 2:02Claude is our main character today. I
66. 2:04list the rest of them here just for
67. 2:06examples that you can use the rest of
68. 2:07them, too. This is the place where
69. 2:09you're going to talk to your AI and
70. 2:11where the AI is going to work. And since
71. 2:13you clicked into this video, I kind of
72. 2:14can assume that you already have been
73. 2:16using Claude. And just in case you don't
74. 2:18know what it is, you can try immediately
75. 2:19at claude.ai and then can ask any
76. 2:22questions you want. And I know a lot of
77. 2:23agency owners or business people who are
78. 2:25going to use Claude chat or Claude for
79. 2:27work very heavily. But today our main
80. 2:29character is Claude Code, which is a
81. 2:31different species. The reason why it's
82. 2:33different is that everything in your
83. 2:34claude.ai is going to be stored on
84. 2:36Anthropic's cloud. So you actually don't
85. 2:39own any of these things, okay? Claude
86. 2:40Code instead is something you will need
87. 2:42to download to your laptop as a desktop
88. 2:45app and you will be able to connect it
89. 2:46to all these tools and then all the
90. 2:48sessions and all the chat history and
91. 2:50all the skills are going to be local.
92. 2:52And this is what we're going to try to
93. 2:53show you today, okay? You can click on
94. 2:55download for Mac OS if you're on a Mac
95. 2:57OS or I'm sure there's a way to download
96. 2:59it on Windows, too. If you just click on
97. 3:01new, you can open a new chat into
98. 3:02something like this. And please bear
99. 3:04with me if you're already familiar with
100. 3:05Claude. I guarantee that I will dive
101. 3:07into more interesting use cases very
102. 3:10quickly. And this is just an intro for
103. 3:12the beginners. Now that we have started
104. 3:13talking to your local Claude Code, the
105. 3:15first thing you should think about,
106. 3:16always, is how can I set up a company
107. 3:18brain for the rest of the team, okay? I
108. 3:21would consider the brain to have three
109. 3:23main pillars. The first thing is what I
110. 3:25call a handbook, which is something that
111. 3:27you write as some kind of durable
112. 3:29long-term memories for your agent. And
113. 3:31they could be things like the offers and
114. 3:33prices you offer to your clients. They
115. 3:34could be the tone of how you should be
116. 3:36talking to you and the SOPs of your
117. 3:39company. And what is something true
118. 3:41about your business? I have stored
119. 3:42something like this in a Notion page
120. 3:45where you can you can see that I have a
121. 3:46handbook here and the handbook's
122. 3:48basically telling me uh what we're
123. 3:49offering at waku.one, which is a shared
124. 3:51memory and a board for teams and their
125. 3:53agents to collaborate together. All
126. 3:55right, this is the explanation for our
127. 3:56company. And you you probably have to
128. 3:58have some rules, for example, uh for
129. 4:00sponsorships, uh
130. 4:01anything over $3,000, needs a yes from
131. 4:04Sean, okay? Or any code sales pitches
132. 4:06get no reply, stuff like that, okay? You
133. 4:08can turn this into something more
134. 4:09complicated, but it's like Obsidian,
135. 4:11right? You can also store something like
136. 4:12this in your notes, in your Obsidian.
137. 4:14For me, I'm just storing such a thing in
138. 4:16Notion, and uh, I'll show you later how
139. 4:19you will be able to connect this into
140. 4:21your chief of staff, so that you can get
141. 4:22it up to working. The second thing is
142. 4:24called a record. If you own your own
143. 4:26brand, if you have your own agency, or
144. 4:28you're just selling software to your
145. 4:29clients, you probably have heard of this
146. 4:31term called CRMs. A lot of technical
147. 4:33people will sometimes prefer to use
148. 4:34database by themselves, uh, which I
149. 4:36would recommend starting with, uh,
150. 4:38Superbase, which is a good tool, but,
151. 4:40uh, if you're more technical, feel free
152. 4:41to just use AWS for everything. But, if
153. 4:43you're someone who is running your own
154. 4:45business, running your own team, and you
155. 4:47don't really have time to worry about
156. 4:48this, uh, having a CRM, or a just a
157. 4:50Google Sheet, could be really helpful
158. 4:52for storing these records, okay? And
159. 4:54this is just a place for you to store
160. 4:55information about your customers, your
161. 4:57deals, and your dates, okay? And in
162. 5:00today's example, um, later I'm going to
163. 5:02show an example using HubSpot, uh, which
164. 5:05is also connectable to your AI. And the
165. 5:08third thing is what we call the memory.
166. 5:09For those who are familiar, you probably
167. 5:11have watched my previous memory system,
168. 5:13uh, videos, which are more technical.
169. 5:15But, for today, in plain English, what
170. 5:17memory does is something that agents has
171. 5:19made decisions on, or you have made a
172. 5:21decision on something, or you have done
173. 5:23something, or the agents have done
174. 5:24something, anything that has been done,
175. 5:26instead of something that's long-term,
176. 5:28like what the handbook or playbook
177. 5:30would, uh, would be stored in some kind
178. 5:32of drives, right? Or it's also not a
179. 5:35customer information coming in from
180. 5:36emails, or dropped into your CRM system.
181. 5:39It's something that you want to keep
182. 5:40sharing across your chats and the tools,
183. 5:43so that your agents will always be fed
184. 5:45with the right context, and context is
185. 5:48everything, okay? You might heard that
186. 5:50some AI models are getting stronger, you
187. 5:52know, some agent harnesses, like Hermes,
188. 5:54are getting really popular, or even uses
189. 5:57really popular, like that one of the
190. 5:58most downloaded apps in the US, or
191. 6:01across the world in the past few weeks.
192. 6:03Um, literally, they cannot do anything
193. 6:04without memories. Okay? Memories could
194. 6:06be chat history uh, uh, on Claude AI,
195. 6:08could be chat history in your Claude
196. 6:10code sessions, but you just need to
197. 6:11prepare it really well and then feed it
198. 6:13to your agents. Okay? So, these three
199. 6:15are what I call the brain for a Claude
200. 6:16code. And then we're going to start
201. 6:17worrying about how does it get things
202. 6:19done? If you're not familiar with this,
203. 6:21there are two main things. Number one is
204. 6:22skills, number two is artifacts. These
205. 6:25are the things that we use every single
206. 6:27day by running our own company. And
207. 6:29skills is basically a recipe that you
208. 6:31want to teach your machine how to do
209. 6:33things. Okay? For example, how do we
210. 6:35even triage the inbox? How do we prepare
211. 6:37for the meeting? How do we write a quote
212. 6:39for the clients? How do we do some
213. 6:41weekly reviews? Skills essentially is
214. 6:43something that allows you to not
215. 6:45repetitively explain something to your
216. 6:47AI. And the AI should be able to trigger
217. 6:49a skill to proceed to work on something,
218. 6:52which also in the memory terms is called
219. 6:54procedural memories. Okay? And then
220. 6:55artifacts is like a dashboard that you
221. 6:58just saw earlier. I'll show you exactly
222. 6:59how you can create this in a bit, but
223. 7:01this is something that we find really,
224. 7:03really helpful when we use Claude as our
225. 7:05chief of staff to share information
226. 7:07across the rest of the team and for team
227. 7:09discussions. We don't write PowerPoints
228. 7:11anymore these days. We write artifacts
229. 7:13and we tell Claude to use a similar
230. 7:15design system to create the artifact so
231. 7:18that the rest of the team will be able
232. 7:19to see at least like a similar template
233. 7:20for PowerPoints. Okay? You can also come
234. 7:22to the sidebar and click on customize to
235. 7:24find out about skills over here. You can
236. 7:27use some of the skills by other people.
237. 7:28If you use QuickBooks to bookkeeping
238. 7:30your small business, bank fees,
239. 7:32reconciliation reports and everything,
240. 7:33you can just click on plus and then
241. 7:35bring it into your system. All right?
242. 7:37But we don't we're not going to show
243. 7:38QuickBooks today. We're just going to
244. 7:39show you some of the skills that we
245. 7:41built in house in a bit, but yeah, this
246. 7:43is a very important thing to have. I
247. 7:45would consider all of these to be the
248. 7:48absolute theoretical part of building a
249. 7:51context around you know, your agent.
250. 7:53What actually makes your Claude your
251. 7:55chief of staff is you should inject the
252. 7:57actual context into your agent, which in
253. 7:59this term we call it the connectors.
254. 8:02Okay? The connectors are basically MCPs
255. 8:04before. Somehow the AI just love
256. 8:06renaming things and now they're called a
257. 8:07connectors at clock code. Okay, they're
258. 8:09just MCPs basically. Maybe there's
259. 8:10something more on top of that. I will
260. 8:12feed all these contacts from the company
261. 8:15rules you hold in notion and drive and
262. 8:18to the rekkers or CRMs where like
263. 8:20HubSpot is one of the examples, or you
264. 8:22can use Waku memory to share the
265. 8:25decisions and memories across teams and
266. 8:26agents
267. 8:28all the way to workspace where you have
268. 8:29Gmail, calendar, Slack where where the
269. 8:32work actually arrives to your agents.
270. 8:34And last but not least, you can use
271. 8:36these tools like Granola, Calendly, or
272. 8:38Linear to record meetings, book
273. 8:40meetings, and set up tasks. So, all
274. 8:42these tools are connectors, which you
275. 8:45need, as I mentioned earlier, to inject
276. 8:46context into your clock code to turn it
277. 8:49into achieve a staff that actually
278. 8:51understand what exactly is going on in
279. 8:52your world, okay? And the connections
280. 8:53again are in the same place. If you come
281. 8:55to customize over here, okay? You can
282. 8:57see there's a connectors tab over here,
283. 8:59right? And if you scroll down a little
284. 9:00bit, you can see I we're connected with
285. 9:02like Google Drive, calendar, Slack,
286. 9:03Notion, uh I lost CM, we're not using
287. 9:06it. We're using Linear. Google Docs,
288. 9:08Superbase, Figma, blah blah blah blah
289. 9:09blah, right? And you can also add some
290. 9:11like custom connectors if you build your
291. 9:13own thing, right? In our case, we built
292. 9:16Waku memories, which you can just add in
293. 9:18by https api.waku.one/mcp
294. 9:22and click on continue. And because this
295. 9:24already exists, I already added it. If I
296. 9:26just search Waku over here, you can see
297. 9:28that it's already connected. That was
298. 9:29connectors, okay? Now you have contacts
299. 9:31from all of these things. If we start a
300. 9:33new chat right now, and make sure that
301. 9:35you create your own folder for storing
302. 9:37everything here, right? In our case, I
303. 9:39created a folder on my laptop called
304. 9:40Chief of Staff. I can ask it questions
305. 9:42be like, what connectors do you have
306. 9:45access to now? So, you can see it told
307. 9:48me that I'm connected to Gmail, Slack,
308. 9:50Google Calendar, Calendly, Notion, blah
309. 9:52blah blah HubSpot, Stripe, Figma, Canva,
310. 9:54and for memory and board, we have Waku
311. 9:56here, okay? We're ready for adding this
312. 9:58context layer on top of your agent. And
313. 10:00before we jump into the real examples,
314. 10:02you should make sure that you will
315. 10:03always be the one who will approve um
316. 10:06the emails that you want to send as a
317. 10:07draft. None of these emails or none of
318. 10:09these like information injections should
319. 10:11be giving orders to your agent because
320. 10:13you don't want someone who sends you an
321. 10:15email and then that email has a prompt
322. 10:16and then that prompt is obviously
323. 10:18fishing something and then you are just
324. 10:19giving away some of your information to
325. 10:21that person. You don't want that to
326. 10:23happen. And I think most of the time
327. 10:24these agents are smart enough to not
328. 10:26allow that to happen. And then last but
329. 10:28not least, you should see the work where
330. 10:30you want to check out the cost of the
331. 10:32agents, the tokens, and also you want to
332. 10:34see, for example, how much contacts you
333. 10:36have used in each chat and eventually
334. 10:38finish each one of these tasks. Okay. I
335. 10:40hope this intro is helpful and now let's
336. 10:43jump right into these five tasks to
337. 10:46experience what an AI Chief of Staff
338. 10:48would do for us at Clockwork. Okay. So,
339. 10:50what I'm going to do now is that I just
340. 10:51copied the link for this artifact and
341. 10:53I'm going to paste it here on the
342. 10:54browser. And because I'm logged in with
343. 10:56the same account, I'm able to read it
344. 10:57from here. Okay. So, that on my
345. 10:59Clockwork I can focus on doing the
346. 11:01tasks. So, right now I open the sidebar
347. 11:03and I click on plus new, okay, and turn
348. 11:06off this sidebar. Uh remember the first
349. 11:08thing we do is that we want to set up
350. 11:09the computer, make sure we are in the
351. 11:11right folder for everything. If you have
352. 11:13not done anything like that, make sure
353. 11:15you create an empty folder and then you
354. 11:17enter this folder like this. And a good
355. 11:19habit to have, if you're not technical,
356. 11:20is that you should use a cloud.md file.
357. 11:23So, I just open it with cursor over
358. 11:25here. You can see that the cloud.md is
359. 11:28clearly saying that you should only work
360. 11:30with certain rules here. For instance,
361. 11:32we're demoing this video, so I don't
362. 11:34want the rest of the world to see all my
363. 11:35emails. So, it should always work with
364. 11:38the Gmails with the demo label on it and
365. 11:41the handbook lives in Notion. So, later
366. 11:44if I tell it to pull in my handbook, it
367. 11:46knows because your agent will by default
368. 11:48read the cloud.md in the folder that
369. 11:51you're working in, okay? So, the first
370. 11:52thing is we should plan for tomorrow's
371. 11:55meeting. So, let's click into it and
372. 11:57scroll down a little bit. We're just
373. 11:58going to quickly go through it and then
374. 11:59follow the examples and show you some
375. 12:01quick aha moments, okay? So, today
376. 12:03you're my Chief of Staff. Use only the
377. 12:05demo calendar, mail label demo, and
378. 12:07Notion pages under Chief of Staff demo.
379. 12:09Draft never send confirming one line.
380. 12:11And just to confirm that, if we copy
381. 12:12this prompt and put it here, this is
382. 12:14asking for tomorrow's morning brief,
383. 12:16which connected tools will we use and
384. 12:17why in one line each. Do not call them
385. 12:20yet. So, this is a good way to quickly
386. 12:21check what exactly Clockwork is going to
387. 12:23use as your AI chief of staff. And uh
388. 12:25now it's telling me that it's using uh
389. 12:27Google Calendar, Gmail, Slack, Waku
390. 12:29Board, Granola, Linear, GitHub, and
391. 12:31HubSpot. The work for us is that we want
392. 12:33to make my morning brief for tomorrow,
393. 12:35November 5th, as an artifact, okay?
394. 12:37Remember, artifact is one of the work
395. 12:39that uh eventually you want your AI
396. 12:40chief of staff to deliver. And we should
397. 12:42use only the demo calendar, which in my
398. 12:44case, I'll show you, okay? We have a
399. 12:46demo calendar right here, and uh we have
400. 12:48a few meetings for tomorrow. We have a
401. 12:50weekly stand-up, we have a catch-up with
402. 12:53a VC uh called Redwood Peak from Dana.
403. 12:56These are all made up, by the way. Uh we
404. 12:57have a studio intro with Marcus, we have
405. 13:00a
406. 13:01Meridian discovery call, which is a
407. 13:03potential client in our HubSpot. If you
408. 13:05can see, we have a company called
409. 13:07Meridian, and we are going to work on a
410. 13:10pilot with $5,000 of a deal. And last
411. 13:13but not least, we have a sponsorship
412. 13:14deal review, which had a $4,000
413. 13:17collaboration with 60-second
414. 13:18integration. I just made things up, it
415. 13:20it doesn't exist. It should work in
416. 13:21these following orders with decisions I
417. 13:23must make, my five meetings with
418. 13:25one-line prep each, and anything
419. 13:26suspicious, and keep it to one screen,
420. 13:28okay? Now, let's just copy this prompt
421. 13:30and then paste it here and see what
422. 13:31happens, okay? So, now Clockwork is
423. 13:33trying to think. You can always click on
424. 13:35this little arrow to see what it's
425. 13:36doing, all right? And now it's using a
426. 13:37skill called Anthropic Skills Morning.
427. 13:40So, it knows I'm preparing some kind of
428. 13:41morning brief. It automatically
429. 13:43triggered the right skill for the right
430. 13:44thing. And it says it's reading the demo
431. 13:46calendar, the demo labeled mail, and the
432. 13:48Monday Scrum page. I should show you the
433. 13:51demo emails, too. So, this is the demo
434. 13:53tab of the emails, and uh for some of
435. 13:55the folks that I mentioned earlier, like
436. 13:57the studio collaboration deal is right
437. 13:59here. If I click into it, right? And and
438. 14:01I'll just mark it as unread still. And
439. 14:03then Dana from Redwood Peak Ventures was
440. 14:06asking us for a 30-minute catch-up on
441. 14:09Waku cuz she potentially could be our
442. 14:11investors. So, these are the demo
443. 14:12emails, um which are pretty much synced
444. 14:14with the calendars here. Taking quite
445. 14:16some time. Let's look at what it's
446. 14:18doing, right? It's already taken a
447. 14:19minute and something. So, it tried to
448. 14:21understand, okay, what labels are there
449. 14:23in my Gmail and then make sure that
450. 14:25we're using the demo label only. And
451. 14:27then for Notion, it was reading the
452. 14:29Monday scrum. Uh, I do apologize for not
453. 14:32explaining that. So, you can see that in
454. 14:35our chief of staff related demo, uh, our
455. 14:38Clockwise very smart enough to figure
456. 14:40out that it's in the Notion, right? And
457. 14:41there's a Monday scrum here. Right?
458. 14:43Click into it. I have a clear agenda,
459. 14:45last week's decision, and the open asks,
460. 14:48right? For example, we should draft a
461. 14:50pilot proposal for Meridian. Okay. Uh,
462. 14:52cool. So, now it had created this, uh,
463. 14:55artifact for us, okay? And this artifact
464. 14:57is saying that there's a few decisions
465. 14:59for me to make, right? I should accept
466. 15:01or counter this sponsorship deal from
467. 15:04this person, right? Do you want to say
468. 15:05yes or no to this studio collaboration,
469. 15:08and so on and so forth. And in my five
470. 15:10meetings, there is a brief here, and I
471. 15:12can look up and something suspicious.
472. 15:14One of our emails was an IT help desk
473. 15:15urgent email, and this looks like
474. 15:17something fishy. So, it marked it out,
475. 15:19right? There's a something suspicious
476. 15:20here. So, why do I have to do this
477. 15:21myself? What I should have is it should
478. 15:23be done automatically. So, I'm going to
479. 15:25ask it, right? I can say, "We should
480. 15:28schedule this for tomorrow morning at
481. 15:317:00 a.m." Again, let's check out what
482. 15:33it's doing, okay? It's creating a
483. 15:35scheduled task for morning brief at 7:00
484. 15:36a.m., okay? And you can see the details
485. 15:38here that it wrote down. Guys, this is
486. 15:40all about context, okay? It knows the
487. 15:42context that you know. We have the
488. 15:43Google calendar, use the demo emails,
489. 15:45okay? And then we have Notion, where
490. 15:47there's a Monday scrum under YouTube
491. 15:50folder and everything. Without all these
492. 15:51context and without all these connectors
493. 15:53we talked about, your agent won't be as
494. 15:55smart as this. They will have no idea
495. 15:56what's going on. So, it's really, really
496. 15:58important. So, I think for any agent to
497. 16:01be a chief of staff, context is
498. 16:02everything. Connecting to these
499. 16:04connectors and MCPs are everything. So,
500. 16:06now it says that we have scheduled this
501. 16:08as a task at 7:00 a.m., okay? I guess
502. 16:10what we can do is that we can click on
503. 16:12scheduled here. You can see that there's
504. 16:14a morning brief at 7:00 a.m. I think
505. 16:16this was a previous one I made. This was
506. 16:17a new one I just made, okay? And you can
507. 16:19see the details here. They have wrote
508. 16:21the instructions for me. Uh, the scope,
509. 16:23like what exactly are the tools that you
510. 16:25should look at, and what are some of the
511. 16:26safety things that you should check,
512. 16:28okay? And the page should be, uh, in
513. 16:30this following order. So, it will run on
514. 16:33weekdays at every 7:00 7:00 a.m., okay?
515. 16:35Uh, but maybe I just want to run it now,
516. 16:37right? I can just click on run now. And
517. 16:38you will see this task running right
518. 16:39now. Okay, but what happened tomorrow
519. 16:41morning at 7:00 a.m. on my laptop?
520. 16:42Because now it's doing it for me, okay?
521. 16:44I just click into it, and you can see
522. 16:46exactly what it did, all right? So, you
523. 16:47see that this is the context it just
524. 16:49injected here from, um, the scheduled
525. 16:51task, and it's using the exact same
526. 16:53tools that we did, all right? It's
527. 16:54reading the Gmail, we're getting every
528. 16:56email thread. Um, now reading the Google
529. 16:58Calendar. I know some people are going
530. 16:59to ask, "What about the security? What
531. 17:00about these issues?" My answer is, I
532. 17:02don't know. I think people will just
533. 17:04eventually get used to it, and, uh,
534. 17:06people don't care as much, uh, compared
535. 17:09to maybe a year or two ago, where
536. 17:11everyone's like, "I'm not going to share
537. 17:13my emails with an AI." And, um, now I
538. 17:15feel, at least in the startup world, or,
539. 17:18uh, among a lot of the engineers, people
540. 17:20are just giving it anyways. And I'm sure
541. 17:21a lot of product managers do that, too.
542. 17:23And agency owners, business owners,
543. 17:25people are doing the same things. So,
544. 17:26you can see that we got this report
545. 17:28already, and, uh, I would call that a
546. 17:31success, okay? So, that was the first
547. 17:32task. You can plan for tomorrow, and we
548. 17:34used a lot of these tools. So, what's
549. 17:36next? We kind of already covered some of
550. 17:38them, okay? So, for the inbox, we're
551. 17:40going to draft some replies to these
552. 17:41emails, uh, for Dana, for Mark and all
553. 17:44these people, and then eventually they
554. 17:46should be a draft instead of sending
555. 17:47anything, so that we are the ones who
556. 17:49are making the decision. So, all you got
557. 17:51to do is to write a task to your agent
558. 17:54who has all the context, and ask her to
559. 17:56do the job for you. So, he searched for
560. 17:58the tools. He's using Notion. Uh, it was
561. 18:01checking the handbook again. It's pretty
562. 18:03slow sometimes. So, he just finished
563. 18:05writing all the drafts. So, if I just
564. 18:07come back to my Gmail, and, uh, you can
565. 18:09see all these emails have a little draft
566. 18:11here, right? But if we click into
567. 18:12drafts, we can see the details here.
568. 18:14Yep. Thanks for the note. A pilot is how
569. 18:16we usually start, blah, blah, blah. You
570. 18:18can just send it. Uh, but these are fake
571. 18:20accounts, so they won't exist, okay?
572. 18:22But, maybe Dana, who's this fake venture
573. 18:24capital, if I click on send, it will be
574. 18:26sent here as done. So, I will consider
575. 18:29this as done. So, you might be wondering
576. 18:30what's the difference between just
577. 18:31sending emails using agents. The
578. 18:33difference is that your agent now has
579. 18:35full context on your company. It knows
580. 18:37everything about the contacts, about the
581. 18:39CRMs, about the previous records of
582. 18:41communications. And when it now writes
583. 18:43emails, it's just so much faster. You
584. 18:45you don't really need to buy some of
585. 18:46those tools out there to help you reply
586. 18:49to your clients. All you need to do is
587. 18:50kind of, you know, schedule task here
588. 18:52and ask it to reply questions. You can
589. 18:55do it yourself. This is your AI chief of
590. 18:56staff. So, the third one is prepare for
591. 18:59your meetings, okay? Because tomorrow we
592. 19:01have this meeting with this venture
593. 19:03capital firm called Redwood Peak
594. 19:05Catch-up. And what we want to do is that
595. 19:07we want to prepare for that catch-up
596. 19:08with Dana. And we want to use her email,
597. 19:10the handbook on Waku Memory because on
598. 19:12Waku Memory, I'll assume that you have
599. 19:14connected with Waku Memory for quite
600. 19:16some time, so it knows about you and
601. 19:18knows about knows about the project. It
602. 19:20will create a one-pager later telling me
603. 19:22who she is, what she asked, what I
604. 19:24promised, three questions I should ask
605. 19:25her. Okay, let's just ask this question
606. 19:27to our chief of staff. Let me paste that
607. 19:28in.
608. 19:30Okay, so you see that it's calling Waku
609. 19:32Memories here, doing some memory calls,
610. 19:34pulling the relevant information.
611. 19:36Meanwhile, I will show you if you come
612. 19:38to waku.one, which is a portable memory
613. 19:42layer for agents and teams to
614. 19:43collaborate together. We started as an
615. 19:45open source product and we hit more than
616. 19:472,000 stars in a couple months' time.
617. 19:50Feel free to try it out. And the way to
618. 19:52set up is really simple. You just come
619. 19:54to this main website and click on copy
620. 19:56of this prompt and just paste it into
621. 19:58your cloud code and it will set things
622. 19:59up for you. Or you can do the MCP setup
623. 20:01that I showed you earlier, okay? And
624. 20:03what I'm trying to show you is that
625. 20:04after you sign in, you can click into
626. 20:06the console and within memories, I've
627. 20:08already got a chief of staff folder here
628. 20:10with something related to Dana. And this
629. 20:12was a previous memory that I had with
630. 20:13her, okay? And basically, this partner
631. 20:16asked me for evidence of company usage
632. 20:18and Shawn promised some usage examples,
633. 20:21okay? So, I think in the next
634. 20:24preparation for the meeting, we should
635. 20:26definitely prepare for that because
636. 20:26that's where
637. 20:27that was her ask. If you scroll down to
638. 20:30Dana, you can see that the preparation
639. 20:32was telling us about who she was, what
640. 20:35she asked for, and she was asking for
641. 20:37some evidence that people will come back
642. 20:39to our product every week, and what we
643. 20:41promised is three usage examples. So,
644. 20:43this has prepared me for three questions
645. 20:45to ask her, something that not checked,
646. 20:48and the after call half I don't know.
647. 20:50These are just the stuff that the clock
648. 20:52came up to me. You should put in the
649. 20:53thoughts to really like think about how
650. 20:55they should prepare the meetings for
651. 20:57you. Feel free to edit something in your
652. 20:59Notion pages, your handbooks. You can
653. 21:02create another page calling it, "Oh,
654. 21:03this is how we should reply to VCs and
655. 21:05stuff like that." I guess we'll pass
656. 21:07here. The fourth stage is we want a
657. 21:09one-page for people and agents to share
658. 21:11decisions and memories together. So, the
659. 21:13work we're going to do is basically we
660. 21:16want to draft the team's team update,
661. 21:18what was shipped, was blocked, decisions
662. 21:20needed, use only the scrum page and Waku
663. 21:22memory, and then list of decisions as
664. 21:24separate one-line items I can record,
665. 21:26okay? Again, I'll just paste that in.
666. 21:28It's searching memories on Waku, got
667. 21:30everything connected. It's literally
668. 21:31just searching the information. For
669. 21:33example, you can see that this one saw
670. 21:34that Waku reached 2,000 stars in about 3
671. 21:37months with no paid ads, a hosted
672. 21:39product with paying users shipped within
673. 21:40weeks, and we have about 135,000
674. 21:43audience across different platforms. And
675. 21:45these memories are just going to be
676. 21:47stored there and shared across teams,
677. 21:49okay? To be honest, if you're not me,
678. 21:50you probably won't see what is really
679. 21:52going on here. But if this is your own
680. 21:54context, it would make a lot more
681. 21:56clearer sense. I remember for instance
682. 21:58this company called Meridy. The
683. 21:59decisions needed is that we want to
684. 22:00confirm the proposal from their pilot,
685. 22:02and then there's a price list in our
686. 22:04memory saying that our starter and team
687. 22:06plans are $2,000 and $5,000. So, these
688. 22:09are the stuff that you want your chief
689. 22:11of staff to be able to fetch
690. 22:13immediately, okay? And these decisions
691. 22:15should be shared across your teammates,
692. 22:17okay? We do have a feature called Waku
693. 22:19team space where you can create a team
694. 22:21for your companies, and you can share a
695. 22:23lot of these decisions by using this
696. 22:25feature called board. Okay, what you got
697. 22:27to do is that you can just say, "Hey,
698. 22:29tell Sasha about our prep on Dana from
699. 22:33Waku board." So, again, it's using all
700. 22:35these connectors from the team shared
701. 22:37memory and decision layer and then
702. 22:39started posting something that uh we
703. 22:41have just prepared by our chief of staff
704. 22:43all above here. It will ping the message
705. 22:44to Sasha. Okay, I'll just pull in the
706. 22:46email from Sasha right away because it
707. 22:48should have received an email. And I
708. 22:50just went to Sasha's email and then
709. 22:52check the board and I can see there is a
710. 22:54information sent from Shawn about Dana.
711. 22:56Okay, this is the board message. What
712. 22:58happens is that we also receive an email
713. 23:00right here um from [email protected] where
714. 23:03my teammate Shawn was telling me me as
715. 23:05in Sasha now is that we have a
716. 23:07preparation for Redwood Peak uh catch-up
717. 23:09with Dana from this venture capital.
718. 23:11I'll just be able to see uh you know,
719. 23:13these uh team decisions from our
720. 23:14teammate. Uh last but not least, from
721. 23:16send a quote to the CRM. Okay, there was
722. 23:18a person called Tessa which we haven't
723. 23:20paid much attention to yet. So, Tessa
724. 23:22was asking us that their product ops
725. 23:24team at Meridian is looking for a shared
726. 23:26memory across their agents and they were
727. 23:28asking us for a quote, right? And we
728. 23:29just send them an email over here. Okay,
729. 23:32but the tasks was that we should read
730. 23:33this email, write a one-page pilot
731. 23:35proposal for them, and save it as a PDF.
732. 23:38We should not invent any price or date
733. 23:41or term because the price and date and
734. 23:43term are all in our handbook. All right,
735. 23:45there's a price list here for how much
736. 23:47we're charging these clients. Okay, so
737. 23:49then you should draft a reply to Tessa.
738. 23:51Okay, we mistakenly send a reply over
739. 23:53here because earlier we were just like
740. 23:55in a rush replying to emails, but now we
741. 23:57should do it properly. And here, we're
742. 23:59probably going to use HubSpot. I'm going
743. 24:00to copy this prompt and I'm going to ask
744. 24:02our chief of staff to work on it. Let's
745. 24:04see what happens.
746. 24:06Okay, very quickly, so it was trying to
747. 24:08fetch information from Notion and
748. 24:10failed. And then it was checking some of
749. 24:12the PDF libraries and project folders.
750. 24:15Fetching from Notion again, found a tool
751. 24:18to create PDFs. I'll just leave it to
752. 24:21work. Cool, it created this PDF for me
753. 24:23and honestly it doesn't look very nice.
754. 24:26So, I'll just say, "Can we make it look
755. 24:29nicer by following the same design
756. 24:32system
757. 24:34as wakku.one?" So, again, because we
758. 24:36have this shared team space, it kind of
759. 24:38remembers that we have certain rules
760. 24:40within our team of how we should do
761. 24:42things, and uh it's just using these uh
762. 24:45these files. You remember how it should
763. 24:47function. Built wakku.one style proposal
764. 24:49and render to PDF.
765. 24:51Create a screenshot here. Oh, so much
766. 24:53nicer. I love this a lot more. Oh, wow.
767. 24:56Look at this. It looks nice, doesn't it?
768. 24:57Yeah, very nice. It's prepared for
769. 24:59Tessa. It's a pilot proposal for
770. 25:01Meridian Streaming. It's a team pilot.
771. 25:03It's shared memory and board for teams
772. 25:05and AR agents for the product subs
773. 25:06teams, about 40 people, and we're
774. 25:08quoting a $5,000 price for 4 weeks.
775. 25:11Monthly upkeep is $500, and payment
776. 25:13should be net 14 and stuff. Very cool.
777. 25:15So, let's check out the drafts.
778. 25:17Uh we can see that right here. And
779. 25:18somehow it's not attaching it, so we
780. 25:20should just tell it uh hey, we should
781. 25:22attach it to the draft of the email and
782. 25:24then send it over.
783. 25:25Oh, this is using the browser for me,
784. 25:27and it just attached this proposal. This
785. 25:29is a cursor that Clocko is using. What
786. 25:31Clocko is doing is just taking
787. 25:33screenshots real time and use the
788. 25:34computer for me. I think it's sent. So,
789. 25:37let's check. Look at this. So, they
790. 25:38applied to Tessa for me and then created
791. 25:41this quote for us. And I'm just going to
792. 25:42say, "Hey, we should update that to uh
793. 25:45HubSpot, too. And uh can you turn this
794. 25:47into a skill in the future for how we're
795. 25:49going to reply to these quote requests
796. 25:52and CRM update?" Thanks.
797. 25:55Yep, now it's using the HubSpot CRM. It
798. 25:57found out about Tessa, Meridian
799. 25:59Streaming. It's really, really
800. 26:00convenient. Again, remember what we say?
801. 26:02It's all about context. It has the
802. 26:04context about who the client is, where
803. 26:07they are on the CRM, where some of the
804. 26:08emails that we have replied. And given
805. 26:10all the context regarding the handbook,
806. 26:12the records, the memories, and all these
807. 26:13connected tools, you will be able to
808. 26:15generate this PDF quote for this client
809. 26:19and then get things done for us. And
810. 26:20then eventually I can ask it to create a
811. 26:22skill for me. Okay, you see? Look at
812. 26:23this skill. The skill is basically just
813. 26:25checking all the contacts we just said,
814. 26:27and then there's a clear instruction
815. 26:29here. Remember, this is a procedural
816. 26:30memory. Read before writing, pick the
817. 26:32plan, invent nothing, one page proposal
818. 26:34PDF, draft the reply, send on Shawn's
819. 26:37yes, and HubSpot update, and eventually
820. 26:39have a report, okay?
821. 26:41Add a note to CRM, too. Now, it's adding
822. 26:43it to the CRM objects. Let's come back
823. 26:45to Meridian, and let's take a look
824. 26:47again.
825. 26:48You can see that in the recent activity,
826. 26:49something has been updated. There's a
827. 26:51new note here saying that there's a team
828. 26:53pilot proposal sent, all right, for
829. 26:55$5,000. There's a link here. I click
830. 26:57into it.
831. 26:58It's the same thing. Okay, that's pretty
832. 27:00much it. We have finished the five jobs
833. 27:02for this Chief of Staff.
834. 27:04Well, I'm really curious about what you
835. 27:05think, and I I believe if you're a
836. 27:06technical, please bear with us that this
837. 27:09video is about showing people, showing
838. 27:11product leaders and business owners how
839. 27:13they can use Claude code as their Chief
840. 27:15of Staff from end to end. I hope this
841. 27:16was helpful for a lot of you guys, and
842. 27:19uh let me know what else you want to
843. 27:20watch, because this was a pretty
844. 27:22introductory end to end workflow for how
845. 27:24you can set up the Claude code all the
846. 27:26way to connect with all these brains,
847. 27:28and set up the work, set up the skills,
848. 27:30and set up all these connectors in order
849. 27:32for things to be functional. And even
850. 27:34you can schedule things, and make sure
851. 27:35that they tell you things. One more
852. 27:37thing that Claude does these days is
853. 27:39that we have a Claude tag, which is for
854. 27:42teams to collaborate at the same time.
855. 27:43So, I can just ask Claude tag, and I can
856. 27:45say, "Hey, what's up with Tessa's deal?"
857. 27:48at Claude. You're pretty much just
858. 27:50running it here over here in Slack using
859. 27:52Claude tag.
860. 27:53Cool. Okay, it can allow you to read it.
861. 27:56Now, it's checking the CRM for the deal,
862. 27:57okay? Check the recent emails, send the
863. 27:59answer. So, Claude is trying to be this
864. 28:02AI employee within Slack for us, and I'm
865. 28:05looking forward to how much it will
866. 28:06evolve. So far, I think this is what's
867. 28:08been helpful for us to run the company
868. 28:10using Claude as our sort of AI Chief of
869. 28:12Staff to do a lot of things that are
870. 28:14non-technical related, but we have used
871. 28:16enough context to to simulate how a
872. 28:18business are supposed to use Claude as
873. 28:20the AI Chief of Staff. And if you're
874. 28:22interested in the future, we're happy to
875. 28:23show you more things related to
876. 28:25technical people, how how our engineers
877. 28:27or technical teams are going to use as
878. 28:29their executive assistant or Chief of
879. 28:31Staff, or however you want to call it,
880. 28:33okay? And uh you can see that it got the
881. 28:35contacts and uh it's really amazing that
882. 28:38you have connected your cloud to all the
883. 28:39contacts once, it just knows everything
884. 28:41everywhere. Again, I hope this is
885. 28:43helpful and tell me if you have any
886. 28:44questions. Feel free to try out our
887. 28:46tools, try out Claude, and join our
888. 28:49community. Uh we have all the links
889. 28:51everywhere. Uh feel free to click into
890. 28:52them and um I will see you next time.
891. 28:54Thank