Enterprise
Engagement surveys and manager tools for large organizations
For organizations above 2,500 employees, with indicative prices published.
An annual agreement covering engagement cycles for the whole organization and manager seats for everyone who needs them. Annual agreements start at $25,000. The quote sets out which cycles, seats and deployment work it covers.
What a cycle costs at this size
The five base packages up to 2,500 employees are bought in the app. The two above that are quoted, and their indicative prices are published so you can take a number to your finance team before you talk to anyone.
| Employees | One cycle | Per employee | How it is bought |
|---|---|---|---|
| Up to 100 employees | $999 | $9.99 | In the app |
| 101–250 employees | $1,799 | $7.20 | In the app |
| 251–500 employees | $2,999 | $6 | In the app |
| 501–1,000 employees | $4,999 | $5 | In the app |
| 1,001–2,500 employees | $9,499 | $3.80 | In the app |
| 2,501–5,000 employees | $15,499 | $3.10 | Quoted |
| 5,001–10,000 employees | $24,999 | $2.50 | Quoted |
The per-employee price falls as headcount grows, at every row rather than only the quoted ones. The figures above 2,500 continue the same curve; they are not a different pricing approach for larger customers.
Above 10,000 employees there is no published figure. We have not run a cycle at that size, so any number here would be a guess.
What manager seats cost at this size
The manager tools are priced per manager, never per employee, and the rate falls as you add managers. Seats up to 500 are bought and changed in the app; above that they are part of the agreement. The figures here are billed annually; bought in the app and billed monthly, each seat costs $3 a month more, on the same bands.
500 managers
$35,532
a year — an effective $5.92 per manager per month
750 managers
$52,032
a year — an effective $5.78 per manager per month
1,250 managers
$83,526
a year — an effective $5.57 per manager per month
The ladder is graduated, which means each band prices only the managers inside it: the first 24 seats are always $7 a manager a month, billed annually, whether you buy five or five hundred, and only the seats past each boundary get the cheaper rate. Adding managers never lowers your total. Cycle top-up blocks follow the same principle: they come ten or fifty seats at a time, depending on the package, and each seat costs what the seats beside it cost.
The cheapest rung is $5 a manager a month, and it prices only the seats from the 1,000th on — the effective rates above are what a bill actually works out at. Your employees are not counted, not licensed, and do not appear on the invoice — a company of 10,000 people with 1,200 managers is a 1,200-seat customer.
What the agreement covers
An annual cycle allowance
Up to 4 cycles in the year, on one renewal date and one purchase order, rather than a separate purchase each time. Below this size cycles are bought one at a time, which is right for a company that runs one a year and wrong for one that pulses quarterly.
Single sign-on, and a roster that keeps itself
SAML single sign-on for your managers is supported and set up per customer with your identity provider. A roster that keeps itself is built: Microsoft Entra ID or Okta push it through SCIM 2.0, and the changes are applied when an owner or admin confirms. A roster read from an HR system’s own API requires development. The status of each item is set out below.
The paperwork procurement asks for
Our data processing agreement, with its standard contractual clauses, applies by reference to the terms and is counter-signed on request. You also get a sub-processor list with notice of changes, a named contact, and a security review answered by a person.
The works-council pack
A document covering what is asked, what is stored, who can see which numbers, what the reporting floor does, and why no free-text answer is shown as written. It is written for a works council or a European employee representative body, and requires development for your agreement.
A higher limit on the people each manager keeps records for can be part of the agreement. The standard limit is 35 people, a fair-use ceiling that is too low where one manager leads many people, as in retail, hospitality and manufacturing.
Connections
Each connection is off until someone in your workspace turns it on. Here is what each one connects, who turns it on, and what it can see.
Slack and Microsoft Teams, for survey invitations
An owner or admin connects your Slack workspace or a Teams flow. An engagement cycle can then send its invitations and reminders as direct messages, each carrying the person’s own link and nothing about anyone else. Anyone Slack cannot find, or does not reach within six hours, gets the email instead. A Teams flow does not confirm that a message arrived, so everyone invited through Teams gets the email as well. Anyone can ask for email instead, from a link in any message. Facets keeps no Slack or Teams identity for anyone.
Before a cycle opens, a reach check counts how many people on its roster Slack can find, and messages nobody. If your workspace removes the Slack app or revokes its access, direct messages stop at once, every owner and admin is told by email, and invitations go by email until it is reconnected.
Slack and Microsoft Teams channels
A manager can connect a channel of their own to a project or an idea board. It gets what everyone on the project or board can already see, such as updates and a daily list of tasks done, due and overdue, and never a comment, a vote or a figure about one person. A manager’s own channel can also be told how many check-ins are due, and that their group’s survey results are ready or a commitment’s check is due, with no figure and no name. An engagement cycle can have a channel too, told only that the survey is open or closing.
Microsoft 365 and Planner
A manager connects their own Microsoft 365 work account and sends a project’s tasks to a Planner plan in your organization. After that, completing a task on either side completes it on the other at the next check. What is sent is what everyone on the project already sees of each task. Survey answers, Leadership 360 answers and People records never go. Your Microsoft 365 admin may need to approve the app once. Microsoft lists it as TeamFacets.
Microsoft Entra ID and Okta
An owner connects your identity provider, which then keeps the engagement roster through SCIM 2.0. For each person, Facets keeps their name, work email address, manager, department, whether they are active and their end date, and writes nothing back. Changes reach the roster when an owner or admin applies them, or each hour where an owner has turned that on. A manager is shown the names of people it says report to them, and adds them only by pressing to. SAML single sign-on is set up with us, per customer.
Microsoft Power BI
A manager makes a key, and Power BI reads, read-only, what that manager sees of their projects, goals and Workload. The feed carries names but never an email address, a comment or a survey answer. Of a People record, it carries only the person’s name and the hours a week noted for them. Replacing or stopping the key ends the old one at once.
Calendars
Anyone signed in can make a personal calendar link, so that Outlook or another calendar app fetches their own dates and titles. A manager can also email the person they meet a calendar invitation for a repeating 1:1, with the times and the manager’s name and nothing written about the person.
Where your data lives
There are three arrangements, and the difference that matters is who holds the credential that can read the database. The instrument and the reporting floor are the same in all three.
A dedicated instance we run
Available with setup
Your own database and your own deployment rather than a share of ours — in the region you pick, on your retention and deletion timetable, with an export of everything whenever you ask for one.
Who can read the raw answers: no signed-in account, yours or ours. Only server code holding our service credential can read those tables.
What it takes: provisioning rather than engineering. It is how Facets already runs, once per customer.
Your cloud account, we operate it
Requires development
The same deployment, inside your own Amazon, Microsoft or Google account. The tenancy, the backups and the infrastructure bill are yours. Running it, patching it and answering for it stay with us, through an access path you can revoke without asking.
Who can read the raw answers: the application credential is ours, and the disks and the snapshots are yours. An administrator in your own account with a reason has a route the first arrangement gives nobody.
What it takes: a containerized build and a migrator that runs itself. Both are engineering we do for the engagement, scoped and quoted before anything starts.
Your servers, you operate it
Requires development
An image you pull into your own registry — an internal GitLab is a perfectly good one — and run behind your own firewall, with no outbound connection required. The written half of a report falls back to the deterministic version, so nothing has to leave the building to be written up.
Who can read the raw answers: your administrators. That is the point of the model and it is also what it costs, which is the paragraph below rather than a footnote.
What it takes: everything the second arrangement needs, plus the operator tooling stripped out, an entitlement path that works with no payment processor attached, and a route for upgrades. The most work of the three by a distance.
What moving the install toward you actually costs
The reporting floor, the joint unit-and-manager suppression and the rule that no free-text answer is ever shown verbatim are enforced by code, running on a database nobody at your organization can read. That is the basis of what your employees are told before they answer a single question. On your own servers it becomes an undertaking instead: the floor is a row somebody with the credential can edit, and the raw answers are one query away. We will not ship that arrangement with the wording your people see left as it is — that wording is written for them, and they have to be told who is operating the install. If that is unacceptable, it is the wrong model and one of the first two is the answer.
None of the three has a list price. Each is quoted before anything starts, because the cost is setup and ongoing support, and both depend on the arrangement you pick, whether it has to run with no network, and how often you want upgrades.
What is available, and what needs work
Each item below has one of three statuses. The quote states which items your agreement includes, what each depends on, and the dates.
Available now
- Manager seats, invitations, seat reassignment when somebody leaves, and an organization-wide administration view.
- The engagement survey and its reporting rules: groups below the reporting minimum hidden, and results with a range showing their uncertainty at every level of your organization.
- A roster that keeps itself. Microsoft Entra ID or Okta push it through SCIM 2.0. The changes are applied when an owner or admin confirms them, or each hour where an owner has turned that on.
- An engagement cycle can be answered in English or Spanish, one language a cycle, chosen when you set it up. The results, themes and written summary are in English.
- Self-serve export, whatever happens to the agreement: an owner or admin downloads the workspace’s rosters, team packs and engagement summaries, and a manager each person’s record. Individual notes and leadership briefs stay with the people they are about.
Available with setup
- SAML single sign-on. Supported and set up per customer, with your identity provider. It has not yet been walked end to end with a customer’s identity provider, so the first one is done with us in the room rather than over a support ticket.
- A dedicated instance. Provisioning we can do today, once per customer.
- The annual cycle allowance and a higher people limit. Both are terms recorded in your agreement.
Requires development
This is built to order: work we scope, price and put a date against in the agreement.
- More languages. An engagement cycle can be run in English or Spanish, one language a cycle; the team survey and the Leadership 360 exist in English. Each further language has to be translated and checked item by item, so it is weeks of careful work, priced into an agreement that needs it.
- A roster from an HR system’s own API. Reading a roster from an HR system directly, rather than through Entra ID or Okta, needs that vendor’s partner registration or a unified API. It is built for the agreement that needs it.
- A cloud or own-server install. Putting the install in your cloud account or on your own servers needs a containerized build, a migrator that runs itself and the operator tooling stripped out.
- The works-council pack. Written for your agreement.
SOC 2 and ISO 27001 are not held
These are outside audits, not features we can ship on a schedule. If your procurement needs a SOC 2 Type II report before you can sign, tell us in the first conversation and we will scope it into the agreement as work with a date, with the outcome depending on the auditor. The security page lists what is in place meanwhile.
If you need any of these before you can sign
Say so in the first conversation. Each item you need goes into the agreement with a date against it.