Systems | Development | Analytics | API | Testing

Most data warehouse projects fail. Not because the technology is wrong. Because the design is. Three weeks for a number that should take three minutes. AI agents generating plausible reports nobody can trace. Two ERPs naming the same metric differently. The spreadsheet swamp. The fire drill before every audit. These problems live in the warehouse layer, in how data is modeled, governed, and made available to the people and AI agents that read from it.

These terms show up in every other LinkedIn post about AI. Everyone uses them slightly differently. So here's how we think about them at Keboola, and what they look like in practice.

Every enterprise AI story right now follows the same plot. You pick a system — Salesforce, Workday, SAP, NetSuite — and you bolt an AI agent on top of it. The agent can summarize deals. It can write follow-up emails. It can pull a report without you clicking through five dashboards. It is genuinely useful. And it is not transformation. What you have built is a smarter interface on top of a system designed for humans.

Earlier this year we started asking a simple question to finance leaders we met at events, on calls, and in roundtables: where do you actually start with AI in finance? The answers were consistent enough that we decided to do something about it. We invited 30 CFOs, finance directors, and finance managers to a business breakfast at our Prague office. A morning with peers who are all trying to answer the same question: where do I actually start?