Planhat

Planhat's own data model, workflow engine, project and task management and dashboards carry the product, and all of them keep working without a model. The Planhat AI Platform (AIP) is included in every plan beside templated and advanced automations, and an Upgraded AI Platform add on extends it for enterprise wide rollouts, with AI deployment sold as a professional service. The company dates to 2015 and spent seven bootstrapped years building data unification before the current model wave. CRM, customer success and professional services automation are its three solutions, each a complete product without the AI layer.

Automation is metered, which supplies a ceiling, and nothing describes what it may do. On enterprise contracts the volume of automated actions triggered by workflows carries usage based charges, so a workflow running away exhausts a budget visibly rather than silently, and transactional email volume is separately metered on the same basis.

That is a real constraint arising from the commercial model rather than from a published control, and it is a billing mechanism rather than a safety one. What is absent is everything above it: no statement describes what an automation may change, whether it can write into connected systems, whether approval gates exist, what an administrator can constrain by role, or what halts a workflow in progress.

Health scores flag at risk accounts and nothing states whether a flag can trigger outreach or commercial action automatically. The workflows are customer authored, which places responsibility with the buyer without removing the need for controls. Ask what automations can write to connected systems, whether any require approval, and what stops a workflow mid execution.

A separately sold intelligence module with nothing published about what is inside it. The artificial intelligence layer is marketed and priced as its own add on, and no model provider, family or version is named, no model card exists, and no evaluation or accuracy figure appears for any component. Two gaps carry practical weight.

Health scores flag accounts as at risk and drive retention spending, escalation and executive attention, and nothing states how often those flags are right or how far ahead of an actual cancellation they appear, which is the measurement that determines whether the score is worth acting on.

And because scoring is described as configurable, the division between what a customer's own rules determine and what a model infers is itself undisclosed, so a buyer cannot tell which part of a score they built and which part they bought. Ask which models the intelligence module uses, what precision the churn risk flags achieve against realised outcomes and with what lead time, and which elements of a health score are model derived.

Solid independent standing and no retention measurement, which is now three consecutive vendors in this category. A review base of roughly six hundred and eighty six ratings at four and a half out of five, an analyst recognition as a category leader in December 2024, and named enterprise references across data infrastructure, security, technology distribution and reputation software together establish genuine adoption.

What is absent is the measurement the category exists for: no published study shows churn reduction or net revenue retention improvement across a stated customer population over a stated period. That gap now appears at the category leader, at the merged challenger and here, which suggests a category convention rather than a vendor failing, and it is worth stating as such.

Independent reviewers add two operational findings the vendor does not surface: an initial learning curve requiring time to adapt to the platform's breadth, and a recommendation that scale deployments have a dedicated technically capable administrator. Ask for retention improvement measured across a stated cohort and period, and for median time from contract to first working health score.

The platform sends to an existing customer base through a separately purchased module, and none of the surrounding obligations are described. Email marketing is an add on rather than a core capability, and transactional email volume is metered on enterprise contracts, so sending exists and is deliberate rather than incidental.

Recipients are people at companies already under contract with the customer, which answers most of the consent question through that relationship and keeps volumes modest against a marketing platform. What is unaddressed is suppression: nothing published states whether an unsubscribe recorded against a lifecycle email is honoured by workflow triggered messages, whether preference state is held once or per module, or how the customer facing portal capability interacts with mail opt outs.

A platform that can reach the same person through campaigns, automated workflows and portals owes a single suppression view. Ask whether opt out is honoured across all sending surfaces from one preference record, and what governs automated workflow email.

A European headquartered vendor whose privacy documentation was not reached on this pass. No privacy policy contents, processing agreement, subprocessor list, transfer mechanism, retention period or data protection officer was located, and no privacy certification is claimed in anything found.

This records what a buyer could establish before contacting sales rather than a finding of absence, and a Stockholm based company selling into European enterprises would face the documentation question in every deal. The corpus makes the stakes substantial: the platform consolidates support history, product usage telemetry, billing records and engagement data against identified individuals at customer companies, drawn from four separate source systems, and the professional services capability adds project and time records about the customer's own staff.

The distributed team across four continents raises a support access question that nothing published addresses. Ask for the processing agreement, the subprocessor list, the retention schedule, the transfer mechanism for European data, and whether staff outside the region can access production data.

