N2Hive

The first application of this band in the index, and the convention reserves it for exactly this case: a marketed claim that fails the removal test, rather than a competent product making no claim. The lead sentence on every product surface states that through machine learning and automation this is an artificial intelligence driven platform. Every capability then described underneath it is assembly, routing or configuration.

Proposal decks are generated by eliminating manual administrative effort. Vendor fulfilment is handled by routing and tracking logic. The modular framework is customisation. Business intelligence is delivered with drag and drop simplicity and no coding required. Remove the model layer entirely and not one described feature stops working, because nothing in the published description depends on a model to begin with. The claim sits in the positioning and never reaches the product.

What the platform automates is internal routing and document assembly rather than action taken toward a third party, so the exposure this axis usually measures is structurally small here. The controls that do exist are configuration rather than oversight: modules are selected individually, routing rules direct orders to the correct vendor, and dashboards are built by drag and drop.

Across every page read, no permissions model, role definition, approval step, audit record or access log appears, at a platform holding order, contract and billing records for large media organisations and feeding executive reporting from them. The trust centre may carry a permissions position and was left unread.

Machine learning is named in the opening sentence of every product surface and nothing behind it is ever identified: no model, provider, family, version, technique or hosting arrangement appears anywhere. The disclosure problem compounds the centrality problem recorded on the row above. Because no capability is described in enough detail to establish what a model would even be doing, a reader cannot tell whether the transparency gap covers a real layer or an absent one. A vendor that publishes two office addresses, a support line and a live third party trust centre is plainly capable of specificity where it chooses to apply it.

The customer wall is the strongest part and nothing supports it. Nine logos are published under an explicit heading naming them as companies using the platform, and several are large and checkable United States media businesses including a major metropolitan newspaper, a national publishing group and two broadcast groups. That is a real claim placed where a reader can test it.

Behind it: a case study library exists and was left unread, an independent review platform holds a single review on an unclaimed profile, and the only quantified claim anywhere is that the platform doubles a representative's selling time, repeated four times across the page as a slogan with no method, period, customer or measurement basis. One piece of operational evidence deserves credit and appears on the exit and commercial rows too: a published six phase implementation timeline with durations attached to each phase.

Structurally light, because the platform runs proposals, orders and fulfilment rather than outbound campaigns, so there is no sequencing surface to govern. What sits behind it is more than most vendors in this category publish: the parent maintains four dedicated compliance pages covering advertising regulation, accessibility, the European data protection regulation and the California consumer privacy act, gathered under a compliance section in the footer alongside a trust centre.

Advertising regulation is the relevant one here, since the platform routes and fulfils advertising orders for media sellers. All four pages were left unread and are flagged, and no consent, unsubscribe or recipient removal position was located on any read page.

The structure is right even though the contents were not read. A compliance section in the site footer gathers dedicated pages for the European data protection regulation and the California consumer privacy act, alongside advertising regulation and accessibility, with a privacy policy and terms of use published separately and a live trust centre hosted on a named third party compliance platform linked beside them.

Naming two statutes with a page each, and putting a self serve trust centre in the footer rather than behind a request form, is a real posture from a vendor of this size. Held off the top band because every one of those documents was left unread and is flagged, and because nothing located on any read page addresses the individuals whose records pass through a platform holding customer, order, contract and billing data for large media organisations.

The platform supplies no contact data of its own. Records are the customer's own accounts, orders, contracts and campaign results, with reporting pulled from advertising and analytics sources the customer already runs. The provenance question that matters here is different from the category norm and worth a buyer's attention: the parent is a full service advertising agency running programmatic display, audio, native, over the top and email campaigns for its own clients, and it also operates the platform holding sales and order data for media companies. Nothing published states how those two data estates are separated, or whether campaign performance data flowing through the reporting layer is available to the agency side.

Exposure appears structurally low. The platform connects to advertising and analytics sources through interfaces those platforms publish, and nothing anywhere scrapes, rents an identity, rotates accounts, relays through a proxy or simulates human behaviour, which separates this cleanly from most of the current alphabetical stretch.

Held at C on evidence rather than on suspicion: a dedicated integrations page for this product exists and was left unread, the three hundred connector figure quoted in the parent's materials belongs to a sibling reporting product rather than to this one, and no conformance position is stated for any connected platform.

No training or cross customer statement was located, and the cross customer question has an unusually concrete edge here. The published customer wall includes two large newspaper businesses and two broadcast groups, several of which compete with each other for advertising revenue in overlapping markets, and the platform holds their order books, contract terms, pipeline forecasts and representative performance while feeding a business intelligence layer built on all of it.

