Week 1: Fundamentals

Building capacity through people, operations, and technology

What we will cover

  • Three paths to expanding your capacity
  • How to classify your work
  • Matching rhythm to your startup stage
  • Understanding your technical starting point

Three ways to expand capacity

As a solo founder, you face a constant capacity problem. Three approaches exist:

Intentional work design

  • Decide what work should exist
  • Control how work moves through your day
  • Choose when specific work happens
  • Stop running reactively

Skill development

Founder soft skills:

  • Communication with customers
  • Delegation to contractors
  • Protecting your time

Technical skills:

  • Using AI tools
  • Setting up automation

Stage-appropriate operating system

Your habits should match your business reality.

Testing product-market fit needs different rhythms than running a validated business.

Understanding work capacity

Your actual ability to complete work at high quality and reliability.

Not how much you cram in. How much excellent work you sustainably produce.

Output type determines approach

Predictable outputs:

  • Build a checklist or automation
  • Steps are consistent

Variable outputs:

  • Use AI for judgment calls
  • Edge cases need different handling

Four categories of work

Before automating or hiring, understand what you do.

Chores

Mindless, repetitive busywork.

  • Checking email arrivals
  • Copying data between systems
  • Coordinating meeting times

Prime automation candidates.

Repeatable tasks

Work following a consistent pattern.

  • Onboarding new customers
  • Generating monthly invoices
  • Creating weekly reports

Document them, then automate or delegate.

Responsive projects

Unpredictable work requiring adaptation.

  • Handling customer crises
  • Responding to unusual requests
  • Troubleshooting novel problems

Need flexible frameworks, not rigid structure.

Strategic work

Research, analysis, thinking, planning.

Where you create the most value as a founder. The work most founders barely have time for.

Pre-product-market fit

Run rapid learning loops:

  • Form a hypothesis
  • Set up minimum test
  • Execute quickly
  • Extract learnings

Stay organized enough to spot patterns. Nothing more.

Post-product-market fit

Shift toward measurement and optimization:

  • Clear metrics guiding decisions
  • Quarterly objectives cascading to weekly actions
  • Documented processes for repeating what works
  • Regular reporting rhythms

Non-technical founders

  • Start by documenting what you do
  • Learn pattern recognition first
  • Plan to delegate technical implementation early
  • Focus on defining requirements clearly

Some technical background

  • Decide if technology is core to your advantage
  • Recognize what can be automated versus custom built
  • Resist building when buying makes sense

The danger: assuming every problem needs a technical solution you create.

Strong technical skills

  • Watch for technical bias
  • Focus on customer traction, not elegant systems
  • Identify automation opportunities but resist over-engineering

The trap: spending three weeks building what you could buy for $50/month.

AI vs automation

These solve different problems. Using the wrong one wastes time.

Use traditional automation

For completely predictable work.

Can you write out a complete decision tree? If yes, skip AI. Use automation instead.

Use AI

For semi-predictable outcomes requiring judgment.

When work involves handling variation intelligently or processing unstructured information.

Accept that results will vary. That is the point.

Why context quality matters

AI output quality depends on input quality.

  • Fresh, specific information produces better results
  • Cleaned, organized context outperforms raw dumps
  • More relevant context beats more total context

The core takeaway

Resist jumping straight to AI and automation before understanding your work.

Classification and intentional design come first. Understand what you do. Then choose tools to match.

Workshop

What you will create:

  • Completed log of how you spent the past week
  • Each task classified as chore, repeatable, responsive, or strategic
  • Identified friction points where you waste time
  • Three improvement opportunities

Questions?

Next week: Tech Stack - Choosing tools that match your bootstrap reality