TigerLRM

Two model capabilities sit on top of a record system that would work without either.

Lead scoring analyses behaviour, engagement, profile and other factors to rank which prospects a representative should work first. Forecasting projects future revenue from historical data and trends, showing how close a team is to its targets. A chatbot answers common service questions. The vendor markets the product as an artificial intelligence driven record system and announces the integration in a banner at the top of the page.

What a customer is actually buying underneath is deterministic and familiar: contacts, deals, pipelines, tasks, calendars, service records, web form capture, lead routing, a consolidated inbox, text messaging, calling and sequence automation. The enablement modules, playbook, learning management and asset library, are content systems rather than inference.

Scoring is the capability with the most operational weight, because it determines which leads get attention and which are left, and it is a ranking function applied to data the customer already holds rather than something generating outbound content.

Nothing here writes messages to prospects, which distinguishes it from most records in this sweep.

Ask what the lead score is computed from and whether the weightings can be adjusted.

Monitor, audit and assist is stated as a management capability, and the learning system verifies rather than merely delivers.

The vendor frames its enablement layer around ensuring representatives deliver the right message and cadence every time, with tools allowing a manager to monitor, audit and assist teams through all stages of the funnel. Audit is the word that matters, because it implies reviewable records of what was said and done rather than a dashboard of activity counts.

The learning management system pairs training with tests and practical exercises, so competence is checked rather than assumed. For a smaller company without a dedicated enablement function, that is the mechanism that makes a playbook binding instead of aspirational.

Lead distribution assigns automatically by keyword, data background or other factors, and sequence automation handles follow up cadences.

What two passes could not locate: any approval gate over model scored prioritisation, any audit trail described in technical terms, any permission or role model, and any statement of what a representative can override.

The scoring question is the live one, since a lead ranked low is simply not worked and nobody sees the decision.

Ask whether representatives can see and override the lead score.

The provider is named in a banner at the top of the home page, which almost nothing in this index does.

The vendor states twice, prominently, that its artificial intelligence is powered by a specific named commercial assistant from a major provider. That is a real disclosure rather than a hint, placed where every visitor sees it rather than buried in documentation, and it lets a buyer reason about where their data goes and which supplier sits in the chain.

Input descriptions are also better than the norm. Scoring is stated to analyse behaviour, engagement, profile and other data factors. Forecasting is stated to work from historical data and trends. Neither is a full specification, and both tell a buyer more than the usual silence.

What is absent: no model version, no accuracy figure for either scoring or forecasting, no evaluation, no statement of exactly what customer or prospect data is transmitted to the provider, and no training or retention position covering that transmission.

That last gap is the one worth pressing, because naming the provider raises the question of what crosses the boundary rather than settling it.

Ask what customer data is sent to the model provider and what is retained.

Five testimonials with full names, titles and employers, one of them a substantial firm.

The attribution is complete rather than initialled: a vice president of sales and a director of sales enablement at a named technology services company, a senior managing director at a major commercial property services firm who cites twenty three years in the industry, a director of operations at a property business, and a principal at an interiors company. Naming a senior figure at a large services firm is checkable and carries weight.

Two of the five come from the same employer, which is worth noting when weighing breadth.

The quantified claim on the page needs handling carefully. A three hundred percent conversion rate improvement is cited to a software review publication, and the underlying claim concerns record systems as a category rather than this product. The page then slides into applying it to the reader's own company. A buyer should read it as a category statistic, not a vendor outcome.

What two passes could not locate: any case study, any review count or rating on an independent platform, and any outcome figure attributable to a named customer.

Ask what results the named customers actually measured.

The word compliance appears repeatedly and means something different from what this axis measures.

The vendor uses it to describe adherence to the customer's own sales methodology: eliminating the risk of non compliance and ensuring agents deliver the right message and cadence every time. That is internal process discipline, and it is a legitimate use of the word, but a buyer skimming should not mistake it for regulatory posture.

On regulatory compliance the record is thin. The platform sends text messages and places calls through a built in softphone, and two passes located no do not call screening, no reference to the carrier registration framework governing business messaging, no calling hours restriction, no recording notification and no unsubscribe mechanism for email or text sequences.

One acquisition path is genuinely clean and deserves crediting. Leads arrive through web forms the customer places on their own site and landing pages, so the person submitted their details deliberately. That is the strongest consent basis available and it is the primary intake route described.

No purchased database sits behind the product, so nobody is contacted because they appeared in a list of unknown origin.

Ask what do not call screening applies before the softphone dials.

No privacy policy, terms or legal document was reachable from the page examined.

Two passes across the home page located no privacy policy link, no terms of service, no processing agreement, no subprocessor list, no retention schedule, no deletion commitment, no residency statement and no rights request route. The page is entirely marketing copy and testimonials, ending without a legal footer in the retrieved content.

