One-person company operations

Who it is for

Dimension	This solution	Studio / OPC agent
Scope	Full commercial loop	Single project or work order
Founder role	Orchestrator + final approver	Approval gates + exceptions
Fit	Product/channel ready to systematise	Document-heavy knowledge work
Not fit	No corporate account, no templates, expecting full autopilot	Unmanned entire business

Aligned with handbook: delivery models.

Starting OPC methodology

Consulting and implementation follow a fixed five-phase sequence: define the commercial loop and HITL boundaries; decompose processes and system touchpoints; then define agent roles and complete integration. Skipping early phases typically yields outbound actions without accountable owners, reconciliation drift, and founder manual load above the pre-go-live baseline.

Phase	Items to define	Deliverables
Commercial loop	Revenue sources, deliverable boundaries, outbound commitments requiring founder signature	Model notes, red-line list
Main chain & gates	State transitions across the five stages; nodes that must pause for human confirmation	Chain map, gate table, escalation paths
Resources & systems	What exists, what is missing, how CRM/mail/commerce/finance connect	Resource list, integration map
Agent mapping	Per-role tasks, outputs, forbidden actions, hand-offs	Role table, routing and HITL rules
Rollout	Gray scope, day-to-day governance, sign-off criteria	Phased plan, governance rules, acceptance table

Commercial loop

Discovery establishes and documents the revenue model (one-off / subscription / project / commission), deliverable boundaries, and constraints (region, licence, payment terms). Compliance covers entity form, corporate account and separate books—subject to local regulation and professional advice; not legal advice on this page.

Main chain & gates

Operations follow five stages: product definition → market reach → lead follow-up → fulfilment → supply chain. Each stage separates work that can run automatically from actions that must escalate to you. Pricing commitments, contract outbound, payments and public release sit on the freeze list.

Stage	Main chain	Needs you
Product definition	Drafts, pricing trials	Public pricing, patent disclosure
Market reach	Content drafts, scheduling, lead triage	Public release, ad contracts
Lead follow-up	CRM updates, mail drafts, meeting notes	Quote outbound, contract terms
Fulfilment	Work-order split, progress sync	Refunds, SLA changes
Supply chain	RFQ, order drafts, reconciliation	Payment, new supplier onboarding

Resources & systems

Before build: people and time, channels and customers, suppliers and contract templates, existing data (CRM, finance, mail archive). Gaps go into phased delivery—no “available on day one” assumptions. Outbound and payment integrations always use freeze → preview → approve.

System	Use	Access
CRM	Leads, opportunities	Read/write
E-commerce / site	Orders, inventory	Read/write
Payments	Collections, refunds	Read (refunds via HITL)
Mail / IM	Customer comms	Read/draft; outbound frozen
Warehouse	Shipping, stock	Read/write
Finance / tax	Vouchers, invoices	Read; payment via HITL

Agent mapping

Agent clusters are an implementation shape defined only after the main chain and gate specifications are signed off. Repeatable work maps to roles (product, market, sales, ops, supply chain, finance review) with explicit tasks, outputs, forbidden actions and hand-offs. One chain can pilot on OPC agent before scaling across all five stages.

Rollout

In operation: config revision bound to Run; master-data changes trigger freeze and re-review; unapproved outbound target is zero. Illustrative phases—PoC: read-only + drafts + freeze drills; trial: limited-channel gray release; stable ops: five-stage scale-out and sign-off. Timelines vary by scene and joint discovery.

Consulting delivery

Crusbro delivers business model review and process design or redesign along this sequence, then implements against agent-cluster specs on crusbro agent-OS. We do not deliver software first and backfill process later; each phase can be signed off independently or run through to trial operation.

Module	Work	Deliverables
Business model	Revenue and deliverable boundaries, constraints, fit for solo vs studio setup	Model notes, red-line list
Process build	Five-stage map or redesign, gates and escalation, alignment with existing policy	Chain map, gate table, escalation paths
Agent cluster design	Operating-role agents + domain agents mapped to the chain, boundaries and hand-offs, read/write tiers	Role table, integration spec, HITL rules
Implementation	Phased go-live, Harness governance, metrics and sample evidence packs	Acceptance table, replay sample, ops agreement

Domain agents (drawing, vision, freight, etc.) extend the operating chain with shared gates and order-level evidence—see Key workflows below.

Typical scenarios

Scenario 1: Cross-border inquiry loop

The founder approves quotes and contracts; agents merge multi-inbox inquiries, extract SKU and lead time, sync CRM, and draft multilingual replies. Outbound is frozen for preview first; evidence packs are archived by lead ID.

Scenario 2: Asset-light project delivery

Project-based delivery; agents split milestone work orders, sync client progress mail, and produce reconciliation lists with invoice-match suggestions. Payments, compensation and SLA changes always go through HITL.

