Everything you need to ask

Most teams are live within a week. The agent is lightweight, deploys through your existing MDM, and starts producing insight the same day.

Native desktop agents for Windows, macOS, and Linux, with offline capture and deferred sync.

Yes — every plan starts with a 14-day free trial, no credit card required.

Momentum is built to be transparent and consent-aware, with aggregate-first reporting and configurable collection. We help you roll out in a way that meets your local regulations and keeps trust intact.

Yes. Self-visibility is a core principle — people can see their own focus scores and trends, which is exactly what drives healthy behaviour change.

Screenshots are entirely optional and off by default. Most customers run Momentum without them, relying on activity and focus signals instead.

Momentum is SOC 2 Type II and ISO 27001 certified, and GDPR aligned, with regional data residency options.

Yes, on Custom plans, alongside full audit logs.

You can choose your data residency region. Custom-plan customers can discuss private cloud and on-prem options.

Pricing is per user, per month, billed monthly or annually. Annual billing saves 25% on every plan.

Yes, upgrade or downgrade at any time. Changes are prorated automatically.

Annual billing saves 25%. Custom agreements are tailored to your seat count and term.

Every new install lands in your Machines list as Pending. An Admin reviews it and either Approves it — at which point capture data starts flowing into dashboards — or Rejects it. Nothing counts toward analytics until a machine is explicitly approved, so unknown or personal devices never pollute your data.

Yes. Turn on auto-approve in machine settings and any agent installed with a valid tenant invitation is approved the moment it registers. Most teams enable it during an MDM-driven rollout, then switch back to manual review once the fleet is enrolled, keeping the Pending queue as a safety net.

Admins can trigger a remote uninstall from the Machines page — no desk visit or IT ticket needed. You can also disable login for a machine without uninstalling, which blocks the agent from submitting data while you investigate. Both actions are recorded so you can see who did what, and when.

No. The agent keeps capturing active and idle time, app usage, and input counts locally while the machine is offline. As soon as connectivity returns, the backlog syncs and the Timeline view backfills, with offline app usage clearly represented. Flights, site visits, and flaky Wi-Fi don't create blind spots.

It's designed to be invisible in day-to-day use, and you don't have to take our word for it: the Resource Usage module shows the agent's own CPU and memory footprint per machine over time. If a version ever misbehaves on specific hardware, you'll see it in the data before anyone files a complaint.

Start with the Logs module. It separates Info from Error entries and tags each one by source — Daemon, Installer, Task Scheduler, or Upgrade — so you can tell an update failure from a scheduling issue in seconds. The master user grid on the Workforce Dashboard also flags agent status per person at a glance.

