| Build it yourself | Enterprise EX suite | Embeddable engine (IWE) | |
|---|---|---|---|
| Time to a working pulse | Months: survey UI, delivery, scoring, aggregation, dashboards, then the parts below that do not look like work until they are | Weeks to procure, then their timeline; strong if you want a standalone tool, slower if you want it inside your product | A sandbox in an afternoon; production behind a licence and an automated certification check |
| Instrument licensing | Your problem, and a real one: several widely copied scales are not free for commercial use (the WHO-5, for example, is now distributed non-commercial-only). Verbatim reuse of copyrighted items is the trap teams find in legal review, late | Handled internally; you inherit their choices and cannot usually audit them | Licence-clean instrument set as standard, activation gated per instrument in the schema, citations published |
| Anonymity threshold | An if-statement someone writes, and someone else can remove; enforcement quality depends on review culture | Typically enforced in the application layer; thresholds stated in help docs, method rarely published | n≥5 as a database CHECK constraint: sub-floor values are never stored, so no export or admin path can leak them |
| Statistical honesty (intervals, labels) | Possible if you have a statistician; most builds ship bare averages because intervals invite questions | Varies; the market leader advises treating a few points as meaningful rather than publishing a method | 95% t-intervals stored with every value, provisional labels and suppression reasons in the row, certification checks they are displayed |
| Safeguarding | Your duty of care to design, review and maintain; occupational-health review is rarely budgeted | Usually present, configurable by the customer, which is both a feature and the risk | Ships locked: external-first crisis signposting, fixed reviewed copy, not editable by anyone downstream |
| Data portability | Total: it is your database | Export formats vary; aggregate methodology is usually not portable | Aggregates export in the open OWHS format; the method is a public standard, not our documentation |
| Cost shape | Engineering time up front, then maintenance forever; no per-user fee | Per-employee-per-month across the suite, procurement-priced | Published rate card: 7p per enrolled user per month to 100k users, deep dives £1 per completed dive, signposting +3p; free for any employer measuring its own workforce |
| Breadth beyond measurement | Whatever you build | Their real advantage: 360s, engagement action planning, lifecycle surveys, consulting, HRIS integrations | Deliberately narrow: measurement, honest aggregates, routing. It is a component, not a platform |
Measurement is your product's core differentiator, you have psychometric and statistical capability in-house, and you have budgeted the unglamorous parts: instrument rights clearance, disclosure control, safeguarding review, and the maintenance tail. Full control is a real advantage and some teams should take it.
You want a complete employee-listening programme for your own organisation, with consultants, action planning and HRIS integration, and you do not need the measurement inside your own product. The big suites are good at what they are actually for. Their weakness is being embedded: they are destinations, not components.
You are a product team that needs credible, defensible wellbeing measurement inside your own application without becoming a psychometrics company, and you want the honesty properties to be provable to your enterprise clients' auditors rather than promised in your marketing. That is the case the IWE is built for, and the rate card is public.
The n≥5 constraint is published verbatim. The interactive demo shows suppression happening. The export format is an open standard you can read without talking to us. And any employer can use the engine free, forever, at alltoogether.com, which is the strongest evidence we can offer that the licensed product is priced on distribution, not on scarcity.
Intelligent Wellbeing Engine (IWE) and Wellbeing Engine (wellbeingengine.io) are trading styles of All Toogether Ltd, registered in England and Wales, company no. 14775309, registered office Jactin House, 24 Hood Street, Manchester, United Kingdom, M4 6WX. The Intelligent Wellbeing Engine (IWE) is workplace wellbeing measurement software. It is not an insurance product or service, and nothing on this site is insurance or financial advice.
A dedicated licensing entity is being established.