The most expensive slide in the deck
Sessions 1 to 3 built the case for DataOps and showed you what maturity looks like. This one asks the question that follows: what do we actually stand up, and who do we pay? It is a deciding session, so we treat it with care. The wrong platform bet is not fatal, but it is slow and costly to unwind - which is exactly why vendors want the decision made fast and emotionally. Your job is to slow it down and score it.
Three doors, three bets 10 min live
Every platform decision, under the branding, is one of three doors. Each door is a legitimate choice. What matters is knowing which tradeoff you are making with your eyes open, because you cannot optimise for control, speed, and cost all at once - pick two and the third gives way.
LiveWhich door fits which organisation4 min▶
The right door depends less on your data and more on your team and your appetite for owning infrastructure. A concept to hold onto: you are not buying software, you are buying a relationship with a set of tradeoffs that will outlast the person who signed the contract.
- Build your own suits a small number of organisations - usually those where data infrastructure is the product, or where scale and specificity make every managed option a bad fit. It buys maximum control and pays for it in engineering years and key-person risk.
- Buy managed - Databricks, Snowflake, a managed cloud platform - suits most organisations that need value quickly and would rather rent expertise than build it. It buys speed and simplicity and pays for it in licence cost and lock-in.
- Blend with open-source suits teams strong enough to run infrastructure but unwilling to reinvent everything. It buys flexibility and cost control at scale and pays for it in the ongoing operational load of running the stack yourself.
OSS stack vs managed - the honest cost picture 10 min live
The sticker price is the smallest part of the story. An open-source stack looks nearly free because its cost is in people and operations, which never appear on the licence line. A managed platform looks expensive because its cost is all on the invoice. Real total cost of ownership adds the hidden lines back in.
| Cost driver | Open-source stack (Airflow · dbt · Great Expectations · MLflow · Postgres) | Managed platform (Databricks · Snowflake · managed cloud) |
|---|---|---|
| Licensing / subscription | Low - the software is free to use | High - you pay per compute, seat, or credit, every month |
| Engineering time to run it | High - your team installs, upgrades, patches, and babysits the stack | Low - the vendor runs the platform so your team runs pipelines |
| Time to first value | Slower - assembling and hardening the pieces takes months | Faster - live in weeks, value while you are still hiring |
| Lock-in / exit cost | Low - open standards, portable, you can leave | High - proprietary formats and pricing make leaving expensive |
| Talent market | Widely known open tools - easier and cheaper to hire for | Platform-specific skills - fewer people, premium salaries |
| Cost shape | Mostly fixed people cost - flat as data grows | Mostly variable usage cost - rises with every query and terabyte |
LiveWhy the crossover is really about your team3 min▶
The crossover point is not a fixed law of physics - it moves with your organisation. The single biggest lever is whether you already have, or can hire and keep, a team capable of running open infrastructure well.
- Strong platform team, large data volumes: the crossover comes early. Usage fees on a managed platform grow with every terabyte, while your OSS people cost stays roughly flat. At scale, open-source wins clearly.
- No dedicated platform team: the crossover may never arrive. The "free" software still needs paid humans to run it, and if those humans are firefighting the stack instead of shipping value, managed was cheaper all along.
- The trap: counting only the licence line. Leaders adopt open-source to save money, forget to fund the operations, and end up with a fragile stack and a burned-out team - the reliability tax from session 1, self-inflicted.
The startup that went "free" and paid double. A mid-size firm ripped out its managed warehouse to run open-source and cut the invoice in half - then quietly hired three platform engineers to keep it standing and lost two quarters of roadmap to the migration. The licence line fell; total cost rose. Open-source is only cheaper when the team to run it is a decision you make on purpose, not a cost you discover afterwards.
The one-platform bet 6 min live
Whichever door you choose, a second decision follows: converge on one governed platform, or let a tool zoo grow. Teams accumulate tools the way garages accumulate boxes - each one solved a real problem at the time, and together they become impossible to govern. The one-platform bet is the deliberate choice to consolidate.
Self-studyThe case for one platform - and its risk3 min read▶
Converging on one governed platform - one orchestration shell where pipelines run, quality is checked, and access is controlled - pays off in three ways that compound:
- Fewer integrations to maintain. Every tool-to-tool seam is a place data breaks and someone has to fix. Consolidation removes seams, and removed seams cannot fail.
- One place to govern. Access control, lineage, quality gates, and audit are enforceable when there is a single control point. In a tool zoo, governance is a policy nobody can actually see across.
- Easier onboarding. A new hire learns one platform, not seven half-documented tools that each live in a different person's head - which is the resilience-to-turnover argument from session 1.
Score-the-option ★ 12 min · scorecard together
Instead of arguing about the platform, score it. Take your leading option - or all three doors - and rate each against five factors on a simple 1-to-5 scale. The scoring matters less than the conversation it forces: where you disagree is where the real risk lives.
Write your candidate options across the top: build-your-own, buy-managed, and blend-with-open-source. Even if you think you know the answer, score all three - the loser sometimes surprises you.
Score each option 1 to 5 on control: how much can we shape the platform to our needs, without waiting on a vendor's roadmap?
Score each on speed: how fast do we get to first real value - weeks, quarters, or a year?
Score each on total cost (not licence cost - people plus ops plus licence), and on talent: can we realistically hire and keep the team this option needs?
Score each on lock-in: how expensive would it be to leave in three years? Total the columns, then talk about the factor where the room disagreed most. That disagreement is your real decision.
The bank that scored its way out of a bad default. A data leader walked in certain they would build their own platform for "control". The scorecard showed control at 5 but talent at 2 and speed at 1 - they could not staff it and would lose a year. Buy-managed scored lower on control but far higher everywhere it mattered. They bought, shipped in a quarter, and kept the blend door open for later. The scorecard did not make the decision - it made the tradeoff impossible to ignore.
★ Questions to ask your data team
- "If we go open-source, who runs it - and have we funded that team, or just assumed it?" The unfunded ops team is the most common way "free" software becomes the most expensive option.
- "What is our real total cost of ownership - licence plus people plus operations - not just the invoice?" If the answer is only the subscription number, the analysis is not finished.
- "How expensive would it be to leave this vendor in three years?" The exit cost is the true measure of lock-in, and it is cheapest to ask about before you sign.
- "Are we converging on one governed platform, or quietly growing a tool zoo?" If every team picks its own tools, nobody can govern or onboard across them.
- "Where would over-centralising hurt us - which domain genuinely needs to move differently?" This keeps convergence from hardening into a bottleneck.
What this session covers
This session draws on the platform-strategy literature and the total-cost-of-ownership debates around managed data platforms versus open-source stacks. This page covers:
Three questions before you go 🎯 ◐ 90 seconds
1 · The main reason an open-source stack can end up more expensive than a managed platform is...
Open-source moves cost from the invoice to your payroll. If the team to run it is not funded on purpose, total cost of ownership can exceed managed - especially without scale.
2 · The TCO "crossover point" between managed and open-source depends most on...
Managed is usually cheaper early; open-source can win at large scale where usage fees dominate - but only if a capable platform team exists to run it. No team, no crossover.
3 · The one-platform bet trades a tool zoo for one governed platform. Its main risk is...
Convergence gives fewer seams and one place to govern, but pushed too far it creates a rigid bottleneck. The aim is one governed platform with room for domains to move.