Name: Inclusively
Brand: Inclusively

01Common complaints

- If the organization requires a formal, end-to-end ADA accommodation case management system with prescriptive compliance workflows (medical-document handling, hardship analysis, step-by-step interactive process tracking), a dedicated accommodation management product (for example, RAMS or Corada) may be more appropriate. - If the organization already standardizes employee service workflows in ServiceNow and prefers to avoid introducing additional vendors and data flows, extending ServiceNow capabilities may be operationally simpler. - If procurement requires extensive independent validation and peer benchmarks via review platforms (G2 / Capterra / TrustRadius), the vendor’s limited presence on those platforms may be a barrier. - If transparent, public pricing is required for quick budgeting (typical of SMB purchase motions), the demo-led pricing model may slow evaluation. - If the buyer’s security team requires public certifications (SOC 2 / ISO) before engaging, the lack of clear public documentation may prevent progress.

Deal disqualifiers (poor fit)

Small organizations without complex benefits ecosystems.
Organizations that require publicly documented SOC 2 or ISO certifications as a precondition (unless the vendor can provide documentation under NDA).
Buyers that require self-serve pricing and rapid procurement without a sales-led process.

Vendor-acknowledged limitations

Public materials emphasize capabilities but do not provide an explicit public limitations or roadmap page.

Notable limitations inferred from available data

- **Security certifications not clearly public:** This may impede enterprise procurement. - **Sparse independent reviews:** Limited presence on review platforms constrains the ability to validate support, implementation, and operational experiences. - **Integration lifecycle risk:** Reliance on platforms such as Teams and ServiceNow introduces exposure to marketplace rules and lifecycle changes. - **Data sensitivity:** Handling information tied to disability and accommodation requests raises privacy and HR legal considerations; buyers should request detailed data processing agreements and security documentation.

02Why they buy

Advantages (evidenced in public materials)

- **Embedded discovery:** Retain provides a natural-language search experience within collaboration tools and workplace systems. - **Anonymity focus:** Vendor materials describe features intended to allow employees to begin seeking support anonymously, which is intended to reduce stigma. - **Search-signal analytics:** The platform captures employee search behavior and aggregates it into analytics intended for HR and benefits teams.

Areas where competitors may have advantages

Larger platforms and incumbents can provide broader workflow automation, HRIS integration breadth, more mature security documentation, and larger volumes of independent user reviews.

03Field reports

Review platform coverage (G2 / Capterra / TrustRadius)

A key limitation of this research: Inclusively has limited or no discoverable footprint on major B2B review platforms based on the searches performed.

Searches for G2, Capterra, and TrustRadius did not surface an obvious active product review page with review counts.

Consequence: There is less independent, structured review evidence than for many HR and employee experience products.

Vendor-published testimonials (examples)

Inclusively’s website includes employer-side testimonials, presented as vendor-provided statements, such as: - A talent acquisition leader for a professional sports organization noting improved hiring outcomes since partnering with the vendor. - A director of acquisition at a financial services firm praising the technology and solution. - A senior people leader at an entertainment/attractions company commenting that accommodations can be simple and cost-effective. These are curated references and may not reflect typical outcomes across deployments.

Community and social discussion signals

Direct Inclusively-specific community threads were limited. Relevant ecosystem context includes: - A forum thread discussing variability in connector and marketplace app quality in ServiceNow and Teams ecosystems, which highlights that third-party store apps may vary in code quality and that store review processes do not always catch all issues. This is context for buyers planning to deploy third-party marketplace applications; it is not a direct allegation about Inclusively’s connector.

Vendor-reported outcomes (vendor/PR)

From vendor materials (not independently verified): - A Retain case study claims rollout at a large enterprise, rapid integration, substantial automation of self-service requests, and a positive employee satisfaction rating. - Funding and corporate announcements include vendor statements about automation in the accommodation process and potential cost savings tied to disclosure and process improvements. Critical note: These return-on-investment and automation claims are vendor-generated and do not include transparent methodologies or baselines in the public materials.

