Why mid-market teams end up shopping for enterprise workforce planning software
Three weeks before a board meeting, a VP of People at a 900-person logistics company opens the fourth workforce-planning platform's website this month. The homepage shows a slide-deck screenshot, a logo wall of Fortune 500 names, and a button that says "Request a demo." There is no pricing page. There is no self-serve trial. Buried in the footer is a case study from a bank with tens of thousands of employees. She closes the tab and opens another — same layout, different logo wall, same absence of a price.
This is not a coincidence. It is a category mismatch. Most of the workforce-planning and org-design software that ranks for searches like "enterprise workforce planning software" was built for a buyer profile that does not describe a mid-market HR team: a dedicated people-analytics function, a multi-year software budget cycle, and an IT/data-engineering group that can support a platform integration. The trigger for the search is usually the same for everyone, regardless of company size — a board, an executive committee, or a private-equity owner has asked some version of "which of our roles are exposed to AI, and what's the plan?" But the tools that surface first are scoped for organizations ten times larger than the one asking the question.
This gap is not a fringe problem. Gartner's 2024 HR research found that 86% of HR leaders have not implemented strategic workforce planning at all, and a separate Gartner HR Priorities Survey found that 66% of organizations that do plan say the practice is limited to headcount forecasting or that they struggle to demonstrate its ROI. Layer onto that the sheer number of companies in this size band — the National Center for the Middle Market estimates roughly 200,000 U.S. middle-market companies — and the shape of the problem becomes clear: a very large population of HR teams is being asked a company-specific question, with tools built for a much smaller population of much larger companies.
This article breaks down what enterprise workforce planning software is actually built to do, where that scope diverges from mid-market needs, and how to tell early which category you are really shopping in.
What enterprise platforms like Orgvue, Visier, and Faethm are actually built to do
It is worth being precise about what these platforms do well, because the mismatch is structural, not a quality gap.
Orgvue is an enterprise workforce and org-design platform. It supports scenario modeling and maintains a "workforce digital twin" — a live data model of the organization's structure — and includes an AI automation-potential capability layered on top. It is aimed at large organizations running org-design or restructuring initiatives with dedicated project teams, and it does not publish pricing publicly; access starts with a sales conversation.
Visier (Visier People) is a mid-to-large enterprise people-analytics platform. It ships with predictive analytics and a library of pre-built workforce metrics designed to plug into existing HRIS data. It does not publish standard list pricing, and it has no O*NET task-level exposure scoring or redeployment-recommendation engine — its predictive layer is built around workforce metrics generally (attrition, hiring velocity, compensation trends), not occupation-level automation exposure.
Faethm, now part of SAP, is positioned as an enterprise workforce and future-of-work scenario tool. Since its acquisition, it has no standalone self-serve pricing published; it is sold as part of a broader SAP SuccessFactors motion.
All three assume the buyer already has, or is willing to build, an internal analytics capability to configure and interpret the platform. None of them are wrong to make that assumption — it matches their core customer. The mismatch appears only when a company without that capability tries to use the same tool for the same job. For a deeper look at how Orgvue's and Faethm's feature sets map onto smaller-company needs, see our breakdowns of Orgvue alternatives and Faethm/SAP alternatives.
Where the fit breaks down: implementation, team structure, and time
The practical problem shows up in three places, and none of them are about feature lists.
Team structure. Enterprise workforce platforms are generally configured, maintained, and interpreted by a dedicated people-analytics or HRIS team — often several people whose full-time job includes this software. A mid-market HR Strategy Director or VP of People is usually doing workforce planning as one responsibility among many, without a data science function to lean on. A platform that assumes a standing analytics team creates work before it creates insight.
Deployment expectations. These platforms are typically sold and rolled out through a sales-and-services motion rather than a self-serve signup — the "Request a demo" gate is the tell. That pattern exists because the underlying implementation is intended to be configured against a company's specific HRIS and org data, which is a reasonable model for a 20,000-person enterprise and a heavy one for a 900-person company that needs a defensible answer for a board meeting in three weeks, not a quarter.
Governance overhead. Enterprise contracts typically involve procurement review, security questionnaires, and negotiated terms — sensible for a company buying enterprise-wide software, but disproportionate for a team that needs an occupation-level exposure read on a role list, not a permanent org-design system of record. For more on how scenario-planning tools differ in scope, see our workforce scenario planning software guide.
None of this means the enterprise platforms are poorly built. It means they are built for a different starting condition than the one most mid-market HR teams are actually in.
The pricing opacity problem no one talks about
Every one of the three platforms named above shares one trait: none publishes pricing. That is a deliberate go-to-market choice for enterprise software sold through named-account sales teams, and it is worth naming as a buyer-experience fact, not a criticism — enterprise contracts are typically negotiated around company size, module selection, and implementation scope, which makes a published list price impractical for the vendor. But it also means a mid-market buyer cannot self-qualify. There is no way to look at a number and decide whether the platform fits the budget before entering a sales process.
This opacity exists inside a market that is genuinely large and growing. The workforce planning software market was estimated at $2.8 billion in 2024, projected to reach $5.3 billion by 2031 at an 8.7% CAGR, with the workforce planning tools segment specifically sized at $1.5 billion in 2024, according to 6Wresearch and Verified Market Research. A market that size supports many vendors serving very different buyer profiles — which is exactly why "enterprise workforce planning software" and "self-serve mid-market workforce exposure tool" can occupy the same search results while solving different problems.
For teams that decide to go around the software question entirely and hire a consultant to build a one-time occupation mapping instead, it is worth knowing what that route costs directly: independent consultants working this kind of engagement typically bill in the range of $100–$350 per hour, with a median around $150–$200 per hour, according to 2026 data from ConsultFees. That is a real, sourced alternative-cost data point — useful for comparing a one-time manual engagement against a repeatable tool, whichever category the tool falls into.
What mid-market teams actually need instead
Strip away the feature marketing and the actual requirement is fairly specific: a way to produce a defensible, occupation-grounded view of AI exposure across a role list, without a dedicated analytics team, without a multi-month implementation, and without an opaque enterprise sales cycle standing between the question and the answer.
That is the design brief WorkforceAnalysis was built against. It is a self-serve platform that maps an organization's roles to O*NET occupations and scores exposure using a four-dimension rubric, with transparent, published tiers rather than a sales-gated quote. It is worth being precise about what it does and does not do: it produces an occupation-level exposure score to support a workforce planning conversation. It does not forecast layoffs, and it does not tell a company which roles will be automated. Every output is expressed in the product's own vocabulary — Monitor, Review, or Redeployment Candidate — because the score is an input to a human decision, not a substitute for one.
Exposure is an analytical input to a redeployment conversation. It is not a verdict on a role, and it is not a prediction of who gets laid off.
If your team needs to see how this compares against other self-serve and mid-market tools before committing time to any one platform, our comparison of AI workforce planning tools and AI org design tools guide walk through the category more broadly.
A structural comparison: enterprise scenario modeling vs O*NET task-level exposure scoring
The deepest difference between the enterprise platforms above and a tool like WorkforceAnalysis is not price or sales motion — it is the unit of analysis.
Orgvue, Visier, and Faethm generally model at the org-structure or headcount-metric level: departments, reporting lines, scenario what-ifs across cost and headcount. WorkforceAnalysis scores at the occupation-task level, using the U.S. Department of Labor's ONET database — the standardized occupational taxonomy that underlies most U.S. labor-market classification. ONET currently defines 1,016 occupational titles, of which 923 have full data-level detail, spanning more than 55,000 job titles in the U.S. economy, and it is maintained on a regular update cycle (roughly quarterly, with a primary annual update in Q3) across roughly 277 descriptors per occupation. Under the current 2018 Standard Occupational Classification structure that underlies ONET, the Bureau of Labor Statistics recognizes 867 detailed occupations, 459 broad occupations, 98 minor groups, and 23 major groups. WorkforceAnalysis's current build runs against ONET database release v30.3. [This figure should be reconfirmed against the version actually loaded in production before publishing.]
Each occupation in the ONET database carries a list of core tasks with an assigned importance rating. WorkforceAnalysis scores each task against four dimensions — cognitive routine, physical routine, social/judgment, and creative — each on a 0–100 scale — then weights those task scores by the ONET importance rating to produce a role-level exposure score.
A simplified worked example: suppose a role's top three O*NET tasks carry importance weights of 40%, 35%, and 25%. If those tasks score 70, 55, and 30 on the cognitive-routine dimension, the weighted cognitive-routine score is (70×0.40) + (55×0.35) + (30×0.25) = 28 + 19.25 + 7.5 = 54.75. The same weighting runs across all four dimensions, and the four dimension scores together — not a single blended number — are what a Review or Monitor designation is built from. This is illustrative arithmetic using round inputs, not a claim about any specific occupation's actual score.
This site incorporates information from O*NET. Used under the CC BY 4.0 license. O*NET is a trademark of USDOL/ETA.
The practical difference: an enterprise scenario tool tells you what happens to your org chart if you cut a department by 15%. An O*NET task-level exposure score tells you, role by role, which specific tasks inside that role carry high routine-cognitive exposure and which carry high social-judgment or creative weight — the level of detail a redeployment conversation actually needs.
Choosing the right tool for where you are today
The honest decision framework is about company stage, not company size alone.
If you have a standing people-analytics or HRIS-data team, a multi-year software budget, and a mandate to build a permanent org-design system of record, an enterprise platform like Orgvue, Visier, or Faethm may be the right category — talk to their sales teams and ask directly about implementation scope and timeline, since none of the three publish that detail online.
If you are a 200–5,000 employee company that needs a defensible, occupation-grounded exposure read this quarter, without standing up a new analytics function or entering a months-long procurement cycle, a self-serve O*NET-based tool is the structural fit — because it was built for exactly that starting condition, with published tiers you can review at /pricing before you commit any time.
If you're not yet ready to run a full assessment but want a structured way to think through readiness first, the Workforce AI Readiness Assessment Guide is a lower-commitment starting point — a self-directed worksheet for scoping the question before you evaluate any platform, enterprise or otherwise.