Skip to content
Zero Employee Startup
Menu

Zero-Employee Architect Early access

Design the company before you automate it.

The Architect maps every recurring workflow to the right executor (founder, software, AI agent, specialist or human) and produces a blueprint you execute as reversible experiments.
MetricCurrentTarget
Humans
3
target 1
Founder hours / week
42h
target 23h
Recurring workflows automated
46%
target 79%
AI & software / month
$1.9k
target $3.4k
Recurring human cost / month
$9.5k
target $0.4k
Illustrative scenario · hypothetical B2B SaaS · not customer data
§ 01What it determines

Six decisions, made explicitly

  1. 01

    What the founder should own

    Strategy, accountability, high-risk and irreversible decisions — and nothing that recurs mechanically.

  2. 02

    What software should automate

    Deterministic, high-frequency workflows: billing, provisioning, reporting, deploys.

  3. 03

    What AI agents can execute

    Judgement-light work with clear policy: tier-1 support, drafting, research, code changes under review.

  4. 04

    Which specialists remain necessary

    Regulated or rare expertise — tax, legal, audit — bought as a service, not hired as headcount.

  5. 05

    What should remain human

    Relationships, accountability and risk. Zero employees is a constraint to optimise, not a dogma.

  6. 06

    What the economics look like

    AI and software cost, human cost, approval load and founder hours, before and after.

§ 02Method

From capability to blueprint

The same analysis, applied workflow by workflow.
  1. Step 1

    Business capability

    What the company must be able to do: acquire, sell, deliver, support, bill, comply.

  2. Step 2

    Workflow

    The recurring sequences that realise each capability, with frequency and volume.

  3. Step 3

    Current executor

    Who or what executes each step today, and how many hours it takes.

  4. Step 4

    Human / software / agent / contractor

    The cheapest reliable executor for each step under explicit risk rules.

  5. Step 5

    Target operating model

    The redesigned company: what the founder owns, what is delegated, what stays human.

  6. Step 6

    Cost / risk / intervention

    Economics, failure modes, approval load and expected founder intervention.

  7. Step 7

    Blueprint

    A sequenced plan of reversible experiments that moves the company to target.

§ 03Operating model

Current → target

An illustrative redesign of a hypothetical B2B SaaS. Founder time moves from execution to review, and recurring work moves to software and agents.

Current

Founder · 42h / week

  • Engineering14h
  • Marketing10h
  • Support8h
  • Operations7h
  • Sales3h

Other humans

  • Support employee1.0 FTE
  • Marketing freelancer0.5 FTE

Target

Founder · 23h / week

  • Strategy & product8h
  • Sales conversations6h
  • Engineering review6h
  • Approvals & exceptions3h

Delegated execution

  • EngineeringAI agentCoding agent opens PRs; founder reviews and merges
  • SupportAI agentTier-1 agent; escalations and refunds over $100 to founder
  • MarketingAI agentContent drafts and distribution; publish approval
  • OperationsSoftwareBilling, dunning, reporting run deterministically
  • Tax & complianceProfessionalAccountant retained — regulated, high-risk
Illustrative scenario · hypothetical B2B SaaS · not customer data
§ 04Blueprint

Every workflow, assigned and justified

An excerpt of an illustrative blueprint. Each row carries its approval rule and risk level.
Illustrative blueprint excerpt
CapabilityWorkflowCurrentTargetHuman approvalRisk
SupportTier-1 billing and how-to questionsEmployeeAI agentRefunds over $100Low
SupportEscalations and churn-risk accountsEmployeeFounder—Medium
EngineeringDependency and security updatesFounderSoftwareMerge on green CILow
EngineeringFeature implementationFounderAI agentPR review before mergeMedium
MarketingSEO articles and changelog postsContractorAI agentPublish approvalMedium
FinanceInvoicing, dunning, revenue reportingFounderSoftwareNone (policy-bound)Low
FinanceTax filingsProfessionalProfessionalFounder signsHigh
LegalCustomer contract changesFounderFounderLawyer when non-standardHigh

Illustrative · hypothetical company · not customer data

§ 05Principles

Built to be trusted with a company

Workflows, not people
The Architect analyses work at workflow level. It never scores individual employees.
Reversible first
Every change is sequenced as an experiment with a rollback, before any irreversible step.
Read-only before execution
Agents start by drafting and observing; autonomy is earned with measured error rates.
Humans keep accountability
High-risk actions keep a human approval, by design.
§ 06Availability

Start with the score. Request the analysis.

Zero-Employee Score
Live
Architect analysis & blueprint
Early access
Portfolio Control Plane
Research concept

Request an Architect analysis

e.g. 1 founder, 2 employees, 1 part-time contractor.

Online submissions are not connected in this deployment yet, so the form is disabled. Nothing you type here is sent.