BYOV: why we refused to own your enrichment

The most common question I get on sales calls is “what data vendor do you use.” The honest answer is “whichever one you already pay for.” Every time I say that, there is a pause. The buyer was expecting a pitch about our proprietary enrichment. They were expecting a line item that looked like every other event vendor’s line item: platform fee, plus a data add-on billed per record or per credit.

We do not sell that. Luminik is BYOV, bring your own vendor. You bring the Apollo contract, the Clay workspace, the ZoomInfo seats, the Lemlist seats, or the LeadMagic API key you already signed. Luminik orchestrates the waterfall. Your enrichment line on the Luminik invoice is zero, because the enrichment is not on the Luminik invoice. It is on the contract you signed with Apollo last year.

This is a deliberate architectural decision. I want to explain why we made it, and why I think the closed-waterfall model that every other event vendor uses is structurally broken.

The closed-waterfall tax

The standard event-marketing-platform shape goes like this. You pay a platform fee. The platform includes enrichment, because enrichment is where the real margin sits. They charge you per record, per credit, per seat, or bundled inside a tier. Behind the scenes, they buy data from the same three or four providers you could have bought it from directly, and they mark it up. That markup funds the sales team, the booth at SaaStr, and the “free” integrations.

The financial math works for the vendor. It does not work for you. You are paying a second time for data you already have in Apollo or ZoomInfo. And because the vendor bought in bulk, the match rates are worse than the vendor you picked yourself. The vendor you picked was chosen because they had the best coverage for your ICP. The closed-waterfall vendor is using whoever gave them the best wholesale rate that quarter.

The worst part is the data staleness. Closed-waterfall vendors update their databases on a schedule that serves their product roadmap. When you look up an attendee six weeks before RSA, you want the title they hold today, not the title they held eight months ago when the aggregator last indexed LinkedIn. Your Apollo contract refreshes on Apollo’s schedule, which is aggressive, because Apollo’s whole business depends on freshness. The closed-waterfall vendor’s refresh depends on how cheap they can buy the records.

So you pay a margin for worse data. That is the tax. Every customer I have ever onboarded from a closed-waterfall platform has the same horror story: a CSV full of stale titles, wrong companies, and contacts who left the company two quarters ago.

What BYOV changes, mechanically

Three things change when you run event enrichment through your own vendor contract.

One. The data is as fresh as your vendor’s best refresh cycle.

Apollo refreshes its data continuously. Clay lets you configure custom waterfalls. ZoomInfo has a real-time enrichment API. Each of those vendors is optimizing their data pipeline as a core competency, because their enterprise customers buy them specifically for freshness. When Luminik hits their API with your credentials, you get their production freshness.

Two. The waterfall is configurable per event.

For a European fintech event, your best match rates might come from Apollo plus a Clay company-search fallback. For a US cybersecurity event, you might want ZoomInfo primary and LeadMagic for title and mobile enrichment. These are different waterfalls. A closed-waterfall vendor makes one choice for everyone and calls it the product. BYOV lets your RevOps team configure the waterfall per event, per ICP, per region. Luminik passes the lookup through whichever order you set.

This matters when match rates are the difference between walking into an event with a 1,800-target list and walking in with a 600-target list from the same raw attendee CSV. The Series C cybersecurity team at RSA pulled 1,840 ICP-matched records from an RSA attendee list of 43,000. That match rate depended on running their existing Apollo and LeadMagic contracts in a specific order. A closed-waterfall vendor would have handed them a smaller, staler list.

Three. Your vendor DPA stays where it was.

Data processing agreements are an underrated part of enrichment. Under BYOV, the data never touches a new vendor. Apollo is processing the data under the DPA you already signed with Apollo. Your legal team reviewed it once, and the review does not have to happen again for every new tool. Closed-waterfall vendors require a new DPA because a new entity is now touching the data. If you are in fintech, healthcare, or a regulated industry, that single detail can be the difference between a 2-week procurement and a 4-month one.

The objection buyers raise first

“If we have to bring our own Apollo, you are not really giving us enrichment. You are just an API router.”

Technically, that objection is not wrong. We are not selling you enrichment. We are selling you the orchestration of enrichment you already own. The event pipeline has five stages: source, enrich, sequence, capture, attribute. Enrichment is one stage, and we do not want to own it, because the vendors who do own it run it at a quality and scale we cannot match without reselling their data.

What we do own is the logic that wraps enrichment. ICP scoring based on your own profile, target-account matching, score-based prioritization of who to enrich first when the list has 43,000 attendees and you have 10,000 Apollo credits. Those are decisions that live inside Luminik, because they depend on your business context. The enrichment API call itself is pass-through. That is deliberate.

The pricing consequence is that our platform fee is defensible in front of your CFO. The Luminik line on your budget is a platform fee only, no per-record markup. Your enrichment line does not move, because you are not signing a second data contract. When your CFO asks “are we paying twice for enrichment,” the answer is no, and the answer holds up under scrutiny.

What this means for how you evaluate vendors

If you are shopping for an event pipeline platform, the procurement question that separates serious vendors from resellers is “do you include enrichment in your platform fee, or do I bring my own contract.” Any vendor whose answer includes the word “credits” is operating a closed waterfall. They are taking a margin on data you could have bought cheaper, or better, somewhere else.

The follow-up question is “which vendors are supported, and is the waterfall configurable.” If the answer is “we use our proprietary data source,” you have a closed-waterfall vendor trying to sound open. If the answer is a list of real vendor names with configurable order, that is a BYOV platform. Luminik’s integrations page lists Salesforce, HubSpot, Apollo, Outreach, Lemlist, LeadMagic, Clay, ZoomInfo, and Slack, which is the full list we currently orchestrate. The list is named so you can verify it.

The last question, and the one most buyers forget to ask, is “what happens to my data when I churn.” Under BYOV, the answer is “nothing, because your data was never in our database.” The enrichment lives in Apollo. The attributed pipeline lives in Salesforce. The attendee records live in HubSpot. We wrote to systems you own, and when you leave, your systems keep working. You do not pay the exit tax of re-enriching 50,000 historical records because the vendor you left is holding your data hostage.

The strategic reason we made this call

The honest strategic reason we went BYOV is that we did not want to compete with Apollo on data. Apollo’s whole company is building a best-in-class B2B database. We have a small team. If we tried to build a proprietary database alongside event marketing, we would end up with a mediocre version of both. We can do one of these well. Apollo can do the data. We do the event pipeline around it.

That is less exciting than pitching a magic one-vendor platform. But it is the architecture that actually produces better match rates for the customer, and it is the architecture that does not extract a margin on data the customer already bought. Every time I get on a call with an event marketer who has been burned by a closed-waterfall vendor, I watch the relief on their face when they realize they do not have to argue with their CFO about a second enrichment contract.

BYOV is a business-model decision about where the value lives. The value lives in the orchestration. Saying that out loud is how we keep the pricing defensible, and how we stay honest with our customers.