Claude Cowork Prompts for Startup Founders

As a founder, you context-switch between product, fundraising, hiring, ops, and customer conversations. Every day. The information you need to make decisions is scattered across Slack, email, your calendar, and three different project boards.

These are scheduled tasks for Claude Cowork built specifically for startup founders. Each one runs on a schedule, pulls context from your connected tools, and delivers something useful without you lifting a finger.

Want to see what these agents actually produce? Check out the full use case breakdowns for startup founders, with example outputs and copy-paste prompts for each workflow.

To set any of these up: paste the prompt into Cowork and say "Set this up as a scheduled task." Replace [your-email@gmail.com] with your own address.

---

1. Weekly MRR dashboard

Schedule: Every Monday at 7:30 AM

Start every week knowing your number. Not a vague sense of "things are growing." The actual number, with context. See the full weekly metrics use case for a detailed breakdown.

Run every Monday at 7:30 AM.

Step 1: Use the Stripe connector to pull all successful charges from the
last 7 days. For each charge, record: customer name or email, amount,
currency, date, and whether this is a new subscription, renewal, or
one-time charge.

Step 2: Calculate:
- MRR as of today (sum of all active recurring subscriptions)
- New MRR added this week (new subscriptions only)
- Churned MRR this week (cancelled subscriptions)
- Net MRR change
- Total revenue collected this week (including one-time charges)
- Compare to the prior 7-day period: percentage change in MRR and total
  revenue

Step 3: Use the Stripe connector to identify:
- New customers this week (first-ever charge)
- Customers who cancelled or failed to renew
- Any failed charges or payment issues

Step 4: Save the dashboard as
projects/metrics/weekly/YYYY-MM-DD-mrr.md using this format:

# MRR Dashboard — Week of [YYYY-MM-DD]

## Key Numbers
- Current MRR: $[amount]
- New MRR: +$[amount] ([N] new customers)
- Churned MRR: -$[amount] ([N] cancellations)
- Net change: [+/-]$[amount] ([+/-]%)
- Total collected this week: $[amount]

## New Customers
| Customer | Plan | MRR | Date |
|----------|------|-----|------|
| ...      | ...  | ... | ...  |

## Churn
| Customer | Plan | MRR Lost | Reason (if known) |
|----------|------|----------|-------------------|
| ...      | ...  | ...      | ...               |

## Failed Payments
| Customer | Amount | Attempts | Status |
|----------|--------|----------|--------|
| ...      | ...    | ...      | ...    |

## Notes
[Anomalies, trends, or things to investigate]

Step 5: Use the Gmail connector to send the dashboard to
[your-email@gmail.com]. Subject: "MRR Dashboard — Week of [YYYY-MM-DD]".
Body: the full report.

---

2. Friday ship log

Schedule: Every Friday at 5:00 PM

End every week with a record of what actually shipped. Not what was planned. What moved from "doing" to "done."

Run every Friday at 5:00 PM.

Step 1: Use the Notion connector to pull all tasks that were marked as
"Done" or "Completed" this week across all active projects. For each task,
record: task name, project name, and completion date.

Step 2: Use the Granola connector to pull all meeting notes from this week.
For each meeting, extract: any decisions made and any deliverables
mentioned as completed or shipped.

Step 3: Use the Slack connector to scan all channels for messages this week
that reference shipping, launching, completing, deploying, or finishing
something. For each, record: channel, author, and a one-line summary.

Step 4: Combine into a single ship log. Remove duplicates. Group by
project or area (product, growth, ops, hiring).

Step 5: For each area, add a one-line "status" — On Track, At Risk, or
Blocked — based on what shipped vs. what was planned.

Step 6: Add an "Open Items" section listing anything that was expected to
ship this week but didn't, along with the likely reason if you can infer
it.

Step 7: Save as projects/ship-logs/YYYY-MM-DD.md using this format:

# Ship Log — Week of [YYYY-MM-DD]

## Product
**Status:** [On Track / At Risk / Blocked]
- [What shipped, one line per item]

## Growth
**Status:** [On Track / At Risk / Blocked]
- [What shipped]

## Ops
- [What shipped]

## Open Items
| Item | Area | Expected | Likely Reason |
|------|------|----------|---------------|
| ...  | ...  | ...      | ...           |

Step 8: Use the Gmail connector to send the log to
[your-email@gmail.com]. Subject: "Ship Log — Week of [YYYY-MM-DD]". Body:
the full log.

---

3. Inbox zero triage

Schedule: Every weekday at 7:00 AM

Founder inboxes are chaos. Investor intros next to customer complaints next to vendor invoices. This sorts everything before you open Gmail. See the daily planning use case for a broader version that includes calendar and Slack alongside email.

