Temporall

Temporall started in 2018 in the United Kingdom. The idea was that workplace culture could be measured rather than guessed at, and that the data to measure it already existed inside the tools people used every day. The company launched its first platform in March 2019, a real-time culture analytics product that combined survey responses, sentiment analysis and organisational network analysis. In June 2020 it raised a £1m seed round led by Luminous Ventures.

What the company measures has moved with the market. Culture came first, then day-to-day collaboration across Google Workspace, Microsoft 365 and Slack, and now the adoption of AI assistants at work. In January 2026 Temporall launched Tempo, which it describes as the intelligence layer for the AI-enabled enterprise, built to answer what the company calls the AI Value Paradox: heavy spending on generative AI, and little proof of return.

Bitcube has built and run the platform behind that product since February 2018.

Temporall's data had to come from tools Temporall did not own, and each provider changed its APIs, scopes and permission model on its own schedule. The data was the most sensitive an employer holds — mail, calendars, files and messages — so every integration had to be least-privilege and auditable before a customer would connect it. The platform also ran on live customer data from early on, which meant a bad deploy showed up in an executive's dashboard rather than in a test run. The question the product answered kept moving, from culture to collaboration to AI adoption, so the platform had to be re-aimed several times over without being rebuilt each time and without stalling the customers already on it. Enterprise buyers added their own bar: directory provisioning, two-factor authentication, role-based access and control over who could see whose data, all needed before a pilot could start. And organisational network analysis grows expensive faster than headcount does, because the number of possible relationships rises with the square of the number of people.

Alongside every phase, the platform was kept current rather than allowed to age. Angular was upgraded in place from version 5 to version 17, one release at a time, and the component migrations were run one component per pull request so the live product never stopped. Six environments — development, QA, staging, pre-release, demo and production — kept that possible.