Scenario 3: Solo e-commerce peak season

Agents monitor inventory and replenishment thresholds, draft support replies, and verify shipment lists against logistics receipts. The founder locks pricing tables and promo copy gates before peak season.

Scenario 4: Content marketing and lead nurture

Agents draft content from the calendar, schedule posts and adapt for channels; leads entering CRM get tags and follow-up reminders. Public release, ad contracts and brand commitments require founder approval.

Scenario 5: Collections and daily finance close

Agents pull bank flows, orders and invoices, produce daily variance reports; exception payments enter a review queue. Auto-payment stays off; payment approval remains with the founder.

Key workflows

Two layers: the operating main chain (leads, contracts, fulfilment, reconciliation) and domain agents (drawing, vision, freight, etc.). Both run under one Harness, linked by business order ID with shared freeze and evidence.

Operating main chain

Inquiry → quote outbound

Mail/IMAP intake → classify and merge leads → CRM update → quote draft (bound to pricing revision) → freeze preview → founder approval → send → evidence pack by lead ID. Carried by OPC agent (sales/ops roles).

Contract sign-off and project kick-off

Opportunity confirmed → template fill → clause diff highlight → freeze → founder signs → project ID opened → milestone work orders auto-created → client notification draft (frozen before send). Carried by OPC agent.

Fulfilment progress and client sync

Work-order status changes trigger progress summaries; agents draft weekly/milestone mail with deliverable links. Refunds, compensation and SLA changes never auto-execute—they enter the HITL queue.

Procurement and daily reconciliation

RFQ table → order draft (bound to supplier master data) → freeze → approve → ERP/procurement write; end-of-day flow and invoice match with variance report to founder.

Domain agents

Design delivery, outbound QC and cross-border freight plug directly into the operating chain with shared gates and no extra governance stack.

Domain agent	Chain stage	Typical actions	Notes
OPC agent	Leads / fulfilment	Mail-driven work orders, documents, frozen outbound	Default for the operating chain; pilot one path first
Freight agent	Fulfilment / supply	Ocean mail merge, booking/VGM drafts, frozen send	Trade-heavy solos; see smart logistics
Industrial Drawing Agent	Product / fulfilment	Drawing parse, BOM/route, rev checks, freeze before MES	Design or small-batch custom; see smart manufacturing
Industrial Vision Agent	Product / fulfilment	Station inspection, gray-zone review, gates before QMS write	Outbound QC; see industrial vision
Robot Agent	Fulfilment	Station motion orchestration, exception escalation	When a small line or automated cell is in scope

Example: custom parts project (drawing + OPC)

Customer drawing ingested → Industrial Drawing Agent parse and BOM draft → rev conflicts and low-confidence fields to HITL → quote and lead time drafted by OPC agent → frozen outbound → milestones and progress stay on the OPC work-order chain. One project ID evidence pack end-to-end.

Example: pre-shipment QC (vision + ops)

Batch at station → Industrial Vision Agent call and gray-zone queue → pass/reject recommendation frozen → founder or QC approves → QMS/shipping writeback; exception lots replay by order ID.

Example: cross-border fulfilment (freight + sales)

Inquiry and quote on the OPC sales chain; booking-stage mail and attachments in the Freight agent project vault → booking/VGM outbound under the same freeze list → one approval policy covers operating and fulfilment mail.

Implementation: agent cluster

Typical implementation after main-chain and gate specifications are signed off: the founder at the orchestration layer; operating-role agents (product, market, sales, etc.) and domain agents (drawing, vision, freight, etc.) on crusbro agent-OS Harness with tiered system access; high-risk actions routed through freeze gates.

Role	Duties	Forbidden	HITL
Product	Drafts, competitors, pricing trials	External product promises	Pricing and scope
Market	Content drafts, scheduling	Unapproved publish	Public release
Sales	Lead follow-up, quote drafts	Contract signing	Quote outbound
Operations	Work orders, progress, support drafts	Refunds/compensation	SLA changes
Supply chain	RFQ, order drafts	Payment	New suppliers
Finance review	Reconciliation, invoice match	Auto payment	Payment approval

Runs on crusbro agent-OS.

Acceptance metrics

Metric	How measured	Owner
Work-order completion rate	Closed / due in period	Operations
Human intervention rate	HITL steps / total steps	Founder + IT
Unapproved outbound	Audit scan	Security
Reconciliation gaps	Daily open items	Finance

Related products and handbook

• crusbro agent-OS — embeddable kernel and Harness governance
• Business Automation Agent (OPC agent) — operating-chain work orders
• Industrial Drawing Agent · Industrial Vision Agent · Freight Agent — domain options
• Handbook: OPC tutorial