Admins send an invitation from Tenant Management. The employee accepts, installs the desktop agent, and their machine appears in the Pending queue (or is auto-approved if you've enabled that). From acceptance to first data on the dashboard is typically the same day, with no manual account provisioning.

Active and idle time, which applications were in use and for how long, and aggregate input counts (clicks and keystrokes as numbers). That's the full list. It does not read documents, messages, or browsing content, and screenshots are optional and off by default — most customers never enable them.

The agent watches for input activity. When clicks and keystrokes stop for longer than your configured idle threshold, time is marked idle until activity resumes. Thresholds live in General settings, so you decide how long a pause counts as thinking time versus genuinely away from the desk.

Yes. Every User can open their own Timeline and Activity views — the same day strip, app usage, input stats, and productivity score their manager sees. Self-visibility is deliberate: people who can see their own data trust the system, and often improve their own patterns before anyone says a word.

Capture is anchored to the workday you define — office start and end times, expected desk hours, and workday length all live in General settings. Analytics like expected-vs-actual desk time are computed against those boundaries, so an early start or late evening is visible in context rather than silently judged.

Data management at that scope is restricted to your tenant's administrators. Retention follows your plan and configuration, and deletion requests are honoured in line with GDPR obligations.

The score compares time spent in apps you've classified as Productive against the target productive hours you set in General settings, within the context of active desk time. It's your definition of productive work, applied consistently — not a black-box judgement about how busy someone looked. That score is one of four pillars, alongside attendance, security, and AI adoption, rolled into the org-wide Organization Health Score.

Expected desk hours are the daily presence baseline you configure per tenant. The Activity view compares each person's actual active time against that expectation, and the Workforce Dashboard trends expected-vs-actual across the organisation — feeding the Attendance & Compliance pillar of the Organization Health Score. It turns 'are people around?' from a feeling into a measurable, fair baseline.

Idle time never counts as productive, but it isn't hidden either. The Timeline day strip shows active and idle blocks side by side, and department time distribution on the dashboard includes idle explicitly. Long idle stretches usually point at meetings, calls, or calendar problems — context a manager should see, not a verdict.

It's bucketed as Unmarked — neither productive nor non-productive. Unmarked time is reported separately so it can't silently drag scores down, and it doubles as a to-do list: Admins review the Unmarked queue, classify the apps, and the classification applies to future analysis from then on.

The Workforce Dashboard surfaces top and bottom performers and departments as a coaching input, visible to Managers and Admins only — never broadcast to peers. Combined with the expected-vs-actual trend and department breakdowns, it points leaders at where support is needed rather than producing a public leaderboard.

Admins classify each detected application as Productive, Non-Productive, or leave it Unmarked. These global rules drive scoring and every app-usage breakdown across the tenant. New apps appear automatically as agents observe them, so the catalogue builds itself — you just decide what each app means for your business.

Yes — that's exactly what per-department app rules are for. Figma can be Productive for Design and Non-Productive for Finance; YouTube can be Productive for the social media team alone. Department rules override the global classification for members of that department, so one policy never has to fit everyone.

Departments are the organising unit for analytics. The Workforce Dashboard compares departments on productive time, shows each department's time distribution including idle, and highlights top and bottom departments. Assigning people correctly is what makes org-level questions — which function is stretched, which is coasting — answerable.

Classification changes apply from the moment you make them. The underlying usage record is never rewritten — the same minutes simply score differently going forward. This keeps historical reports honest while letting you refine rules as you learn what productive actually looks like for each team.

Front-load an hour to classify your top apps and the long tail mostly takes care of itself. Unmarked time is reported separately, so you'll see when a new tool is accumulating meaningful hours and worth classifying. Most Admins review the Unmarked list monthly; mature tenants touch rules far less often.

A seat is a user whose activity is being captured — Admins and Managers who also run the agent count once, dashboard-only viewers don't need a paid capture seat on Custom agreements. You're billed for active seats per month, and deactivated users free their seat immediately.

Alpha covers up to 25 seats for companies up to 25 employees. When you're ready for more seats, endpoint security, or asset management, upgrade to Alpha AI in the billing screen — the change is prorated, nothing is reinstalled, and all history carries over. Agents, machines, rules, and departments are plan-independent, so upgrading is a billing event, not a migration.

Monthly plans simply bill fewer seats next cycle when usage drops. Annual plans reserve your committed seat count for the term at the discounted rate; you can add seats mid-term at the same per-seat price, prorated, but committed seats aren't refunded mid-term. Custom terms are negotiated.

The 7-day free trial retains 7 days of activity history, Alpha retains 1 month, and Alpha AI retains twelve months, with configurable retention and export on request. Custom retention is contractual — including indefinite retention or aggressive purging, whichever your compliance posture requires. Deleting a tenant removes its data permanently after a grace window.

Card is standard on Alpha and Alpha AI — the 7-day free trial needs no card at all. Custom plans support invoicing with NET-30 terms, purchase orders, and procurement paperwork — security questionnaires, DPAs, and vendor forms included. Annual invoicing is the norm for larger rollouts and locks in the 25% annual discount.

Billing is per user, not per machine. One person running the agent on a desktop and a laptop is still one seat; their activity merges into a single timeline. On plans that include asset management (Alpha AI and Custom), machine approval, remote uninstall, and the rest of device governance carry no extra per-device cost.