One-person company operations
The founder decides and handles exceptions; an agent cluster runs the end-to-end commercial loop (product → market → leads → fulfilment → supply chain). This page describes consulting and delivery, not a chat product. Single work-order automation: Business Automation Agent (OPC agent).
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
Workflow 1: 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.
Workflow 2: 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).
Workflow 3: 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.
Workflow 4: 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.
Delivery models compared
| 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.
Business model design
Discovery clarifies revenue, deliverables, constraints (region, licence, payment terms) and compliance red lines (contracts, invoices, public commitments).
- Revenue model: one-off / subscription / project / commission
- Deliverable boundary: what agents draft vs what founder must sign
- Compliance: entity form, corporate account, separate books (subject to local regulation and professional advice—not legal advice)
Five-stage commercial loop
| Stage | Main chain | Exception escalation |
|---|---|---|
| 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 |
Resource inventory
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.
External IT map
| System | Use | Access | Risk |
|---|---|---|---|
| CRM | Leads, opportunities | Read/write | Write |
| E-commerce / site | Orders, inventory | Read/write | Write |
| Payments | Collections, refunds | Read | High |
| Mail / IM | Customer comms | Read/draft | Outbound |
| Warehouse | Shipping, stock | Read/write | Write |
| Finance / tax | Vouchers, invoices | Read | High |
Outbound and payment integrations always use freeze → preview → approve.
Consulting deliverables
| Phase | Output |
|---|---|
| Discovery | Business model notes, constraints and red-line list |
| Process design | Five-stage chain, gate table, escalation paths |
| Integration design | System map, idempotency rules, read/write tiers |
| Acceptance | Signable checklist, sample evidence pack |
Agent cluster and system architecture
The founder sits at the orchestration layer; six role agents run on crusbro agent-OS Harness; external systems connect with read/write tiers and high-risk actions always use 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; single work-order pilots can start with OPC agent.
Runtime governance
- Payments, contracts, public commitments: freeze list; unapproved outbound count must be zero
- Config revision bound to Run; exceptions replayable by business order
- Master-data changes trigger freeze and re-review
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 |
Phased rollout
| Phase | Duration (illustrative) | Scope |
|---|---|---|
| PoC | ~30 days | Read-only + drafts + freeze drills |
| Trial run | ~60 days | Limited channel gray release, metrics on dashboard |
| Stable ops | ~90 days | Five-stage scale-out, sign-off |
Related products and handbook
- crusbro agent-OS — embeddable kernel and Harness governance
- Business Automation Agent (OPC agent) — single work-order product
- Handbook: one-person company and OPC