Lensmor

Trade shows are one of the few remaining channels where a B2B team pays for the room before it knows who is in it. The stand, the flights, the literature and the week of staff time are committed months ahead; the research into which companies and which people are actually worth an hour of that week usually happens in the fortnight before, across an exhibitor directory, a spreadsheet, LinkedIn and whatever the CRM already holds. Lensmor is built for that fortnight. It positions itself as a workspace for deciding which accounts and contacts are worth reviewing before a show, rather than as another database to search after it.

What Lensmor actually is

Lensmor describes itself as a B2B event intelligence and pre-event sales research platform: it brings event, company, exhibitor and attendee-related information into one workspace so that exhibitors and the teams supporting them can prioritise before they travel. According to the vendor, the platform is designed to help users discover relevant trade shows and event opportunities, review exhibitors and event-related companies, prioritise accounts against a target profile, review attendee-related records with source context, identify relevant roles, review available contact information, filter event-related contacts by company, industry, location, department, management level and job title, and assemble a focused pre-show outreach list. Those are vendor-documented capabilities and we present them as such.

The framing matters more than the feature list. Lensmor is explicit that it is not a generic contact database and not a complete attendee list. It is a prioritisation layer over event-shaped data of varying provenance, which is a narrower and, in our view, more honest claim than the category usually makes.

The distinction that makes it interesting

The most editorially useful thing about Lensmor is that it labels where a record came from rather than flattening everything into one “attendee” column. The vendor describes three materially different kinds of information:

• Visitor data — attendee information provided by event organisers and data partners, available only where it has actually been supplied for that event.
• Official exhibitor — people connected to companies listed on an event's official exhibitor or sponsor pages, which is a documented relationship to the event rather than an inference.
• Social signals — public activity that may indicate interest in, or potential attendance at, an event. This is an indication, not a confirmation.
• Source context — the labelling itself, so a user can tell a supplied record from an exhibitor-linked contact from a likely-attendance signal.

Anyone who has bought an “attendee list” understands why this matters. A public post about looking forward to a show is a reasonable prompt to research an account; it is not evidence that the person walked the floor. Treating those two things as one dataset is how event data loses credibility internally after the first quarter of unanswered emails. Lensmor keeping them separate is a design decision that helps a sales team calibrate effort — and it is also the point at which the buyer has to stay disciplined, because the product cannot stop you from exporting a signal and writing to it as though it were a confirmation.

Who it is for

The fit is narrow and specific: organisations where events are a meaningful part of how pipeline gets created. That includes exhibitors preparing for a stand, field marketing teams whose targets are tied to a show calendar, B2B sales teams working an account list into meetings around an event, RevOps and go-to-market functions trying to make event spend measurable, and the agencies and event consultants doing this work on a client's behalf. For those teams the research problem is real and currently solved manually.

Limitations you should price in

• It is not a complete attendee list, and the vendor does not claim to be one — availability depends on what organisers and data partners have supplied for a given event.
• Visitor data is not available for every event, so coverage will vary by show, region and organiser.
• Social signals indicate possible interest or attendance. They do not prove that anyone attended, and must not be used as if they did.
• Contact information availability varies by record; a prioritised account is not automatically a reachable person.
• Prioritisation is research, not outcome. No tool of this kind guarantees meetings, leads or closed revenue.
• TTML has not tested the data. Every capability above is vendor-documented and unverified by us, which is the single largest caveat on this page.

How it sits next to the rest of a B2B stack

Lensmor is upstream of the systems most teams already pay for. A CRM records the relationship once it exists; a sequencing or marketing platform such as EngageBay sends the outreach, and an always-on contact database such as Apollo answers who matches a profile anywhere. None of them answers which of four thousand exhibitor companies deserves attention at one specific show. That is the gap Lensmor is aimed at, and it is why we would not describe a generic contact database or a CRM as a like-for-like alternative — the workflows only overlap at the point of export.

Verdict