When Faethm shows up on someone else's roadmap, not yours
A People Analytics Lead at a 900-person portfolio company gets a note from the PE sponsor's operating team: "SAP mentioned something called Faethm in our last vendor review — can we get that kind of AI workforce modeling for our roles?" The honest answer is complicated. Faethm was acquired by SAP and now lives inside SAP's enterprise workforce planning ecosystem — which means getting it usually means a broader SAP relationship, an implementation timeline measured in quarters, and a budget conversation that doesn't fit a company running lean HR analytics with one or two people.
This article is for that reader: someone who has heard Faethm's name in the context of SAP's enterprise stack and needs to know, plainly, what it actually is, what it isn't built for, and what a self-serve alternative looks like for a mid-market team that needs a company-specific AI exposure picture without an SAP contract underneath it.
What Faethm actually is inside the SAP stack
Faethm was built as a workforce and future-of-work scenario tool — modeling how automation, skills shifts, and labor-market trends might affect an organization's workforce over time. Since its acquisition, it is positioned as part of SAP's broader enterprise workforce planning capability rather than a standalone product with its own self-serve pricing page. There is no standalone self-serve pricing published for Faethm, and its distribution motion runs through SAP's existing enterprise sales and implementation channels rather than a sign-up-and-start model.
That's not a criticism — it's a description of what the tool was built to do and for whom. Enterprise scenario-modeling platforms like this are designed to sit alongside an organization's existing HRIS, integrate with large-scale workforce data, and support strategic planning conversations at a scale where a dedicated implementation team is already part of the budget. For a company with an existing SAP SuccessFactors footprint and a multi-year workforce planning mandate, that can be the right fit.
For a mid-market HR strategy team without an SAP relationship — or without the appetite to build one just to answer a board's AI-exposure question — that path doesn't exist. There is no self-serve mid-market motion for Faethm today. The question isn't whether Faethm is a capable tool; it's whether its access model matches the size and urgency of your problem.
The structural gap: scenario modeling vs. task-level exposure scoring
The more useful distinction isn't "enterprise vs. mid-market" — it's what the tool is actually scoring. Enterprise workforce scenario platforms are generally built to model macro trends: labor supply, skills demand, headcount scenarios across a large, often multi-country workforce. That's a different job from answering the specific question a board or PE sponsor usually asks first: which of our roles, specifically, have tasks that overlap with what generative AI tools can already do — and what should we do about the ones that do?
Answering that question well requires going below the occupation label and into the task list. That's the level at which the U.S. Department of Labor's ONET database operates: 1,016 occupational titles covering more than 55,000 jobs, described by roughly 277 descriptors and updated on a regular cycle, with detailed task lists tied to each occupation (ONET Resource Center, 2019; U.S. DOL, 2025). The Bureau of Labor Statistics' 2018 Standard Occupational Classification, which O*NET occupations map onto, organizes the U.S. labor market into 867 detailed occupations across 23 major groups (U.S. BLS).
A self-serve exposure tool takes a company's actual role list, maps each role to its nearest O*NET occupation, and scores the underlying tasks — not the job title, not a headcount forecast — against a defined rubric. That's a narrower, more specific output than a workforce scenario model, and it's the output most boards are actually asking for when they say "show us our AI exposure."
How a task-level exposure score is actually built
WorkforceAnalysis scores each mapped role across four dimensions, each on a 0–100 scale:
- Cognitive routine — how much of the role's task list is structured, rules-based analytical or information work.
- Physical routine — how much of the work is repeatable physical or manual task execution.
- Social/judgment — how much of the role depends on negotiation, mentorship, persuasion, or contextual human judgment.
- Creative — how much of the role depends on original ideation, design, or novel problem framing.
Each task within an ONET occupation carries an importance weighting in the ONET data — some tasks are central to the role, others peripheral. The rubric applies that same weighting logic: a role's overall exposure score reflects not just which tasks look automatable, but how central those tasks are to the job as O*NET's own data describes it.
A worked example, using round numbers to illustrate the method rather than assert a fact about any real role: imagine a claims-processing role where O*NET task data assigns 45% of importance-weighted tasks to structured data review and documentation (high cognitive-routine content), 30% to routine communication with claimants (moderate social/judgment content), and 25% to exception handling requiring case-by-case judgment (higher social/judgment, lower routine). A cognitive-routine score built from that weighting might land around 70, with a social/judgment score around 45. The output isn't a verdict on the role — it's an input a manager can use to ask a better question: should we monitor this role's task mix, review it more closely against automation tooling already in use, or start exploring redeployment options for the portion of the work that's most routine?
That's the vocabulary the product uses throughout — Monitor, Review, Redeployment Candidate — deliberately, because an exposure score describes overlap between a role's tasks and what current AI tools can plausibly do. It does not predict who gets laid off, and it is not built to make that call. Whether a scenario-modeling platform like Faethm's SAP-integrated capability or a task-level tool like this one, the responsible use of either is as an input to a human planning process, not a substitute for one.
The WEF Future of Jobs Report 2025 estimates that 39% of workers' current skills will be transformed or rendered outdated by 2030 — a scale of change that argues for tools boards can interrogate line by line, not black-box forecasts.
Where enterprise scenario tools still matter — and where they don't
It's worth being precise about where each type of tool earns its place. If your organization already runs SAP SuccessFactors, has a multi-year workforce planning function, and needs to model labor-market scenarios across tens of thousands of employees in multiple countries, an SAP-integrated capability like Faethm's is doing a job a task-level tool isn't built for — it wasn't designed to compete on speed-to-first-output for a single mid-market company's role list.
Conversely, if your immediate need is a specific, defensible, task-grounded picture of AI exposure for a 200–5,000-person organization — the kind of output a board can review role by role, department by department — a self-serve tool built around O*NET task data and a transparent four-dimension rubric answers a narrower question faster and without an enterprise implementation cycle. Gartner's 2024 research found that 86% of HR leaders have not implemented strategic workforce planning, and a separate Gartner survey found 66% say their workforce planning is limited to headcount planning or struggle to show its ROI — a gap that speaks to demand for tools accessible enough to actually get used, not just licensed.
Our related guide on enterprise workforce planning software goes deeper on how platforms in Faethm's category compare on scope and implementation model. If you're evaluating the wider landscape of AI-specific workforce tools, AI workforce planning tools compared puts several options — including task-level and scenario-based approaches — side by side.
Choosing the approach that matches your team's size
The right choice depends less on brand recognition and more on three practical questions: Does your organization already have the enterprise HRIS relationship a platform like Faethm's requires? Do you need multi-year, multi-country scenario modeling, or a defensible task-level exposure picture you can bring to a board meeting in weeks, not quarters? And does your budget reflect an enterprise software program, or a focused analytics initiative run by one or two people?
If the answers point toward the second option in each pair, a self-serve, O*NET-grounded exposure tool is built for exactly that gap. For a deeper look at how scenario-planning software fits alongside task-level tools, see our workforce scenario planning software guide. And if self-serve access is the deciding factor, our breakdown of what a self-serve workforce assessment tool actually includes — role mapping, the four-dimension rubric, department heatmaps, and redeployment options — walks through the mechanics in more detail.
Next steps
If your team needs a role-level AI exposure picture before your next board or ownership review — not a multi-quarter enterprise implementation — the practical next step is to see the methodology applied to your own role list. Review pricing for the tier that matches your organization's size, or start with our Workforce AI Readiness Assessment Guide to prepare your role and department data before you run your first assessment. Either path gets you a defensible, task-grounded exposure picture without an SAP relationship as a prerequisite.
This site incorporates information from ONET. Used under the CC BY 4.0 license. ONET is a trademark of USDOL/ETA.