See it before it shows

At least three people. That's the limit we've set so answers can remain anonymous, and we don't compromise on that.

Yes. No one sees who answered what, not even the manager.

Results are shown as insights, engagement levels, and question-level averages, never as individual answers. And since a team must have at least three people, it's not possible to work out who said what.

A pulse survey asks everyone the same predefined questions. Beat listens first, picks up on the signals in what you share, pauses where needed, and comes back to what actually matters.

In Story, you describe what's really happening day to day and how it affects the team - both what gives energy and what drains it. Beat weighs that together with the survey answers and how the activities you've chosen land. Every insight is built on all three, so each next question gets a little smarter than the last.

Not more questions - just the right ones, at the right time.

You set the pace. Anything from every week to every other month - and you can change it at any time if you notice the rhythm isn't right.

We start with thirteen questions covering engagement and drivers. After that it varies: Beat asks more questions where something needs to be worked out, and fewer where things are stable. How often you measure also affects the number. But all in all, fewer than you'd think.

Not directly, but indirectly all the time. What you share in Story, how the team answers, and what your activities produce all shape what Beat asks next. So you don't choose the questions, but you influence them every time you share something. Individual questions can't be added or removed, though - they're validated, which is why the results can be trusted.

You create an account and start your trial period, then you're guided through an onboarding flow that walks you through three steps: adding your team, setting up your Beat, and getting started with your Story. If you're quick, everything is done in five minutes.

It stays with you. Story is your own space, and no one else can read what you write there. Beat only uses it to understand the team better and to deliver sharper insights, questions, and activity suggestions. What you share may, however, appear as a short summary in the insights, so the context comes through.

Yes, a central admin can initially launch Beat for everyone, or for a select group of teams, which is handy if you want a shared kickoff. But each manager owns their own Beat and runs their own team. Beat isn't an HR tool - Beat is for the manager and the team.

Yes, with an organization plan. Results and insights are then aggregated at the top level, giving you overview views of teams' development in drivers and engagement. Only selected admins can access the underlying teams' results, and managers never see each other's.

As a manager, you see your own team's results, nothing else. In an organization plan, selected admins can see both the overall picture and the individual teams. That's so someone - often HR or an organizational developer - can support managers and teams in their development. Your Story, however, is always private, even from admins.

No, normally not. The team consists of those who report to you, and as manager you stand outside the measurement. Technically, it's possible to add yourself as a team member, but we advise against it. The leadership questions are asked to the team about you, so it would be odd if you also answered them.