Autonoma logoAutonoma
AutonomaHosted delivery

Autopilot
Operations OS

A complete operating system for solo service-business owners and small agencies who want work to move without living in the founder’s head.

The operating rule

Do not automate confusion. First make the work visible. Then make it repeatable. Then delegate or automate the stable parts.

01 / Foundation

Start here

Run the business without holding every recurring task in your head. This workspace gives you one place to see what repeats, decide what matters this week, document the right way to do the work, and hand off the right decisions over time.

Use this in order

  1. 1. Set your weekly rhythm. Start with the Weekly Operating Rhythm and protect one planning block each week.
  2. 2. Map recurring work. Add every task that returns: delivery, sales, client communication, finance, and admin.
  3. 3. Choose the bottleneck. Pick one recurring task that creates the most drag or requires too much owner attention.
  4. 4. Write the SOP. Document the current best way to complete that task.
  5. 5. Set decision rights. Decide what stays with you, what can be recommended, and what can be owned by someone else.
  6. 6. Check automation readiness. Automate only after the work is stable, clear, and measurable.

Your first 45 minutes

first-45

The example business: The sample rows use Northline Studio, a fictional two-person brand and web studio. They are examples only. Replace them with your own work, clients, roles, and tools.

Keep the system light: This is not a system for tracking every thought. Add only work that repeats, affects delivery, creates risk, or consumes owner attention. Review it weekly; improve one process at a time.

02 / Control panel

Autopilot dashboard

Example — Northline Studio: Protect delivery quality while moving proposal follow-up out of the founder’s inbox.

Write one sentence here. It should describe the operating improvement that matters most this week.

Current focus: Write this week’s operating focus

1. Weekly commitments

Create a linked view of Weekly Operating Rhythm filtered to Week of = this week.

Show: Focus, top three outcomes, owner, Friday review status.

2. Work that needs attention

Create a linked view of Recurring Work Map filtered to Status = Needs attention or Owner attention = High.

Show: Work item, cadence, owner, next review, and handoff path.

3. SOPs to tighten

Create a linked view of SOP Library filtered to Status = Draft or Status = Needs review.

Show: SOP, process owner, last tested, and next action.

4. Decisions waiting to move

Create a linked view of Delegation & Decision Rights filtered to Decision level = Recommend or Decision level = Decide within guardrails.

Show: Decision, current owner, desired owner, guardrail, and review date.

Daily owner check — 10 minutes

daily-check

Weekly scorecard

Use plain language. The point is signal, not reporting theater.

SignalThis weekNotes
Delivery on trackYes / No
Work completed without owner interventionCount
SOPs tested or improvedCount
Decisions delegated or clarifiedCount
Repeating work removed or automatedCount

When the dashboard feels crowded: Remove anything that does not help you make a better decision this week. The dashboard is a control panel, not an archive.

03 / Cadence

Weekly operating rhythm

Use this page to make the week intentional before reactive work fills it.

Recommended cadence

MomentTimePurpose
Monday reset30 minutesSet the operating focus and choose the three outcomes that protect it.
Daily control check10 minutesClear blockers, move decisions, and protect delivery.
Midweek handoff check20 minutesConfirm delegated work has context, a deadline, and a decision owner.
Friday review30 minutesClose loops, capture lessons, and improve one recurring process.

Monday reset prompt

monday-reset

Friday review prompt

friday-review

Weekly Operating Rhythm data

Suggested property types: Week of → Date; Status → Select; Owner → Person or Select; Friday review complete → Checkbox; Top outcome 1, Top outcome 2, Top outcome 3 → Text.

Views: Create three views: Current week — filter to this week. Review queue — filter to Friday review incomplete. History — sort by Week of, newest first.

Week ofOperating focusTop outcome 1Top outcome 2Top outcome 3OwnerStatusFriday review completeNotes
2026-09-07Protect delivery and reduce founder inbox dependencyConfirm every active project milestoneMove proposal follow-up to coordinator checklistDocument client kickoff stepsFounderPlannedNoExample Northline Studio week
2026-09-14Test the new kickoff SOP without adding toolsRun kickoff SOP for one new projectReview handoff questionsClarify scope-change escalationFounderPlannedNoKeep the system light

04 / Visibility

Recurring work map

Make recurring work visible before you try to improve it.

What belongs here

Add work that repeats on a schedule, follows a trigger, or returns often enough to create friction. Examples: onboarding, invoice follow-up, client updates, proposal follow-up, publishing, bookkeeping, and quality checks.

Do not add one-off projects unless they are becoming a repeatable service.

Choose a handoff path

  • Keep — owner work that requires judgment or relationship context.
  • Delegate — work another person can perform with an SOP and clear guardrails.
  • Automate later — stable, repetitive work with clean inputs and a clear outcome.
  • Stop — work that no longer serves delivery, sales, or risk control.

