About Luminik

Event pipeline breaks across list, booth, and CRM handoffs.

Luminik exists because B2B teams need the pre-event list, booth context, follow-up, and CRM attribution to add up to one defensible number.

Why we built Luminik

We spent $100k+ on that event in Q1, and I still have no idea what it moved. That's the scary part.
VP GTM
Series C FinTech (one of our earliest calls)

After talking to field marketers, RevOps leads, and sales reps at Series A-C B2B companies, I kept hearing the same four things:

  • The attendee list arrives three days before the event
  • Reps walk the floor cold, with no target list and no talking points
  • Follow-ups go out on day 11, two weeks after everyone's moved on
  • Nobody can prove what the six-figure event produced

This is where the sponsor-side event motion usually breaks. Luminik exists to change that.

What makes us different

We start building your list 6 weeks ahead of the event

The attendee CSV often arrives three days before the event starts. We source from the open web and from the event platforms your sponsorship entitles you to, weeks out. Your reps walk in with a ranked ICP list rather than a printout.

Attribution lands on the CRM record

Every meeting, capture, and sourced opportunity writes back to Salesforce or HubSpot within 48 hours from event end. The number your CMO reads in the QBR is the number the CRM reports. No screenshots, no PDFs.

One pipeline for all five stages

Source, enrich, sequence, capture, attribute. No CSV exports between tools, so nothing is lost at a handoff. Your team keeps working in the CRM and sequencer they already open every morning.

Who's behind it

Prasad Subrahmanya, Founder and CEO of Luminik
Prasad Subrahmanya
Founder & CEO, Luminik
12+ years building enterprise software; previously Venture CTO at Bain & Company and co-founder/CTO at Mainteny.

Before Luminik became software, I ran this workflow with customers across 50+ B2B events.

That meant the unglamorous work: finding the right accounts in attendee data, fixing messy lists, setting up outbound, writing event-specific campaigns, filling dinners and side events, building the post-event report, and explaining why the CRM did or did not support the event spend.

The failure pattern was consistent: attendee lists lived apart from outreach, floor conversations lived apart from the CRM, and attribution got rebuilt in spreadsheets after the buying window had moved on. Each of those steps had a tool behind it. Nobody owned the handoffs between them.

Luminik is that field work in product form: source, enrich, sequence, capture, attribute, across the CRM, sequencer, and enrichment vendors customers already use. The goal is simple: make third-party events a pipeline channel the business can inspect in the CRM, not a story rebuilt after the fact.

Guided by leaders in marketing, RevOps, and data

Pranshu Tewari
CMO, Coveo
Ashley Naumann
Head of RevOps, Roboflow
Meenal Iyer
VP of Data, SurveyMonkey
Lakshmi Subramanian
Sr. Director of Data, Mitratech
Eugene Katz
Former VP of CS, AuditBoard
Ben Mohlie
CEO, Hyperscale LLC

How we work

Four things that show up in how we build and how we support.

We own the outcome

Your pipeline numbers are our numbers. If an event produces 6 meetings when we promised 10, that sits with us.

Specific over vague

1,840 ICP matches from 43,000 attendees is a number you can check. That is the standard for every claim we make.

We build what breaks in the field

Conference Wi-Fi drops. Finance wants the number in Salesforce. The roadmap starts at those two facts.

No features for the sake of features

If a rep or a marketing leader won't use it on their next event, it doesn't ship.

Want to see how we'd approach your next event?

20 minutes on a real event from your calendar. We'll walk the pre-event sourcing, on-floor capture, and CRM attribution writeback for that specific event.