SOP-EXEC-strategy-request-intake-v1.0¶

1. Purpose¶

Define how strategic requests — new initiatives, capability investments, category pivots, market expansion ideas — are received, documented, and routed into the prioritization and execution pipeline. Prevents strategic ideas from being lost in Slack threads or acted on without proper scoping.

Scope: Requests that are directionally significant — they affect company positioning, resource allocation, or multi-week execution. Tactical task requests go through SOP-EXEC-project-kickoff-v1.0 directly.

2. What Counts as a Strategic Request¶

Type	Examples
New capability investment	"We should build an ecosystem intelligence dashboard for customers"
Category / positioning pivot	"I want to reframe the Assessment as an Ecosystem Revenue Audit"
Market expansion	"Let's go after mid-market SIs as a distribution channel"
Platform or architecture decision	"Should we migrate from Supabase to a different data layer?"
New agent or role creation	"We need a dedicated partner ops agent"
New product or offer	"What if we offered a monthly retainer tier alongside the Assessment?"

Anything the CEO says that starts with "I've been thinking about..." or "What if we..." is a candidate for strategy intake.

3. Intake Points¶

Strategic requests arrive via: - CEO Slack message (any channel) - /Claude/inbox/inbox.md raw capture - CEO Daily Summary flag from an executive - CEO direct session dispatch to chief.staff

chief.staff owns capture. If a strategic request arrives and chief.staff is not in session, the receiving agent flags it in #agent-handoffs and drops a note to chief.staff's session dir.

4. Intake Procedure¶

Step 1 — Capture (within 2 hours of receipt)¶

chief.staff acknowledges the request and files a raw capture note to /Claude/plans/strategy-intake-{slug}-{YYYY-MM-DD}.md:

STRATEGY INTAKE — RAW CAPTURE
──────────────────────────────
Request: {verbatim or close paraphrase of CEO's words}
Received via: {Slack / inbox / session}
Received at: {YYYY-MM-DD HH:MM PST}
Captured by: chief.staff
Status: Raw — not yet classified or prioritized

Step 2 — Clarifying questions (same session or within 24 hours)¶

Before scoping, chief.staff identifies and asks any questions needed to understand the request: - What problem is this solving? - What's the trigger — did something prompt this now? - What does success look like in 90 days? - What's the time horizon? - Is there a specific blocker or constraint to know about upfront?

Answers logged to the intake file.

Step 3 — Classification¶

chief.staff classifies the request:

Classification	Criteria	Next step
Mission candidate	≥2 of 5 Section 10A.2 triggers	Route to project.manager for Mission decomposition
Standard project	Multi-agent or multi-day but not Mission-qualifying	Route through SOP-EXEC-project-kickoff-v1.0
Research first	Not enough information to scope; needs a research phase	Dispatch research request to appropriate agent (category.positioning, financial.research, etc.)
Defer	Good idea, wrong timing — not aligned with current Q2 priorities	Document in `/Claude/plans/backlog/` with rationale; resurface at next quarterly
Rejected	Conflicts with current strategy, resource constraints, or legal/compliance	Document rejection rationale; CEO acknowledges

Step 4 — Brief to CEO¶

Within 24 hours of receiving answers to Step 2, chief.staff sends the CEO a one-paragraph intake brief:

STRATEGY INTAKE BRIEF — {slug}
Date: {YYYY-MM-DD}
Request summary: {2 sentences}
Classification: {Mission / Project / Research / Defer / Reject}
Rationale: {why this classification}
Proposed next step: {specific action}
Resource estimate: {rough sessions/days/agents needed}
Q2 alignment: {aligned / neutral / competes with {current priority}}

CEO approves classification or redirects before any work begins.

Step 5 — Routing¶

On CEO approval: - Mission: project.manager dispatched to decompose per Section 10A - Project: project.manager dispatched per SOP-EXEC-project-kickoff-v1.0 - Research: appropriate research agent dispatched - Defer/Reject: filed to backlog with CEO acknowledgment noted

5. Backlog Review¶

chief.staff reviews the strategy backlog at each quarterly planning cycle (end of each quarter). Items are re-evaluated against current priorities. CEO decides which deferred items get activated, which stay deferred, and which are permanently closed.

Backlog files: /Claude/plans/backlog/{slug}-{YYYY-MM-DD}.md

Change Log¶

Version	Date	Change
v1.0	2026-04-21	Initial draft — sop.manager.

Owner: chief.staff Executive sponsor: chief.staff Drafted by: sop.manager Status: Draft — requires CEO approval Version: v1.0