The Solo Operator Starter Kit

Last verified: 14 April 2026 | Applies to: Pro, Max (Free for basics)

In 30 seconds

You run a business by yourself or with a tiny team. This is your setup checklist: the five workflows to configure in your first week, the plan you actually need, and the order to set things up so each piece builds on the last.

Who this is for

• Freelancers billing clients, managing projects, and handling admin solo
• Solo founders running a product or service business with no employees (or maybe one)
• Micro-teams of 1-3 where everyone wears multiple hats and nobody has time for setup that takes all day

If you manage a team of 10 or more, see Team Rollout instead. This guide is for people whose biggest constraint is time, not headcount.

The recommended plan

Pro ($20/month) is the right starting point for most solo operators.

It gives you access to Cowork, plugins, connectors, scheduled tasks, and 1M context with Opus 4.6 and Sonnet 4.6. That covers everything in this guide.

When to step up to Max ($100/month):

• You hit usage limits regularly (Pro has daily message caps; Max gives 5x or 20x the volume depending on the tier)
• You need Dispatch (send tasks from your phone to Cowork)
• You process very large documents or codebases that need sustained context

Free plan works for exploring. You get Chat, skills, connectors (directory), and Memory. But you cannot use Cowork, scheduled tasks, or plugins. If you want to test whether Claude fits your workflow before paying, Free is fine for a week or two.

Setup order

graph LR
    A[1. Memory] --> B[2. Connectors]
    B --> C[3. A Project]
    C --> D[4. Scheduled tasks]
    D --> E[5. Dispatch]

Each step builds on the previous one. Memory teaches Claude who you are. Connectors give it access to your tools. A Project gives it context for your main focus area. Scheduled tasks automate the recurring work. Dispatch lets you trigger tasks from anywhere.

Do not skip ahead. Setting up scheduled tasks before Memory means Claude does not know your preferences, and your automated outputs will need constant correction.

Step 1: Memory (15 minutes)

Open Claude and start telling it about yourself and your business. Memory captures this automatically.

My name is [your name]. I run [company name], a [what you do] based in [location]. My clients are [describe your typical client]. I use Australian English. When writing for my business, the tone should be professional but approachable. My financial year runs [dates]. I track tasks in [tool]. I manage clients in [tool].

Add anything Claude should always know: your industry, your pricing model, your key clients, your working hours. You do not need to do this all at once. Memory accumulates over time. But frontloading the basics saves you from correcting Claude repeatedly in the first week.

Step 2: Connectors (20 minutes)

Connect the tools you use every day. In Claude Desktop, go to Settings → Connectors and enable:

• Gmail (or your email provider) - for inbox triage and email drafting
• Google Calendar - for meeting prep and scheduling awareness
• Google Drive - for accessing your documents and spreadsheets
• Slack - if you use it for client or team communication

You do not need to connect everything. Start with email and calendar. Add more as you identify needs.

Step 3: A Project (10 minutes)

Create one Project in Claude Chat for your primary focus area. For most solo operators, this is either “Client Work” or “Business Operations.”

Go to claude.ai → Projects → New Project. Give it a name, a description, and upload 2-3 key reference documents (your service offerings, your pricing sheet, your standard proposal template).

This gives Claude persistent context for your most common work. When you ask questions or draft documents inside this Project, Claude already knows your business context.

Step 4: Scheduled tasks (20 minutes)

Set up two scheduled tasks in Cowork:

Morning brief (weekdays at 8am):

/schedule every weekday at 8am: Run my morning brief. Check Gmail for anything urgent from my top clients. Check Google Calendar for today's meetings. Summarise what needs my attention today. Save the briefing to my Morning folder. Keep it under 2 minutes of reading.

End-of-week review (Friday at 3pm):

/schedule every Friday at 3pm: Create my weekly review. Summarise what I accomplished this week based on my sent emails and calendar. List any outstanding client tasks. Identify the top 3 priorities for next week. Save to my Weekly Reviews folder.

Test each one manually first before scheduling. See Scheduled Tasks for the full guide.

Step 5: Dispatch (Max plan only, 5 minutes)

If you are on Max, enable Dispatch in Claude Desktop settings. This lets you send tasks from your phone to your desktop Cowork session.

Use it for moments when you think of something between meetings:

Check if Sarah replied to my proposal email and summarise her response.

If you are on Pro, skip this step. You can always upgrade later.

The five essential workflows

These are the workflows that deliver the most value for a solo operator in the first week.

1. Morning brief

What: A daily briefing that checks your email, calendar, and task list, then produces a prioritised summary.

Surface: Cowork with /schedule

Prompt:

