Commentary

Every company has a way it grows. Who buys, why they buy, what it costs to win them, and what keeps them coming back. That is the engine.

The manifesto puts this first on purpose. A CTO who can't explain how the company grows will build things the company doesn't need. Before the architecture and before the roadmap, the CTO should be able to sit with the CEO and the CFO and describe the engine in their words.

After that, every technical decision gets one test. Does this help the engine run?

Look at the word needed. The vision starts from what this company will need in order to grow, 1 year out and 3 years out. The CTO's favorite stack comes later, if at all.

A good technology vision is short enough for the board to repeat. It says what the company will be able to do that it can't do today, and roughly what it will take to get there. Engineers should be able to read it and know what to say no to.

Technology is one of the biggest lines in the budget, and the CTO owns it. Financial savvy means knowing what engineering costs and what it returns, and being able to talk about both with the CFO without a translator.

It shows up in plain questions. What does this team cost per month? What did the last big project return? Should we build this, buy it, or skip it?

A CTO who can answer those is in the budget conversation instead of waiting to hear how it went.

The CTO doesn't build the technology alone, and after the first few engineers shouldn't try. The job becomes choosing the people, deciding how they are organized, and growing the leaders who will run parts of it.

Assembling takes intent. The right skills, the right mix of experience, and a structure that fits the size of the company. What works for 5 engineers breaks at 40, so the CTO keeps reshaping the team as the company grows.

CTO Levels describes what that reshaping looks like at each size, from a team of 1 to a team of 400.

The word that matters in this sentence is precision. The CTO leads the team to build with precision. Clear priorities, honest estimates, and knowing at any moment what is shipping and why.

Precision doesn't mean a fixed plan. Plans change, and the principles expect them to. What holds steady is clarity about what the team is building, who it is for, and how everyone will know it worked.

The manifesto ends where it began, with the engine. The technology exists to make the business grow, and that is how it gets measured.

So the CTO reports in business terms. Faster onboarding, lower cost to serve, a product customers renew. Deploy counts and uptime matter to the team and belong in the engineering review. In the boardroom the question is simpler. Is the engine running better than it was last quarter?