When SAP announced the acquisition of Prior Labs and committed more than one billion euros over four years to scale it into a frontier AI lab, the immediate reaction across the DACH technology press was predictable: another large-scale AI acquisition, another press release about the transformative power of artificial intelligence. The deeper signal — the one that matters for enterprise AI architecture — was buried beneath the headline number.
SAP's CTO put it plainly: the greatest untapped opportunity in enterprise AI was not large language models. It was AI built for the structured data that runs the world's businesses. That sentence should change how every SAP-centric company in the DACH region thinks about its AI roadmap.
The problem that most enterprise AI ignores
The AI conversation of the past three years has been dominated by large language models. GPT, Claude, Gemini, Llama — the frontier models that generate text, summarise documents, answer questions, and hold conversations. These models are extraordinary at processing natural language. They are also, by design, built for sequential token prediction on unstructured data. Feed them a well-written paragraph and they produce remarkable results. Feed them a table with 40 columns and 100,000 rows of financial transactions and they produce something far less useful.
This is not a criticism of LLMs. It is a statement of architecture. Language models process text as a sequence of tokens. A table is not a sequence — it is a matrix of typed values where the relationship between column 3 and column 27 may be more important than the relationship between adjacent cells. The statistical patterns in a payments table — which customers pay late, which suppliers carry risk, which product lines are trending upward — are fundamentally different from the patterns in a paragraph of English prose.
SAP's own internal assessment was blunt: large language models have only a rudimentary understanding of tables, numbers, and statistics. Anyone who has tried to get a language model to reliably predict churn from a customer transaction table, or to detect anomalies in a financial dataset, knows this is accurate. The models can describe the table. They can write SQL to query it. But they cannot natively learn the predictive patterns within it the way a purpose-built model can.
This matters because the overwhelming majority of enterprise data is tabular. ERP systems, CRM databases, financial ledgers, supply chain records, production logs, HR systems — the operational backbone of every DACH enterprise is structured data in rows and columns. And the AI models that dominated the last cycle were not built for it.
What tabular foundation models actually are
Prior Labs, founded by Frank Hutter, Noah Hollmann, and Sauraj Gambhir, built a class of models specifically designed for tabular data. Their TabPFN model series, published in Nature and validated across hundreds of independent academic studies, set the state of the art on tabular prediction benchmarks. The team — recruited from Google, Apple, Amazon, Microsoft, and Jane Street — represents one of the deepest concentrations of tabular ML expertise assembled anywhere.
A tabular foundation model (TFM) works differently from a language model. Where an LLM is pre-trained on vast text corpora and learns to predict the next token, a TFM is pre-trained on millions of diverse tabular datasets and learns to recognise the structural patterns that recur across tables: correlations between features, non-linear relationships, missing-value patterns, distributional shifts. The model learns what tabular data looks like in general before it ever sees your specific business data.
This pre-training on diverse tables gives TFMs a property that traditional machine learning lacks and that LLMs cannot replicate: strong performance on small datasets. A classical ML pipeline — gradient-boosted trees, random forests, neural networks — requires substantial training data to learn domain-specific patterns from scratch. Hundreds of thousands of rows, sometimes millions, before the model becomes reliable. A TFM arrives with structural intuitions already in place. It has seen enough tables to know that a column with high cardinality and low variance probably behaves differently from one with low cardinality and high variance. Fine-tuning on a few hundred rows of your specific data is often sufficient to produce accurate predictions.
For enterprise contexts where labelled data is scarce — a new product line with three months of sales history, a recently onboarded supplier with limited performance data, a market segment you are just entering — this changes what is possible.
Why SAP is making this bet now
The acquisition is not happening in isolation. SAP also acquired Dremio, a data lakehouse platform, in the same period. The combined signal is clear: SAP is building a vertically integrated stack where the data layer (Dremio and SAP Datasphere), the AI layer (Prior Labs and the existing SAP-RPT-1 tabular model), and the application layer (S/4HANA, Joule, and the SAP Business Technology Platform) are designed to work together.
This is architecturally significant because it addresses the integration gap that has plagued enterprise AI adoption. Today, a DACH manufacturer that wants to predict supplier delays needs to extract data from SAP, transform it into a format suitable for a third-party ML platform, train a model, deploy it somewhere, and then pipe predictions back into SAP. Each step introduces latency, complexity, and failure modes. If TFMs ship embedded within the SAP stack, the prediction capability sits where the data already lives.
SAP's CTO explicitly positioned this against the conversational AI trend. Joule — SAP's conversational assistant — handles the text-based, question-answering layer. But predictions on structured data require purpose-built models, not chatbots repurposed as analysts. Payment delay prediction, customer churn scoring, demand forecasting, supplier risk assessment, credit scoring, anomaly detection in financial data, upsell opportunity identification — these are tabular prediction problems, and SAP is betting that solving them natively will be worth more to its customer base than any number of conversational features.
The timing also reflects competitive positioning. Microsoft has Copilot across its stack but no equivalent tabular AI investment. Salesforce has Einstein but it operates on CRM data, not the full ERP footprint. Oracle has its own AI ambitions but has not made a comparable tabular-specific move. SAP is staking out a position as the enterprise vendor that takes structured data prediction seriously — and for the 77 percent of global transaction revenue that touches an SAP system, that position has considerable weight.
What this changes for DACH enterprises
For companies running SAP as their operational backbone — which describes most large and many mid-sized DACH enterprises — the implications are both strategic and architectural.
The AI architecture question shifts. The prevailing pattern for applying AI to structured enterprise data has been to build RAG pipelines — extract data from SAP, embed it, store it in a vector database, and let an LLM query it. This works for answering questions about the data. It does not work for making predictions from the data. A RAG pipeline can tell you what last quarter's payment patterns looked like. A TFM can predict which invoices will be paid late next quarter. These are fundamentally different capabilities, and the architectural decisions an enterprise makes today — which systems to integrate, which data pipelines to build, which model infrastructure to invest in — should account for both.
The build-versus-buy calculus shifts. If SAP embeds TFM capabilities directly into S/4HANA and the Business Technology Platform, the case for building custom tabular ML pipelines weakens for use cases that SAP's models cover well. The build-versus-buy decision becomes: where do we need custom prediction models tailored to our specific competitive advantage, and where can we rely on SAP's embedded capabilities for standard operational predictions? This is the same logic that applies to any platform capability — you build where differentiation matters and buy where standardisation is acceptable.
Model selection becomes more nuanced. The enterprise AI landscape is no longer just about choosing between LLM providers. As we outlined in the model comparison framework, different model categories serve different purposes. LLMs handle text and conversation. Small language models handle narrow NLP tasks efficiently. TFMs handle tabular prediction. The right architecture uses each where it excels — not a single model type for everything. Enterprises that treat all AI as a language model problem will underinvest in the structured-data prediction capabilities that often deliver the highest operational ROI.
Data quality becomes even more critical. TFMs are pre-trained to handle messy tabular data better than traditional ML — they have seen missing values, inconsistent formats, and noisy labels across millions of training tables. But "better than traditional ML" does not mean "immune to garbage." The data quality dimensions that determine AI success — completeness, consistency, currency, accuracy, and structure — still apply. A TFM will not fix a master data problem where "Siemens AG" appears as five different entities across your SAP modules. It will simply make five separate predictions for what should be one customer.
Vendor selection for the AI stack requires re-evaluation. For SAP-centric organisations, the vendor selection process must now account for SAP's emerging AI capabilities alongside third-party options. Committing to a separate tabular ML platform today may create redundancy if SAP delivers equivalent capabilities natively within 18 months. Conversely, waiting for SAP may mean losing 18 months of competitive advantage from predictions you could be making now. The right approach is to build on standards — clean data, well-defined prediction tasks, documented feature pipelines — that transfer across platforms regardless of which vendor ultimately runs the model.
What to do now
The acquisition is expected to close in Q2 or Q3 2026. Prior Labs will continue operating independently, and the integration into SAP's product suite will take time. Production-ready TFM capabilities embedded in S/4HANA are unlikely before late 2027. That gives enterprises a window — not to wait, but to prepare.
Understand the distinction between LLMs and TFMs. These are not competing approaches. They solve different problems. If your current AI roadmap treats all AI as a language model problem, it has a gap. Map your use cases explicitly: which ones require text processing (LLM territory), which ones require prediction from structured data (TFM territory), and which ones require both?
Assess your data layer. TFMs need clean, accessible tabular data. The same context layer that feeds any AI workflow — accessible data, consistent formats, sufficient freshness, encoded domain knowledge — is the foundation for TFM adoption. If your SAP data is locked behind manual exports and ABAP reports, no model, however sophisticated, will help. Invest in the data accessibility and quality work now so that when TFM capabilities arrive, you can adopt them without a six-month data remediation project blocking the way.
Start with high-value tabular prediction use cases. You do not need to wait for SAP's TFM integration to begin predicting from structured data. Identify the three to five tabular prediction problems that would create the most operational value — supplier risk scoring, payment delay prediction, demand forecasting, churn detection — and begin building the data pipelines, feature engineering, and evaluation frameworks for them. If you use traditional gradient-boosted trees or existing AutoML tools today, that work transfers directly to TFMs later. The feature engineering, the evaluation metrics, and the operational workflows around the predictions remain the same regardless of the underlying model.
Do not over-commit to architecture that conflicts with SAP's direction. Building a large, custom tabular ML platform on a non-SAP stack is risky if your operational data lives in SAP and SAP is about to offer native prediction capabilities. Build modular. Keep your feature pipelines portable. Define your prediction tasks in a vendor-neutral way. This is good engineering practice regardless of SAP's roadmap, but it becomes especially important when your primary data platform vendor is making a billion-euro bet on owning this capability.
The strategic signal
SAP's acquisition of Prior Labs is not primarily a technology story. It is a strategic signal about where enterprise AI value concentrates. The AI hype cycle of 2023 to 2025 fixated on conversational AI — chatbots, copilots, generative content. Those capabilities are real and valuable, but they address only part of the enterprise AI opportunity.
The larger prize — predicting outcomes from the structured data that actually runs operations — requires different models, different architectures, and different data preparation. SAP is the first major enterprise vendor to place a billion-euro bet on this thesis. Whether they execute well remains to be seen. But the thesis itself is sound, and DACH enterprises that understand it will make better AI architecture decisions regardless of which vendor delivers the models.
The companies that treat tabular foundation models as a new category — distinct from LLMs, complementary to conversational AI, and dependent on data readiness — will be positioned to capture value from SAP's roadmap. The ones that continue to treat all AI as a language model problem will find themselves retrofitting their architecture in two years when SAP ships native prediction capabilities that their data cannot support.
Book a Fit Call to assess how SAP's TFM roadmap affects your AI architecture. We help DACH enterprises map their tabular prediction use cases, evaluate data readiness for TFM adoption, and design AI architectures that benefit from SAP's direction without creating vendor lock-in. Book your Fit Call →
References: SAP SE, "SAP to Acquire Prior Labs," press release, May 2026; Hollmann, Müller, and Hutter, "TabPFN: A Transformer That Solves Small Tabular Classification Problems in a Second," Nature, 2025; SAP SE, "SAP Announces SAP-RPT-1 Tabular Foundation Model," SAP TechEd keynote, 2025; SAP SE, "SAP to Acquire Dremio," press release, May 2026; Gartner, "Magic Quadrant for Cloud ERP for Product-Centric Enterprises," 2025 (77 percent of transaction revenue touching SAP systems).