Beyond SuccessFactors: What SAP’s Acquisition of TechWolf Really Means
カートのアイテムが多すぎます
ご購入は五十タイトルがカートに入っている場合のみです。
カートに追加できませんでした。
しばらく経ってから再度お試しください。
ウィッシュリストに追加できませんでした。
しばらく経ってから再度お試しください。
ほしい物リストの削除に失敗しました。
しばらく経ってから再度お試しください。
ポッドキャストのフォローに失敗しました
ポッドキャストのフォロー解除に失敗しました
-
ナレーター:
-
著者:
概要
They cover why TechWolf chose SAP, what a context graph does for AI agents, how the deal could lower AI costs for HCM vendors, and whether TechWolf can stay open to every tech stack.
Note: SAP entered into a definitive agreement to acquire TechWolf, subject to the customary closing conditions. The deal is expected to close in Q4 2026, numbers aren't disclosed
QUESTIONS ANSWERED
What is TechWolf, and what is SAP actually buying?
TechWolf is a headless data layer for skills and work. It figures out what work is happening in a company and what skills people have and need, then feeds that into enterprise systems and AI agents. SAP gets the product, the in-house AI models, and the team.
What is a context graph, and why do AI agents need one?
A context graph takes data from systems of record and maps it into one connected picture of skills, work, and the external market. Agents pointed straight at a system of record handle simple lookups fine. On harder questions, like which training moves people into data roles, they read piles of irrelevant data. That drives up cost and raises the risk of bias and hallucination. A context graph puts only the right information into the agent’s context window.
How does a context graph lower AI costs for HCM vendors?
Agents don’t have to search through as much data. Jeroen says that at organizations of 50,000 to 100,000 people, the difference is about an order of magnitude. That’s TechWolf’s own estimate, so test it with your own harder questions. Stacia ties this to her HBR piece on HCM vendors passing AI costs to customers through consumption pricing.
What is the “pancake guy” problem with AI and people data?
One Slack message about leftover pancakes led an LLM to label an engineer “the pancake guy” in an onboarding game. In promotions or redeployment, one stray data point could pigeonhole someone and keep them from roles they’re qualified for. Grounded, auditable data across a wide range of signals helps prevent this.
Can TechWolf stay “Switzerland” inside SAP?
Jeroen says TechWolf will keep serving customers on any tech stack, since closed architecture takes options away from customers. Stacia adds that openness takes more than one side. If competitors pull back integrations, much of the value of a cross-system graph falls apart.
TIMESTAMPS
[00:39] – Introduction to Jeroen Van Hauttev and TechWolf
[01:54] – Why TechWolf chose SAP
[04:17] – What SAP is buying: product, models, and team
[05:49] – How a context graph changes what AI agents can do
[08:07] – How a context graph lowers AI costs
[08:40] – The pancake guy story and AI reliability
[12:05] – Can TechWolf stay open inside SAP?
[13:25] – Stacia’s reflection on the conversation
RESOURCES & LINKS
- SAP Buys TechWolf: The Fight for the Skills and Tasks Layer
- How to Respond to the Coming AI Cost Shock
Connect with TechWolf
- TechWolf Official Website: https://www.techwolf.ai/
- Jeroen Van Hautte on LinkedIn: https://www.linkedin.com/in/jeroenvanhautte/
Connect with RedThread Research
- RedThread Research Official Website: https://redthreadresearch.com/
- RedThread Research on LinkedIn: https://www.linkedin.com/company/redthread-research/
- Stacia Garr on LinkedIn: https://www.linkedin.com/in/staciashermangarr/
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません