A named fractional CTO writes who you hire next, and in what order. The same note says when to add a lead, what process to keep, and who owns each part of the code.
You are past the first few engineers. The next hiring decision either keeps shipping moving, or it adds a layer you do not need yet.
You have engineers. The important changes still wait on you.
You know you need someone. You are not sure which role.
A board, an advisor, or a peer said you need a manager. You want a written test first.
Two people change the same code. Nobody is the owner.
We have four engineers. I still review every pull request.
Founder, B2B SaaS
I do not know if the next hire should write code or manage the others.
Founder, Series A
We added meetings so we would look like a bigger team. Shipping got slower.
Head of product, software
Three people touched billing last month. None of them owns it.
COO, SaaS
CTO 2.0 puts one named person on that. You get a hire order, a lead decision, and an owner for each part of the code.
Hire for the work that is stuck. A title from a larger company is not a plan.
The next role is the work that is waiting. It is not a job title you saw somewhere else.
A lead does not replace someone who can do the stuck work.
Do that before you open the search, so the first hire does not set the shape of the team by accident.
A specialist, a second team, and a lead wait until the people you have can ship without you in every review.
A lead is a hire, not a default. We write the signals with you, then you decide.
You can still see the whole team.
The team is waiting on one person.
A lead here still knows the code. The work is reviews and decisions. It is not a new set of meetings.
Process should make the next release easier. If it slows shipping, it does not belong on this team yet.
Enough for a new person to ship.
These slow a team this size.
Every part of the code has one name. Other people can still change it. Only one of them is the owner.
| The product customers use | One named engineer |
|---|---|
| Money, accounts, or customer data | One named engineer |
| Deploys and production access | One named person |
| Code that everyone touches | An owner, written down |
Two names on one area means one owner and one helper. A new hire gets an area, or they pair with an owner. They do not take the whole repository.
FiscalNote builds software that helps organizations follow legislation, regulation, and policy. From January 2021 through March 2022, Maxiom staffed five to six full-stack engineers and an engineering manager on a rewrite of large portions of the flagship product. The team had worked with that manager before. The work started in Ruby on Rails and later expanded to PHP, WordPress, and Python. About 20 to 25 other engineers were committing to the same codebase, on four to five teams that sometimes worked on the same parts of the product. Releases went to production often, behind feature flags, in a DevOps-enabled codebase. The engineers worked in the tools FiscalNote already used, including Jira, Slack, and Confluence, and they followed FiscalNote's process. This page is a fractional CTO who writes your hire order, when a lead is worth adding, and who owns the code. The FiscalNote work was staff augmentation on a team that was already large. It was not this engagement.


When a review needs more hands, Maxiom engineers in Ashburn, VA do the work under your CTO's direction. Same standards, same owner.
Meet MaxiomNo. You get a written hire order and a description of the role. You make the hire. Maxiom can staff engineers later, if you ask. The FiscalNote case study on this page is staffing: five to six engineers and an engineering manager on a rewrite, inside the process FiscalNote already used. That was not this engagement.
Yes, when a lead would sit between you and a team that is still small. Add a lead when changes wait on one person, or when parts of the code have no owner.
No. We write the few steps you keep, and the steps that would slow a team this size. We do not bring a process from a larger company.
Each part of the code has one named owner. That person reviews changes to it and can explain it. Other people can still work there. They are not the owner.
No. We are not auditors. We do not certify the team, the process, or compliance. You get the hire order, the lead decision, and the ownership map.
Oversight is a review of an outsourced team. That page is at https://cto20.com/outsourced-dev-oversight. A stalled build gets a read-out and a call to continue or stop. That page is at https://cto20.com/rescue-a-stalled-software-project. AI strategy picks which uses get a pilot. That page is at https://cto20.com/ai-strategy-for-product-teams. This page is for your own engineers, once you are past the first few: who to hire next, when a lead helps, and who owns the code.
Book a time. It is a 30-minute call about who is on the team, what is stuck, and the hire you are considering. You get a clear yes or no on fit.
The people you have, the hire you are considering, and what is stuck. You leave with a clear yes or no.