That may be a rendering artefact rather than a true absence, and a buyer should check the live site before concluding the documents do not exist.

What makes it worth pressing is the data flow the vendor itself advertises. The product transmits customer information to a third party model provider for scoring and forecasting, which the vendor names openly. Naming the provider is good practice; it also means a subprocessor relationship exists and should appear in a published list, and none was found.

The holdings are the ordinary record system set plus service tickets, communication history across email, text and calls, and whatever the chatbot captures from customers.

A services arm additionally places the vendor's own staff inside customer accounts.

Ask for the privacy policy and the subprocessor list.

No database is supplied, and the primary intake route is the cleanest one available.

Two passes across the home page and independent coverage located no contact database, no record count, no enrichment engine, no lead finder, no intent data and no third party data supplier anywhere in the product. The vendor sells a place to manage relationships, not a source of them.

Leads arrive through web forms the customer places on their own website and landing pages. Somebody filled in a form. That is consent given deliberately by the person concerned, and it removes the provenance question that dominates this axis for most records in this index.

Segmentation operates on data the customer already holds, dividing leads by industry, location, company size and product interest.

The one unexplained element is what feeds the scoring model. The vendor states it analyses behaviour, engagement, profile and other data factors, and profile data could mean information the customer captured or information drawn from elsewhere. Nothing distinguishes the two.

Ask whether lead scoring uses any data beyond what the customer has captured.

Every channel here belongs to the customer, and the one external dependency is a commercial licence.

Communication runs through the customer's own web forms, their own email, text messaging and a built in softphone. Two passes located no social network automation, no scraping, no browser extension operating a third party property, no account renting and no capability depending on another platform failing to notice it.

That is a categorically different position from most of this sweep and it follows from what the product is. A record system managing a company's own pipeline has no reason to reach into somebody else's network.

The one external relationship is the named model provider, which is a paid commercial service used as intended, and disclosing it openly is the correct handling.

Two residual questions. Third party listings report that interfaces are available, and no integration is named anywhere on the vendor's own surfaces, so what the platform connects to and under what arrangements is unestablished. And the text messaging and calling capabilities imply telephony providers that are not identified.

Ask which telephony provider underlies the messaging and softphone features.

The provider is named and nothing else about handling it is published.

Naming the model supplier is credited fully on the disclosure axis and it is the right thing to have done. It also creates an obligation this record cannot see discharged: if customer and prospect data is transmitted to an external provider for scoring and forecasting, a buyer needs to know what is sent, what is retained there, and whether it may be used for training. Two passes located none of that.

On the model itself: no accuracy figure supports lead scoring, which decides which prospects a representative works and which are quietly left, and no evaluation supports forecasting used to set expectations about revenue. Neither carries an error rate.

On security the record is empty. Two passes located no security page, no certification, no audit, no encryption statement, no access control description, no incident response process, no breach notification commitment, no named security contact and no vulnerability disclosure route.

The services arm adds a dimension nothing addresses, since the vendor's own staff work inside customer accounts as sales managers and enablement professionals.

Ask what access vendor services staff have to customer data.

Nothing here manufactures a false impression of who is making contact.

Two passes located no persona, no rented identity, no cloned voice, no automated social action generating fake attention and no generated outbound content presented as personally written. Communication leaves from the customer's own email, their own number and their own representatives. Against the records built this week that is a meaningfully cleaner position.

The primary intake is a web form, so most people in the system asked to be there.

One automated surface does face customers and carries no described disclosure. A chatbot answers common questions instantly on the service side, and nothing states whether the person interacting with it is told they are talking to software rather than a support agent.

Two further gaps sit on the outbound channels. Text messaging is built in with no unsubscribe mechanism described, and softphone calling carries no recording notification, in a product sold across jurisdictions with differing consent requirements.

Ask whether the chatbot identifies itself as automated.

Interfaces are reported to exist and not one integration is named.

Independent listings state that interfaces are available and that the product runs on mobile browsers. The vendor's own page says it integrates with many other tools and platforms a customer may already use, and then names none of them. Two passes located no integration directory, no interface documentation, no authentication scheme, no webhooks and no protocol server.

For a record system that is the material gap, because a record system that does not connect to a customer's mail, calendar, marketing and accounting systems becomes a second place to type things. A buyer cannot establish whether their own stack is supported.

What the platform does consolidate is internal: a multi channel inbox bringing email, text and calling into one view, so a representative is not switching between tools for the conversation itself.

A mobile application extends access, and the enablement modules put playbook content and assets in the same system as the pipeline.

Ask which systems are supported natively and whether interface documentation is published.

Nothing about the infrastructure was located on any surface examined.

What can be inferred is minimal: the product is delivered as a hosted service, customer information is described as stored in one place and accessible from any device, and independent listings confirm it runs on mobile browsers alongside a mobile application.

