Your work, done with you.

I'm setting up Claude Cowork for the first time. Help me decide which connectors to authenticate first so I don't waste the first hour turning everything on.

MY ROLE: [e.g. Founder of a 3-person consultancy / Product manager at a B2B SaaS / Solo creator]

MY STACK (list everything I use weekly):
- Email: [Gmail / Outlook / other]
- Calendar: [Google / Outlook / other]
- Documents: [Google Drive / OneDrive / Dropbox / Notion / other]
- Tasks: [Notion / Linear / Jira / Asana / Todoist / other]
- Comms: [Slack / Teams / Discord / none]
- Code: [GitHub / GitLab / none]
- CRM: [HubSpot / Salesforce / Pipedrive / none]
- Finance: [QuickBooks / Xero / Zoho / none]

MY TYPICAL WORKWEEK:
[3-5 sentences on what your week looks like — meetings, writing, deciding, shipping, etc.]

THE RECIPES I WANT TO RUN FIRST:
[Pick 3 from the recipe library, e.g. "meeting prep, solo retro, inbox reset"]

GIVE ME:

## 1. Top 3 connectors to authenticate today (~15 min)
- Connector name
- Which recipes it unlocks
- Why this one before others

## 2. Tier 2 connectors for this week (~15 min more)
- Connector name
- Trigger: which recipe makes me reach for it

## 3. Skip for now
- Connectors I shouldn't bother with yet
- Criteria: would I use it more than once a week?

## 4. Scope per connector
- Read-only or read-write?
- Default recommendation: read-only until I've run the workflow 10 times and trust it.

## 5. The 30-day check-in question
- One question to ask myself in 30 days to decide which connectors to add or drop.

REVERSIBILITY:
Recommend only. Never authenticate on my behalf. I click through OAuth.

This is my first real test of Cowork. Do something useful but small so I can see how it works without risk.

TEST PROCEDURE:

