Practifi

The platform reading applies and the vendor's own commercial structure supports it. The client relationship system, pipeline, workflow automation, compliance monitoring and reporting were the product before inference arrived, and the intelligence suite shipped in December 2025 as an add on that existing clients activate through an account representative rather than as a capability woven through what they already had. Strip it out and the platform runs.

The company's own framing that the suite applies an artificial intelligence first framework across the platform sits awkwardly beside its being sold and switched on separately. One dated event would change this grade: a second product described as natively artificial intelligence based is announced for release on 25 August 2026, and if it ships as described this record should be re graded against it.

The autonomy is described and the oversight is not. Published material states that follow ups are generated automatically and that workflow actions are triggered without manual intervention, which is the capability being sold and is stated as a benefit rather than qualified.

Searched for what a person reviews before a generated follow up reaches a client, whether generated content is distinguishable from staff written content inside the client record, whether an approval step exists before an automated workflow action executes, and how a firm audits what the suite did on its behalf, and located none of it. A client relationship system is the firm's record, and content entering it automatically without a described gate becomes indistinguishable from the rest over time.

Searched for an accuracy figure, an error rate, a benchmark, a validation method, a grounding or citation guarantee linking a generated summary back to the conversation it came from, a drift statement or a revalidation cadence, and located none.

The claim most in need of measurement is the one about relationship intelligence surfacing what matters and organising the information that counts, because a summary that omits a material client instruction is wrong in a way nobody notices: the adviser reads a clean summary and never learns what it left out. Nothing published addresses completeness in either direction.

Two advisory firms are named as customers, and they are named on a third party software directory rather than in the vendor's own material, which is a distinction this index applies consistently: a directory entry is not the vendor's published claim and its provenance cannot be established. Searched the company's own material for a named client, a case study or a quantified result from either the platform or the intelligence suite, and located none. The suite shipped in December 2025, so the absence of measured outcomes is expected rather than evasive. The queued check is the vendor's own customer stories material, which would likely settle it.

Searched for a statement on whether client records, meeting content or communications processed by the intelligence suite are used to train, tune or evaluate any model, whether content is retained by any model provider, and whether material from one advisory firm can inform output shown to another, and located none.

The question is complicated here in a way the vendor has not addressed publicly: because the product runs natively on another company's enterprise platform, a buyer needs to know whose terms govern content that passes through the intelligence layer, and nothing published states whether the answer is the vendor's, the platform provider's, or both.

Recorded as an unverified absence. The platform holds the unified client record for advisory firms, spanning demographics, assets, goals and full engagement history, and the intelligence suite now adds conversation content to that record. Searched for a retention schedule, a deletion commitment, a description of how meeting content is handled once summarised, and any data processing terms, and located none.

The underlying enterprise platform the product is built on carries its own extensive privacy documentation, and whether the vendor relies on that or publishes its own position is precisely what is unclear.

A certification claim exists and it fails the test twice over, which is worth setting out because it is the kind of claim that would otherwise be credited on a quick read. A third party software directory states that the company adheres to leading security standards including a named international standard and a named government framework.

The first problem is provenance: the claim sits on a directory rather than on the vendor's own material, and this index checks the domain on every credential. The second is wording: adheres to and compliance are not the words a certified organisation uses. Neither failure means the certifications are absent, only that nothing located establishes them. A trust or security page on the vendor's own domain is the queued check.

A software supplier to advisory firms holds no licence and requires none, and no penalty attaches. The platform performs compliance monitoring for its customers, which is a product capability rather than any supervised status of the vendor, and the two should not be read together.

The unaddressed question is the ordinary one for this category: records held in a client relationship system are examinable material for a regulated advisory firm, and nothing published describes how a firm would demonstrate to an examiner which entries in that record were generated rather than written.

The exposure sits in prioritisation rather than in any explicit judgement about a person. A system that surfaces insights, decides which client context is worth raising and generates follow up actions is allocating adviser attention across a book, and a systematic tendency in what it raises directs service toward some clients and away from others without anyone choosing that.

Searched for any account of how the suite decides what to surface, whether its output was examined for systematic effects across client type, account size or engagement history, and whether a firm can inspect why one client was flagged and another was not, and located none.

Searched for a warranty, an accuracy commitment, a service level, a correction obligation or any allocation of responsibility between vendor and advisory firm, and located none, and no disclaimer placing it plainly on the firm was located either.

The exposure follows from the autonomy the product advertises: a follow up generated and sent automatically, or a workflow action triggered without manual intervention, is an act the advisory firm performed as far as its client and its regulator are concerned. Nothing published addresses what happens when one of those actions is wrong.

The platform underneath is named clearly and the models are not, and here that gap creates a genuine ambiguity rather than a simple silence. This index treats a named platform or host as an infrastructure disclosure rather than a supplier disclosure, and that rule applies.

What makes this instance sharper is that the enterprise platform the product is built on ships its own artificial intelligence services, so a reader told that the product is native to that platform and that it now has artificial intelligence capabilities cannot tell whether the models are the platform provider's, a third party's, or the vendor's own. Searched product pages, the launch announcement and the blog for any resolution and located none.

The architectural decision does most of the work on this axis. The platform is built natively on a major enterprise application platform rather than as standalone software, which means it inherits that platform's integration tooling, application ecosystem and enterprise identity and permission model without the vendor building any of it, and firms already running that platform elsewhere in the business gain a common foundation.

An electronic mail client integration is named, with follow up recommendations surfacing inside it. Held below the top grade because no wealth specific connection is named individually: custodians, portfolio accounting, planning tools and document systems are the integrations an advisory firm evaluates on, and none of them appears in the material located.

Recorded as an unverified absence, with an unusual feature worth noting. Because the product is built natively on a major enterprise application platform, its hosting and residency characteristics are substantially inherited from that platform, which operates published regional infrastructure, so a determined buyer could establish more here than for most vendors in this index. The vendor itself states none of it.

Searched for hosting regions, storage location, a tenancy statement or any residency commitment in the vendor's own material and located none, which leaves a buyer inferring its data location from the platform underneath rather than reading it.

One structural fact is published and no number is. The intelligence suite is an addition to the platform that clients activate separately rather than an included capability, so a buyer knows the artificial intelligence carries its own commercial line, and the newly announced second product is described as sold alongside the existing platform rather than replacing it, which implies a further separate charge. Searched for any rate, per seat figure or tier and located none. For a vendor whose stated customer range spans firms of ten employees to ten thousand, the pricing model is the thing a small firm most needs and least can see.

Breadth here is by firm size rather than by institution type. The buyer is a wealth management or financial advice business and nothing else, with no bank, insurer or asset manager segment addressed, but within that the stated range runs from roughly ten employees to enterprises of ten thousand, which is a genuine spread requiring different configuration, permissioning and support models at each end. The company describes serving firms internationally rather than in a single market. Held below the top grade because the single buyer type is a real limit and because the published customer evidence supporting the international claim was not located.