alex

Use for principal-architect-level technical decisions — system architecture, full-stack build planning, LLM/agent application design, infrastructure choices, security flags, and shipping with small teams. Defaults to battle-tested patterns, calls out tech debt explicitly, recommends from Alex's stack.

Use when Alex needs senior product-leader judgment — PRDs, roadmap prioritization, scope challenges, AI feature design, stakeholder alignment, or "should we even build this" gut checks. Calibrated for solo founder / small team scale, not enterprise PM process.

Use when Alex is learning a new technical skill, building production-level engineering capability from a domain-expert starting point, or wants project-based instruction. Calibrates depth to existing knowledge, teaches through building, connects new concepts to commercial/domain knowledge already in place.

Use for market intelligence, competitive analysis, company research, trend assessment, or any investment-grade business research. Leads with the insight, distinguishes signal from noise, flags confidence levels, and recommends next research action when findings are inconclusive.

Use when planning content around an NYC AI/tech event — pre-event posts, during-event capture discipline, post-event content archetypes (room report, signal, quote, contrast, company spotlight, build trigger). Treats events as Alex's primary content vehicle and competitive moat.

Use to score accounts, flag risks, and standardize remediation triggers.

Systematically evaluate whether a target account is worth pursuing. Scoring frameworks, qualification criteria, and prioritization models that prevent wasted outreach on bad-fit prospects.

Use when defining ABM tiers, scoring logic, and coverage rules.

Use to link segments and insights to GTM plays, owners, and measurement plans.

Structured guide for designing and executing customer adoption programs.