Triage each work item

QuestionWhat it reveals
What triggers this work?Whether the start point is clear.
What good looks like?Whether quality can be checked.
Who owns the next step?Whether work can move without the founder.
What breaks most often?Where the SOP needs detail.
What could safely change?Whether to simplify, delegate, or automate.
Recurring Work Map data

Suggested property types: Cadence, Area, Handoff path, Status, Owner attention → Select; Current owner, Next owner → Person or Select; Next review → Date; SOP exists, Stable process → Checkbox.

Views: Create views for Owner attention high, Ready to delegate, Ready to automate, and Stop / simplify.

Work itemAreaCadenceTriggerCurrent ownerNext ownerOwner attentionHandoff pathSOP existsStable processStatusNext reviewNotes
Client project status updateDeliveryWeeklyThursday delivery reviewFounderProject leadHighDelegateNoNoNeeds attention2026-09-11Use a consistent update format before handoff
Proposal follow-upSalesWeeklyMonday planning blockFounderCoordinatorHighDelegateNoYesNeeds attention2026-09-11Coordinator can own tracking and follow-up within guardrails
New client kickoffDeliveryPer projectSigned agreement and start dateFounderProject leadMediumDelegateYesNoImprove SOP2026-09-18Test with one project before expanding
Invoice reminderFinanceWeeklyInvoice reaches reminder dateFounderCoordinatorLowAutomate laterYesYesReady to automate2026-09-18Human owner handles exceptions
Friday operating reviewOperationsWeeklyFriday review blockFounderFounderMediumKeepYesYesActive2026-09-11Keep founder-led while business is small
Monthly portfolio cleanupMarketingMonthlyFirst business dayFounderFounderLowStopNoNoStop / simplify2026-09-30Only resume when it supports active sales work

05 / Repeatability

SOP builder

An SOP is the current best way to complete recurring work. It is not a manual for every edge case.

SOP page template

Duplicate this block for each documented process.

[Process name]

Purpose

What business outcome does this process protect?

Trigger

What starts the process, and when?

Owner

Who is accountable for a completed outcome?

Time standard

How long should this normally take?

Definition of done

What must be true before the process is complete?

Inputs

What information, files, access, or decisions are needed before starting?

Steps

1. 2. 3. 4.

Quality check

What should be checked before handoff or completion?

Escalate when

What situations require owner review or a different decision maker?

Improve next

What was unclear, slow, risky, or repeated during the last run?

Build SOPs in the right order

sop-order

A strong SOP tells the person running it how to produce a completed outcome, when to escalate, and what to improve next. It does not pretend every edge case can be anticipated.
SOP Library data

Suggested property types: Status, Area, Risk level → Select; Process owner, Backup owner → Person or Select; Last tested, Next review → Date; Delegable, Automation candidate → Checkbox.

Views: Create views for Draft, Needs review, and High risk.

SOPAreaPurposeProcess ownerBackup ownerStatusRisk levelLast testedNext reviewDelegableAutomation candidateNotes
New client kickoffDeliveryStart projects with complete context and clear next stepsFounderProject leadDraftMedium2026-09-042026-09-18YesNoAdd the final client preparation request
Proposal follow-upSalesEnsure every open proposal has a clear next stepFounderCoordinatorNeeds reviewLow2026-09-012026-09-15YesYesClarify follow-up limit before closing
Invoice reminderFinanceFollow up on overdue invoices without delaying exceptionsFounderCoordinatorActiveMedium2026-08-282026-09-25YesYesFounder handles payment-plan exceptions
Friday delivery reviewOperationsSurface delivery risk before next weekFounderProject leadActiveHigh2026-09-042026-09-18YesNoKeep decisions and actions visible

06 / Authority

Delegation & decision rights matrix

Delegation fails when responsibility moves without authority. This matrix makes both explicit.

Decision levels

LevelMeaning
InformThe owner decides; others need context.
RecommendThe person researches options and recommends a decision.
Decide within guardrailsThe person decides inside an agreed range or rule.
OwnThe person decides, acts, and reports outcomes.

Write guardrails, not vague permission

Useful guardrails state the limit, trigger, and escalation point.

Weak: “Handle client requests.”

Clear: “Approve scope-neutral client changes. Escalate anything that adds delivery time, changes the agreed outcome, or affects the deadline.”

Delegation conversation

delegation-conversation

Delegation & Decision Rights data

Suggested property types: Area, Decision level, Risk, Status → Select; Current decision owner, Desired decision owner → Person or Select; Review date → Date.

Views: Create views for Founder-held, Ready to move, and Needs guardrails.

