LumApps (with Beekeeper)

How a message reaches every employee: a news feed and announcements on phone, browser and shared devices, targeting by site, department, role and language, access for staff without a company email address (invite codes, phone number, personnel number, QR codes, kiosk or shared devices), push notifications, mandatory reading with read confirmation, urgent alerts, scheduled posts, and reach analytics per message and audience.

0 — Not a communication tool; the company cannot publish news or announcements to employees in the product.

3 — A news feed or announcement channel for employees with company accounts; targeting, access without a company email address and reach figures are basic or not described.

5 — News and announcements targeted by group, site or role, delivered to a mobile app with push notifications and to the browser, employees without a company email address able to log in, and views or reach shown per post.

8 — Targeting by site, department, role and language from HR data, login documented for staff without email or company devices (personnel number, SMS code, shared devices), mandatory reading with read confirmation and reminders, urgent alerts that override quiet settings, scheduled and multi-channel posts (app, email, intranet, screens), and reach analytics per audience.

10 — Reach that can be proved: delivery and reading tracked per channel against the whole workforce, offline access and low-bandwidth delivery documented, crisis messages with acknowledgement and escalation, aggregated reports exportable, and the reach analytics described with the data they use.

What employees can look up: intranet pages and a content management system, documents and policies with versions and owners, search across content and connected systems, a people directory and org chart, multilingual content with machine translation of posts and pages, content review and expiry, and access from the app as well as the browser.

0 — No pages or documents; the product carries only messages that scroll away.

3 — Files or simple pages can be shared; search, translation, a people directory and content governance are basic or not described.

5 — Pages and a document area with permissions, search across the content, a people directory, content available in the mobile app, and posts or pages translatable into several languages.

8 — A content management system with templates, page ownership, review dates and versioning, search across connected systems (SharePoint, Google Drive or similar), automatic translation of posts, pages and comments into named languages, an org chart from HR data, and pages readable offline.

10 — Knowledge that stays current: content lifecycle and expiry enforced, search and AI answers that cite their sources and respect permissions, analytics on what is searched and not found, accessibility of the content stated against WCAG, and a full export of pages and documents.

How the workforce answers back and gets started: comments, reactions and moderation, employee surveys and pulse checks with anonymity rules, recognition, user-generated posts and communities, onboarding journeys for new starters including those without a desk, event and campaign pages, and the measures the vendor offers to report engagement.

0 — One-way only; employees cannot react, comment or answer in the product.

3 — Likes and comments on posts; surveys, moderation and onboarding are basic or not described.

5 — Comments and reactions with moderation, surveys or polls sent to targeted groups with results shown, employee posts or communities, and an onboarding area or journey for new employees.

8 — Pulse and engagement surveys with a stated anonymity threshold, automated onboarding journeys timed from the start date and reaching new starters before their first shift, recognition, communities with moderation rules, and engagement reported per group without exposing individuals.

10 — Listening that leads to action: survey results tied to follow-up tasks and published back to the workforce, anonymity and minimum group sizes documented, onboarding journeys measured by completion, and engagement data exportable for analysis.

Whether the product can be rolled out under German co-determination and data protection: guidance or a template for a works agreement (Betriebsvereinbarung, § 87 BetrVG), no individual performance or behaviour monitoring by default, read and usage analytics aggregated or configurable, use on private phones without a company device (BYOD) with work and private data separated, quiet hours and availability settings, voluntary use without an employee email address, data minimisation and deletion, and accessibility.

0 — Built to monitor the behaviour or performance of individual employees, with that monitoring sold as a feature.

3 — A general GDPR statement; works council, use on private phones, analytics on individuals and quiet hours are basic or not described.

5 — Use on private phones described with what the employer can and cannot see, analytics shown in aggregate, notification or quiet-hour settings, and works councils or employee representatives named as a topic with information offered.

8 — A works-agreement template or checklist published, individual tracking off by default or switchable per tenant, read confirmations limited to messages that require them, quiet hours enforced, a login without a private email or phone number, data minimisation and deletion periods stated, and accessibility to WCAG or BITV stated.

10 — Co-determination built into the product: every analytics view and its granularity documented for the works council, configuration logged, employee-facing privacy notices in the app, minimum group sizes for every report, and published references of works-council-approved rollouts.

How the product fits the company's systems and is run: Microsoft 365, SharePoint, Teams and Google Workspace integration, user provisioning from the HR system or directory (Entra ID, SAP SuccessFactors, Personio, Workday), single sign-on and SCIM, roles and admin rights by site or department, an API and webhooks, integrations with shift planning and payroll for frontline links, white-label apps, and an export of content and users when leaving.

0 — Stand-alone with manual user lists and no integration of any kind.

3 — Users imported from a file and a few links to other tools; single sign-on, provisioning and an API are basic or not described.

5 — Single sign-on with named identity providers, users provisioned from a directory or HR system, Microsoft 365 or Google Workspace integration, several named integrations, and a documented API.

8 — Automated provisioning by SCIM or HR connector including staff without email, delegated administration by site or department, integration in Microsoft Teams and SharePoint, connectors for named HR, shift and payroll systems, webhooks, a white-label app option, and an audit log.

10 — Runs as part of the company's systems: a public developer platform with versioned API and SDKs, every integration documented, a status page and stated SLA, and a full export of content, users and analytics that a successor system can import.

Who the contracting entity and the parent company are, where employee profiles, messages, files and usage data are hosted, and who the subprocessors are (hosting, push notifications, email and SMS delivery, video, translation, AI models, analytics, support). Independently sourced by the sovereignty pipeline; an employee app holds data on the whole workforce, often on private phones, so the whole chain counts, not only the database.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (push delivery, translation, AI, email, analytics, support) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, or self-hosting on the customer's own servers, data export and deletion documented, and certifications published with their scope rather than implied.

Whether a buyer can compute the real annual cost from public pages alone: price per user or per employee, whether frontline and desk staff are priced differently, platform or base fee, which modules (intranet, employee email, surveys, translation, AI, a white-label app) cost extra, minimum seats and term, and setup and onboarding fees.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or a free tier exists, but how cost scales with users, modules or a branded app is unclear.

5 — Tiers are public with their per-user or base price and main inclusions, but at least one commonly needed piece (frontline users, translation, a branded app, extra modules) is unpriced or "on request".

8 — Every tier priced publicly with its scaling rule (per user, per frontline user, per active user), add-ons and a branded app priced, minimum seats and term, setup fees and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given headcount and module set, with every add-on, setup, support and branded-app fee and the cancellation and data-return terms published.