## 1. Verify the connectors I authenticated
For each connector I have on, do ONE read-only action and confirm success:
- Calendar → "I can see N events in the next 7 days."
- Gmail → "I can see N unread messages in your inbox."
- Drive → "I can see N files modified this week in your /Documents folder."
- Notion → "I can see your N most recent pages."
- Slack → "I can see the last 5 channels you read."
- GitHub → "I can see your last N commits."
- (and any others I've authenticated)

If any fails, tell me which connector to re-authenticate. Do not try to fix it yourself.

## 2. Read one Downloads file
Pick the most recently modified file in my Downloads folder.
- Tell me its name and what it appears to be.
- Summarize the content in 3 sentences.
- Suggest which folder it should probably live in.
- DO NOT MOVE IT.

## 3. Preview my next 3 calendar events
- List date, time, title, attendees for each.
- For each: do I have a related document or recent email thread for this person?
- DO NOT modify the events.

## 4. Confirm the reversibility rule
Read this back to me word-for-word so we both agree:

"I am running read-only by default. I do not send, post, publish, delete, or move anything unless you explicitly ask. I show you a draft before any action. If I'm not sure whether an action is reversible, I stop and ask."

If you can do steps 1-4 without errors, you are cleared to run real recipes.

REVERSIBILITY:
Read-only. No moves, sends, deletes, or modifications anywhere.

Build me a personal context document I can save as me.md and reference in every future Cowork chat.

INPUTS — I'll point you at:
- My LinkedIn export or About page
- My company's About / Mission page
- My 3 most recent customer-facing emails (from Sent)
- My last 2 weekly reviews or status notes (if any)
- One project doc I'm genuinely proud of

ALSO USE:
- My calendar (last 30 days) as behavioral evidence
- My Sent items (last 30 days) for voice

PRODUCE me.md WITH THESE SECTIONS:

## Role
- Title and what I actually do (not the job description)
- Who pays me / who I report to
- What I'm accountable for

## Recurring work
- 3-5 projects or workstreams that are always on

## People I work with most
- For each: relationship, what we work on together, communication style

## My writing voice
- 4-6 sentences in my actual style (extracted from sent items)
- Vocabulary I use, vocabulary I avoid
- Length preference (short emails vs long, formal vs casual)

## Tools I trust
- My current stack
- Tools I'm migrating to or away from
- Tools I will NOT use (and why)

## How I want Cowork to behave
- Always draft, never send
- Read-only on financial data
- Always summarize before doing
- Always ask before chained destructive actions
- Anything else specific to me

OUTPUT:
A markdown document ready for me to save as me.md.

REVERSIBILITY:
Read-only on all sources. Drafts me.md for my review. Never saves to Drive directly — I copy the final markdown myself.

MY CONTEXT:
[Add anything else you want Cowork to know about me]

I'm considering an investment and need thorough due diligence. Analyze this opportunity.

INVESTMENT: [COMPANY NAME / STOCK TICKER / ASSET]
INVESTMENT TYPE: [Public stock / Private company / Real estate / Crypto / Other]
AMOUNT CONSIDERING: [AMOUNT]
TIME HORIZON: [Short-term < 1 year / Medium 1-5 years / Long-term 5+ years]

---
CONDUCT THIS ANALYSIS:

## 1. OVERVIEW
- What does this company/asset do?
- Business model in one paragraph
- Key products/services + target market

## 2. FINANCIAL ANALYSIS
(Public companies)
- Revenue and growth trends (last 5 years)
- Profitability metrics (gross/net margins)
- Balance sheet health (debt, cash position)
- Cash flow analysis
- Valuation metrics (P/E, P/S, PEG vs industry)

(Private / other)
- Funding history and last round terms
- Revenue estimates if available
- Burn rate if known

## 3. COMPETITIVE POSITION
- Top 3 competitors
- Market share + the moat (or lack of one)
- Where they lose

## 4. MANAGEMENT & LEADERSHIP
- Key executives and their track records
- Insider ownership %
- Recent insider buying/selling
- Any red flags (lawsuits, sudden departures)

## 5. GROWTH CATALYSTS
- Specific events that could move price up
- Product launches, expansions, regulatory wins
- Each with rough timeline

## 6. RISKS
- Industry / company-specific / regulatory
- For each: probability (H/M/L) and impact (H/M/L)

## 7. RECENT NEWS & SENTIMENT (last 90 days)
- Significant news items
- Analyst ratings and price targets
- Notable social/forum sentiment

## 8. COMPARISON
- vs 2-3 alternatives in the same space
- Why this over competitors (or not)

## 9. VALUATION
- Fair / over / undervalued
- What needs to be true for the price to be justified
- Bear / base / bull price targets

## 10. RECOMMENDATION
- Buy / hold / avoid
- If buy: at what price, with what position size
- Three things to monitor monthly

---
MY INVESTMENT STYLE: [Conservative / Moderate / Aggressive]
MY PORTFOLIO CONTEXT: [What else I own, for diversification]

SOURCING & RELIABILITY (do not skip):
- Cite a source for every hard number (revenue, margin, price target, insider %).
- Rate each source High / Medium / Low reliability (filing or earnings call = High; blog or forum = Low).
- If you cannot verify a figure, say "unverified" — never invent a number to fill a section.
- List what you could NOT confirm so I check it before I commit a dollar.

Be direct. Tell me what you actually think, not just neutral analysis.

I need comprehensive research on a topic. Create a detailed report I can reference.

TOPIC: [YOUR TOPIC]
DEPTH: [Quick overview / Standard 3-5 pages / Deep dive 10+ pages]

STRUCTURE THE REPORT AS:

## Executive Summary
- 3-5 bullet findings
- Bottom-line conclusion
- Recommended action if applicable

## Background & Context
- What this topic is about
- Why it matters now
- Key players / stakeholders

## Current State
- What's happening today
- Recent developments (last 12 months)
- Key statistics + data

## Key Findings
- Finding 1 [with evidence]
- Finding 2 [with evidence]
- Finding 3 [with evidence]
- ... (as many as warranted)

## Different Perspectives
- Perspective A: who believes this and why
- Perspective B: who believes this and why
- Areas of consensus
- Areas of debate

## Implications
- For [ME / MY INDUSTRY / MY DECISION]
- Risks to consider
- Opportunities

## Recommended Actions
- What I should do based on this
- Prioritized next steps
- Timeline if applicable

## Sources
- List every source used
- Reliability rating per source (High/Med/Low + why)
- Note any information gaps

## Questions for Further Research
- What you couldn't find
- What would require deeper investigation

SPECIFIC ANGLES I CARE ABOUT:
[Add the questions or angles you want covered]

MY CONTEXT:
[Why I'm researching this — helps tailor findings]

Save the final report as a markdown document I can reference and share.

I want a complete audit of every recurring subscription I'm paying for — and a plan to cancel what I'm not using.

SOURCES TO SCAN:
- My Gmail inbox: search "subscription", "renewal", "auto-renew", "your invoice", "monthly billing", "thanks for your purchase"
- 12 months of credit-card or bank statements (CSV attached)
- Apple ID / Google account subscription pages (screenshots if shared)
- 1Password / Bitwarden export if I provide it

FOR EACH SUBSCRIPTION:
- Service name + category (Streaming / SaaS / News / Cloud / Other)
- Cost: monthly equivalent + annual total
- Billing cadence (monthly / annual / lifetime)
- Next renewal date
- Last time I touched it (from emails or activity)
- Cancellation URL or step-by-step instructions
- "Likely forgotten?" flag if no activity in 60+ days

PRODUCE:

## 1. The full list
Table: Service | Monthly | Annual | Renews | Last used | Cancel link

## 2. Total damage
- Monthly total
- Annual total
- Annualized cost of "forgotten" ones (the headline number)

## 3. Recommended cancellations
- Tier 1 — cancel today (no activity in 90 days)
- Tier 2 — cancel after this billing cycle (using but not enough)
- Tier 3 — keep (used weekly, essential)

## 4. Drafted cancellation emails
For services that require email cancellation (no self-serve), draft the email — do not send.

## 5. The savings number
"If you cancel Tier 1 + Tier 2: $X/month, $Y/year."

REVERSIBILITY:
Never cancel anything yourself. Never click cancellation links. Produce the report. I do the clicks.

MY CONTEXT:
[Anything specific — e.g. "I run a one-person business, flag anything tax-deductible"]

Find me the best deal on a product or service I'm about to buy.

WHAT I WANT TO BUY: [PRODUCT NAME, MODEL, OR EXACT SERVICE]
CATEGORY: [Software / Hardware / Travel / Services / Other]
QUANTITY: [N]
TIME PRESSURE: [Need today / This week / Flexible]
SHIP-TO: [CITY, COUNTRY]

DO THIS:

## 1. Identify the canonical item
- Exact product or plan (SKU if applicable)
- Manufacturer / publisher price
- Standard features at that price

## 2. Survey real prices today
At least 8 places (whichever apply):
- Manufacturer site
- Amazon
- 3 specialty retailers
- 2 marketplaces (eBay, FB Marketplace for hardware)
- Refurbished / open-box (Apple Refurb, BackMarket, Woot)
- Education / non-profit / startup discount programs I qualify for

For SaaS, also check:
- Annual vs monthly pricing
- Coupon code sites (RetailMeNot, Honey, dealhack)
- Bundle deals
- Lifetime deals on AppSumo / StackSocial

## 3. Total cost of ownership
Not just sticker. Include:
- Shipping
- Tax (estimate at my zip)
- Recurring fees
- Switching cost from my current solution

## 4. The table
Source | Price | Shipping | Tax | All-in | Condition | Notes

## 5. The recommendation
"Cheapest: X at $Y. Best value: Z at $W because [reason]. Avoid: A because [reason]."
Plus: should I wait? (upcoming sales, price history if available)

## 6. Direct purchase links
For the top 2 options, give me direct links.

REVERSIBILITY:
Never purchase. Never enter payment info. Produce the comparison. I click buy.

MY CONTEXT:
[Anything that affects the choice — e.g. "I'm in Singapore, willing to pay 20% more for local warranty"]

Look at my calendar and help me work better next week.

LOOK AT:
- All events for [DATE RANGE — default: the next 7 days]
- Pattern of the last 30 days for baseline

DO THIS ANALYSIS:

## 1. The week's shape
- Total meeting hours per day
- Number of meetings per day
- Longest unbroken focus blocks
- Days with > 5 meetings (red zones)

## 2. Anti-patterns to fix
- Back-to-backs > 3 in a row (no buffer)
- Meetings without an agenda in the description
- Recurring meetings I'm on but haven't actually attended 3+ times
- Single-attendee meetings (could be a doc?)
- Meetings before 9am or after 6pm I didn't explicitly accept

## 3. Focus time to protect
Suggest 2–3 deep-work sessions per week.
Based on:
- Open gaps that already exist
- My historical productive hours (if I share)
- Meetings I could legitimately decline or shorten

## 4. Decline candidates
List 3–5 meetings where my presence is optional.
For each: organizer, why I might not need to be there, draft polite decline message.

## 5. Reschedule candidates
List meetings that would work better at a different time.
For each: current slot, suggested slot, draft message proposing the change.

## 6. New meetings I should hold
Based on my open threads and commitments, what 1:1s or check-ins should I schedule?
Draft the invite description for each.

OUTPUT FORMAT:
Markdown report. Drafts in fenced blocks I can copy.

REVERSIBILITY:
Never decline, reschedule, or send anything. Never modify the calendar. Draft messages — I send them.

MY CONTEXT:
[Role, boss, team dynamics that should inform tradeoffs]

Turn a process I do regularly into a step-by-step Standard Operating Procedure I can hand off.

THE PROCESS: [BRIEF NAME — e.g. "Monthly invoice run", "Onboarding a new client", "Posting a blog"]

WHO WILL USE IT: [Future me / Junior teammate / Virtual assistant / New hire]

HOW I'LL DESCRIBE IT TO YOU: [Pick one]
- Voice memo transcript I'll paste
- Screen recording transcript
- Bullet list of what I do
- Walk-through chat where you ask me questions

---
PRODUCE THIS SOP:

## Overview
- Purpose
- When to run (trigger + frequency)
- Approximate time to complete
- Required access / tools

## Prerequisites
- Accounts and logins needed
- Files or templates required
- Permissions
- Skills assumed

## The procedure
Numbered steps. Each step has:
- Action verb at the start ("Open", "Click", "Paste", "Send")
- Exact location (URL, app, menu path)
- Expected result
- Screenshot placeholder: [SCREENSHOT: what to capture]
- Common error + fix (if any)

## Quality checks
- How to verify the output is correct
- Self-check questions before marking complete

## Handoff section
- Who to escalate to if something breaks
- Where to log completion
- Where the artifact ends up

## Edge cases
- What's different on the first run
- International customers / weekends / month-end / etc.

## Revision log
- Date of this version
- What I'd test changing next quarter

INTERVIEW MODE:
Ask me 5–8 sharp questions to fill gaps in my description.
Then write the SOP.
Then ask 2 more questions to fill any holes in the draft.

OUTPUT:
Markdown SOP saved as a document I can drop into Notion or Drive.

REVERSIBILITY:
You write the SOP. Never automate or execute the process. The SOP is for humans.

MY CONTEXT:
[Industry, team size, anything that affects tone or detail]

Help me reconstruct my business or personal expenses for tax season (or quarterly review).

PERIOD: [DATE RANGE — e.g. "2025 calendar year" or "Q1 2026"]
PURPOSE: [Tax filing / Reimbursement / Budget review / Audit prep]

SOURCES I'LL PROVIDE:
- Email inbox (search receipts: "receipt", "order confirmation", "your invoice", "thank you for your purchase")
- Credit-card / bank CSV exports (attached)
- Downloads folder receipts (PDFs and images)
- Recurring subscriptions list

---
DO THIS:

## 1. Receipt extraction
For every charge over [$X], find the matching receipt.
For each:
- Date
- Vendor
- Amount + currency (and converted USD if foreign)
- Payment method
- Description
- Category

## 2. Categorization
- Software / SaaS (deductible for business)
- Hardware / equipment (capex, possibly depreciable)
- Travel (airfare, hotels, ground, meals — rules apply)
- Meals & entertainment (typically 50% deductible)
- Professional services (legal, accounting, consultants)
- Marketing / advertising
- Office supplies
- Education / training (deductible if business-related)
- Health insurance (if self-employed)
- Personal (not deductible — keep separate)

## 3. Tax-deductible flags
For each item, flag:
- DEDUCTIBLE (clearly business)
- LIKELY DEDUCTIBLE (defensible with supporting note)
- AMBIGUOUS (ask me a follow-up)
- NOT DEDUCTIBLE (personal)

## 4. Missing receipts
List charges on statements with no receipt found. Sorted by amount desc.
Each: vendor, date, amount, "where to look" hint (vendor portal, app, etc.)

## 5. Spreadsheet
Output a CSV ready to import into QuickBooks / Xero / Wave / Zoho Books.
Columns: Date | Vendor | Amount | Currency | Category | Tax flag | Receipt link | Notes

## 6. Summary memo
- Total spend
- Spend by category
- YoY change (if I share prior data)
- Top 5 vendors
- Anomalies worth investigating

REVERSIBILITY:
Read-only. Never categorize anything in QBO directly. Never delete receipts. Produce the spreadsheet — I import it.

MY CONTEXT:
[Self-employed? S-corp? Schedule C? Country? Industry-specific deductions?]

Generate my personal weekly review. This is for me, not for my boss.

WEEK ENDING: [DATE — default: today]

SOURCES:
- Calendar (all events, including ones I declined or didn't attend)
- Gmail sent items (what I committed to)
- Notion / Drive (what I wrote or worked on)
- Linear / Jira / GitHub (what I shipped or moved)
- Slack DMs and channels I read (key threads)
- A note from me (optional): [OPTIONAL NOTE]

---
PRODUCE THIS REVIEW:

## Wins
3–5 things I actually accomplished. Specific, one-line outcome each. No "worked on X" — only "delivered X" or "decided X".

## Losses or stalls
1–3 things that didn't move. Honest cause: my time? Their dependency? Unclear scope?

## What I learned
2–3 lessons. Specific to a moment that happened this week. Each tagged with a context where I'd reuse it.

## Promises I made
Every commitment I made this week — who I owe what, by when, current status.

## Surprises
Things I didn't expect at the start of the week that ended up mattering. (These are usually signals.)

## Anti-portfolio
Things I'm consciously NOT doing — to prove I made a choice, not just forgot.

## Energy audit
Times I felt the best (sources of energy).
Times I felt drained (sources of friction).
Pattern worth changing next week?

## Next week — the one thing
The single most important outcome for next week. Not three. One.

## The 4-week theme spotter
If you have my last 4 reviews, what theme is emerging? What are my own actions telling me about what I actually care about right now?

OUTPUT:
Markdown document. Save as a dated file in [Notion page / Drive folder] so I can run this every Friday and compare.

REVERSIBILITY:
Read-only. Never modify Notion pages or Drive docs. Just produce the markdown.

MY CONTEXT:
[Role, what's on my mind, what I'm consciously trying to improve]

Help me get to inbox zero without losing anything important.

INBOX SCOPE:
- All unread mail in my primary inbox
- Last 30 days of read-but-not-archived (the "I'll get to it" pile)
- Spam folder for false positives I should rescue

---
DO THIS:

## 1. Triage every message into one of seven buckets:
- REPLY-NOW — Important, quick to handle, < 2 minutes
- REPLY-LATER — Important, needs thought, > 5 minutes
- WAITING — I'm waiting on someone else, just track
- TASK — Becomes a to-do, not a reply
- READ — Newsletter or article, save and read later
- ARCHIVE — Already handled, no action
- DELETE — Spam, expired promotions

## 2. REPLY-NOW emails
Draft the reply. Do not send.
Keep under 5 sentences unless tone requires more.
Use my style (pull from sent items as voice samples).

## 3. REPLY-LATER emails
- Summarize the thread (2 lines)
- Suggest the shape of my reply (decision needed / info needed / soft no)
- Estimate time to draft a full reply
- Sort by deadline + relationship importance

## 4. WAITING
- Pull out the commitment + person + when promised
- Flag any that have waited > 5 days for a nudge
- Draft the nudge

## 5. TASK
- Extract the action
- Suggest the right list (calendar block, task manager, project file)
- Draft the task description

## 6. READ
- Categorize the newsletter / source
- Note which I haven't engaged with in 30+ days
- List unsubscribe candidates with unsubscribe URLs

## 7. The queue
Prioritized work queue:
- "Spend 10 min: process REPLY-NOW (count: N, all drafted)"
- "Spend 30 min: review REPLY-LATER (count: N, ranked by deadline)"
- "Schedule: TASKs go to [my system]"
- "One-click: unsubscribe from [N] sources"

## 8. Trends
- Top 5 senders by volume
- Top 5 threads I keep avoiding (be honest)
- Patterns in what's overwhelming me

REVERSIBILITY:
Drafts only. Never send. Never archive or delete. Never mark as read. Never unsubscribe — give me the URLs and I'll click.

MY CONTEXT:
[Job, communication style, things to never miss, sensitive senders]

Organize my Desktop, Downloads, and Documents folders. Find duplicates. Recommend deletions.

FOLDERS TO SCAN: [Default: Desktop + Downloads + Documents]
DEPTH: [Just these / Include subfolders / Up to N levels]
OS: [macOS / Windows / Linux]

---
DO THIS:

## 1. Inventory
For each folder:
- Total files and total size
- File-type breakdown (docs, images, screenshots, archives, code, video, other)
- Oldest file and newest file
- "Stale" files: not opened or modified in 6+ months

## 2. Proposed structure
Suggest a folder tree:
- 01_Active (last 30 days)
- 02_Reference (older but I might need it)
- 03_Archive (older than 1 year, rarely touched)
- 04_To_Sort (need a human pass)

Plus topical subfolders if patterns emerge (e.g. "01_Active/Pradhya", "01_Active/Personal").

## 3. The move plan
For every file in scope:
- Stay in place
- Move to [proposed path]
- Delete
- Merge with [existing file]

Don't actually move anything — produce the plan.

## 4. Duplicates
- Exact duplicates (same hash) — keep newest, list deletable copies with full paths
- Near-duplicates (same filename, different folders) — flag for review
- Screenshot floods — "Screen Shot 2026-01-15 at 14.23.png" × 47 — bulk action proposal

## 5. The clutter list
- Files I downloaded but never opened
- Installers I no longer need (old DMGs, ZIPs)
- Browser-generated junk (10 versions of "Untitled.pdf")
- Cache / temp files safe to remove
- Empty folders

## 6. Sensitive file warning
Files that might contain sensitive data (filenames with "tax", "passport", "id-", "contract", "salary", "medical") — flag separately, never propose to move or delete without my explicit yes.

## 7. The shell script
Generate `cleanup.sh` (or `cleanup.bat`) with:
- Every move and delete as an explicit command
- A `--dry-run` mode that just prints what it would do
- A header comment explaining what it does
- A `--backup` mode that copies to a temp folder before deleting

REVERSIBILITY:
You produce the plan and the script. You do NOT move, rename, or delete anything yourself. I review the script. I run `--dry-run` first. I run for real only when I'm sure.

MY CONTEXT:
[Cloud-synced folders (Drive, Dropbox, iCloud)? Anything in scope I should treat as sacred (don't touch)?]

Draft my monthly investor update from what actually happened this month.

MONTH: [Month Year]

SOURCES TO READ:
- Calendar (every event this month)
- Linear / Jira (closed tickets, shipped features)
- GitHub (merged PRs, releases tagged this month)
- KPI dashboard or spreadsheet (if shared)
- Sent emails (commitments I made)
- Slack #wins or #shipped channel
- My last 2-3 investor updates for tone + format reference

PRODUCE THIS UPDATE (600-800 words):

## TL;DR (3 bullets)
- The single most important thing this month
- The biggest miss or risk
- The one ask for investors

## Metrics
- MRR / ARR + change vs last month and goal
- New customers + churn
- Net revenue retention
- Cash + months of runway
- 1-3 north-star metrics specific to my business

## Wins
- 3-5 specific shipped things
- Each: what shipped + early signal of impact

## Lowlights & risks
- 1-3 things that didn't go well
- Honest about why
- What we're changing

## Hires & team
- New hires this month
- Open roles (with the profile)
- Departures (if any)

## Asks (the most important section)
- Intros: specific people or companies
- Customer leads: profile of customers we want
- Hiring: roles where investors might know talent
- Feedback: 1-2 strategic questions

## Next month
- Top 3 priorities
- Big milestones to watch for

USE MY VOICE:
Pull from my last 2 investor updates as voice samples. Match the sentence length, the directness, the in-jokes if any.

REVERSIBILITY:
Draft only. Never send to investors. I review, edit, send through my normal channel.

MY CONTEXT:
[Stage, sector, last round, any sensitivities to know about]

Prep me for an interview tomorrow.

THE INTERVIEW:
- Company: [COMPANY NAME]
- Role: [ROLE TITLE]
- Interviewer(s): [NAME · LinkedIn URL]
- Format: [Behavioral / Technical / Case / Panel / Other]
- My target start: [DATE or "ASAP"]

SOURCES:
- Their website (Careers + About + Blog)
- The interviewer's LinkedIn + recent Twitter/posts if public
- Their last 4 funding rounds or earnings calls (if public co)
- Glassdoor / Levels.fyi for comp + culture signals
- The job description (paste below or attach)
- My resume (attach)

PRODUCE:

## 1. The company brief (1 page)
- What they do, in one sentence
- Business model + key revenue lines
- Stage + funding + key investors
- Recent strategic moves (last 12 months)
- The 3 things they likely care about right now

## 2. The interviewer brief
- Tenure at company
- Background (where they were before)
- What they post or write about
- 3 things to mention that show I've done my homework

## 3. The role decoded
- The actual job behind the job description
- 3 likely day-1 priorities
- 3 things that could go wrong in the first 90 days

## 4. Questions to ask (10)
- 3 about the role
- 3 about the team
- 2 about the company strategy
- 2 about the interviewer's journey

## 5. Likely questions they'll ask
- 5 behavioral they will ask (with STAR-ready bullet I'd use)
- 3 hard ones I should rehearse
- The one curveball they might throw

## 6. My stories ready
- 3 stories from my career that fit this role
- For each: situation, action, result, what I learned
- Tag each with which interview question it answers

## 7. Red flags to watch for
- 3 things to listen for that would change my interest

REVERSIBILITY:
Research and prep only. Never apply, never send messages to anyone at the company.

MY CONTEXT:
[Resume highlights, what excites me about this role, any deal-breakers]

Turn my call notes into a complete write-up: CRM entry, follow-up email, and task list.

THE CALL:
- Type: [Discovery / Demo / Follow-up / Renewal / Internal]
- Customer or person: [NAME, COMPANY]
- Date: [DATE]
- Duration: [N minutes]

INPUTS:
- My typed notes (paste below or attach)
- Transcript from Granola / Otter / Read.ai (if I have one)
- Calendar event with attendees
- The prior thread in this conversation (Gmail)

NOTES:
[Paste your notes here]

PRODUCE:

## 1. The CRM-ready summary (5 sections)
- **Who was on the call:** Names + roles
- **What they said:** Their stated needs, pains, current situation
- **What I said:** What I committed to, what I offered, what I demoed
- **Decisions made:** Anything we agreed on
- **Open questions:** Things to follow up on

## 2. The follow-up email (drafted)
- Subject line (clear, action-oriented)
- 4-6 sentences max
- Recap the one thing we agreed
- The single ask
- Calendar link or specific next step

## 3. The task list
Table: Task | Owner | Deadline
- Tasks for me (immediate next 24h)
- Tasks for the customer (if any)
- Internal handoffs (sales engineer, legal, etc.)

## 4. The deal/relationship signal
- Sentiment (warm / neutral / cool)
- Risks observed
- Champion vs blocker on their side
- Probability change (up / down / flat)

## 5. What I learned (for me)
- One thing I'd do differently next call
- A question I should have asked

REVERSIBILITY:
Drafts everything. Never logs to the CRM directly. Never sends the follow-up. I approve and send.

MY CONTEXT:
[My role, what stage of the deal, any sensitivity]

I have hundreds of pieces of user feedback across channels. Cluster them and tell me what users are actually saying.

SOURCES (last 90 days unless otherwise noted):
- Support tickets (Zendesk / Intercom / Help Scout)
- Slack channels where customers post (if connected)
- Customer call transcripts (Granola, Gong)
- NPS / CSAT survey responses (CSV attached)
- App store / G2 reviews (if applicable)
- Twitter / LinkedIn mentions (if I provide them)

PRODUCE:

## 1. The themes (5-8 clusters)
For each theme:
- Name (short, evocative)
- Frequency (count + % of total)
- Trend (rising / steady / declining over the period)
- 3-4 verbatim quotes (with source)
- Sentiment (frustrated / confused / delighted / pragmatic)

## 2. The hidden themes
- Things mentioned often as side-comments, not the main complaint
- "Polite" feedback that's actually serious
- Quotes from power users that read different from new users

## 3. The contradictions
- Where users disagree with each other
- Where users disagree with our public roadmap

## 4. Suggested PM actions
- For each top theme: ship / investigate / accept / deflect
- Effort estimate for ship-able fixes
- Risk of doing nothing on each theme

## 5. Customers worth interviewing
- 3-5 people who said something specific and articulate
- For each: what to ask + why their case is interesting

## 6. The 3-slide engineering pitch
- One theme per slide
- Verbatim quote
- Suggested move + estimate

OUTPUT FORMAT:
Markdown report I can drop into Notion.

REVERSIBILITY:
Read-only across all sources. Never replies to customers. Never edits tickets.

MY CONTEXT:
[Product, target user, current roadmap so themes can be tagged "already planned"]

Generate the standup digest for my team. What did each person ship yesterday and what's blocked.

THE TEAM:
- Names: [LIST OF TEAM MEMBERS]
- Where they work: GitHub orgs, Linear teams, Slack channels

SOURCES TO READ (last 24 hours):
- GitHub: merged PRs, opened PRs, review comments per person
- Linear / Jira: tickets moved (any column change), comments added
- Slack: each person's posts in #team-eng and other relevant channels
- Calendar: meetings each person had

PRODUCE:

## 1. Per-person update (5 bullets max)
For each team member:
- ✅ Shipped: PR titles + impact
- ⏳ In progress: ticket title + state
- ⏸ Stuck: blocker + who they need
- 📅 Today: from their calendar / assigned tickets
- 🔔 Worth surfacing: anything notable

## 2. Team-level signals
- Total PRs shipped vs rolling 7-day average
- Bottlenecks (PRs waiting for review > 24h)
- Risks (people working solo on critical paths)

## 3. The blocker list (most important)
Table: Blocker | Blocked person | Who can unblock
- Anything blocked > 48h gets flagged

## 4. Questions for me to ask in standup
- 3 questions surfaced from the data
- Each tied to a specific person/blocker

## 5. Things I can skip
- Routine work that doesn't need air time
- Status that's clear from the data

OUTPUT FORMAT:
Markdown. Concise. Standup is 15 minutes total.

REVERSIBILITY:
Read-only. Never posts to Slack, never updates tickets, never reassigns work.

MY CONTEXT:
[Team size, sprint cycle, what I'm trying to make more visible]

Of my renewals this quarter, which 3-5 are at highest risk of churning?

CONTEXT:
- Renewal quarter: [QUARTER, e.g. Q3 2026]
- Total accounts up for renewal: [N, or "look it up in CRM"]

DATA SOURCES:
- CRM (Salesforce, HubSpot): account size, last touch, owner, history
- Support tickets per account (last 90 days)
- Product usage data if available (logins, feature adoption, MAU/DAU)
- Champion / sponsor status (still employed?)
- Last NPS response per account

PRODUCE:

## 1. The full ranked list
Table: Account | ARR | Renewal date | Risk score (1-10) | Top 2 risk signals | Owner

## 2. The top 5 at-risk accounts (deep dive)
For each:
- Why they're at risk (specific signals, not vibes)
- What we've done about it so far
- What we should do in the next 2 weeks
- Who else internally should know
- The unlock: the one move that would change the trajectory

## 3. The drafted outreach
For each top-5 account, draft:
- Subject line
- A 4-sentence email to the champion
- A 3-bullet talking-points doc for the CSM's call

## 4. The internal nudges
- Slack messages I should send to coworkers about specific accounts

## 5. The pattern
- Across at-risk accounts, what's common?
- Is the risk a product issue, a CSM staffing issue, or a segment issue?

REVERSIBILITY:
Drafts everything. Never sends, never logs to CRM, never tags accounts.

MY CONTEXT:
[My role, what counts as a save, our renewal motion]

Prep me to negotiate. Give me a playbook with their likely moves, my counters, and scripts.

THE NEGOTIATION:
- Type: [Salary / Vendor renewal / Office lease / Service contract / Other]
- Other party: [NAME / COMPANY]
- What I want: [SPECIFIC OUTCOME]
- What I'll walk away over: [BATNA]
- Time horizon: [When this needs to happen]

DATA TO PULL:
- Their public pricing (if applicable)
- Market comp (Levels.fyi, BuiltIn, industry reports — research this)
- My prior agreement or current contract
- Their incentives (quarterly close, fiscal year end, etc.)
- Anything they've said publicly

PRODUCE:

## 1. The opening
- What I should ask for first (the anchor)
- The supporting evidence (3 points)
- The tone (warm / firm / collaborative)

## 2. Their likely moves
- 3 opening positions they might take
- For each: why they'd open there + my counter

## 3. The script for 3 turns
- Turn 1 (their open): What they say / what I say
- Turn 2 (their counter): What they say / what I say
- Turn 3 (the deal): The closer move

## 4. Their pressure points (leverage)
- 3 specific reasons they want this deal to close
- How to surface them without being mercenary
- What I should NOT bring up (because it weakens me)

## 5. My non-negotiables
- Walk-away conditions
- Items I'll never give up
- The clear "no" sentence

## 6. The trade matrix
- Things I value > they value (give these up last)
- Things they value > I value (concede these for big asks)
- Things equal-value (use as currency)

## 7. The closing
- The phrase that makes "yes" easy for them
- What to do if they say "let me think about it"
- The follow-up email if I have to walk

REVERSIBILITY:
Plans only. Never sends messages to the other party. I rehearse the script myself.

MY CONTEXT:
[Background, relationship history, what I really want vs what I'll accept]

Plan a trip with all the details handled.

THE TRIP:
- Cities + dates: [CITY 1 from-to · CITY 2 from-to · ...]
- Travel reason: [Business / Personal / Conference / Family]
- Travelers: [N adults · N kids · ages]
- Budget: [TOTAL or per-day]
- Constraints: [Dietary, mobility, can't-miss meetings, etc.]

SOURCES:
- My calendar (catch conflicts during travel dates)
- My email (existing flight/hotel confirmations to incorporate)
- Passport expiry date (I'll share)
- Frequent flyer / hotel program tier (I'll share)

PRODUCE:

## 1. Calendar conflict check
- Every event during travel dates that needs handling
- Suggested action per conflict (decline / reschedule / dial in / delegate)
- Drafted decline messages where needed

## 2. The day-by-day itinerary
- Morning / midday / evening per day
- Travel time between things factored in
- Buffer for jet lag on day 1
- One must-do + one easy backup per day

## 3. Booking checklist
- Flights: routes, suggested airlines (with my loyalty tier), departure windows
- Hotels: 3 options per city in budget, with one stretch pick
- Local transit: best mode per city (Uber / metro / car / walking)
- Reservations needing > 7 days notice (restaurants, museums)

## 4. Pre-trip checklist
- Visa requirements per country (if international)
- Passport expiry check (> 6 months from return date)
- Vaccinations / health requirements
- Travel insurance suggestion
- International data plan / SIM
- Currency / payment cards that work abroad

## 5. The packing list
- Climate-aware basics
- Business need vs personal
- Easy-to-forget stuff (adapters, chargers, melatonin)

## 6. Emergency contacts
- Embassy info per country
- Insurance hotline
- Family contact card formatted to print

## 7. The 24-hour-before run
- Things to do the day before flying
- Things to set up (out-of-office, mail hold)

REVERSIBILITY:
Plans only. Never books flights or hotels. Never confirms reservations.

MY CONTEXT:
[Loyalty programs, dietary, fitness routine I want to maintain, anything else]

Draft this week's newsletter from my week. In my voice. Ready for me to edit and send.

NEWSLETTER CONTEXT:
- Name: [NEWSLETTER NAME]
- Audience: [WHO READS IT]
- Frequency: [Weekly / Bi-weekly]
- Length: [SHORT 300w / MEDIUM 500-700w / LONG 1000w+]
- Tone: [Conversational / Analytical / Punchy / Reflective]

SOURCES:
- This week's Notion notes / Drive docs
- Sent items (anything I wrote in long form this week)
- Calendar (what I attended, who I talked to)
- Drafts folder (anything I started but didn't publish)
- My last 5 newsletters (for voice + format reference)

PRODUCE:

## 1. The hook (opening line)
- 3 variations
- Each should make a regular reader stop scrolling

## 2. The main piece
- One clear claim or story
- 3 supporting moves (specific examples, data, or counterpoints)
- A satisfying landing

## 3. The bonus section (if relevant)
- 1-3 short items: links, things I'm reading, a question to readers

## 4. The CTA
- One specific ask (no more than one)
- Reply to / share with / book a call / etc.

## 5. The signoff
- In my voice (pulled from samples)

## 6. The metadata
- Subject line (3 variants, A/B testable)
- Preview text
- Suggested send time based on past open rates if I share data

## 7. The pieces that didn't make it
- Stories from the week that didn't fit
- Save these in a "future newsletters" doc

REVERSIBILITY:
Draft only. Never sends, never schedules. I copy the final version and send myself.

MY CONTEXT:
[My niche, the one thing readers value most, anything off-limits this week]

Prep me for tomorrow's 1:1 with [TEAM MEMBER].

THE PERSON:
- Name: [NAME]
- Role: [ROLE]
- Last 1:1: [DATE]
- Cadence: [Weekly / Bi-weekly / Monthly]

SOURCES:
- Their work in the last 1:1 cycle:
  - GitHub (PRs they shipped, code review they did)
  - Linear / Jira (tickets they closed, moved, opened)
  - Notion / Drive (docs they wrote)
  - Slack (channels and DMs they were active in)
- Our last 3 sets of 1:1 notes (Notion or Drive)
- Their goals doc / career conversation notes if I have them

PRODUCE:

## 1. What they shipped
- Specific output since last 1:1 (with impact lines)
- Quality observations (PR review patterns, code quality)
- Pace observations (faster / steadier / slower than usual)

## 2. What they're working on
- Current focus + how it's progressing
- Anything stuck

## 3. What's changed about them
- Tone / morale signals from Slack
- New skills demonstrated
- Patterns worth surfacing

## 4. Follow-through on last 1:1
- Things they said they'd do, status of each
- Things I said I'd do (most important to track)

## 5. Three things to discuss tomorrow
- Specific topics, not generic categories
- For each: why now, what good looks like coming out of it

## 6. Three questions to ask
- Open questions, not yes/no
- Questions that surface what they aren't saying

## 7. What I shouldn't bring up
- Things that would feel like surveillance
- Things they should be allowed to raise first

## 8. After-meeting tasks
- Things I'll likely commit to
- Notes I should take during the meeting (not just after)

REVERSIBILITY:
Read-only. Never DMs the person before the 1:1. Never modifies their tickets or goals.

MY CONTEXT:
[How long they've been on the team, what we're working on changing, any sensitivities]