Solo Operator Commercial OS

Archon now ships with a commercial operating system for solo operators. It is designed for SaaS, agency / service, and creator / productized businesses, with a shared lifecycle and model-specific tactics inside the assets.

The operating model is cross-provider first:

• Core behavior lives in workflows, commands, artifacts, and approval gates.
• Claude can use optional skills for sharper execution.
• Codex can still run the workflows because the required instructions stay in the command files.

Lifecycle

The bundled workflow family covers the full path from idea to post-launch support:

1. archon-solo-operator-intake
2. archon-problem-solution-fit
3. archon-offer-positioning
4. archon-gtm-plan
5. archon-pipeline-activation
6. archon-launch-readiness
7. archon-go-live-command
8. archon-post-go-live-stabilization
9. archon-customer-success-loop
10. archon-solo-operator-commercial-os

When To Use What

Use archon-solo-operator-commercial-os when you want the full guided lifecycle with approvals between major stages.

Use the modular workflows when you only need one slice:

• archon-problem-solution-fit for a blunt commercial go / pivot / hold decision
• archon-offer-positioning when the offer exists but is not yet sharp enough to sell
• archon-gtm-plan when you need a 30/60/90 revenue motion
• archon-pipeline-activation when strategy exists and execution assets are missing
• archon-launch-readiness before going live
• archon-go-live-command for launch-day planning
• archon-post-go-live-stabilization and archon-customer-success-loop after launch

Artifact Contract

These workflows chain through a stable set of artifacts in $ARTIFACTS_DIR:

• operator-brief.md
• market-evidence.md
• offer-brief.md
• icp-and-messaging.md
• gtm-plan.md
• pipeline-playbook.md
• launch-readiness.md
• go-live-runbook.md
• post-launch-review.md
• customer-success-plan.md

Each stage should read existing artifacts first and extend them, not overwrite them blindly. This makes the workflows useful both as a single end-to-end run and as a modular operating system.

Example

archon workflow run archon-solo-operator-commercial-os \
  --branch feat/solo-operator-commercial-os \
  "B2B SaaS for independent recruiters. Early beta. Need first 5 paying customers in 60 days and a safe go-live plan."

Optional Claude Skills

Claude users can pair these workflows with optional skills under .claude/skills/:

• solo-operator-intake
• problem-validation
• offer-positioning
• gtm-planning
• discovery-sales
• launch-ops
• post-launch-success

These sharpen execution but are not required for correctness.