
Claude Setup Homework for Brooks
If you get stuck, ask Claude!
Step 1: Plan and apps
Step 2: Document every system you work in
No connecting yet. Just list every system, app and account you touch in a normal month, so Bill can map what connects natively, what goes through Composio, and what has no connector. Fill in the table below and send it to Bill. The rows are just ideas to get you started; replace, remove or add rows so it reflects the systems you actually use.
| System | What you use it for | Account email or login owner | Who on your team uses it |
|---|---|---|---|
| Email (each account) | |||
| Calendar | |||
| File storage (Dropbox, etc.) | |||
| Point of sale | |||
| Website / online store | |||
| Accounting | |||
| Payments / bank | |||
| Shipping | |||
| Inventory / appraisal tools | |||
| Marketing / social | |||
| CRM / customer list | |||
| Other |
Do not put passwords in this table.
Step 3: Update your settings
This is the focus for now. Connectors come in our next session. All of these are in Settings in the Claude desktop app.
- Who you are and the roles you juggle
- How you want answers (length, tone, formatting likes and dislikes; Bill's include no em dashes and no emojis)
- Rules you care about, such as "never send an email without my approval, show me the draft in chat first"
Starter personal preferences (from Bill's)
Copy any that fit into your personal preferences, then add your own:
I prefer brief responses. No em dashes ever, no emojis, and no bold text unless I ask for it. When I ask for an email draft, show it in the chat with To, CC and Subject. Never send anything without my approval. Write drafts in my own voice, based on my sent mail. Every draft is a reply to the email it answers unless it is a completely new email. Never write emails with hard line breaks inside paragraphs. Use the native connector first for my accounts and Composio as the backup. Do not use the browser for an account that has a connector. Never put passwords, logins or sensitive documents in an email or attachment; use a secure link. Before suggesting next steps, check my recent email and past chats so you don't suggest work that is already done. When judging results (ads, sales, changes), use longer time periods; a few days is too short. When updating a file or spreadsheet, don't change past data without asking me first.
Good to know
- Chats vs Projects: a chat is a one-off conversation. A Project is for a bigger effort with a beginning and an end (like selling the store). What you put in a Project stays inside that Project; memory outside Projects is shared across all your chats
- Never type passwords or account numbers into a chat. Connectors (coming next session) use a secure sign-in, so Claude never sees your password
- Be thoughtful about confidential deal details involving public companies
- Claude allows only one native connector per service, so two Google Workspace accounts, for example, need a different setup. That is why Step 2 matters
Step 4: Get familiar with Claude Docs, Sheets and Slides
When you ask Claude for a document, spreadsheet or deck, it builds it as a live Claude Doc, Sheet or Slides file instead of an attachment. You can edit it yourself, comment on it for Claude to fix, share a link, and download it as Word, Excel, PowerPoint or PDF.
Step 5: Send it over and book the next session
Your checkmarks and table entries save in this browser only. When the Step 2 table is done, copy it into an email to Bill.