Jostle

Name: Jostle
Brand: Jostle

Helping employees succeed. Anytime, anywhere.

Est 2009|Raised $7.3M|85 Ref Customers

LinkedIn 4K|Web traffic 7K|FTEs 65|HQ Vancouver, British Columbia, CA

MarketsInternal Communications & Intranet

Published Oct 15, 2026

01Common complaints

- Company sizes or stages where this product is over-provisioned or underpowered - Very small teams that can meet needs with existing collaboration tools (for example, Microsoft Teams/Slack plus a lightweight wiki such as Confluence, Notion, or Google Sites) may not justify per-user costs. - Very large enterprises with strict certification and governance requirements should confirm vendor-provided certification evidence; publicly available materials in this dataset did not document vendor-level SOC 2 Type II or ISO 27001 certifications. - Industries or use cases where competitors may be better aligned - Highly regulated industries that require formal audits and detailed security documentation may prefer vendors with clearly published certification status and enterprise security collateral. - Organizations building a comprehensive digital employee experience program with advanced editorial workflows, multi-language publishing governance, and broad channel orchestration may prefer enterprise-focused solutions. - Technical requirements that are not clearly documented - Organizations requiring SCIM-based provisioning, detailed audit logs, or explicit data residency controls should confirm these features with the vendor prior to purchase. - Budget considerations - If an organization already holds Microsoft 365 licenses and is able to invest internal effort to configure SharePoint as an intranet, the incremental monetary cost of a separate intranet product should be weighed against internal maintenance and governance costs. - Specific workflows or integrations where the product may be limited - Customers requiring highly customized events/calendar workflows should validate fit; reviewer feedback cited limitations in events/calendar customization. - Procurement red flags - If per-user pricing is not clearly visible or consistent for an organization (for example, due to dynamic rendering on the vendor site), request a written pricing sheet that specifies included modules and add-ons. - Current limitations acknowledged by the vendor - Vendor materials reviewed do not provide a comprehensive list of product limitations beyond general positioning content. - Features on the roadmap (not yet available) - Roadmap details were not located in the retrieved excerpts. - Scale limitations - Scale limitations were not documented in the accessible sources. - Security or compliance gaps - Public materials reviewed reference SOC 2/ISO 27001-compliant infrastructure providers but do not clearly document vendor-level SOC 2 Type II or ISO 27001 certification. Buyers requiring formal compliance evidence should request reports and certificates directly from the vendor under NDA as appropriate. - Technical debt or architectural limitations mentioned in reviews - Not explicitly documented in the review excerpts captured for this research. - API limitations or integration constraints - The vendor references a Platform API and API/SFTP sync in product materials. Specific API limitations were not detailed in the accessible sources and should be validated in technical evaluation.

02Why they buy

- Competitive advantages evidenced by customer feedback (as reported by reviewers) - Mobile access to a centralized library for field staff is valued in user reviews. - Read-and-sign acknowledgement tracking for critical communications is reported positively by reviewers. - Differentiators claimed by the vendor (not independently validated) - The vendor emphasizes a simpler intranet-style experience and targeted communications; independent validation of these claims was limited in the retrieved excerpts. - Areas where competitors have advantages - Enterprise-focused platforms may provide more extensive structured publishing workflows and multi-language publishing governance. - Social-first platforms may provide broader native content formats and engagement mechanics for programs prioritizing social interaction.

03Field reports

- Review-platform availability and accessibility - TrustRadius review content was accessible and included both positive and critical commentary. Access to other major review platforms was observed, though the crawl used for this research encountered retrieval limitations for some pages. - TrustRadius — positive quotes and outcomes - Field access / mobile knowledge access - "Being able to access the Library from the Jostle app on our phones while out in the field working with patients is incredible." (Verified user, TrustRadius; incentivized flag noted.) - Read-and-sign acknowledgement workflow - "Being able to send an important memo and having the team sign off that they read it… being able to track who has read the memo and who hasn't." (Verified user, TrustRadius.) - TrustRadius — negative/critical quotes (usability, navigation, customization) - Dashboard / navigation complexity - "I think that the dashboard is not well designed. I feel like I have to go through a lot of navigation panels to find the right information." (Reviewer, TrustRadius; incentivized flag noted.) - Library customization gaps - "the library of Jostle needs a lot of customization and a lot of features have to be added…" (Reviewer, TrustRadius.) - Events customization limitations - "needs more customization with the events function… customize the calendar." (Reviewer, TrustRadius.) - Export limitations - "Issue downloading published contents to common file formats like PDF." (Reviewer, TrustRadius.) - Reddit / community perspectives (anecdotal) - SharePoint vs third-party platform tradeoffs - Community discussions note tradeoffs between adopting a third-party intranet product and using SharePoint (already included in many Microsoft 365 licenses). One thread referenced a migration from Jostle to SharePoint in a community context. - Competitive mentions in sysadmin discussions - Jostle appears in lists of third-party platforms for employee communications and engagement alongside MangoApps and Workvivo in sysadmin community discussions. - Why customers chose Jostle (patterns suggested by reviews) - Improved communication reach and organization compared with older intranet implementations (implicit in user feedback). - Mobile access for frontline or field staff (explicit in review excerpts). - Read receipts / acknowledgment tracking for critical communications (explicit in review excerpts). - Why some customers leave / churn reasons (evidence limitations) - Direct, detailed churn analyses were not prominent in the accessible source set. Some community threads mention switching to SharePoint, frequently framed as a licensing/availability tradeoff rather than a detailed product criticism.

