Owning Your Tech Stack Is the New Owning the Means of Production

The honest answer

If the platforms you depend on changed their pricing tomorrow, how much of your revenue would be at risk?

If the answer is more than 20 percent, you do not own your business. You rent it from the platforms.

This is not a new observation. Marx noted that ownership of the means of production determines who captures value. The means of production in a digital business in 2026 are not factories and machines. They are the software systems, data pipelines, and workflow infrastructure that create and deliver the product. The question is the same as it was in the 19th century: who controls the means? Who captures the surplus?

Platform-dependent businesses answer: the platform. Stack-owning businesses answer: the business. The compounding difference between those two answers, sustained over five to ten years, is the difference between a business and a perpetual licensing arrangement.

The platform dependency trap

Platform dependency is not inherently bad. Every business uses platforms. The question is at what layer of the stack the dependency sits.

A dependency on AWS for compute infrastructure is relatively safe. AWS pricing is stable, predictable, and competitive because of market structure. Switching costs are high but manageable for a technically capable team.

A dependency on a single social platform for distribution is dangerous. Meta has changed organic reach mechanics at least six major times since 2012. Each change transferred value from businesses that built on Meta's organic reach to Meta's advertising revenue. The businesses that did not own an email list or a direct channel lost that audience permanently.

A dependency on a platform-specific tool for core client delivery is the most dangerous. If your agency's entire SEO workflow runs on a single tool that changes its pricing or discontinues a feature, the cost flows to your gross margin immediately. You have no negotiation leverage because the cost of switching mid-engagement is your client relationship.

The platform makes this bet easy to ignore because the day-one cost of platform adoption is low. The API is free to start. The tool has a monthly plan. The integration takes a weekend. The long-term cost — the years of pricing increases, feature deprecations, and terms changes — accrues slowly and invisibly until it is too large to reverse without rebuilding from scratch.

What stack ownership actually means

Owning your stack does not mean building everything from scratch. It means owning the layer of the stack that is specific to your business.

The commodity layers — compute, storage, email delivery, authentication — are not worth owning. They are cheap, well-maintained, and switching-cost manageable. Use the best vendor and move on.

The proprietary layers — the logic that makes your delivery unique, the data that reflects your client relationships, the workflows that encode your institutional knowledge — are worth owning.

For a digital agency in 2026, the proprietary layer includes:

The delivery pipeline. The sequence of steps from client onboarding to deliverable handoff. If this pipeline runs on a platform that owns the workflow definition, a pricing change or terms update can affect every client engagement simultaneously. If the pipeline runs on code you own, you control the change surface.

The client data model. The structured history of what you have delivered, what worked, and what did not. This data is the raw material of every improvement to the delivery model. If it lives in a third-party CRM under a subscription that can be revoked, you are a data breach or a pricing dispute away from losing the institutional knowledge of the entire business.

The AI inference layer. In 2026, most production AI workflows run on API calls to foundational models. The specific model version, the prompt engineering, and the output post-processing are proprietary. The foundational model is not. Owning your AI layer means owning the orchestration, the prompts, and the evaluation framework — not building a foundational model yourself.

The compounding advantage of stack ownership

Every improvement to a platform-owned workflow improves the platform. Every improvement to a stack-owned workflow improves the business.

This is the compounding mechanism. Over three to five years of incremental improvements to a delivery pipeline you own, the pipeline becomes meaningfully more efficient, more reliable, and more capable than what any platform can offer as a general solution. The improvements are specific to your clients, your delivery patterns, and your team's strengths. The platform cannot replicate them because the platform serves thousands of businesses, not yours.

First Round Review's 2024 research on technology-enabled services firms found that companies with proprietary technology layers in their delivery stack commanded acquisition multiples 2.3 times higher than comparable firms with purely platform-dependent delivery. The multiple reflects the permanence of the asset — a custom stack cannot be replicated by hiring away a team. It has to be built from scratch (per First Round Review, 2024).

The compounding also operates in client retention. A client whose delivery runs on your proprietary pipeline has a switching cost that a client served through commodity platforms does not. Not because you have designed the stack to create lock-in — the goal is not to trap clients — but because the institutional knowledge encoded in the pipeline is not transferable to a competitor without rebuilding.

AI makes ownership more accessible

The economics of custom stack ownership changed materially in 2023 and 2024.

Before large language models were accessible via API, maintaining a custom delivery pipeline required a standing engineering team of 5 to 10 people. The cost was prohibitive for agencies under $10 million in revenue.

In 2026, a team of 2 to 3 engineers with access to foundational model APIs can maintain a sophisticated custom delivery pipeline. The AI handles the cognitive tasks that previously required specialists. The engineers maintain the orchestration and the evaluation framework. The agency owns the output.

This is the structural shift. Stack ownership, previously reserved for well-funded technology companies, is now accessible to agencies at the $1 million to $5 million revenue level. The agencies that recognize this early and invest in custom stack development are building moats that platform-dependent competitors cannot close without making the same multi-year investment.

Anthropic's published research on AI deployment in professional services notes that the highest-leverage AI implementations in 2024 and 2025 were not off-the-shelf tools applied to existing workflows but custom integrations that embedded AI into proprietary delivery pipelines (per Anthropic, 2024). The leverage comes from the integration, not from the model.

The practical argument for staying on platforms

I want to be honest about the counterargument, because it is real.

Platform dependency is operationally faster. A well-designed SaaS platform handles provisioning, security updates, compliance, and uptime that a custom stack requires you to manage. The opportunity cost of building custom infrastructure is the feature development you are not doing.

For most agencies under $2 million in revenue, the opportunity cost argument is probably correct. Build on platforms. Move fast. The switching cost of rebuilding on owned infrastructure later is real but manageable.

The calculation changes above $2 million in revenue, when the platform costs are material and the delivery pattern is stable enough that a custom pipeline would not require constant rebuilding. Above that threshold, the compounding from stack ownership starts to outweigh the operational convenience of platform dependency.

What this means in practice

Look at the software your agency pays for each month. Identify the tools where (a) the vendor could raise prices by 30 percent and you would have no alternative but to pay, and (b) the workflow is specific to how you deliver your service, not generic.

Those are the dependency risks worth resolving. Not by ripping and replacing immediately, but by identifying the proprietary workflow logic embedded in each tool and asking: can we encode this logic in something we own?

For most agencies, the first custom build worth making is the client data model — a structured database of delivery history, client context, and performance data that lives in your systems, not in a third-party CRM. The second is a lightweight automation for the most repetitive delivery tasks. The third is an evaluation framework for any AI outputs that touch client work.

Each of those three is a step toward owning the means of your production. Each step compounds. The compounding is slow at first and then, as Naval would put it, irreversible.

See striveloom.com/case-studies for examples of how we have applied this framework to our own delivery stack and to client technology builds. The pattern is consistent: own the proprietary layer, use platforms for the rest, and compound the proprietary layer every quarter.