CTO2.0A MAXIOM VENTUREMaxiom TechnologyBook a time →
Past the first few engineers

Scale your engineering team

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.

  1. TodayYou, plus a few engineers
  2. ThenThe role after that, written first
  3. LeadOnly when the signals say so
Who it's for

For founders who are still the bottleneck.

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.

  1. 01

    Still the reviewer

    You have engineers. The important changes still wait on you.

  2. 02

    About to open a role

    You know you need someone. You are not sure which role.

  3. 03

    Told to hire a lead

    A board, an advisor, or a peer said you need a manager. You want a written test first.

  4. 04

    Ownership is fuzzy

    Two people change the same code. Nobody is the owner.

What we hear

The team grew. You are still the system.

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 order

What to hire next, and in what order.

Hire for the work that is stuck. A title from a larger company is not a plan.

  1. 01
    First

    Name the stuck work

    The next role is the work that is waiting. It is not a job title you saw somewhere else.

  2. 02
    Second

    Hire that one person

    A lead does not replace someone who can do the stuck work.

  3. 03
    Third

    Write the role after this one

    Do that before you open the search, so the first hire does not set the shape of the team by accident.

  4. 04
    Not yet

    Leave the rest off the list

    A specialist, a second team, and a lead wait until the people you have can ship without you in every review.

The lead

When to add a lead.

A lead is a hire, not a default. We write the signals with you, then you decide.

Not yet

You can still see the whole team.

  • You can review the risky changes without holding up the release.
  • Each part of the code already has a name next to it.
  • A new person would know who to ask on day one.

Add a lead

The team is waiting on one person.

  • Changes wait on you, and the release slips.
  • Two parts of the code have no owner.
  • You are about to hire, and the new person would not know who decides.

A lead here still knows the code. The work is reviews and decisions. It is not a new set of meetings.

Process

Keep the process light.

Process should make the next release easier. If it slows shipping, it does not belong on this team yet.

Keep

Enough for a new person to ship.

  • One written way a change gets to production.
  • A short review on changes that can hurt a customer.
  • A weekly note: what shipped, what is stuck, and who owns it.

Do not add

These slow a team this size.

  • A tool for a ritual the team does not have.
  • A meeting for a decision that fits in a note.
  • A process copied from a much larger company.
Ownership

Keep code ownership clear.

Every part of the code has one name. Other people can still change it. Only one of them is the owner.

Who owns each part of the code
The product customers useOne named engineer
Money, accounts, or customer dataOne named engineer
Deploys and production accessOne named person
Code that everyone touchesAn 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.

NDA before accessSigned before anyone sees a repository or environment.
Read-only by defaultWrite access only when you grant it, for a named task.
Your code stays with youThe work happens in your environment.
You make the hireWe write the order. We do not recruit unless you ask.
Proof from the Maxiom record

Work the team has already shipped.

FiscalNote
Staff augmentation

Engineers and a manager inside a multi-team rewrite

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.

Ruby on Rails · PHP · WordPress · Python · Feature flags
Read the case study
Who the CTOs are

Three CTOs. One engineering team behind them.

Antonio Chagoury

Antonio Chagoury

Founder and CEO, Maxiom
Enterprise software and healthcare AI
Microsoft MVP20+ years
  • Founded and runs Maxiom, building software since 2002
  • Built software for AABB, the blood and biotherapies association
  • Built the Rezeo AI video resume platform
  • Published on software architecture
Washington DC-Baltimore Area
Gaurav Bagul

Gaurav Bagul

CTO, Maxiom Technology
Healthcare and AI SaaS
AWS Certified Security Specialist15+ years
  • Leads engineering as CTO of Maxiom Technology
  • Builds HIPAA and GDPR compliant digital health products
  • Platforms serving clients in the USA, UK, and Europe
  • Cloud on AWS, Kubernetes, and Terraform
Pune, India and Austin, TX

Nik Kalyani

Fractional CTO
Zero-to-one platforms and protocol architecture
Founder25+ years
  • Founder of Xibit and Vitruveo
  • Hands-on architect of L1 and L2 protocols and production smart contracts
  • Scaled systems across distributed teams for 25+ years
  • Zero-to-one product development
California

When a review needs more hands, Maxiom engineers in Ashburn, VA do the work under your CTO's direction. Same standards, same owner.

Meet Maxiom
FAQ

Straight answers.

Do you recruit the next hire?

No. 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.

Will you tell us to wait on a lead?

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.

Will you install a new process?

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.

What does code ownership mean here?

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.

Do you certify the team, the process, or compliance?

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.

How is this different from the other CTO 2.0 pages?

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.

How do we start?

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.

Also on CTO 2.0
30 minutes

Tell us who is on the team.

The people you have, the hire you are considering, and what is stuck. You leave with a clear yes or no.

Book a time →