Loading today’s stories
Build1 distinct publisher3 min readUpdated
A vendor-adjacent staffing model prices a do-it-yourself internal developer platform at 60 people and $7.5M a year. The arithmetic it leaves out sits on both sides of the trade.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
The 60 is an org chart before it is an engineering estimate. Seven product functions, at seven to nine engineers each, with a couple of scrum masters and product owners on top [3][4]. Divide the payroll by the heads and you get $125,000 on the nose [1], which tells you what the model does not carry: no benefits or employer tax load, no tooling budget, no cloud bill, and no premium for the coordinators over the engineers. The real annual number is above $7.5 million, and this model cannot tell you by how much.
The version executives approve is one team, weekend work, a control plane with some YAML over it [7]. Against the scoped organisation, that is 12 to 15 percent of the headcount [2]. One of seven functions gets funded and the other six do not stop existing. They land on the person in each development group who does the glue between the platform and the applications, which is the line the business case spreadsheets do not have [12].
The buy side of the comparison is softer than the build side. The collected ratios include 45 app teams to 5 operators in one shop and 300 app teams to 4 in another [10], which is 9 teams per operator against 75, a factor of 8.3 between two samples measured the same way [3]. Per developer it runs 200 to one at the tightest and 500 to one at the loosest [4]. Sizing an operate team off these means deciding which sample you believe before you start.
The piece stops one line short of the arithmetic that settles it. Five operators at its own $125,000 figure cost $3.125 million over five years, against $37.5 million of build payroll [6], leaving roughly $34.4 million of room for licenses, support and migration before buying stops winning [5]. That is the number the vendor paper would have to fill in, and the published version does not [6]. The ceiling is generous enough that most contracts fit under it, which is presumably why the calculation runs in this direction.
Both sides have a thumb on the scale. The figures come from a VMware Tanzu Platform paper the author helped update, and he flags it in his second paragraph [8]. The counterweight is that engineers get promoted for shipping platforms, and "we shipped a platform built on Kubernetes" reads better in a packet than "we onboarded everyone to a thing we paid for" [14]. What survives both incentives is the structure. Seven functions have to be staffed whether or not anyone named them in the proposal, and the glue people are already on payroll under other titles [12].
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
Most executives signing off do not see the total, because it is spread across multiple cost centers under "engineering".
Aligning a platform team with something like the CNCF platform reference architecture produces about seven product teams: infrastructure, operations, deployment, runtime and middleware, database, security, and coaching/developer enablement.
Each of those teams is a two-pizza team of 7 to 9 engineers, and adding a couple of scrum masters and product owners brings the total to about 60 people.
The author states the numbers come from a recent VMware Tanzu Platform paper he helped update, and tells readers to flavour them with vendor salt.
The visible cost of a commercial platform is one license number on one purchase order, while build-your-own headcount is spread across cost centers, often done in the shadows, and looks like normal hiring, so nobody sums it.
The cheap version of the pitch executives hear is one team, weekend work, and a control plane with a bit of YAML on top; it ships v1 and becomes a maintenance burden nobody wants to own.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Single vendor-adjacent source; arithmetic checkable, inputs not
One article carries the entire cluster, and it discloses that its central numbers come from a VMware Tanzu Platform paper the author helped update. The internal arithmetic is verifiable (60 x $125,000 = $7.5M; $37.5M over five years; a 7-9 person team is 12-15 percent of 60), but the inputs are not: the operator ratios are anonymous and undated, the shadow-platform claim rests on unquantified conversations, and the resume-driven-development study is referenced without title or authors. No independent data corroborates the 60-person model.
No dated deployment or usage disclosure in the cluster
The supplied material contains no release, deployment, benchmark, pricing or named usage disclosure. The only quantities resembling adoption are anonymous developer-to-operator ratios collected by the author over an unspecified period, with no organisation, product or date attached, which cannot be treated as observed adoption.
Precision on the build side, silence on the buy side
The claims run ahead of the evidence in a specific, measurable way: build cost is stated to the dollar ($7.5M/year, $37.5M/five years) while the recommended commercial alternative carries no price at all, leaving roughly $34.4M of five-year headroom unexamined. The salary-only model excludes benefits, tooling and infrastructure, and the operator ratios offered as the counterfactual vary by up to 8.3x within the same unit. The vendor provenance is disclosed, which restrains the score from going higher.
Disclosed vendor origin behind a buy recommendation
The author states the figures come from a recent VMware Tanzu Platform paper he helped update, and the same paper supplies the 12-18 month velocity-gap claim; the article's conclusion favours buying a commercial platform. The commercial interest is therefore direct and load-bearing on both sides of the comparison. Disclosure is explicit and pre-emptive, which is why this is scored as a transparent rather than concealed incentive.
High confidence in the gaps, low in the magnitudes
What is checkable is checkable with certainty: the provenance disclosure, the absence of any license price, the salary-only construction of $7.5M, and the dispersion inside the operator ratios all read directly off the text. What cannot be assessed from one vendor-adjacent source is whether 60 people is the real cost of a working platform for any given organisation, or whether the buy side clears the roughly $34.4M of headroom the article leaves open.
build
Per-developer environments hit their ceiling the day one engineer ran five agents1 distinct publisher
build
Ten of the twelve agentic AI terms are renames. Two of them are your problem1 distinct publisher
product
Kyverno sits on the security budget line, and three of its four verbs go unused1 distinct publisher
product
Contract expiry, not architecture, moved 1,500 State Farm workloads in ten months1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 21, 2026