# Key Concepts

_The frameworks this book builds on, one page each_

**In short:** Gareth Price's _Applied Alchemy_ rests on six frameworks for the startup CTO: the four stages of the role, the business acumen gap, the maker-to-multiplier shift, the operating rhythm, strategic technical debt, and the difference between rushing and speed. Each has its own page with a definition, an example from the book and a first step to take this week.

The four stages are the map. The other five describe what the role asks of you as you cross it: the translation skill that keeps CTOs in post, the identity shift away from code, the structure that replaces it, and the judgment to borrow and move fast without breaking things.

Four stages of a startup CTO

The four stages of a startup CTO are Coder, Manager, Director and Strategist: four different jobs the role becomes as a company grows, each needing skills the previous stage never taught. [What Are the Four Stages of a Startup CTO?](what-are-the-four-stages-of-a-startup-cto.html)

Business acumen gap

The business acumen gap is the distance between what a CTO knows and what they can communicate in the language the business acts on, and the most common reason founding CTOs lose their jobs. [What Is the Business Acumen Gap?](what-is-the-business-acumen-gap.html)

Maker-to-multiplier shift

The maker-to-multiplier shift is the CTO's transition from writing the code to creating the conditions in which others write it well, trading a craft identity for leverage. [What Is the Maker-to-Multiplier Shift?](what-is-the-maker-to-multiplier-shift.html)

CTO operating rhythm

A CTO operating rhythm is a set of recurring activities at daily, weekly, monthly, quarterly and annual cadences that gives the CTO role the structure it lacks, so urgent work cannot crowd out important work. [What Is a CTO Operating Rhythm?](what-is-a-cto-operating-rhythm.html)

Strategic technical debt

Strategic technical debt is a deliberate shortcut taken to ship sooner and managed like a loan: you know what you borrowed, what interest it charges and when you will repay it. [What Is Strategic Technical Debt?](what-is-strategic-technical-debt.html)

Rushing versus speed

Rushing versus speed is the difference between skipping safeguards to ship now, which creates problems that slow you down later, and removing friction so small, tested, reversible changes ship often and safely. [What Is the Difference Between Rushing and Speed?](what-is-the-difference-between-rushing-and-speed.html)

**Start with the book:** [Introduction: The Role Nobody Prepared You For](introduction.html) and [Chapter 1: The Four Stages](1-four-stages-cto-evolution.html).

---

## Frequently Asked Questions

1. _What frameworks does Applied Alchemy use?_  
Six: the four stages of a startup CTO (Coder, Manager, Director, Strategist), the business acumen gap, the maker-to-multiplier shift, the CTO operating rhythm, technical debt as a strategic instrument, and the difference between rushing and speed. The four stages are the map; the others describe what the transitions between stages ask of the CTO.
2. _What is the most important skill for a startup CTO?_  
Translation. Applied Alchemy's core argument is that what decides whether a startup CTO survives is not their architecture, code quality or technical judgment but their ability to turn technical reality into business language, and their willingness to operate as a business leader, not just a technical one.
3. _Where should a first-time CTO start?_  
With the four stages, to see which job you are actually doing now, then the operating rhythm, to give the role the structure it lacks. The book advises reading Part I first whatever your stage; it takes less than an hour and reframes everything that follows.
4. _Did Applied Alchemy invent these frameworks?_  
No, and it says so. The four stages draw on CTO coach Viktor Nyblom and Daniel Jarjoura, the business acumen gap on executive adviser Adelina Chalmers, maker and multiplier on Pat Kua, and technical debt on Ward Cunningham. The book brings them together for the startup CTO, with examples and first steps for each.
5. _Are these frameworks useful for CTOs at larger companies?_  
Yes. The Director and Strategist stages cover organisations from 45 to several hundred people, and the business acumen gap and the operating rhythm apply at any size. The book is written for founding CTOs, scaling CTOs, and CTOs deciding whether it is time to step aside.