How does it differ from Beekeeper, Speakap, Workplace or Workvivo?
White-label communication platforms go live quickly and are good at standard mechanics (news feed, chat, push, simple documents). They reach their limits at three points: with complex role and location segmentation (multi-brand, franchise, healthcare divisions with separate collective agreements), with integrations to an unusual HRIS or sector-specific system (WFM in retail, scheduling in healthcare, TMS in logistics), and on price as you grow, since active-user fees add up quickly once adoption picks up. Custom costs more at the start and less in the long term, and you retain ownership of data, mechanics and governance. We will also tell you honestly when a white-label solution is enough: if your organisation has a flat structure and no exotic integrations, it can be a perfectly good first step.
Native or cross-platform: what do you recommend?
It depends on the mechanics and your internal capacity. For standard internal communication flows (news feed, push, chat, documents), Flutter or React Native work excellently and deliver simultaneous releases on iOS and Android from a single codebase. For apps that rely heavily on hardware (NFC for clocking in on the shop floor, camera for incident reports with geo-tagging, offline working in poor coverage, complex push segmentation via OS features), we more often choose native: Swift for iOS, Kotlin for Android. We advise case by case: we can deliver both approaches, and do both well.
How does the works council process (right of consent) work?
An app that processes employee data and sends push notifications falls under the works council's right of consent. We involve the works council from the discovery phase, not as a final step. Concretely, we deliver a draft DPIA, a privacy statement, an overview of the data collected and a description of the moderation and notification powers. Transparency is on our side: no black-box AI, no hidden data exports to third parties. For organisations where the works council formally advises on IT choices, we produce a short internal document in phase one so that the director and the works council secretary are working from the same facts.
How do you handle GDPR and employee privacy?
Employee data demands a different level of care than customer data: the employee-employer relationship is unequal by definition, so consent is usually not a tenable legal basis. We build on other grounds (performance of the employment contract, legitimate interest) and keep profiling to a minimum. Segmentation by location and role type is operational; segmentation by individual behaviour is only done in aggregate and always in consultation with the works council and the data protection officer. We set up a data vault, apply retention rules per data category and log all administrative access. We take care of the DPIA as part of the build.
How does the app support multiple languages?
Multi-language support is part of the architecture from day one. Every UI string is translatable, content (messages, documents, surveys) can be supplied per language or translated automatically, and push notifications are triggered in the recipient's preferred language. For production, hospitality and cleaning organisations this is rarely optional: a safety notice that only arrives in Dutch for a Polish- or Romanian-speaking team doesn't achieve its purpose.
How do you handle employees without a work email address?
A large group of deskless workers has no work email address. We provide alternative onboarding flows: PIN access linked to the employee number, a magic link via a personal email address, phone validation via SMS, or a QR code invitation handed over by their manager. For organisations that don't want to process personal data, we build a variant using only the employee number and a site PIN. SSO remains available for office-based staff with a corporate identity.
Does the app work on personal phones and on shared devices?
Both. On personal phones, the app works like a normal app with a personal login and a privacy layer that prevents company data from leaving the app (for example, no automatic backups to iCloud). On shared devices in production or warehouse environments, we build a shift mode: you log in at the start of your shift with your PIN or NFC badge and are logged out automatically at the end of it. History stays safe in the backend, not on the device.
Does the app work offline?
For reading company news, viewing procedures and checking your schedule, the app works offline: content is cached in the background and is available without a network connection. Messaging and pulse surveys need a connection, but messages are stored temporarily and sent as soon as the connection returns. This matters for sectors with poor coverage on site (warehouses, underground storage, production halls, some healthcare locations). Push notifications arrive as soon as the device is back online: not always instantly, but reliably.
How does the app relate to our intranet and MS Teams?
An internal communication app rarely replaces your entire digital workplace. It replaces the part that currently doesn't work for the majority of your employees: the people with no, or limited, access to the intranet and MS Teams. For office staff, Teams or the intranet remains the main environment. That's why we always build a synchronisation layer: company news that appears in the app also appears on the intranet. For mixed groups, we deliver a desktop web version of the app, often in combination with our
employee portal service.
How do you measure whether the communication works?
We set up analytics for activation (the percentage of staff who have actually activated the app), engagement (daily and weekly openers, average reading time per article, push response), reach (which segments read which messages, and which segments are structurally not being reached) and pulse results where those are in use. Alongside quantitative measurement, we also measure qualitatively: a short interview cycle gives you insight faster than dashboards alone.
Who owns the code and data?
You do. We hand over the full source code, schemas, build pipelines and deployment scripts. The data lives in your cloud or with a hosting partner of your choice, with an EU data centre as the default. If you later want to continue with another agency, or take it over in-house, you can: there is no lock-in on the technology or the data layer. We earn our money from good work that lasts, not from clients who are stuck.
What determines the cost of an internal communication app?
The biggest cost drivers are the complexity of the role and permissions model, the number of integrations (HRIS, scheduler, DMS, payroll, e-learning, sector-specific), the depth of messaging and the knowledge library, the number of languages, and whether the platform runs multi-tenant or single-tenant. Native versus cross-platform and brand-specific motion design also play a role. We work in sprints with fixed sprint budgets: no surprises, and you can steer the scope sprint by sprint.
How long until we can go live?
A first working version with login, news feed, push segmentation and a simple knowledge library can be on TestFlight and the Google Play internal track for pilot use within a few sprints. For a full mobile intranet with an HRIS integration, scheduler integration, messaging and multi-language support, we plan a programme of several sprints. We often roll out in phases so that a first site or division can start while we keep building, which gives us feedback that we can act on straight away ahead of the wider launch.
Can you also start from an existing SaaS product that we're replacing?
Yes, that is one of the most common starting points. Organisations outgrowing Beekeeper, Speakap or Workplace usually arrive with a lot of content (old messages, knowledge articles, channel structure) and a hurdle in getting users used to something new. We build a migration script that transfers content and channels (where the source API allows it) and make sure the first version of the new app feels familiar enough to make the switch smooth. It's often a good moment to take another look at your
employee portal too: poor adoption is partly linked to a desktop environment that no longer fits either.