Step 1: Choose the right OS
Lead Response OS for inquiry speed. Content Ops OS for publishing consistency. Founder Ops OS for executive triage and follow-up.
Use this exact sequence when testing a real client. Do not skip verification. The product is not “installed” until the handoff evidence passes.
Universal onboarding sequence
Lead Response OS for inquiry speed. Content Ops OS for publishing consistency. Founder Ops OS for executive triage and follow-up.
Business name, timezone, intake sources, email/draft channel, alert channel, escalation threshold, approval owner, and first test scenario.
Run the installer with the client slug, business name, and timezone. Confirm operating rules were created.
Run the matching verifier. Require success=true, fail=0, worldClassScore ≥ 95, and a fresh traceId.
Open the safety matrix and prove unsafe sends, publishing, spending, refunds, calendar changes, and commitments are blocked.
Explain what was installed, what it does, what it refuses to do, and what evidence proves readiness.
Run one real client scenario in supervised mode. Human approves the first send/publish/commitment before scaling.
Per-product commands
bash agentic-os/installers/lead-response/install.sh --client CLIENT --business "Client Name" --timezone America/Denver bash agentic-os/installers/lead-response/verify.sh --client CLIENT
Use when slow lead follow-up is costing deals.
bash agentic-os/installers/content-ops/install.sh --client CLIENT --business "Client Name" --timezone America/Denver bash agentic-os/installers/content-ops/verify.sh --client CLIENT
Use when content is inconsistent, stalled, or approval-heavy.
bash agentic-os/installers/founder-ops/install.sh --client CLIENT --business "Client Name" --timezone America/Denver bash agentic-os/installers/founder-ops/verify.sh --client CLIENT
Use when the founder is the bottleneck for decisions, follow-up, and prioritization.