Beside that sits the agency question recorded on the licensing row, since the same company sells advertising services into the market its platform customers sell into. Nothing published addresses separation on either front. A live trust centre exists and may carry a position; it was left unread.

Almost nothing on this axis engages, which is worth recording plainly rather than treating as an absence of evidence. The platform produces proposals and contracts for counterparties the seller is already in a commercial conversation with, routes orders to vendors under existing agreements, and captures responses through forms and links.

No message is generated to a stranger, no identity is substituted, no account is rented and no detection avoidance language appears anywhere across the pages read. What remains unaddressed is narrow: whether a recipient of an automatically assembled proposal deck is told how it was produced, in a product whose positioning claims machine learning generated it.

The evidence available is thin and points in a promising direction. A dedicated integrations page for this product exists and was left unread, the parent's reporting product advertises more than three hundred connectors, and the modular design implies data movement between the platform's own components rather than out to a customer's other systems.

What could not be located on any read page: a named connector to any system of record, a programmatic interface, webhooks, developer documentation or a marketplace listing. For a platform sold on connecting sales and operational workflows and feeding executive reporting, the absence of any named external destination on the product page itself is the gap, and the integrations page is top of the re verify list.

Hosting, region and residency are unaddressed on every page read. What the vendor does publish is corporate location in unusual detail for a company this size: two full street addresses across two states, a main line, a separate regional line and a dedicated support number, plus a named operating entity. Knowing where the company sits is not knowing where the data sits, and a platform holding order books and contract records for large media organisations leaves that question open. The trust centre would ordinarily carry an infrastructure statement and was left unread.

A live trust centre hosted on a named third party compliance platform, linked from the site footer under a compliance heading, reachable without a request form or a sales conversation. That artefact in that position is the thing this index has spent the whole alphabetical block finding missing: the two vendors graded immediately before this one both assert certifications with no trust centre behind them, one of them naming a certification that does not exist.

Around it sit dedicated pages for accessibility, the European regulation, the California act and advertising regulation. Held off the top band for a reason that is about this read rather than about the vendor: the trust centre's contents were not opened, so no attestation, report type, audit date or scope can be recorded, and no control set, certification or infrastructure detail is enumerated on any page the vendor itself serves. Opening it is top of the re verify list and would move this row in either direction.

No price appears anywhere, in any form, for any module. There is no pricing page, no pricing entry in the navigation, no unit of pricing, no tier, no range, no floor and no example, and every route converges on contacting sales, requesting information or completing a gated form to view materials.

The modular framework is sold as the central commercial argument, with the promise that a buyer stops paying for features they do not need, and the number that would let anyone evaluate that argument is absent. One disclosure runs the other way and deserves recording because it is genuinely uncommon: a published six phase implementation timeline with durations attached, running from a one to two week audit through a four week onboarding to a two week launch. Telling a buyer this is a three to four month implementation while telling them nothing about cost is a partial disclosure very few vendors make at all.

Nothing on export, deletion, retention or post termination rights was located on any page read, at a platform that accumulates precisely the records a media sales organisation would find hardest to rebuild: order history, contract terms, vendor fulfilment records, billing and the business intelligence layer built on top of them.

A terms of use and a privacy policy are published and both were left unread, and a live trust centre sits beside them, which is why this holds at C rather than lower. The migration question is live for a second reason worth noting: three of the four sibling products in this family now resolve to a different domain and a different platform login, so a buyer should establish which estate this product will live on before committing records to it.

Structural, and the structure genuinely removes the exposure rather than hiding it. The platform runs no outbound campaigns and no sequencing surface: it assembles proposals, routes orders and captures responses through forms and links, so there is no sending reputation to protect and no volume governor to publish. The parent sells email marketing as an agency service, and that is a separate engagement delivered by people rather than a capability of this product. No warming, throttling, bounce, complaint, suppression or authentication mechanism appears anywhere, and on this product none of them would have anything to govern.

Six industries each carry a dedicated page, covering healthcare, media and agencies, nonprofit and religious, gaming, retail and automotive, and the buyer is named as a sales, marketing and customer acquisition leadership team. The problem is that the vendor's own evidence contradicts the breadth.

All nine published customer logos sit in a single one of those six verticals, media and publishing, and the company's own origin story explains why, describing the platform as built to solve the administrative burden facing representatives selling digital and print media. The other five industry pages have nothing behind them on any page read.

Coverage detail is otherwise blank: no company size band, no seat minimum or ceiling, no customer count, no geography beyond two domestic offices, and no statement of who should not buy. The vendor also describes its market as covering both business and consumer facing organisations without distinguishing what changes between them.