Practical, deeply reasoned writing on technical due diligence, value-up engineering, organizational design, and how technology decisions translate into investment outcomes.
日本語版はこちらA framework for assessing engineering capability without code review: development process, PRs, deployment frequency, docs, incident history, and five interview questions.
A 3-class taxonomy of technical debt (intentional, accidental, environment-driven), the startup-specific accumulation mechanics, and how to evaluate it in tech DD.
A tech-literacy guide for investors and operators: map Python, TypeScript, Go, Rust, Java, Ruby, and PHP across five business-decision lenses.
A hub article defining what technical DD is, why it matters, and how its seven evaluation axes interlock. Detailed methodology lives in dedicated articles.
Technical debt is not just ugly code. Mapped against financial debt, this reframes its essence, four-quadrant taxonomy, and business impact for investors.
A non-engineer's framework for evaluating a target's engineering organization, from pre-meeting quantitative checks to four interview lenses and PMI design.
A comprehensive, CTO-grade checklist for the purpose, evaluation axes, and concrete line items of technical DD in startup investing.
How to time the CTO hire across product phases, when to use a technical advisor instead, and a practical framework for evaluating candidates.
Questions about anything you read here, or a specific engagement you're considering — we're happy to discuss.
Get in touch