Vendor-published case studies exist (examples retrieved)

McFarland case study PDF (vendor-published)
Connect Wireless case study PDF (vendor-published)
"Intranet success kit" PDF (vendor-published)

Critical evaluation of case-study evidence

These case studies are vendor-produced materials. Any ROI, engagement, or productivity metrics they contain should be treated as vendor-provided unless methodology, baseline, and independent verification are supplied.
The "Intranet success kit" references productivity and cost figures in vendor materials; without detailed methodology in the excerpts reviewed, these figures should be considered illustrative rather than definitive.

Mixed results / failures

No vendor case studies describing failed implementations were located in the retrieved excerpts. Independent negative implementation stories specific to Jostle were not prominent in this dataset.

04Best fit

Ideal Customer Profile

- Company sizes (practical ICP estimate based on available evidence) - Small-to-mid market up to mid-enterprise (organizations ranging from smaller businesses to several-thousand-employee enterprises) based on review excerpts and vendor positioning. - For very large organizations, fit depends on governance, security certification requirements, and publishing workflow needs; these should be validated in a proof of concept. - Industries and verticals where adoption is strongest (evidence-based examples are limited) - Healthcare and field-service contexts may benefit from mobile library access noted in user reviews. - Distributed workforces (branch/field) are emphasized in vendor messaging; independent adoption patterns were limited in the accessible excerpts. - Roles and personas - Decision makers - Head of Internal Communications - HR Director / VP People - IT Director / Security (for identity and governance requirements) - End users - Frontline and field staff who require mobile access - Managers who need read-and-acknowledgement tracking for critical communications - Pain points and challenges the product addresses - Low intranet adoption and content sprawl - Important updates missed due to email/chat volume - Need for accessible HR policies and resources for distributed staff - Qualification criteria (good fit) - Organization seeks an intranet-style "home" with a simpler user experience than complex SharePoint builds - Mobile-friendly access to policies and resources is a priority - Requirement for internal news/updates with read-and-acknowledgement tracking - Deal disqualifiers (poor fit) - Organizations that require vendor-level SOC 2 Type II or ISO 27001 certification as a strict procurement condition and cannot accept infrastructure/provider-level compliance without formal vendor reports - Organizations that need advanced editorial workflows, multi-stage approvals, or deep enterprise-grade analytics and cannot validate capability in a pilot - Organizations expecting the platform to replace workforce-management systems (scheduling/timeclock) should consider specialized WFM solutions instead

05The pitch

What the product does (core value proposition in objective terms)

- The vendor describes Jostle as an employee engagement and intranet-style platform intended to help employees connect, locate information, and receive updates while aiming to reduce volume from email/chat and minimize intranet sprawl. (Vendor-provided page excerpt.) - Core themes in the vendor messaging - A single space for culture and recognition (e.g., shout-outs, celebration) - Communications described by the vendor as "noise-free" and targeted to relevance - A knowledge repository intended to improve findability and support AI-assisted answers (JostleAI) - Multi-channel delivery: mobile app, email digest/newsletter, digital signage (JostleTV), and integrations

Target market and market positioning

- The product is positioned for organizations seeking a simpler, lower-IT-overhead alternative to classic intranets (commonly SharePoint) or a more structured "home base" than chat tools. - Likely buyer personas (inferred from product focus and community discussions) - Internal Communications / Corporate Communications - HR / People Operations - Operations leaders for distributed/frontline teams - IT (primarily for identity/integrations/governance)

Get a comprehensive analysis of Jostle including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →