Claude Code Projects can help you prepare a feature launch, follow competitors, produce a newsletter, make sense of user feedback, or plan a webinar. Here are five ideas for founders, writers, and product leads looking for a first project.
Each example has several connected tasks and a result you can use. Some suit recurring work; others help you carry a project through to a deadline.
Why these five examples?
The redesigned Projects gives you one conversation that coordinates separate task threads. You describe the work, and Claude starts threads and follows their progress. How Projects works
That makes it worth trying when you would otherwise manage several conversations yourself. Each example below includes work that can happen separately, followed by decisions or documents that need to come together.
| If you want to… | Try this project | What you could get |
|---|---|---|
| Get a feature ready for users | Feature launch | Updated docs and announcement drafts grounded in the implementation |
| Keep up with competing products | Competitor tracking | A sourced report of relevant changes |
| Publish regularly from your own material | Weekly newsletter | An issue built from your notes, sources, and chosen angle |
| Decide what user problems to investigate | Feedback analysis | Themes linked to the original feedback |
| Prepare several materials for one event | Webinar preparation | An agenda, speaker notes, and email drafts that agree |
These are ideas to adapt to your own work. The document-based examples need no repository. Availability is still rolling out on Pro and Max; look for Projects at claude.ai/code or in the desktop app’s Code tab. Access and setup
1. Get a feature ready to launch
A feature launch suits founders and product leads who handle both the product and its communication. Finishing the code still leaves the help page, release note, announcement, and questions about what is actually ready.
Imagine your app is adding CSV export. Give the project the feature brief, implementation, current guide, and a past announcement. The cloud repository version of this example needs the required GitHub access. Repository setup
You could ask one thread to check the implementation against the brief and another to find gaps in the guide. Their findings give the coordinator a basis for organizing the documentation and announcement work.
Suppose export leaves out private fields. That detail belongs in both the guide and the announcement. Ask the coordinator to compare the drafts, flag conflicting claims, and bring the remaining questions back to you.
The useful result is a launch package: a report of open issues, revised instructions, and announcement drafts. If the feature changes before launch, you can return to the same project and ask which materials need updating.
An opening request:
Help me prepare the CSV export launch. Check the implementation and current guide in separate threads, bring the findings together, and identify what we need to resolve before drafting the launch materials.
2. Follow changes across competing products
Competitor tracking suits people who keep revisiting the same products. Perhaps you want to know which tools added a feature, changed their plans, or started serving a different audience.
Give the project your product list, official source links, and the questions you care about. Include a previous report if you have one. A founder planning a roadmap and a buyer choosing software will want different conclusions.
You could assign a thread to each product. Ask the coordinator to bring the findings into one report, with source links and a clear distinction between a new announcement and an older feature you have only just discovered.
This is where separate threads need a shared brief. Otherwise, one might return a feature list while another focuses on pricing, leaving you to do the comparison yourself.
The result could be a weekly update showing what changed, why it matters to your questions, and what remains uncertain. Keep the approved report as a baseline for the next review.
An opening request:
Review these competitors separately, then combine the findings into one update. Compare with our last report, link the official sources, and distinguish confirmed changes from your interpretation of what they mean for us.
3. Turn a week’s notes into a newsletter
A newsletter project suits writers who already collect ideas but struggle to turn them into a regular issue. It gives the ongoing editorial work a home: choosing an angle, checking sources, and deciding what deserves another mention.
Bring your notes, saved links, recent issues, and a short description of your readers. Include the view you want to express. Your material gives Claude something specific to work with.
After you choose an angle, one thread could check its external claims while another compares it with past issues. The coordinator can bring both findings into the outline and subsequent draft.
For example, an old issue may have introduced a tool that has since changed. The archive check can help you build on what readers already know, while the source check establishes what is new.
The result could be one issue with a clear point, supported claims, and questions where your input is still missing. Read it for whether it says what you mean; our AI writing guide covers that part.
An opening request:
Help me choose an angle from this week’s notes. Once I choose, check the sources and compare it with past issues in separate threads, then bring the findings into an outline for the next newsletter.
4. Find patterns in user feedback
Feedback analysis suits product leads facing scattered tickets, interview notes, and feature requests. It can help answer a concrete question, such as why new users get stuck during setup.
Bring the relevant records, their source IDs, and some product context. Agree on a small set of categories before splitting the material into batches, so separate threads use the same definitions.
Ask the coordinator to combine their findings while keeping the links to original records. That lets you follow a broad claim such as “setup is confusing” back to the particular steps people struggled with.
For example, several requests for a tutorial may point to the same unclear permission screen. A useful report would show that connection and propose what to investigate, with the evidence attached.
The result could be a brief of recurring problems, contradictory feedback, and follow-up questions. When another batch arrives after a product change, ask whether the same problems still appear.
An opening request:
Help me understand where users get stuck during setup. Agree on categories, analyze separate batches of feedback, and combine the results into themes with source IDs and proposed follow-up questions.
5. Prepare a webinar and its supporting materials
A webinar project suits educators, founders, and community organizers preparing several pieces of content for the same event. The agenda, speaker notes, invitation, and follow-up all need to support the same promise to attendees.
Bring the audience, topic, available time, confirmed event details, and teaching material. Once you settle the agenda, separate threads could develop the speaker notes and draft the event emails.
The coordinator then has a concrete editorial job: compare the materials. Does the invitation promise a live demo that has no place in the agenda? Do the speaker notes leave enough time for questions?
If you shorten the event or change its focus, ask which documents the decision affects. Keeping that revision in one project can reduce the work of explaining the change to each separate conversation.
The result could be an event package ready for your review. After the webinar, add what actually happened before asking for the final follow-up message.
An opening request:
Help me prepare this webinar. Once we agree on the agenda, develop the speaker notes and email drafts in separate threads, then check that the materials agree on the content and event details.
Which one should you try first?
Choose work you already do and have materials for. If feedback is piling up, start there. If an event is coming, use its brief. You will have a clearer basis for judging whether the project helps.
Start with a small assignment. Multiple threads draw on the same plan allowance, so review the first result before expanding the work. Usage and cost
For the writing examples, our app, StashBase, gives you a place to keep sources and drafts, work with Claude or Codex, and review changes in the prose. Writing in StashBase
You can bring a draft back from Projects for revision. Keep the source material and the version you approve together, so the next issue, launch, or event has useful work to build on.