Cybersecurity Ecosystem Show

The episode contains useful operational guidance on OEM structures, deal mechanics (royalty models, floor pricing), and product fit criteria. However, it relies heavily on anecdotal war stories rather than systematic frameworks, and spends considerable time on basic definitions and context-setting. The practical insights (e.g., standardized SDKs, avoiding high-touch customization, revenue concentration risk) are valuable but scattered throughout rather than densely packed.

“if you don't have your product productized in a form where you can have standard published APIs...if you don't have those two things, your product is probably not a good fit”

“you really want to make sure that no single OEM is going to be more than 10%, ideally no more than 5% of your overall revenue”

The core framework (OEM vs. MSSP vs. channel) and advice (standardized APIs, avoiding custom builds, revenue concentration) are sensible but not particularly novel in B2B SaaS/software partnerships. The anecdotes about Yahoo Toolbar and DLP provide some color, but the underlying principles are fairly standard practice. The distinction between OEM and technology partnerships is useful but not groundbreaking.

“criteria number one...they are taking our APIs, our SDKs...criteria number two is that they are embedding your product in whole or in part into their product”

“You go to war with the army you have, don't try to invent a new army once you've started the war”

Chad Lovin brings legitimate depth: 20 years in OEM/partnerships, hands-on roles at multiple companies (small startup, NetWitness, Reversing Labs), and exposure to both inbound and outbound OEM. He has executed deals and learned from failures. However, he is not a household name, has not built a major platform from scratch, and his perspective is largely tactical/operational rather than strategic/visionary. Solid practitioner but not a marquee guest.

“I've been with Reversing Labs for a little over a year. Although I've got a long history with them. I've been on the other side of the table as a licensee, licensing them inbound for oem, partnering with them, um, competing with them”

“I've lived, ate and breathed [OEM] and have done so for 20 years”

The episode includes some concrete examples (Yahoo Toolbar, NetWitness/Reversing Labs deal, DLP product failures) and specific deal mechanics (seven-figure Yahoo contract, 25% revenue concentration scenario, $50/year per-user pricing hypothetical). However, most numbers are round/anecdotal and lacking precision. No data on OEM market size, adoption rates, or performance benchmarks. Many claims remain general ("a couple hundred large OEM cybersecurity vendor prospects") without supporting evidence.

“it was Yahoo at the time, uh, paying us seven figures, which was for us was enormous”

“we had 25% of the revenue...generated by a single OEM”

The host asks reasonable follow-ups and does probe into details (floor pricing, product fit, differentiation from MSSPs). However, the questioning is largely receptive and confirmatory rather than challenging. The host seldom pushes back, tests assumptions, or ask harder questions like ROI impact, failure rates, or whether OEM is a crutch for weak standalone products. The conversation meanders somewhat and occasionally goes off-agenda without discipline.

“Very cool for your perspective...I'd love to hear...just curious your thoughts there”

“Fascinating. That's so interesting. I love the derivative aspect”