Check my Gmail for unread messages since 5pm yesterday. Flag anything from [list your key clients]. Check my Google Calendar for today's meetings. For each meeting, note the attendee and topic. Review my TASKS.md for anything due today or overdue. Produce a briefing with three sections: Urgent, Today's Meetings, and Task Reminders. Save to ~/Morning/[today's date].md.

Why it matters: Instead of opening three apps and spending 20 minutes piecing together your day, the briefing is waiting when you sit down.

2. Inbox triage

What: Categorise incoming emails by urgency and draft replies for the important ones.

Surface: Cowork (daily via schedule or on-demand)

Prompt:

Read my unread Gmail messages. Categorise each as: Urgent (needs response today), Action Needed (needs response this week), FYI (no response needed), or Low Priority. For Urgent and Action Needed emails, draft a reply. Save the triage summary to ~/Morning/inbox-triage-[today's date].md.

Why it matters: Email is the biggest time sink for solo operators. Triage turns reactive inbox checking into a structured 5-minute review.

3. Weekly financial snapshot

What: A quick summary of your financial position for the week.

Surface: Cowork

Prompt:

Read my financial tracker at ~/Documents/finances/2026-tracker.csv. Calculate: total revenue this month to date, total expenses this month to date, outstanding invoices (amount and count), and cash position. Compare revenue to my monthly target of $[amount]. Format as a brief financial snapshot and save to ~/Reports/financial-snapshot-[today's date].md.

Why it matters: Most solo operators check their finances sporadically. A weekly snapshot keeps you aware of your position without logging into multiple banking and invoicing tools.

4. Client communication templates

What: A skill that applies your communication style to all client-facing writing.

Surface: Chat or Cowork (via a custom skill)

Create a skill at ~/Documents/claude-skills/client-comms/SKILL.md:

# Client Communications

## Voice
- Professional but friendly
- First person ("I") not corporate "we"
- Short paragraphs, clear language
- Always include a specific next step or call to action

## Email structure
- Subject: specific and action-oriented
- Opening: get to the point immediately
- Body: one topic per email
- Closing: clear next step with a date

## Rules
- Never use "just checking in" as an opener
- Always reference the specific project or deliverable
- If delivering bad news, lead with it, then provide the plan to resolve
- Match the client's formality level (if they write casually, respond casually)

Then use it: “Using my client-comms skill, draft a follow-up email to [client] about [topic].”

Why it matters: Consistent, professional communication builds trust. A skill ensures your emails maintain quality even when you are rushing between tasks.

5. End-of-week review

What: A structured reflection on the week, plus priorities for the next one.

Surface: Cowork with /schedule

Prompt:

/schedule every Friday at 3pm: Run my weekly review. Check my Gmail sent folder for this week to see what I worked on. Check my Google Calendar for meetings I attended. Review my TASKS.md for completed and outstanding items. Produce a review with: Accomplishments (what I shipped or delivered), Outstanding (what carried over), Lessons (one thing that went well, one to improve), and Next Week Priorities (top 3). Save to ~/Weekly Reviews/week-ending-[Friday's date].md.

Why it matters: Without a regular review, weeks blur together and you lose track of progress. This takes 2 minutes to read and keeps you honest about where your time goes.

What to skip for now

These features are valuable at team scale but add complexity without proportional benefit for a solo operator:

• Admin controls and SSO. You are the only user. Skip.
• Audit logs and compliance exports. Relevant for regulated teams, not solo operators.
• Private plugin marketplace. For Enterprise teams distributing custom plugins internally.
• Multiple Projects. Start with one. Add more only when you genuinely need separate contexts (e.g., two very different clients or a side project).
• Complex skill libraries. Start with one or two skills. Build more as you identify recurring patterns, not upfront.

Cost comparison

What Claude Pro replaces or supplements for a solo operator:

Tool	Typical cost	What Claude covers
Virtual assistant (part-time)	$500-2,000/month	Email triage, scheduling, research, document drafting
Jasper / Copy.ai	$40-80/month	Client communications, content writing, proposals
Notion AI or similar	$10-20/month	Document creation, knowledge management
Financial dashboard SaaS	$20-50/month	Basic financial snapshots and reporting
Meeting prep service	$30-50/month	Meeting briefs, context gathering
Total replaced	$600-2,200/month
Claude Pro	$20/month

Claude does not fully replace all of these tools. You may still want a dedicated accounting system, a proper CRM, or a project management tool. But for a solo operator, Claude handles the “glue work” between these tools: the summarising, drafting, triaging, and reporting that otherwise eats your day.

Related

• First 30 Minutes - getting started from zero
• Choosing a Plan - detailed plan comparison
• Daily Operating System - the full daily workflow framework
• Workplace Memory - making Claude remember your context
• Scheduled Tasks - automating recurring work
• Inbox Triage - the full email triage workflow

---

Something wrong or outdated? Let us know →

Get weekly workflows. Subscribe to the newsletter.