About Luminik

B2B events are broken.
We're fixing attribution.

Luminik exists because most teams can't prove what their events produced. Late prep, disconnected workflows, no defensible number. We fix that.

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 shows up three days before the show
  • 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 booth actually produced

Not one-off issues. This is how most B2B teams run events. Luminik exists to change that.

What makes us different

We start building your list 6 weeks before the floor opens.

Most teams get the attendee CSV three days before the show. We source from event platforms, exhibitor directories, and speaker lists weeks out. Your reps walk in with a ranked ICP list, not a printout.

Attribution lands in Salesforce, not a vendor dashboard.

Every meeting, capture, and sourced opportunity writes back to your Salesforce or HubSpot within 48 hours of floor close. 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. No handoff loss. Your team keeps working in the CRM and sequencer they already use every morning.

Who's behind it

Prasad Subrahmanya, Founder and CEO of Luminik
Prasad Subrahmanya
Founder & CEO, Luminik
Previously Venture CTO at Bain & Company; cofounder and CTO at Mainteny.

I spent five years in enterprise software shipping to Fortune 500 buyers, then three years at Bain on the venture side, helping portfolio companies stand up their GTM function. The question I heard most often from mid-market B2B SaaS marketing leaders was the same one: "We spent six figures on Money20/20 last quarter. How much pipeline did it actually produce?"

The honest answer was almost always "we don't know." Attendee lists arrived three days before the show. Reps walked in cold. Badge scans landed in a CSV that never made it into the CRM. By the time anyone reconciled follow-up, the opportunity window had closed. The $50K+ event intelligence tools stopped at "who's attending." The scan apps stopped at the badge. The closed event suites reported attribution inside their own dashboard. Three tools, three handoffs, three places the pipeline leaked.

Luminik is the system I wish these teams had. One pipeline from attendee sourcing through post-event attribution, running on the Salesforce, HubSpot, and enrichment vendors they already pay for. Built so the CFO sees the number in the CRM they already trust. If that sounds like the problem you are solving, we should talk.

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 the floor produces 6 meetings when we promised 10, that's on us, not on the event.
Specific over vague
1,840 ICP matches from 43,000 attendees. Not 'strong coverage.' We run on real numbers.
We build what breaks in the field
Reps get flaky conference Wi-Fi. CFOs need Salesforce, not a vendor screenshot. The roadmap starts there.
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 attribution writeback to Salesforce or HubSpot on that specific show.