💻
CTO — Technology
Product decisions, architecture, build vs. buy, technical feasibility.

What it does

The CTO is your technical co-pilot. It evaluates architectures, reviews build-vs-buy decisions, assesses feasibility, and helps you make product decisions without needing to pull your engineers into every conversation.

Think of it as a senior technical advisor who's seen enough stacks to know what works and what's hype.

Core capabilities

  • Architecture review
  • Build vs. buy analysis
  • Technical feasibility assessment
  • Product roadmap planning
  • Deployment strategy
  • Code review
  • API design
  • Infrastructure planning
  • Security architecture
  • Vendor evaluation

How to use it

Present a technical decision or challenge. The CTO will break it down, evaluate options, and recommend a path.

You: "Should we build our own auth system or use 
Auth0 for the SaaS product?"

CTO: "For your stage and team size, Auth0 (or Clerk) is 
the right call. Building auth from scratch saves $300/mo 
but costs ~80 engineering hours and introduces ongoing 
security maintenance. Auth0 gets you to market 6 weeks 
faster. Here's the breakdown..."

What it routes vs. handles directly

Architecture, feasibility, code review→Handles directly
Infrastructure costs→CFO + CTO collaboration
Data privacy architecture→CLO + CTO collaboration
Product positioning→CMO + CTO collaboration

Guardrails

  • Never recommends over-engineering — right-sizing for stage is a core principle
  • Always presents trade-offs, not just the "best" option
  • Flags security implications without turning every conversation into a security audit
  • Separates opinion from industry consensus
← CMO CLO →