Nebulock's thesis is that waiting for the alert is waiting too long. Demand generation has the same failure mode. Most programs measure the activity they can see, and never find out what the pipeline they lost was doing.
Four stages, run as one loop. Same shape as a hunt: gather signal, resolve it to context, act on it, and prove what the action was worth.
Taken straight from the job description. Each one answered with work already shipped, not a plan to try.
Every requirement you listed, in your order, answered with something that actually happened.
I have spent fifteen years marketing security software to people who are professionally suspicious of marketing. Application security at Veracode. Runtime detection at Capsule8. API and application protection at ThreatX. All three have since been acquired. I know what it sounds like when a vendor is guessing, because I have watched practitioners walk away from it.
Nebulock's positioning is the part that made me stop scrolling. "By the time an alert fires, it's already too late" is exactly the argument I have been making about demand generation for a decade. A form fill is a lagging indicator of a decision that was made upstream, weeks earlier. The work is to be in the account before the buying committee has named the problem out loud.
The founding-team part is the part I have done best. At Capsule8 I was the first technical marketing hire. There was no demand gen function, no martech, no process, and no one to hand me a playbook. I built it, and the company went from $300K ARR to over $3.5M before Sophos acquired it. That is the "nice to have" on your list, already done, at a security startup, through to an exit.
And rather than tell you I ship fast, I built this. Researched your brand, matched your design system, wrote the copy, built the page, deployed it on my own infrastructure. A weekend, using the same category of AI tooling the role offers. I'd rather show the work than describe it.
Your nice-to-haves list intent data platforms: Bombora, 6sense, Demandbase. At ThreatX I owned and deployed 6sense — chose it, rolled it out, and then lived with the consequences of both.
Standing a platform up is the easy half. The hard half is what happens to the signal afterwards: resolving it to accounts, routing it to the SDRs who have to act on it, and proving it produced pipeline rather than dashboards. At DeleteMe I architected signal-based lead orchestration for Sales prospecting, routing behavioral and firmographic signal into prioritized outbound, then layered AI workflows on top to increase its velocity and personalization.
The platform is a data source. The orchestration is the skill, and the orchestration is the part that takes years.
Happy to walk through any number on this page, or the ones that didn't work. Those are usually the more useful conversation.
neildupaul@gmail.com>