Overview

A first-week setup for solo operators: Inbox, This Week, Projects, Clients or Pipeline, Money/Admin, Reusable Assets, SOPs, and only then automation or agents.

When to use this

You have too many scattered notes, client threads, assets, automations, and AI workflows, and need a system that protects judgment instead of adding bureaucracy.

Set Up One Home Base This Week

A one-person company needs fewer places to look. Create one primary workspace with seven visible areas: Inbox, This Week, Projects, Clients or Pipeline, Money/Admin, Reusable Assets, and SOPs. Keep the names plain so the system still makes sense on a tired Friday.

  • Inbox: unsorted tasks, requests, ideas, and links.
  • This Week: one to three outcomes plus the next actions that move them.
  • Projects, Clients or Pipeline, Money/Admin, Reusable Assets, and SOPs: the places work goes after capture.

Run The First Week Without Automation

Do the first pass manually so you can see the actual pattern. Capture tasks, pick weekly outcomes, follow up with clients or customers, ship work, file receipts, and reuse assets before building any automation around a fantasy version of the business.

  • Daily: empty quick captures into Inbox and move only urgent items.
  • Weekly: choose This Week outcomes and confirm client or customer follow-ups.
  • Friday: file Money/Admin items and save anything reusable.

Write The Checklist Before You Automate It

Repeated work should become a written SOP first. If the steps are stable and rules-based, automate them. If the work needs language understanding, synthesis, or tool use with judgment, use an agent with approval and observability.

  • Manual judgment stays with the operator.
  • Deterministic and low-risk tasks move to automation.
  • Agentic workflows get rules, approvals, traces, and review.

Keep Approval For Risky Actions

Agents and automations come later because they can affect customers, money, reputation, and production systems. Keep explicit approval before sending invoices, emailing customers, publishing, deploying, deleting files, changing credentials, or moving money.

  • Automate reminders and routing before customer-facing actions.
  • Require review for invoices, emails, contracts, publishes, deploys, deletes, and money movement.
  • Delete unused fields, dashboards, and automations in a monthly cleanup.

Method

  1. Create seven top-level areas in one workspace: Inbox, This Week, Projects, Clients or Pipeline, Money/Admin, Reusable Assets, and SOPs.
  2. For the first week, capture every loose task, client promise, invoice reminder, idea, and asset into Inbox instead of sorting while busy.
  3. Each Monday, move only one to three outcomes into This Week and attach them to Projects or Clients or Pipeline.
  4. Use Money/Admin for invoices, taxes, renewals, receipts, subscriptions, legal dates, and other obligations that should not live in memory.
  5. Save good proposals, snippets, decks, prompts, checklists, and examples into Reusable Assets when they can speed up the next similar job.
  6. Write an SOP for repeated work before turning it into a template, automation, or agent workflow.
  7. Add agents and automation later, only after the manual checklist is stable and approval rules are clear.

Before you start

What to gather this week

  • Current tool stackList where tasks, clients, money, files, notes, and automations live today.
  • Recurring work listWrite the repeated admin, delivery, sales, and publishing tasks that need a home.
  • Client or customer pipelineBring active leads, promises, follow-ups, proposals, and delivery dates into view.
  • Reusable assetsCollect proposals, snippets, decks, checklists, prompts, and examples worth reusing.
  • Weekly calendarUse real availability to choose a small number of outcomes instead of aspirational planning.

Helpful workspace areas

  • InboxCapture loose tasks and ideas quickly without sorting everything while busy.
  • This WeekKeep only the outcomes and next actions that matter before the next review.
  • Money/Admin checklistTrack invoices, taxes, renewals, receipts, subscriptions, and legal dates outside memory.
  • SOP folderWrite the manual checklist before you turn a process into automation or agent work.

Decision points

Should this be documented, automated, or delegated to an agent?
Document when the flow is repeated but still changing. Automate when the rules are stable and low-risk. Use an agent when the task needs language understanding, synthesis, or code, and keep approvals for consequential steps.
Which workspace should be the center?
Use the tool that can hold projects, SOPs, pipeline, asset library, and reviews with the least maintenance. Do not choose a heavier system until a simple one fails in real work.
How many goals should a one-person company track?
Use one to three quarterly objectives and one to three measurable results per objective. More goals usually create reporting work instead of operating clarity.

Common mistakes

  • Starting with tool shopping instead of the weekly operating loop.
  • Automating a messy process before writing the SOP.
  • Letting agents send, publish, bill, deploy, or delete without explicit approval.
  • Copying enterprise OKR, CRM, and PM rituals into a solo business.

Troubleshooting

The workspace feels complete but nothing ships faster.
Remove dashboards and fields until the weekly outcomes, next actions, and reusable assets are visible on one screen.
Automations keep breaking or needing attention.
Move unstable flows back to an SOP, prefer API-triggered automations, and avoid UI automation until the process is stable.
Agents produce impressive drafts but create follow-up cleanup work.
Add tighter instructions, examples, review gates, and a definition of done before expanding the agent's role.

Sources

This playbook is authored from multiple references. Open the originals to inspect details, examples, and current guidance before adapting it.

Notes

Business-operations guidance only. Agent and automation workflows can affect customers, data, finances, and production systems; keep approval gates for consequential actions.

Comments

0 comments
No comments yet.