Your First Real Project

Theory’s over. Let’s do something real.

🔄 Quick Recall: In the last lesson, you learned to read, create, edit, and organize files. You learned the safety checklist: right folder, backups, “don’t delete,” read before edit. Now we’ll put all of that together.

This lesson gives you three complete project walkthroughs — pick the one closest to your actual work. Each one takes 15-20 minutes to complete in Cowork.

Project A: Turn Messy Notes Into a Professional Report

Best for: Managers, consultants, analysts, anyone who turns raw information into polished documents.

The scenario: You have a folder with scattered meeting notes, a few data files, and loose thoughts. You need a clean, shareable report by end of day.

Step 1: Set the stage

Create a folder with your source material — or use existing notes you already have. Then open Cowork and give it context:

I'm a [your role] at [type of company].
I need to create a monthly progress report for my team lead.

In this folder, you'll find:
- Meeting notes from the past 2 weeks (various .md and .txt files)
- A CSV with project task statuses
- Some loose notes I took during a client call

Please do the following:

1. Read everything in the folder
2. Create a file called "march-progress-report.md" with:
   - Executive summary (3-4 sentences)
   - Key accomplishments this month
   - Issues and blockers (with proposed solutions)
   - Metrics from the CSV (tasks completed, in progress, blocked)
   - Next steps for April

Format it professionally — my team lead will skim the summary
and read details only if something catches their eye.

Show me your plan before you start writing.

Step 2: Review and refine

Cowork will show you its plan. Check that it found all the files. Check that the structure matches what you need. Approve, and let it run.

When you get the first draft, don’t accept it as-is. Give feedback:

Good start. A few changes:
- The executive summary is too long — trim to 3 sentences max
- Move the metrics table to the top, right after the summary
- Under blockers, add the vendor delay that's in the client call notes
- Tone down the language in the issues section — less alarming, more "here's what we're handling"

This refinement loop is where Cowork shines. It keeps the full context, so each iteration gets closer to exactly what you need.

✅ Quick Check: Why is “show me your plan before you start writing” a useful addition to your prompt?

Project B: Clean and Analyze a Spreadsheet

Best for: Data analysts, finance teams, operations, marketing — anyone who works with messy data.

The scenario: You’ve got a CSV export from your CRM/tool that’s messy — duplicate rows, inconsistent formatting, missing fields. You need clean data and some insights.

I'm a marketing analyst. I have a CSV export from our email campaign tool.

Please do the following:

1. Read "campaign-data-march.csv" and tell me:
   - How many rows and columns
   - Any obvious data quality issues (duplicates, missing values, inconsistent formats)

2. Create a cleaned version called "campaign-data-march-clean.csv":
   - Remove exact duplicate rows
   - Standardize date format to YYYY-MM-DD
   - Fill missing "campaign_name" values with "Unknown"
   - Remove rows where both open_rate and click_rate are 0 (dead records)

3. Create an analysis file called "campaign-insights.md" with:
   - Top 5 campaigns by open rate
   - Top 5 campaigns by click rate
   - Average open rate vs industry benchmark (assume 21.5% for SaaS)
   - Any campaigns that are significant outliers (above or below)
   - Recommendations for next month (based on what performed well)

Start with step 1 so I can verify before you modify anything.

The refinement loop: After reviewing the initial analysis, you might say:

The cleaned data looks good. But for the insights:
- Break out results by campaign type (newsletter vs promotional vs transactional)
- Add a "per-weekday" analysis — are campaigns sent on certain days doing better?
- Include the raw numbers alongside percentages

Project C: Create a Content Calendar

Best for: Content marketers, social media managers, founders doing their own marketing.

I'm a content marketer for a B2B SaaS company.

I need a content calendar for April 2026. Please:

1. Create a file called "content-calendar-april.md" with:
   - 4 blog post ideas (with title, target keyword, brief outline)
   - 12 social media posts (3 per week, mix of LinkedIn and Twitter/X)
   - 2 email newsletter topics
   - 1 case study outline

2. For each blog post, include:
   - Working title
   - Primary keyword to target
   - 5-point outline
   - Estimated word count
   - Target audience segment

3. For social media posts, include:
   - Platform (LinkedIn or X)
   - Post text (ready to copy-paste)
   - Best posting day/time
   - Hashtags (3-5 per post)

Format everything as a clean markdown document I can share with my team.
Our product is [describe your product].
Our audience is [describe your audience].

This project shows Cowork at its creative best — it doesn’t just generate ideas, it structures them into an actionable plan you can hand off or start executing immediately.

The Pattern Behind Every Project

Notice what all three projects have in common:

Context — who you are, what you’re working on, who the output is for
Specific deliverables — named files, clear sections, defined output
Format guidance — how it should look, what tone to use
Checkpoints — “show me step 1 first” or “show me your plan”
Refinement — follow-up with specific feedback to dial it in

This pattern works for almost any Cowork task. Memorize it. Use it. Every time.

Try It Right Now

Pick the project closest to your work. Swap in your real data. Run it. If none of these fit perfectly, adapt the structure:

I'm a [role] at a [company type].
I need to [deliverable] for [audience].

Here's what I have: [describe your source files]

Please:
1. [First step — usually reading/analyzing]
2. [Second step — usually creating/organizing]
3. [Third step — usually formatting/polishing]

Show me your plan before starting.

That template handles 80% of Cowork use cases.

Key Takeaways

Context (role + audience) changes everything about Cowork’s output
Ask Cowork to show its plan before executing
Use refinement prompts — specific feedback within the same session
The universal pattern: Context + Deliverables + Format + Checkpoint + Refine
Real projects produce better learning than hypotheticals — use your actual files

Up Next

You’ve completed a full project. Next, we’re adding superpowers: connectors. Google Drive, Slack, GitHub, and 35+ other tools — all accessible from inside Cowork.