The list was not the problem. The reason to meet was.

The Client

Search that works on the catalogs most tools give up on.

LupaSearch sits behind the search bar on complicated ecommerce sites. Large catalogs, technical attributes, hundreds of filters, and often four or five country storefronts running off one product feed. When a shopper types a query the site cannot answer, they land on a zero result page. That page is where revenue quietly leaks out.

Multilingual search is where it gets sharp. A shopper searching in one language on a storefront built in another usually gets nothing back. LupaSearch fixes that, and the numbers behind it are not soft: a 30% drop in no result rate at Audimas, a 48% lift in search conversion at Lemona, up to 69% at Kesko Senukai.

The company is Lithuanian, bootstrapped, and sells to mid-market and enterprise retail.

The Challenge

A real market, a finite one, and one person to work it.

LupaSearch had the product and the proof. What it did not have was a growth team. Growth was one person, a co-founder, carrying outbound alongside everything else a bootstrapped founder carries.

The reflex in that position is to turn on volume and hope reach solves it. We started somewhere else. Before writing a single sequence, we mapped what the addressable market actually looked like, because the answer to how do we sell more depends entirely on how many people there are to sell to.

The Approach

Map the market. Then find the reason they will actually take the meeting.

Part one was the market map. We rebuilt the ICP from LupaSearch's own customer data instead of from assumptions. The original qualification rules, 200K monthly visitors and a 10K SKU floor, disqualified over half of LupaSearch's own active customers. So we threw them out and derived new ones from the accounts that were already winning: vertical-specific traffic floors, an archetype filter for regional subsidiaries of global groups, and a competitor detection layer that reads which search vendor a prospect is already running. That produced roughly 2,000 qualified accounts, enriched to contact level and segmented into three profiles, each with its own angle.

Part two was the hook. A finite pool changes the playbook. Volume does not work when the total list runs to a couple of thousand accounts and every wasted touch burns one you cannot replace. What a finite list needs is not more sends, it is a better reason to reply.

Shoptalk Europe in Barcelona gave us one. We ran a two-week sprint into a curated list of attending accounts, across email, LinkedIn, and phone, with one job: get the founder in front of the right buyers in booked slots rather than a hallway hope. The finding was almost uncomfortable in its simplicity. The same email, to the same people we were already contacting, started booking meetings once the invite carried Shoptalk and a date.

The Takeaway

The reason to meet, not the list, moved the numbers.

The strongest finding was not the meeting count. It was that the same accounts who had ignored a product pitch booked time when the invite carried an event and a date. That is a repeatable play, and the list, the copy, and the playbook stayed with LupaSearch when the sprint ended, ready for the next event.