Case study · Enterprise AI

Building a field motion that generated $89M in direct pipeline.

A leading AI company needed four major third-party events to do more than create visibility. MoonLight built the operating motion that connected those rooms to enterprise sales activity.

$2Bactive enterprise pipeline engaged
$89Mdirect Stage 1 pipeline generated
4major enterprise events in one month

The event calendar was set. The revenue motion was not.

The company was preparing for a concentrated month of major cloud and data-platform conferences. Strategic accounts, active opportunities, partners and senior buyers would all be in the room. Attendance alone was not the objective. The events needed to create measurable sales activity.

MoonLight was brought in to build and run the third-party field marketing motion across all four programs.

The challenge

The work had to connect account priorities, internal teams, onsite execution and follow-up across overlapping, high-visibility events. It also needed a measurement system that distinguished meaningful commercial engagement from booth traffic.

  • Prioritize the right accounts before each event.
  • Align sales, partnerships, product and event stakeholders.
  • Create useful reasons for enterprise buyers to engage.
  • Capture enough context for sales to take the next action.
The operating principle

The measurement and follow-up system had to be designed before the first event began—not after the exhibit hall closed.

What MoonLight built.

1. Start with the accounts

Planning began with the commercial opportunity: which accounts would be present, where they were in the buying process and which conversations could move them forward.

2. Build one operating motion

MoonLight connected field marketing, sales, partnerships, product, executives and external event teams around a shared plan. Ownership, staffing, messaging, lead capture and follow-up were established before teams arrived onsite.

3. Design for meaningful engagement

The programs were built to create substantive conversations with enterprise buyers—not simply traffic. Account meetings, product engagement and direct interaction with the people responsible for advancing opportunities were the priority.

4. Make follow-up part of the event

Lead context, routing and sales follow-up were treated as part of execution rather than post-event administration. Revenue teams could see who engaged, why the conversation mattered and what should happen next.

The result.

Across four enterprise events in one month, the program supported engagement with $2 billion in active enterprise pipeline and generated $89 million in direct Stage 1 pipeline.

The outcome did not come from a single booth, dinner or campaign. It came from treating field marketing as a revenue system: start with priority accounts, coordinate the organization around them and design every event around the next commercial action.

The takeaway

Enterprise events create pipeline when buyers have a reason to engage and the revenue organization has a disciplined way to act on that engagement.

Discuss a similar program