The Build-or-Buy Decision Has Become Too Easy
For most of the last decade, the cost of building forced a pause. A team that wanted its own deployment dashboard or secrets workflow had to justify weeks of engineering time, and that justification usually surfaced the real question: does this capability make the business different, or does it simply need to work?
Coding tools have collapsed that cost. As The New Stack’s analysis of the Octopus findings put it, the effort of writing code has largely disappeared while the effort of owning it remains. Maintenance, upgrades, security patches and governance all arrive the day after launch, and they grow with every feature a team decides to build for itself.
High Performers Buy More Than They Build
The report’s most practical finding is how the strongest teams behave. Adopting an existing tool was the most common primary approach across the features platform teams own, ahead of building on a template or from scratch, and high performers leaned even further toward established tools.
Their reasoning was rarely ideological. The most common explanation was a cost-benefit analysis, followed by a preference for open source and a fit-and-requirements assessment. One respondent summarized the logic as building what makes the company unique and adopting what is standard, while keeping long-term cost and lock-in in view.
Custom Work Should Earn Its Place
Pablo Gerboles Parrilla, who founded Alive Devops after years of building software for clients across industries, has a blunt view of how engineering partners should approach requests. “We don’t just build what clients ask for, we build what their business actually needs,” Gerboles Parrilla said. “Most dev firms are order-takers.”
The same standard applies inside a company. A platform team that builds every request it receives is functioning as an internal order-taker. A team that asks what the business needs first will often discover that a mature tool already solves the problem, and that the scarce engineering hours belong somewhere customers will notice.
Strategy Gaps Show Up as Maintenance Debt
The cost of building without a clear reason rarely appears in the sprint where the feature ships. It shows up six months later, when the engineer who built the custom incident tool has moved to another project and nobody else understands its configuration. It shows up again during the next framework upgrade, when the homegrown component blocks the migration.
The Octopus data points in the same direction. Teams building mostly from scratch were more likely to lean on AI for legacy modernization and language migration, which suggests the work that follows a custom build is where those teams spend their energy. For small and mid-sized companies, that maintenance burden lands on the same handful of engineers expected to ship product.
Small, Deliberate Tools Beat Sprawling Platforms
None of this argues for buying everything. Some capabilities, such as local development environments and golden-path project templates, are tightly bound to a company’s stack and benefit from custom work. The report found these features skewed toward templates for exactly that reason.
Gerboles Parrilla’s advice to smaller companies has always favored restraint. “You don’t need a massive system overhaul,” he said. “Sometimes the best automation solutions are small, simple tools that make a huge difference.” That philosophy runs through the DevOps consulting work his team takes on, where the first deliverable is often a decision about what not to build.
A Better Starting Question for Platform Teams
The more useful question is whether the team can explain, in a sentence, why a given capability deserves custom code. If the answer involves competitive differentiation or a constraint no available tool handles, building may be right. If the answer is that building was faster this week, the team is borrowing time from its future self.
Platform teams that write down that reasoning before they start tend to make fewer reversals later. The written rationale also helps new engineers understand which parts of the platform are strategic and which are simply plumbing. A one-page decision record kept next to the code is usually enough. It should name the capability, the alternatives the team considered, the reason for building and the person who will maintain the feature after its original author moves on.
Discipline Matters More When Building Is Cheap
For a self-funded tech founder like Gerboles Parrilla, every engineering hour has a direct cost, which is part of why his companies have stayed lean while growing. Cheap code does not change that math, because ownership still costs what it always did.
The platform teams that pull ahead over the next few years will be the ones that treat easy building as a reason to slow down the decision. They will build less, buy deliberately and keep their custom work focused on the small set of capabilities that actually set their business apart.