Run every weekday at 7:00 AM.

Step 1: Use the Gmail connector to pull all unread emails received in the
last 24 hours. For each email, record: sender name, sender email, subject
line, and a one-sentence summary of the content.

Step 2: Classify each email into one of these categories:
- Needs Reply Today — requires a personal response within the day
- Investor / Fundraising — anything from investors, VCs, or related to
  fundraising
- Customer — feedback, support requests, or feature asks from users
- FYI Only — informational, no action needed
- Delegate — someone on the team should handle this
- Low Priority — can wait until next week or later

Step 3: For every email classified as "Needs Reply Today" or "Investor /
Fundraising", draft a suggested reply. Match the tone of the original
sender. Keep replies under 100 words unless the topic requires more.

Step 4: Save the triage as
projects/inbox-triage/YYYY-MM-DD.md using this format:

# Inbox Triage — [YYYY-MM-DD]

## Needs Reply Today
| From | Subject | Draft Reply |
|------|---------|-------------|
| ...  | ...     | [draft]     |

## Investor / Fundraising
| From | Subject | Summary | Draft Reply |
|------|---------|---------|-------------|

## Customer Feedback
| From | Subject | Summary | Type (bug/feature/praise) |
|------|---------|---------|--------------------------|

## Delegate
| From | Subject | Suggested Owner | Reason |
|------|---------|-----------------|--------|

## FYI Only / Low Priority
| From | Subject | Summary |
|------|---------|---------|

Step 5: Use the Gmail connector to send the triage to
[your-email@gmail.com]. Subject: "Inbox Triage — [YYYY-MM-DD]". Body: the
full triage.

---

4. Meeting debrief

Schedule: Every weekday at 6:00 PM

Founders sit in meetings all day and forget half of what was decided by the next morning. This captures every decision and action item before you lose it.

Run every weekday at 6:00 PM.

Step 1: Use the Granola connector to pull all meeting notes recorded today.
For each meeting, extract: meeting title, attendees, and the full
transcript or notes.

Step 2: For each meeting, produce a structured debrief:
- Summary (3-5 sentences covering what was discussed)
- Decisions Made (list each decision as a single clear sentence)
- Action Items (who owes what, with a deadline if mentioned)
- Open Questions (anything raised but not resolved)

Step 3: Cross-reference action items with TASKS.md. If an action item
matches an existing task, note it. If it's new, flag it for addition.

Step 4: Save each debrief as
projects/[relevant-project]/meetings/YYYY-MM-DD-[meeting-title-slug].md.

If the meeting doesn't map to an existing project, save it to
projects/general/meetings/.

Step 5: Compile all debriefs into a single daily summary. Format:

# Meeting Debrief — [YYYY-MM-DD]

## [Meeting Title]
**Attendees:** [Names]
**Summary:** [3-5 sentences]

### Decisions
- [Decision]

### Action Items
- [ ] [Owner]: [Task] — [Deadline or "No deadline set"]

### Open Questions
- [Question]

---

[Repeat for each meeting]

Step 6: Use the Gmail connector to send the compiled summary to
[your-email@gmail.com]. Subject: "Meeting Debrief — [YYYY-MM-DD]". Body:
all debriefs in order.

---

5. Monthly investor update draft

Schedule: Last Friday of every month at 3:00 PM

Investor updates are the thing every founder knows they should send but puts off because it takes too long to compile. This does 80% of the work.

Run on the last Friday of every month at 3:00 PM.

Step 1: Pull all weekly MRR dashboards from projects/metrics/weekly/ for
this month. Calculate:
- MRR at start of month vs. end of month
- Net new customers
- Churn rate
- Total revenue collected

Step 2: Pull all ship logs from projects/ship-logs/ for this month.
Compile a list of everything that shipped, grouped by area.

Step 3: Use the Notion connector to pull any hiring-related tasks or
updates from this month. Note: new hires, open roles, and interview
pipeline status.

Step 4: Use the Granola connector to pull meeting notes from any investor
or board-related calls this month. Extract key discussion points or
commitments made.

Step 5: Use the Gmail connector to scan for any notable customer emails
this month — large deals closed, important feedback, or churn reasons.

Step 6: Compile into an investor update draft using this format:

# Investor Update — [Month YYYY]

