BYOV: why we refused to own your enrichment
Closed-waterfall enrichment trades data quality for margin. Why Luminik runs on the Apollo, Clay and ZoomInfo contracts your team already owns.
TL;DR: Luminik is BYOV, bring your own vendor. Your enrichment line on the Luminik invoice is zero, because the enrichment is not on the Luminik invoice.
When buyers ask “what data vendor do you use,” the answer is “whichever one you already pay for.” Luminik can run enrichment through a customer-owned vendor contract.
If your event platform also sells enrichment, compare that charge with the data contract you already hold. Check the coverage, refresh schedule and cost of both options.
We do not sell that. Luminik is BYOV, bring your own vendor. You bring the contract you already signed:
- The Apollo contract.
- The Clay workspace.
- The ZoomInfo seats.
- The Lemlist seats.
- Or the LeadMagic API key.
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 gives RevOps control over which providers run the lookups and where the data costs appear.
What to check when enrichment is bundled
An event marketing platform may bundle enrichment like this:
- You pay a platform fee.
- The platform includes enrichment in its offer.
- They charge you per record, per credit, per seat, or bundled inside a tier.
- Behind the scenes, they buy data from the same 3 or 4 providers you could have bought it from directly, and they mark it up.
Ask how much of the charge covers data access and how much covers the platform workflow.
If the bundled records duplicate data you already have in Apollo or ZoomInfo, you may be paying twice for the same access.
Match rates depend on the providers, the audience and the lookup process. Compare the bundled option with your existing provider on a sample of the same target accounts.
Check the refresh date too. When you look up an attendee 6 weeks before RSA, a title last verified 8 months ago may need another check.
Ask whether a lookup uses the provider’s current record or a cached copy, and when that copy was refreshed.
Inspect the output for stale titles, wrong companies and contacts who left 2 quarters ago. Bundled enrichment and customer-owned providers both need those checks.
What BYOV changes, mechanically
3 things change when you run event enrichment through your 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 fixed provider order may not fit every audience. 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. Compare provider coverage on the same input list before drawing a conclusion about match rates.
Three. Review the data processing path.
Your existing Apollo agreement covers your relationship with Apollo. Adding a platform can introduce additional data processing, so review the full workflow and its agreements.
For a fintech, healthcare or other regulated buyer, procurement timing depends on the processing arrangement and review requirements. Do not assume that BYOV alone determines whether procurement takes 2 weeks or 4 months.
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 5 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 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
One. “Do you include enrichment in your platform fee, or do I bring my own contract.”
Ask what the credits pay for, which providers supply the records and whether your existing contracts can be used. Compare the total cost for the same audience and lookup volume.
Two. “Which vendors are supported, and is the waterfall configurable.”
If the answer is “we use our proprietary data source,” ask how the records are sourced and refreshed. For BYOV, confirm which customer-owned provider contracts you can connect and whether you control their lookup order.
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.
Three. “What happens to my data when I churn.”
That is the last question, and the one most buyers forget to ask. 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. For a database of 50,000 historical records, confirm which fields remain in your CRM and which require continued vendor access before ending the contract.
The strategic reason we made this call
We chose BYOV so we could focus on event workflows rather than build a competing contact database. Apollo’s whole company is building a serious 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.
The customer keeps control of provider choice and lookup order. Match rates still need to be measured against the accounts and regions the team targets.
For the budget review, separate the platform cost from the data contracts and check whether the proposed setup duplicates any existing spend.
The platform fee pays for the event workflow around enrichment: prioritization, provider lookups, CRM matching and the next action for sales.