No external corpus is licensed and the provenance question concerns what the unified data foundation does with what it gathers. Everything originates in the customer's own systems, whether the customer record platform, support ticketing, product analytics or billing, so there is no purchased database or third party feed to trace. What is unstated is aggregation.

A platform whose stated purpose is unifying fragmented data across hundreds of customers accumulates a substantial cross customer picture of how recurring revenue businesses behave, and nothing published states whether health scoring benchmarks, churn signals or the intelligence module draw on patterns derived from the wider base, or whether any anonymised aggregation occurs.

For a vendor selling configurable health scores, whether the configuration templates or scoring defaults encode learnings from other customers is a fair question. Ask whether any cross customer aggregation informs health scoring, benchmarks or the intelligence module, and in what form.

Integration runs through conventional sanctioned routes across the systems the platform consolidates. Connections reach customer record platforms, support ticketing systems, product analytics tools and billing platforms through their own published integration surfaces, which is the ordinary and low exposure arrangement for a data unification product, and nothing resembling credential storage, scraping or unsanctioned automation appears anywhere in what was located.

The vendor's own position is as a consumer of data from those systems rather than a writer of automated actions into third party platforms, which limits the permission scopes it needs to hold. Held below the top band because no stated conformance position against any specific platform's terms was found, which is the distinction the grading convention draws here, and because the breadth of systems consolidated means the platform depends on continued interface access across four categories of third party software without any published statement about what happens if one narrows. Ask what permission scopes each connector requests, and whether any named platform conformance commitments exist contractually.

A separately sold intelligence module reading a consolidated corpus, with no stewardship position located. The platform holds support history, product telemetry, billing records and engagement data tied to named individuals at customer companies, plus professional services records about the customer's own staff, and the intelligence add on reads across all of it.

Nothing published states whether that material trains or tunes any model, which providers process it when the module runs, what retention applies to prompts and outputs, or whether anything crosses a tenant boundary. No governance document, evaluation record, red teaming artifact or independently audited management standard for artificial intelligence was located.

The commercial structure raises one additional question worth asking directly: because the intelligence layer is a separate purchase, a buyer should establish whether the data commitments differ between the core platform and the module, or whether one set of terms covers both. Ask whether consolidated customer data trains or tunes any model, which providers process it, what retention applies, and whether the add on module operates under the same data terms as the platform.

Communication reaches an existing customer under the sending company's brand, and the scoring layer is where the question remains. Email campaigns, workflow messages and customer facing portals are branded to the customer's business and directed at people who already hold a contract with it, so no impersonation arises and no cold contact requires disclosure. What is unaddressed is that individuals at customer companies are profiled.

Support tickets, product usage, billing behaviour and engagement are combined into a view of each person and each account, health is scored, and risk is flagged to the vendor's customer, without anything published describing what notice reaches the individual or how they would exercise rights over the resulting profile. The portal capability is the one place an external person interacts directly with the platform, and nothing states what they are told about the data held behind it. Ask what notice reaches individuals at customer companies whose activity is consolidated and scored, and what the customer facing portal discloses about the data behind it.

Consolidation is the product rather than a feature of it, which makes the integration surface load bearing. The platform's stated purpose is unifying data that sits fragmented across customer record systems, support ticketing, product analytics and billing, so the connectors are not an accessory to the value proposition but the mechanism delivering it, and reviewers consistently identify configurability and integration with existing tools as strengths.

A flexible data foundation underneath means the platform accommodates a customer's own object model rather than imposing a fixed one, which matters for organisations whose customer structure does not fit a standard account and contact shape. The unlimited user model amplifies the ecosystem effect, since data unified once is reachable by sales, support, success and product teams without licensing each of them separately.

Held below the top band on verification: no developer documentation, interface reference, authentication model, rate limits or integration inventory was reached on this pass, and reviewers note that realising the configurability requires a technically capable administrator. Ask for the interface documentation, the current integration list, and what administrative capability a full deployment assumes.

No deployment or residency information was reached on the routes taken this pass. No hosting provider or region is named, no European or United Kingdom residency election is described, no tenancy model is stated, and no recovery time or recovery point objective appears.

