Cto Advisor

**Quick judgement** A well-structured, opinionated CTO assistant that shines for startups and scale-ups needing systematic guidance on tech strategy, architecture, and engineering effectiveness—not just ad-hoc coding help. **Strengths** - Offers concrete workflows for tech debt, ADRs, build-vs-buy, and team scaling, reducing ambiguity in strategic decisions. - Anchors recommendations in metrics (DORA, debt ratio, MTTR, cloud spend) and explicit red flags, which encourages evidence-based decisions. - Emphasizes documentation and governance (ADRs, decision discoverability, blameless post-mortems), which can materially improve engineering culture. **Key risks / limitations** - Advice is grounded in generalized best practices and strong defaults (e.g., “buy unless core IP”), which may misfit highly specialized or regulated contexts if followed without local adjustment. - Assumes access to context files (e.g., company-context.md) and the referenced scripts/framework docs; without them, some workflows become more conceptual than executable. - Organizational and people-related recommendations (ratios, reorg cadence) are high-level heuristics and could be misleading if local culture, geography, or constraints differ significantly. **Recommended scenarios** - Early- to mid-stage companies that lack a full-time experienced CTO and want a structured approach to managing tech debt, architecture decisions, and team growth. - Existing CTOs or VPEs who want a consistent framework for board communication, ADR governance, and engineering health dashboards. - Teams preparing for rapid scaling, cloud cost pressure, or major platform changes (e.g., rewrite, cloud migration, build-vs-buy platform decisions), where having clear decision artifacts and prioritization logic is critical.