## TL;DR
[3 sentences: what happened, what's working, what needs help]

## Key Metrics
| Metric | This Month | Last Month | Change |
|--------|-----------|------------|--------|
| MRR    | $...      | $...       | +/-N%  |
| Customers | N      | N          | +/-N   |
| Churn Rate | N%    | N%         | +/-    |
| Revenue | $...     | $...       | +/-N%  |

## What shipped
- [Grouped by area, one line per item]

## What's working
- [2-3 things going well, with evidence]

## What's not working
- [1-2 honest challenges]

## Team
- [New hires, departures, open roles]

## Asks
- [Intros, advice, or resources you need from investors]

Step 7: Save as projects/investor-updates/YYYY-MM.md.

Step 8: Use the Gmail connector to send the draft to
[your-email@gmail.com]. Subject: "DRAFT — Investor Update [Month YYYY]".
Body: the full update. Do not send to investors. This is for review only.

---

6. Competitor pulse

Schedule: Every Monday at 9:00 AM

You can't monitor competitors every day. But you should know when something changes. This scans your connected tools for any mentions and surfaces what matters.

Run every Monday at 9:00 AM.

Step 1: Read the list of competitors from CLAUDE.md. If no competitor list
exists, ask me to add one and stop.

Step 2: For each competitor, use the following connectors to find mentions
from the last 7 days:
- Slack connector: any messages mentioning the competitor name
- Gmail connector: any emails mentioning the competitor name
- Granola connector: any meeting notes mentioning the competitor name

Step 3: For each mention found, record:
- Source (Slack / Gmail / Granola)
- Date
- Who mentioned it
- One-line summary of the context

Step 4: Group findings by competitor. For each competitor with mentions,
write a 2-3 sentence summary of what's happening.

Step 5: If no mentions were found for any competitor, note "No competitor
activity detected this week."

Step 6: Save the report as
projects/competitive/weekly/YYYY-MM-DD.md using this format:

# Competitor Pulse — Week of [YYYY-MM-DD]

## [Competitor Name]
**Mentions this week:** [N]
**Summary:** [2-3 sentences]

| Source | Date | Who | Context |
|--------|------|-----|---------|
| ...    | ...  | ... | ...     |

## [Repeat for each competitor]

## No Activity
[List any competitors with zero mentions]

Step 7: Use the Gmail connector to send the report to
[your-email@gmail.com]. Subject: "Competitor Pulse — Week of
[YYYY-MM-DD]". Body: the full report.

---

7. Content repurposing pipeline

Schedule: Every Tuesday at 9:00 AM

Founder-led content is the highest-leverage marketing channel for early-stage startups. But most founders write one post and move on. This turns every piece into five.

Run every Tuesday at 9:00 AM.

Step 1: Use the Notion connector to check for any long-form content created
or updated in the last 7 days — blog posts, essays, launch announcements,
or changelog entries. Also check the projects/content/ folder for any new
documents added in the last 7 days.

Step 2: If no new content is found, save a log entry to
projects/content/repurposed/YYYY-MM-DD-log.md noting "No new content to
repurpose this week." Use the Gmail connector to send: Subject "Content
Pipeline — [YYYY-MM-DD] — Nothing to process", Body: "No new content
found this week." Then stop.

Step 3: For each piece of content found, produce the following repurposed
versions. Match the tone and voice of the original exactly — do not add
filler or change the perspective:

**LinkedIn post — Hook-driven**
Open with a counterintuitive claim or surprising finding from the content.
3-5 short paragraphs. End with one question or call to action. Max 1,200
characters.

**LinkedIn post — Lesson-learned**
Open with a specific mistake or unexpected result. Walk through what
happened and what you learned. End with the takeaway. Max 1,200
characters.

**X thread (5 posts)**
Post 1: The core insight in one punchy sentence. Posts 2-4: Supporting
points, one per post. Post 5: A call to action or question. Each under 280
characters. No hashtags.

**Email to customers / waitlist**
150-250 words. Conversational. Open with the core idea. One section of
what it means for them. Close with one call to action.

**HackerNews-style comment**
A self-contained insight from the content that would work as a standalone
comment on a relevant HN thread. 100-200 words. Factual tone, no
self-promotion.

Step 4: Save all versions as separate files inside
projects/content/repurposed/YYYY-MM-DD-[source-title]/:
- linkedin-hook.md
- linkedin-lesson.md
- x-thread.md
- email-update.md
- hn-comment.md

Step 5: Use the Gmail connector to send all repurposed versions to
[your-email@gmail.com]. Subject: "Content Repurposed — [Source Title] —
[YYYY-MM-DD]". Body: all five versions in order, each with a clear label
as a heading.

---

Where to start

Don't set up all seven at once. Pick the one that fixes your biggest pain this week.

If you don't know your MRR without opening Stripe: weekly MRR dashboard.

If you dread writing investor updates: monthly investor update draft.

If your inbox controls your morning: inbox zero triage.

Set one up. Run it for a week. Add the next one when the first feels automatic.

Need the full Cowork setup first? Start with the setup guide.