Two passes located no hosting provider, no region, no data centre, no residency commitment, no tenancy or isolation model, no encryption statement, no backup position, no continuity plan, no uptime commitment and no status page.

The residency question has a specific edge here because of the disclosed model integration. Data transmitted to an external provider for scoring and forecasting crosses a boundary the vendor has named but not mapped, and where that processing occurs matters to any buyer with obligations about where personal data travels.

The holdings are the ordinary record system set plus communication history across three channels, service tickets and chatbot conversations.

A buyer outside the vendor's home market would need this resolved before migrating a customer database.

Ask where data is hosted and where model processing occurs.

No security material of any kind was located.

Two passes across the home page and independent listings found no certification, no audit report, no examination, no penetration test, no trust portal, no dedicated security page, no encryption statement, no access control description, no subprocessor list, no vulnerability disclosure route, no named security contact and no status page. No privacy policy or terms link appeared in the retrieved content either.

Some of that may be a rendering artefact and a buyer should check the live footer before concluding the documents are absent.

What makes the gap material is the combination of what this platform holds and what it does with it. A record system stores a company's entire customer base, its pipeline, its communication history and its service records. This one additionally transmits data to an external model provider, and additionally places the vendor's own staff inside customer accounts through its services arm.

Each of those three is a question a supplier assurance review would ask, and there is currently nothing published to answer any of them.

Ask whether any independent security assessment exists.

The vendor says free repeatedly and independent sources disagree about what that means.

The home page states in a banner that no credit card is required to sign up and to try it free, and describes the platform itself as free and feature rich. That is an unambiguous signal and it removes the usual barrier to evaluation.

Independent coverage complicates it. One listing reports the product is free for up to ten users and ten dollars monthly beyond that, which if accurate would be among the cheapest arrangements in this index. Another states directly that there is no lifetime free plan. Those cannot both be right, and neither is confirmed on the vendor's own pricing surface, which was not reached in this pass.

Two further costs sit outside whatever the software price is. Premium add ons are referenced in a customer testimonial and priced nowhere. And the enablement services arm supplies full and part time sales managers and enablement professionals, which is a staffed engagement with no rate published anywhere.

That services cost is likely to exceed the software cost substantially for any customer who takes it.

Ask what the free tier includes, what add ons cost, and how enablement services are charged.

Interfaces are reported to exist, which is the whole of what can be established.

Independent listings confirm that interfaces are available, and that is the only programmatic route recorded. Two passes located no documentation for them, no authentication scheme, no webhooks, no export mechanism described in product terms, no format, no deletion commitment, no retention position after cancellation and no account closure process.

The vendor describes storing all customer information in one place and accessing it from any device, which speaks to consolidation rather than extraction.

What would accumulate here matters more than in most records because of what the product is. A record system holds the customer base itself, the pipeline, years of communication history across email, text and calls, service tickets, and in this case the enablement content a company wrote for itself: its playbook, its training courses, its asset library. That last category is original work product created inside the platform, and whether it travels is a question no other record in this batch has to ask.

Ask whether playbook content, courses and assets can be exported.

Three outbound channels and no discipline described on any of them.

The platform sends email through sequential follow up automation, sends text messages, and places calls through a built in softphone. Two passes across the home page and independent listings located no warm up capability, no sender authentication guidance, no inbox or domain rotation, no address verification, no bounce handling, no placement testing, no sending limits, no reference to the carrier registration framework governing business text messaging, and no caller identity reputation monitoring.

That absence is less consequential here than for a dedicated outbound platform, because this product is built around leads who arrived through a web form rather than cold lists, and messages go to people who submitted their details. Deliverability failures follow volume and complaint rates, and both are lower on that traffic.

It is not zero risk though. A consolidated multichannel inbox with sequence automation can send at meaningful volume, and text messaging in particular is gated by carrier registration that a customer would need to complete themselves without any guidance from the vendor.

Ask what is required before text messaging can be sent from the platform.

One segment, named plainly, with a product shaped for its actual constraint.

The vendor states its target as small to medium sized businesses and the design follows from that. The stated aim is to minimise clicks, remove extraneous fields and avoid the cumbersome workflows and intricate interfaces of complex record systems, which is the real reason such systems fail at that size: representatives stop entering data and the pipeline becomes fiction.

Bundling the enablement layer serves the same constraint. A company of thirty people will never buy a separate playbook tool, learning system and asset library, and the services arm goes further by supplying the enablement professional such a company would not employ.

The named customers span technology services, commercial property, property investment and interiors, which is a reasonable spread for a general purpose product.

What two passes could not locate: any geography, any industry vertical page, any company size band beyond the general claim, any language beyond English and any statement of which markets are served.

Ask which markets and regions the platform is sold in.