Common reasons buyers might select Inclusively (inferred)

Preference for an embedded, natural-language support discovery capability integrated into tools employees already use (Teams/ServiceNow) rather than a separate portal.
Interest in capturing employee search behavior as a real-time signal source instead of relying solely on periodic surveys.
A taxonomy-driven approach intended to centralize various types of support (benefits, resources, accommodations).

Reasons buyers may not select or may churn (evidence-limited)

Definitive churn reasons are unclear given limited third-party reviews. Plausible reasons include:

Security or compliance teams rejecting the platform’s data-handling model.
Low utilization if communications and change management are insufficient.
Preference for consolidating workflows into existing platforms (for example, ServiceNow or an HRIS).

Case Study 1: Large enterprise software company (vendor-published)

Reported items in the vendor-published case study include: - Pain points: employees could not find support; a static wiki was ineffective; redundant accommodation processes across teams. - Reported results: rollout at a large enterprise, a short integration period, significant automation of self-service requests, and a positive employee satisfaction rating. Critical evaluation: This is a vendor-authored case study. The customer name is not disclosed in the summary page, and the public excerpt does not provide complete methodological detail for satisfaction and automation metrics.

Case Study 2: Major CRM provider (vendor-published) and partnership announcement

The vendor publishes a CRM-specific case study with directional usage metrics and describes an initial pilot that led to expanded collaboration.

Critical evaluation: These metrics are directional and vendor-published; they do not directly indicate measured productivity or retention outcomes.

04Best fit

Company sizes

Mid-market to enterprise organizations; typically organizations with complex benefits ecosystems and distributed employee populations.

Industries and verticals

Enterprises with significant knowledge-worker populations and fragmented toolsets, such as technology, financial services, healthcare/pharma, professional services, and large multi-site employers.
Organizations with established accessibility or DEI programs or those that experience moderate to high volumes of accommodation requests.

Roles and personas

Decision makers: VP HR, Head of Total Rewards/Benefits, Head of Employee Experience, Accessibility/DEI leaders
Influencers: HR Operations, Legal/Compliance, IT (Teams/ServiceNow administrators), Security/Privacy
End users: employees seeking support, managers coordinating adjustments, HR accommodation specialists

Qualification criteria (strong fit)

Benefits and resources are spread across many portals and employees have difficulty locating support.
The organization seeks near-real-time demand signals in addition to periodic surveys.
There is a desire to increase utilization of existing support programs (EAP, accessibility tools, wellness resources).

05The pitch

What the product does (objective value proposition)

Inclusively is a workplace employee support and workforce intelligence platform that helps employers (1) make employee support (benefits, resources, accommodations, policies) easier to find and use and (2) use employee search and interaction data to understand demand, gaps, and return on investment of workforce investments. Inclusively currently emphasizes two primary solutions: - **Retain**: A workforce intelligence and employee support discovery layer that integrates into existing workplace systems (e.g., Microsoft Teams, ServiceNow, SharePoint) to allow employees to search in natural language and receive recommendations for “Success Enablers” (benefits/resources/accommodations). It also provides analytics to HR and benefits leaders. - **Hire**: A recruitment solution intended to connect employers with candidates from underrepresented or less-recruited talent pools and to support candidates through the hiring and onboarding workflow using the same Success Enabler taxonomy. Vendor materials state the product aims to reduce friction and stigma in requesting workplace support by enabling anonymous discovery and applying a standardized taxonomy for support resources.

Target market and positioning

**Positioning:** A B2B HR, benefits, accessibility, and workforce strategy platform, with particular relevance for enterprises focused on improving: - accommodations and accessibility workflows - benefits utilization and workforce ROI analytics - inclusive hiring and candidate support **Typical buyers / stakeholders:** HR leadership, Total Rewards/Benefits, Employee Experience, DEI/Accessibility offices, and HR operations; in some enterprises, IT/ServiceNow/Teams owners may also be stakeholders due to required integrations.