Lusha Buyer Intent Topics Limit, Lusha Email Finder Extension, and DMARC: What RevOps Should Actually Evaluate
2026-08-14 · Julian Hartwell
-
Three scenarios, one question: what's the total cost?
-
The layers you're actually paying for
-
Scenario 1: small team, manual outbound, no sales engagement platform
-
Scenario 2: scale-up team with a sales engagement platform
-
Scenario 3: renewal time and a flat budget
- What should revenue operations teams evaluate in DMARC?
-
How to figure out which scenario you're in
-
My bottom line
Three scenarios, one question: what's the total cost?
If you are trying to decide whether Lusha is the right contact database for your sales team, I cannot give you one clean answer. I can tell you that the search for a single answer is usually what leads to bad procurement decisions.
I work in procurement and I manage a revenue operations budget. My job is to compare vendors, model total cost of ownership, and stop hidden fees from showing up on invoices. I've tracked every software order we've made for years, and I've watched more than one team buy a tool because it solved a symptom, not the system around it.
Here's what I've learned: the right Lusha plan for you is the one that fits your workflow, your sales engagement platform, and your email deliverability. There are three scenarios that cover most of the teams I talk to. Start there.
The layers you're actually paying for
Before I walk through the scenarios, let's name the layers. A contact database gives you people and companies. The Lusha email finder extension gives your SDRs a fast way to find and verify addresses while they are doing research. Buyer intent topics tell you which accounts are showing signals related to a product or topic. A sales engagement platform turns all of that into automated cadences.
If you're only comparing vendor price lists, you're missing the interaction between those layers. A cheap contact database with low match rates can make an expensive sales engagement platform useless. An email finder extension that saves two seconds per lookup can pay for itself if your SDRs do hundreds of lookups a day.
DMARC sits underneath all of this. I'll get to that in a minute because it's the most overlooked cost in revenue operations.
Scenario 1: small team, manual outbound, no sales engagement platform
This is the most common situation for early-stage B2B companies. You have two or three SDRs, a CRM, and a whole lot of manual research. You do not need a heavy API integration on day one. You need a focused contact database and a browser extension that makes your SDRs faster.
For this scenario, I would start with a smaller plan and the Lusha email finder extension. The extension is the tool your SDRs will use in their actual workflow. They'll find a name, look at the company, verify the email, and write a personalized message without tabbing into a separate platform.
People often ask me about the Lusha buyer intent topics limit in this scenario. My honest answer: two or three active topics is usually enough for a small team. If you're only doing manual outbound to 200 accounts, you don't need seven intent topics. A lower limit can even help you focus. I've seen teams turn on every possible topic and then ignore all of them. The unused topics didn't just waste money; they made reporting noisy.
Counterintuitive as it sounds, the smallest plan that still gives you reliable email verification is often the best purchase for this stage. You want to build the habit of using the tool. Scaling to a bigger contract before you have repeatable outbound playbooks is how you end up with a low-usage renewal fight.
Scenario 2: scale-up team with a sales engagement platform
Everything changes when you add a sales engagement platform. Now you're running cadences, following up automatically, and sending a lot more email. The contact database is no longer just a list; it's the fuel for your revenue engine.
In this scenario, the Lusha buyer intent topics limit matters more. Let's say you have a sales engagement platform that can route a lead to a different sequence based on intent. If you track AI infrastructure as one topic, that account might get one workflow. If you also track data compliance because that's a second buying committee signal, you need capacity for both. A limit that seemed small at first can start dictating your segmentation strategy.
I don't have hard data on Lusha's current topic caps because they change by plan and over time. But I can tell you what to ask, and this applies to any contact database vendor:
- How many active buyer intent topics does the plan include?
- What exactly happens when you hit the Lusha buyer intent topics limit? Does it stop tracking, or does it still show you the data in a report?
- Can you swap topics throughout the quarter, or is there a lock-in period?
- Is intent data refreshed, and does a refresh count against your API credits?
The last question is the one that surprises people. I've compared costs across eight vendors for a deal like this, and the vendor with the lowest list price had separate API access fees, a smaller contact database, and an intent module that charged per refresh. The expensive vendor was actually cheaper once I modeled the year. That's why I keep a TCO spreadsheet for every big purchase.
Also check integration depth. If you're using the Lusha email finder extension, does it sync back to your sales engagement platform automatically, or does it only export a CSV? If it only exports, you've just added a manual step that will be first to break when the team gets busy. Look for native integrations or a clear API workflow.
Scenario 3: renewal time and a flat budget
Maybe you already have Lusha. Maybe you have another contact database and you're considering a switch. The question is not whether the tool is good. The question is whether you're using what you're paying for.
This is where my cost-controller brain takes over. When I audit a renewal, I start with usage data. How many seats does the team actually use? How many Lusha email finder extension lookups happen per month? Which buyer intent topics have ever triggered a workflow or a saved list? How much of the contact database overlaps with what's already in your CRM?
The first time I did this audit properly, I found that one team was paying for 40 seats but only 22 were active. We also had three intent topics that had not fired a single actionable alert in 90 days. We were about to renew at a higher tier because the original admin thought the team needed the biggest package. The vendor quote for renewal was 14% higher than year one. After we trimmed seats and topics, the renewal was lower than the original contract.
That's the counterintuitive part: cutting features is often better than switching vendors. A newer, cheaper vendor might look attractive until you count migration time, training, and data enrichment. The cost of switching is not just the subscription difference; it's the two weeks your SDRs lose changing habits.
However, there's another path. If you're currently using one contact database plus a separate intent data tool, check whether a different plan with a higher Lusha buyer intent topics limit could replace the second tool. I built a cost calculator after getting burned on hidden fees twice, and it showed that consolidating two vendors into one was a better move for us. The budget work isn't automatic, but it's worth running before you decide anything.
What should revenue operations teams evaluate in DMARC?
I said DMARC was the most overlooked cost. Let me explain why.
DMARC stands for Domain-based Message Authentication, Reporting, and Conformance. The technical spec is RFC 7489. It tells receiving email servers what to do with messages that fail SPF and DKIM checks. If your team sends from your company domain through any sales engagement platform, DMARC directly affects whether those emails arrive.
This is relevant to Lusha and any other contact database purchase because a verified email address is worthless if your sender reputation is bad. You can pay for a very good contact database, send to a clean list, and still see terrible open rates because your domain is not authenticated properly. I don't have hard data on industry-wide DMARC failure rates, but I can tell you what I've seen in our own logs: the campaigns that failed authentication were the ones that wasted the most time on follow-up and the most credits on lost messages.
Here is what I tell revenue operations teams to evaluate:
1. SPF and DKIM alignment
SPF defines which servers are allowed to send email for your domain. DKIM attaches a cryptographic signature. DMARC checks whether those pass and align with the domain in the From header. A common issue is a sales engagement platform that sends through its own infrastructure but uses your domain in the From address. If the alignment isn't set up, even your legitimate emails can fail.
2. DMARC policy level
Your DMARC policy can be p=none, p=quarantine, or p=reject. p=none tells receivers to see the report but do nothing. p=quarantine tells receivers to treat failures as spam. p=reject tells receivers to block them. Most teams should start at p=none, review the reports, then move to p=quarantine. Moving to p=reject too early can block legitimate email, and debugging email at scale is not a fun place to be.
3. Reporting and review cadence
DMARC generates XML reports that go to your rua address. If nobody is reading those reports, you don't actually have email visibility. Set up a process to review them monthly. This is a classic process gap. We didn't have a formal DMARC review process until a legitimate campaign failed authentication and a customer emailed asking if we'd been hacked. After that, I added DMARC reports to the monthly RevOps checklist. It should have been there from day one.
4. Every domain and every third-party sender
If you use subdomains for marketing or replies, make sure DMARC is present on those subdomains. Check all third-party services that send email: support tools, calendar apps, lifecycle email, webinars, and sales engagement platforms. Each sender needs to be SPF-allowed or DKIM-signed. Otherwise, those services can cause a percentage of your legitimate email to be placed in quarantine.
5. Post-delivery monitoring
DMARC is not the same as inbox placement. You need to monitor reachability with tools like Google Postmaster Tools and Microsoft SNDS. Look at bounce codes, spam complaints, and unsubscribe rates. If you see a jump in spam complaints, it might be a list quality problem, not a DMARC problem. The point is to have enough visibility to know which one you're looking at.
How to figure out which scenario you're in
You can use this as a quick diagnostic.
- Do your SDRs rely on automated cadences in a sales engagement platform? If no, you're in Scenario 1. If yes, you're in Scenario 2.
- Is your current contract up for renewal within 90 days and does the budget team want to reduce spend? Scenario 3.
- When was the last time your team looked at DMARC reports? If the answer is 'never,' deal with that before you buy more contacts. This was the gap in our own stack, and it cost us trust.
Once you know your scenario, don't ask the vendor which plan should I buy. Ask them what the total cost will be for the features you'll actually use. That question tells you more than any pricing page.
My bottom line
There is no single Lusha plan that fits every B2B sales team. There is no contact database that is so good it fixes broken email deliverability. And there is no sales engagement platform that can make up for a team that doesn't know which intent topics to chase.
I like Lusha because it fits cleanly into a lot of workflows without requiring a dedicated operations person. But I'd say the same about any vendor if the total cost math made sense. My bias is toward the system: contact database, email finder extension, buyer intent topics, sales engagement platform, DMARC, and the people using them.
Run the audit. Read the reports. Trim what you don't use. Then you'll know if the Lusha buyer intent topics limit matters to you or if it's just a number on a comparison sheet. That's the cheapest thing you can do all year.