DecisionAreaCurrent decision ownerDesired decision ownerDecision levelGuardrailRiskStatusReview dateNotes
Schedule client kickoffDeliveryFounderProject leadDecide within guardrailsSchedule within agreed project timeline; escalate conflicts or deadline riskMediumReady to move2026-09-18Use the kickoff SOP
Send proposal follow-upSalesFounderCoordinatorOwnUse approved follow-up language; escalate pricing or scope questionsLowActive2026-09-11Coordinator updates next action date
Approve scope-neutral client requestDeliveryFounderProject leadDecide within guardrailsNo added delivery time; escalate new deliverables or deadline changesMediumNeeds guardrails2026-09-18Document examples after each decision
Change project price or termsSalesFounderFounderOwnFounder approval requiredHighActive2026-09-30Keep as owner decision
Choose monthly marketing tasksMarketingFounderCoordinatorRecommendBring two options tied to current sales focusLowReady to move2026-09-25Founder makes final choice for now

07 / Automation

Automation-readiness checklist

Automation should remove stable repetition, not hide an unclear process.

Test before you automate

automation-test

If any answer is no, improve the process first.

A practical readiness scale

ReadinessMeaningNext move
1 — UnclearWork changes each time or relies on hidden judgment.Map the work.
2 — DocumentSteps exist but are not consistently followed.Test the SOP.
3 — StableSame trigger, steps, and output most times.Delegate or use a simple checklist.
4 — ReadyInputs, rules, exceptions, and quality checks are clear.Design an automation.
5 — MonitoredAutomation runs with an owner and review rhythm.Improve exceptions and maintenance.
Automation Readiness data

Suggested property types: Readiness, Area, Priority, Status → Select; Process owner → Person or Select; Next review → Date; Trigger stable, Inputs clean, SOP tested, Exception owner, Quality check → Checkbox.

Views: Create views for Ready to design, Improve first, and Monitor.

Candidate processAreaReadinessTrigger stableInputs cleanSOP testedException ownerQuality checkProcess ownerPriorityStatusNext reviewNotes
Invoice reminderFinance4 - ReadyYesYesYesYesYesCoordinatorMediumReady to design2026-09-18Automate reminders only; retain human exception handling
Proposal follow-up reminderSales3 - StableYesYesNoYesYesCoordinatorHighImprove first2026-09-11Test the SOP and close-out rule first
New client kickoffDelivery2 - DocumentYesNoNoYesNoProject leadHighImprove first2026-09-18Inputs vary by project type
Friday delivery reviewOperations2 - DocumentYesNoYesYesNoFounderMediumImprove first2026-09-18Keep human judgment central

08 / Examples

Example workflows

These examples show the level of clarity to aim for. They use fictional Northline Studio operations and do not require any specific software.

Workflow 1 — New client kickoff

Trigger: A client approves a proposal and confirms the project start date.

Outcome: The client knows the next step, the internal team has context, and the project has a scheduled kickoff.

  1. Confirm the signed agreement and project start date.
  2. Create the project record using the kickoff checklist.
  3. Send a welcome message with the kickoff date and preparation request.
  4. Add the project to the delivery schedule.
  5. Prepare the kickoff agenda and required inputs.
  6. Run the quality check: agreement, contacts, scope, timing, and access are all recorded.

Decision rights: The project lead owns scheduling within the agreed timeline. Scope changes or timing risks go to the founder for review.

Automation readiness: Level 3. The checklist and client message can be standardized; scope review remains human.

Workflow 2 — Weekly proposal follow-up

Trigger: Monday planning block.

Outcome: Every open proposal has a clear next step or is closed out.

  1. Review open proposals from oldest to newest.
  2. Confirm the decision maker, decision date, and last meaningful contact.
  3. Send a concise follow-up where a response is due.
  4. Mark the next action and date.
  5. Close stalled opportunities after the agreed follow-up limit.

Decision rights: A coordinator may send follow-ups and update records. Pricing changes, custom terms, and new scope require founder approval.

Automation readiness: Level 4 if proposal stages and follow-up timing are reliably maintained.

Workflow 3 — Friday delivery review

Trigger: Friday review block.

Outcome: Next week begins with risks, client expectations, and ownership visible.

  1. Review active work against promised milestones.
  2. Flag any risk to scope, quality, timing, or capacity.
  3. Confirm the next client-facing update for each active project.
  4. Capture one process lesson in the SOP library or work map.
  5. Choose one operating improvement for next week.

Decision rights: Project leads own status reporting. The founder decides on deadline changes, resource tradeoffs, or major client escalation.

Automation readiness: Level 2. Keep this human until project data and quality signals are consistently recorded.

Operating principle

Make the next week easier than the last.

Back to start