The gap is notable specifically because the vendor is Swedish, which would ordinarily make European residency an easy claim to make and a natural part of its positioning against American competitors, and no such claim was located either way.

The distributed operating model across Europe, North America, South America and Asia Pacific raises a second question nothing addresses: whether support staff in any of those regions can reach production data containing consolidated customer records, billing history and individual level engagement profiles. For a platform holding the complete post sale picture of a customer's entire book of business, both questions are procurement gates. Ask which regions host the platform, whether European residency is available, what the tenancy model is, and which staff locations can access production data.

No certification, attestation or trust surface was reached on the routes taken this pass. No trust centre, service organisation control report, international information security certification, penetration testing statement, vulnerability disclosure route or enumerated control page was located.

This records verifiability before a sales conversation rather than a judgement about the underlying programme, and a vendor whose named customers include data infrastructure, security and enterprise technology companies would not have completed those procurement processes without documentation, so it very likely exists behind a request. Two features of the operation make the questions sharper than company size alone would suggest.

The platform consolidates data from four categories of source system, so a compromise reaches further than a single application breach would. And the unlimited user model means access is granted broadly across an organisation by design, which makes access control and audit logging more consequential here than in a seat constrained product. Ask which certifications are held with audit periods and auditors, and what access controls and audit logging govern the unlimited user model.

Every plan is quoted, and no price, unit or tier appears anywhere on Planhat's site. The pricing page sets out what all plans include, from the data model, open API and native integrations to automations, the Planhat AI Platform, dashboards and audit logs, then names four add ons: Upgraded AI Platform, Advanced Service, Email Marketing and Advanced Portals.

Managed services and professional services, covering onboarding, technical deployment, AI deployment, 24/5 support and strategic advisory, sit behind the same enquiry form. Planhat sells several user types, including View Users. There is no trial or self serve purchase.

Nothing published addresses leaving, and the flexible data model that makes the platform valuable also makes exit expensive. No statement of export scope or format was located, nothing describes whether the unified customer records, configured health scoring, workflow logic, portal content and professional services history leave with a departing customer, and no retention period, deletion timeline or renewal notice term appears. The specific exposure is configuration rather than raw data.

The platform's differentiator is a data foundation shaped to the customer's own model, built with technical administrator effort over time, and reviewers identify both a learning curve and a need for dedicated administrative capability, so what a departing customer would struggle to reproduce is the shape they built rather than the records inside it. Source data largely remains in the originating systems, which is a genuine mitigation worth recording. Ask what exports and in what format, whether health scoring configuration and workflow logic are portable, and what the deletion timeline is after termination.

The platform sends through a purchased module at metered volume, so the exposure exists rather than being architecturally absent, and none of the discipline is described. Email marketing is an add on and transactional email volume carries usage charges on enterprise contracts, which confirms sending is a real and deliberate capability rather than incidental notification traffic.

Recipients are an existing customer base rather than a purchased list, which keeps reputational stakes well below an outbound product. Nothing published states whether mail leaves from vendor infrastructure or the customer's own domain, who configures authentication records, what bounce handling applies, or how sending reputation is isolated between tenants on shared infrastructure.

The metering is a cost control rather than a deliverability control, and a customer billed per message has an incentive to send fewer rather than a mechanism to send better. Ask which domain sends, who configures authentication, what bounce and complaint handling applies, and how tenant reputation is isolated.

The fit is stated at both ends, and the pricing architecture is itself a coverage decision. Independent analysis describes the target precisely as business to business recurring revenue companies with hundreds to thousands of customers, multiple product lines and cross functional teams needing a flexible data first platform, and states equally plainly who should not buy it, naming very early stage companies with small customer bases and organisations wanting only a ticketing system.

Publishing where a product stops fitting is rarer than publishing where it starts. The unlimited user model extends coverage sideways rather than upward, letting sales, support and product teams work in the platform without seat cost, which is why the vendor can credibly position across three functions. Geographic reach is real rather than claimed, with hubs across Europe, North America, South America and Asia Pacific and a customer base concentrated in enterprise technology.

Held below the top band because the vendor's own segment statements were not reached on this pass, no industry pages or localisation were located, and the account based model means a small team serving a very large customer base faces enterprise pricing without being an enterprise. Ask what the smallest viable deployment is by account volume.