You nailed it, Chris. Vibe code is really the low-end, questionable-quality solution that, if iterated on correctly, will replace certain SaaS categories. If not because of the technology advantage, then because of the financial rationale. An enterprise-developed vibe app is a capitalizable asset, whereas a SaaS subscription is an operating expense. That's why the CFO is probably more important than the CIO/CTO in determining whether vibe-coded AI gets traction in the enterprise:
Great question! Generally speaking - yes. Having a data lake doesn't eliminate the need for system(s) of record.
A data lake serves as a repository for analyzing data and maintaining a historic archive for permanence, rather than a platform for acting on it in real-time. Because of this, you still need "systems of record" (like Salesforce) to support the essential, day-to-day operations of the business.
Think of the data lake as the place for answering complex questions and looking at long-term trends, while the systems of record remain the engine(s) for your daily workflows. Different SORs typically support different functions (i.e. Sales, HR, Finance, etc...) - but can then all integrate and archive to the same data lake for analysis.
Happy to have a follow-up discussion on this if you'd like to dive deeper!
You nailed it, Chris. Vibe code is really the low-end, questionable-quality solution that, if iterated on correctly, will replace certain SaaS categories. If not because of the technology advantage, then because of the financial rationale. An enterprise-developed vibe app is a capitalizable asset, whereas a SaaS subscription is an operating expense. That's why the CFO is probably more important than the CIO/CTO in determining whether vibe-coded AI gets traction in the enterprise:
https://www.linkedin.com/pulse/enterprise-ai-asset-saas-expense-tim-jones-d9qpe/?trackingId=IuAiW9r6TOuF9NUfjcKZaA%3D%3D
Excellent post. Spot on.
If you have a data lake with (in theory) all of the data, do you even need a “system of record” like SF eventually?
Great question! Generally speaking - yes. Having a data lake doesn't eliminate the need for system(s) of record.
A data lake serves as a repository for analyzing data and maintaining a historic archive for permanence, rather than a platform for acting on it in real-time. Because of this, you still need "systems of record" (like Salesforce) to support the essential, day-to-day operations of the business.
Think of the data lake as the place for answering complex questions and looking at long-term trends, while the systems of record remain the engine(s) for your daily workflows. Different SORs typically support different functions (i.e. Sales, HR, Finance, etc...) - but can then all integrate and archive to the same data lake for analysis.
Happy to have a follow-up discussion on this if you'd like to dive deeper!