Your First Wins

The Confidence Gap

There is a gap between knowing Co-Work can automate your work and actually having it do something for you — something real, something that runs without you asking, something that makes your morning a little better. This module is built to close that gap as fast as possible.

The three quick wins chosen for this module are not arbitrary. They are specifically selected for fast setup, low risk, and an immediately visible result. And each one seeds a skill you will codify properly in Module 6. Think of this module as the proof-of-concept run for your full automation system.

Quick Win 1: File Organization

This is the fastest confidence builder in the entire course. Start with this prompt:

"My downloads are a mess. I'd like you to organize them for me, please. Show me a preview of what you plan to do before you do it."

The last sentence is not optional. Co-Work will show you a categorized list — documents, images, videos, installers, archives — and propose a folder structure before touching anything. Review the proposal. Adjust it if needed. Then approve.

After you see the result, add the scheduling step:

"Create a scheduled task: every day at 10 PM, go through all my downloads and organize by type. Always show me a preview first."

Quick Win 2: The Morning Briefing

The morning briefing is the most cited first automation across all seven community sources for this course. Five of seven sources recommend it specifically as the first real Co-Work win. It is not a coincidence — it is the fastest way to feel what Co-Work actually is.

The basic version requires Gmail and Google Calendar connected (done in Module 4). Start simple:

"Create a morning brief: tell me all my appointments today, summarize my most important emails from the last 24 hours, and tell me the three most important things I need to focus on."

Run it. Read the output. Now refine it. Add the elements that would actually make your morning better:

• Current weather at your location (add a weather connector or Chrome for weather sites)
• Any unresolved tasks from yesterday's to-do list (if you use Notion or a similar tool)
• News in your industry (via RSS connector or Chrome)
• Anything from specific people — a key client, your manager, a pending deal

Paul's advanced version uses a different first prompt: "Build my morning report." Co-Work will interview you about what you want in the report — asking about your priorities, your data sources, your preferred format. Let it ask. The interview produces a better brief than most people would write by hand.

Once the briefing output looks right — truly useful, not just okay — schedule it:

"Set up this morning brief on a schedule every weekday at 6:30 AM."

Quick Win 3: Your First Scheduled Task Running

Scheduling the morning brief (or the file organizer) creates your first scheduled task. Understanding the scheduling interface now — before you build anything more complex — prevents confusion later.

Navigate to Settings → Scheduled Tasks → New Task. The interface has five fields:

• Name — short, descriptive, verb-led (e.g., "Daily Morning Brief")
• Prompt — the full task instruction, written exactly as you would type it in chat
• Schedule — dropdown with options: manual, hourly, daily, weekdays, weekly. Select daily or weekdays for the morning brief.
• Model — Sonnet for routine tasks; Haiku for very simple ones; Opus for complex analysis that needs deep reasoning. Morning brief: Sonnet. Community guidance: Paul and Jack Roberts both use Sonnet for most scheduled tasks.
• Output folder — where Co-Work saves the output. Point it to ~/CoWork/Output/ to keep everything organized.

The Pattern You Just Lived

Stop and notice what happened in this module. You ran two tasks manually. You refined them until the output was genuinely useful. Then you scheduled them to run automatically. That sequence is not incidental — it is the core pattern of everything this course teaches.

Module 6 adds a critical step that Paul acknowledges is missing from this module's version of the pipeline: create a skill before scheduling. A skill is the quality-controlled, codified version of a workflow — and it belongs between "refine" and "schedule." Building a skill is the difference between scheduling a prompt and scheduling a process. That is where we are going next.

Preventing Automation Anxiety

Two tasks running automatically — things you did not manually trigger — can feel unsettling the first time. That feeling is appropriate. Here is how to stay in control:

• Both quick wins in this module run with "preview before acting" instructions. Co-Work shows its plan before executing any write operation.
• You can pause or cancel any scheduled task at any time: Settings → Scheduled Tasks → select the task → Pause or Delete.
• Review task history regularly early on: Settings → Scheduled Tasks → History. Check that tasks ran when expected and produced the output you intended.

Co-Work will not take irreversible actions without your guardrails triggering a review — if you set them up correctly in Module 2. If you skipped Module 2's guardrail setup, go back and do it now before you run any more write-permission tasks.