Alternatives to GUIDEcx
Other Customer success and onboarding vendors we measure, sorted by how much they publish that GUIDEcx does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 27 that differ from GUIDEcx on at least one criterion we measured for both. Public transparency score, not a product or security rating.
GUIDEcx has 7 gaps in what we could measure: Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “publishes and GUIDEcx does not” is the one that closes them.
| Vendor | Score | Publishes, and GUIDEcx does not | GUIDEcx publishes, and they do not | |
|---|---|---|---|---|
| Dockdock.us | 74/100 | 4 Status page with history, Public pricing, Uptime SLA with a figure, +1 | nothing | Compare |
| Userflowuserflow.com | 48/100 | 4 Status page with history, Public pricing, Uptime SLA with a figure, +1 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Gainsightgainsight.com | 61/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Navatticnavattic.com | 57/100 | 3 Subprocessor list, Public pricing, HTTPS enforced with HSTS | 2 Data location stated, Certifications named | Compare |
| ClientSuccessclientsuccess.com | 52/100 | 3 Subprocessor list, Public pricing, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Chameleontrychameleon.com | 48/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Whatfixwhatfix.com | 43/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Catalystcatalyst.io | 35/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Arcadearcade.software | 57/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Inline Manualinlinemanual.com | 57/100 | 2 Status page with history, Public pricing | 1 Named privacy contact | Compare |
| Pendopendo.io | 52/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| Custcust.co | 39/100 | 2 Public pricing, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.