How a Healthtech CTO Scaled to 100 Engineers Without Tripling Meetings (Composite)

This post describes a hypothetical scenario based on common patterns we observe in distributed engineering teams. It is not a specific customer. Details have been generalized, and the outcomes are framed in directional terms rather than as precise measurements.

The CTO in this composite leads a healthtech engineering organization that grew from 40 engineers to 100 over an 18-month period. The growth was funded by a Series C and concentrated in two areas — a new platform team to support a hospital integrations product, and a clinical-AI team focused on a diagnostics adjacency. The company was distributed across US East, US West, and Western Europe.

The structural problem

Engineering organizations typically experience meeting load growth at roughly 1.5 times the headcount growth rate during scaling phases. The CTO's own calendar had previously expanded to about 30 hours of weekly meetings; if the organization grew 2.5x without intervention, the CTO's calendar was on track to break entirely, and the engineering managers below would experience the same dynamic at their level.

The compounding factor was the healthtech regulatory frame. Decisions needed to be traceable; engineering changes that touched the hospital integrations product required a particular audit posture; the on-call rotation across time zones was non-negotiable. The team could not respond to scaling by relaxing the coordination discipline. The discipline had to scale with the headcount, ideally with less meeting overhead per engineer rather than more.

The intervention

The CTO made wrap-based coordination a hiring-and-onboarding expectation from the first day of the scaling phase. New engineers were trained to write wraps as part of their first-week ramp, and to query the Representative for context before pinging a teammate. Existing engineers ran scoped Representatives for their areas, which absorbed routine questions from the new hires.

The CTO also instituted a meeting policy that pre-empted the typical scaling failure mode: no recurring meeting could be added to anyone's calendar without explicitly retiring an existing meeting or demonstrating that the new meeting could not be replaced by a wrap-and-query interaction. The policy was applied to the CTO's own calendar first as the demonstration case.

The directional results

Eighteen months into the scaling phase, the team reported the following directional outcomes. The CTO's weekly meeting load grew from 30 hours to roughly 34 hours — a small increase rather than the predicted 50 to 75 hours. The average engineering manager's meeting load grew from about 15 hours per week to roughly 18 hours. The total engineering meeting overhead, expressed as a percentage of engineering time, remained roughly flat, which was a significant outcome at this scale.

The audit posture held throughout the scaling phase. The wrap layer produced a traceable record of engineering decisions and working state, which the compliance team referenced during two audit windows that fell inside the scaling period. The compliance team's working relationship with engineering, which had historically been strained because engineers viewed compliance as a productivity tax, improved measurably — engineers cited the lighter audit-prep load as the main reason.

The friction the team did not anticipate was at the engineering-manager-hiring layer. Several externally-hired managers came in with a Scrum-and-OKR mindset and tried to layer additional ceremonies on top of the wrap discipline. The CTO had to coach these managers to reduce ceremonies rather than add them; one ultimately left over the cultural mismatch.

What the CTO would do differently

The retrospective surfaced three lessons. First, hire engineering managers whose first instinct is to remove process, not add it; the cultural fit at the manager level determined whether the scaling worked. Second, train new hires on the wrap discipline in their first week, not their first month — the habits set in the first week persist. Third, treat the audit posture as a feature of the coordination layer, not a separate compliance project; the integration is what kept the cost flat.

Frequently asked questions

Is this a real healthtech?

No. This is a composite based on common patterns we observe in healthtech engineering organizations that scale rapidly under regulatory constraints. The structural pattern — declared state as both coordination and audit infrastructure, hiring-stage cultural fit on managers, meeting policy as a forcing function — is what we see consistently.

Can any engineering org grow 2.5x without growing meeting load?

Not without intentional design. The default is that meeting load grows faster than headcount during scaling phases. Holding it flat requires both a coordination layer that absorbs routine questions and a leadership commitment to not adding meetings as the first response to new coordination needs.

What about the engineering managers' team-level meetings?

Squad-level meetings stayed similar in shape — one weekly synchronous touchpoint per squad — but standups were retired. The engineering manager spent more time reviewing wraps and querying Representatives, and less time facilitating standup conversation. The trade was favorable at this scale.