This hub gathers competing go-to-market sequencing theses — how to enter, what to prove first, and when to expand. One mainline argues bottom-up: [developer-first PLG] (FocusSequencing_ADR002) starts with solo developers and small teams on Claude Code/Cursor/Windsurf, then expands to executive and content use cases once value lands. A second route runs top-down: a [Strategy/CTO team pilot] (Observation_FocusSequencing_PilotExpand) of 5-10 people over 30 days, adding a second role mid-pilot to show network effects, then org-wide within 60. A third frames the beta as [content → people → process] (Narrative_ThreePhaseBeta) — prove with content, then add people, then show partners. Underwriting all of it, a [revenue tradeoff] (Narrative_RevenueTradeoff) commits to forgoing [amount]-80K to protect product-vision integrity. The [strategy rubric] (RubricAssess_Strategy_ADR001) names focus/sequencing as a scored alignment axis. No human reconciliation crowns a single entry path; the three sequences sit side by side, each with a different first wedge.
Witness phrases
verbatim Add collective memory to your repo, never write README again
verbatim Forgoing [amount]-80K to maintain product vision integrity
verbatim Phase 1: Run content as proof. Phase 2: Add people to process. Phase 3: Show the process to organizational partners.
verbatim Pilot with Strategy or CTO team (5-10 people) for 30 days; add second role mid-pilot to demonstrate network effects; expand org-wide within 60 days.
verbatim Bottom-up vs top-down entry: developer-first PLG (solo devs, small teams) versus a Strategy/CTO team pilot — opposite first wedges into the org.
verbatim Three distinct 'prove-it-first' sequences coexist — content-first, developer-first, and team-pilot — with no single agreed starting proof.
verbatim Sequencing discipline is costly: willingness to forgo [amount]-[amount] in revenue to keep the chosen focus rather than chase near-term demand.
In this area
ObservationFocusSequencing_ADR002 Developer-first adoption (PLG motion): Solo developers / small teams using Claude Code, Cursor, Windsurf. Hook: 'Add collective memory to your repo, never write README again'. Expansion: Once developers see value, expand to executive/conten
NarrativeNarrative_RevenueTradeoff Strategic Focus Over Near-Term Revenue
NarrativeNarrative_ThreePhaseBeta Three-Phase Beta: Content → People → Process
ObservationObservation_FocusSequencing_PilotExpand Pilot with Strategy or CTO team (5-10 people) for 30 days; add second role mid-pilot to demonstrate network effects; expand org-wide within 60 days.
RubricAssessmentRubricAssess_Strategy_ADR001 Exemplary strategic alignment: directly addresses positioning thesis, moat/leverage, focus/sequencing, and risk/guardrails; decision rationale maps to strategy framework