# tinycto

The CTO playbook for founders and new engineering leaders, plus an AI advisor that answers in your situation's terms.

- Website: https://tinycto.com
- Listing: https://openack.co/p/tinycto
- Not evaluated. Its 18 claimed capabilities are the founder's word; nobody has checked them yet.

In the founder's words (not checked by OpenACK):

> tinycto is an operating playbook for running a high-performing engineering org, written by JP LeBlanc from real experience scaling engineering teams. It is built for founders acting as de facto CTO and for first-time tech leads and engineering managers. The curriculum covers hiring, team design, delivery, technology strategy, reliability, leadership and scaling. Every lesson is tagged by company stage (0-5 up to 150+ engineers) and depth, so readers get the material that fits where they are now instead of a feed of generic posts. On top of the free curriculum, tinycto offers an AI-native transformation guide that helps a CTO make their whole company AI-native, practical tools such as the Prompt tax calculator and the Intent document builder, and a paid MCP server. The MCP server brings tinycto into Claude, ChatGPT and other AI assistants, where it can give an opinionated, cited answer to your specific engineering-leadership situation.

## Capabilities

- **not evaluated**: Get an opinionated answer to your own engineering-leadership question, citing the lessons it draws on
- **not evaluated**: Browse a structured CTO curriculum organized into tracks
- **not evaluated**: Read a full engineering-leadership lesson for free without signing in
- **not evaluated**: See which company stage and depth level each lesson is for
- **not evaluated**: Follow step-by-step playbooks for common engineering-leadership situations
- **not evaluated**: Read JP's published opinions on engineering-leadership debates
- **not evaluated**: Read the AI-native company guide chapter by chapter
- **not evaluated**: Build a personal AI-native transformation profile for your company
- **not evaluated**: Get a personalized AI-native report for your company
- **not evaluated**: Challenge a constraint that blocks AI adoption and get a ruling (Constraint Court)
- **not evaluated**: Log a progress check-in on your AI-native transformation
- **not evaluated**: Estimate your team's prompt tax with a calculator
- **not evaluated**: Draft an intent document with a guided builder
- **not evaluated**: Create an API key to connect tinycto to Claude, ChatGPT or another AI assistant over MCP
- **not evaluated**: Follow how-to guides for specific engineering-management tasks
- **not evaluated**: Look up engineering-leadership terms in a glossary
- **not evaluated**: Track your progress through the curriculum from your dashboard
- **not evaluated**: Request a residency, where JP works alongside a founder or first engineering lead

## What the statuses mean

- **confirmed** (ACK): a person from OpenACK signed in with a test account and saw it work.
- **not confirmed** (NAK or ?): it was tried and didn't work, or we couldn't reach or check it. Not proof it's missing, but not verified.
- **not evaluated** (—): nobody has checked it. It's the founder's word only.

Treat only "confirmed" as verified. A result is a record of one evaluation on the date shown, not a guarantee.