Steven Etzler shares and promotes small, peer-learning events for enterprise technology leaders, including executive dinners and lunch-and-learns on topics such as AI, infrastructure, and financial services.
They are most useful for running small peer-learning executive dinners and lunch-and-learns around enterprise technology conferences.
Best for
Brands planning executive dinners or lunch-and-learns around major conferences for technology leaders.
Not for
It does not fit always-on paid posting, video campaigns, broad developer reach, or open large events.
Key takeaways
Piggyback a private executive dinner onto a major conference.
Judge the room by fit, not headcount, about twenty well-matched executives.
Topics include agentic AI in production and infrastructure cost, capacity, vendor risk.
Check first: Ask for recent confirmed results from comparable executive dinners and lunch-and-learns.
Main ideas
Piggyback a private executive dinner onto a major conference · Judge the room by fit, not headcount · Peer-to-peer learning with practitioners and vendors in the same panel
Audience
18,719 LinkedIn followers · about 20 leaders Stated group size, Kansas City lunch-and-learn
Steven Etzler shares practical ideas for bringing enterprise technology leaders together in small, peer-learning events. Their posts cover how to make a conference-week dinner worthwhile and promote events focused on putting agentic AI into production in financial services, and managing infrastructure cost, capacity and vendor risk.
Etzler’s event advice focuses on what makes a gathering useful to busy executives: a convenient venue, careful timing, a well-matched group and more time for peer conversation than formal presentations.
In their conference-dinner playbook, they recommend using speaker lists to find relevant guests and inviting qualified local leaders beyond conference attendees.
Etzler's posts make one developed argument, illustrated by two events: the best return from a major conference or tradeshow comes from hosting a small, private peer event alongside it—usually a dinner or lunch—rather than adding another session to the agenda.
Read more
The advice is practical: where to hold the event, when to schedule it, whom to invite, and how small to keep the room. Two partner-hosted events for enterprise technology leaders demonstrate the approach, one on agentic AI in financial services and the other on infrastructure cost and vendor risk.
Piggyback a private executive dinner onto a major conference
The strongest way to get a return from a conference or tradeshow, in Etzler's account, is to borrow its audience rather than compete with it.
Read more
Target buyers are already gathered in one city; the challenge is giving them a reason to step away from the conference for a few hours.
Six practices underpin the argument: choose a venue within walking distance of the conference or its main hotels, since crossing town after a full day adds friction; pick a restaurant that sells the experience on its own; cross-reference the speaker list against ideal-customer and target-account lists, then invite the best fits; check the official agenda before choosing a night, since receptions, customer dinners, and partner events compete for the same evenings; keep formal programming short so peer conversation takes over; and curate a small group.
Etzler also recommends inviting qualified local executives who are not attending the conference and starting recruitment several weeks ahead, before executive calendars fill.
The closing point is a shift in mindset: don't build another conference session; build the conversation people wish they had more time for during the conference.
The post says twenty highly relevant executives around a table can be far more valuable than a much larger event. It outlines the benefits of a great venue, seamless check-in, strong hospitality, limited formal programming, and plenty of time for conversation, then asks what others are doing to piggyback successfully.
Two posts carry near-identical text, presenting one settled position rather than a view that shifted between posts.
Across the posts, room quality matters more than size, and attendance is controlled.
Read more
The Kansas City event is described as an intimate group of about twenty leaders, with registration links for those seeking consideration for an invitation. The dinner playbook applies the same principle, recommending qualified local executives beyond conference attendees to broaden relevance, not headcount.
The New York financial-services dinner is nearly at capacity, and the post provides a registration link for those seeking consideration for an invitation. The Kansas City lunch-and-learn is described as an intimate group of about twenty leaders nearing capacity, with the same invitation process.
Peer-to-peer learning with practitioners and vendors in the same panel
Etzler's events are framed as peer learning rather than vendor pitches.
Read more
Their panels pair customer-side practitioners with vendor technologists, creating an exchange between buyers and suppliers rather than a product presentation. Etzler describes the format as peer-to-peer learning and networking in a private room, and names the speakers; the panel shows the room they assemble, not their own arguments.
The New York session, part of a national roadshow with Hewlett Packard Enterprise and NVIDIA, names Sanchet Pachpute of New York Life, Clyde Gillard of HPE, Moses Acosta of SHI, and Shrivathsan Sambath Kumar of UBS. The Kansas City lunch-and-learn with HPE GreenLake names Pedro Vazquez of Garmin, Jon Hickel and Malcolm Ferguson of HPE, Cortney Jonas Burnos of Transcom, and Robert Goodwin of Lightedge.
Two topics worth a room: AI moving to production, and infrastructure economics
Etzler puts buyer-side operational questions, not speculation, before enterprise technology leaders.
Read more
One event asks what it takes to move agentic AI from pilots into secure, scalable production in financial services: governance and auditability, protecting sensitive financial data, preparing enterprise data for AI, managing infrastructure and AI costs, and identifying the use cases with the greatest business value.
The other focuses on what the post calls the infrastructure supercycle: navigating cost, capacity, and vendor risk.
Both address decisions buyers are already making.
The attendee lists published with the New York post—IT, engineering, data, and AI leaders from banks, insurers, asset managers, and consulting firms—show whom the framing targets.
The New York post lists attending institutions including Barclays, BNY, BNP Paribas, Capital One, Citi, Deutsche Bank, EY, Fiserv, Guardian Life, KPMG, Morgan Stanley, MUFG Bank, New York Life, Nomura, Robinhood, State Street, TD, and UBS. Attendees can expect practical peer insights on balancing innovation, security, regulatory requirements, performance, and cost.
This post explains the method behind the events Etzler posts about, rather than announcing a specific dinner.
Read more
It answers the question planners ask first: what makes a conference-week dinner worth an executive's evening?
The post argues that a private executive dinner is one of the best ways to get more return from a major conference, because the audience is already concentrated in one city.
It lists six practices: keep the venue walkable from the conference or main hotels, since asking people to cross town after a full day adds friction; choose a restaurant strong enough to sell the experience on its own; cross-reference the conference speaker list with your target account list and invite the best fits; check the official agenda before picking a night, because receptions and partner events compete for the same evenings; keep formal content short and shift quickly into peer conversation; and favor a curated group, noting that twenty well-matched executives can beat a much larger room.
The post also suggests inviting qualified local executives who are not attending the conference and starting outreach several weeks ahead as calendars fill.
The closing line states the intent plainly: don't build another conference session; build the conversation people wish they had more time for during the conference.
For brands planning a campaign
A usable planning checklist for an agency brief: venue proximity, timing against the official agenda, speaker-list prospecting, a guest cap instead of an open list, and a recruiting timeline measured in weeks. These points let teams compare proposals point by point.
The clearest example of the dinner format in practice: it shows how the topic is framed, who is put on the panel, and how invitations are handled—more useful to a planner than a general description of the format.
Read more
The post announces a peer-learning dinner in a private room at Butter NYC, part of a national roadshow with Hewlett Packard Enterprise and NVIDIA, titled From Pilot to Production: Operationalizing Agentic AI in Financial Services.
Four speakers are named: a CIO from New York Life, an AI go-to-market leader at HPE, an engineering leader at SHI, and a director of AI product engineering at UBS.
The discussion covers what it takes to move agentic AI from pilot programs into secure, scalable production, including governance and auditability, protecting sensitive financial data, preparing enterprise data, managing infrastructure and AI costs, and identifying the use cases with the most business value.
The post lists attending institutions across banking, insurance, asset management, consulting and technology, and directs readers to a registration link in the comments, noting that the room is close to capacity.
For brands planning a campaign
A concrete model for a co-hosted dinner: two technology vendors, an end-customer-heavy speaker panel, a topic aimed at a regulated industry, and invitations handled through a registration link and capacity limit rather than open attendance. Useful as a template for proposing co-sponsors or writing panel briefs for a similar event.
See the smaller, daytime version of the same peer-learning model and how a technical topic becomes a panel that mixes customer and vendor voices.
Read more
It shows what a lunch-and-learn looks like alongside a full dinner.
The post announces a lunch-and-learn in Kansas City with Hewlett Packard Enterprise GreenLake, titled The Infrastructure Supercycle: Navigating Cost, Capacity and Vendor Risk.
The panel names five speakers: the head of global information security at Garmin, two HPE specialists, a vice president of AI and digital solutions at Transcom, and a vice president of solutions architecture at LightEdge.
The event is described as peer-to-peer learning in a private room at The Capital Grille, with an intimate group of about twenty leaders and registration through a link in the comments as the room approaches capacity.
For brands planning a campaign
A lower-commitment format for the same audience and topic area: a daytime meal, a roughly twenty-person room, and a panel balanced between end-customer practitioners and vendor technologists. Worth proposing when a client wants to reach enterprise infrastructure buyers without the cost or scheduling weight of an evening dinner.
Piggybacking executive dinners on major conferences
Etzler's clearest recurring argument is that the strongest way to get returns from a major conference or tradeshow is to host a private executive dinner alongside it rather than add another conference session.
Read more
The post sets out six practices: choose a venue within walking distance of the conference or its main hotels; pick a restaurant strong enough to sell the experience on its own; cross-reference the conference speaker list with ideal-customer and target-account lists; check the official agenda before choosing a night, since receptions, partner events, and customer dinners compete for the same evenings; keep formal programming short and let peer conversation take over; and limit the room to roughly twenty relevant executives rather than chase headcount. It also recommends inviting qualified local executives who are not attending the conference and starting recruitment several weeks ahead of the event.
Speaker-list prospecting cross-referenced with target-account lists, recruitment starting several weeks ahead, a curated room of about twenty, and a walkable private venue.
Warns against recreating a conference session: limited formal programming is the point of the format, not a shortfall.
For brands planning a campaign
A ready-made planning frame for agencies building executive dinners around conferences. It identifies the decisions that drive returns—location, venue quality, timing against the official agenda, and audience curation—and offers a concrete targeting method: cross-reference the speaker list with target-account lists.
Two posts describe a national peer-learning roadshow run with technology partners.
Read more
In New York, a private-room session with Hewlett Packard Enterprise and NVIDIA covered moving agentic AI from pilots into production in financial services, with end-user executives from New York Life and UBS alongside vendor technologists from HPE and SHI.
In Kansas City, a lunch-and-learn with HPE GreenLake covered infrastructure cost, capacity, and vendor risk, with speakers from Garmin, Transcom, Lightedge, and HPE.
Both events are invitation-based, target roughly twenty enterprise technology leaders, and promote a registration link for people to be considered for an invitation.
A panel of four to five speakers pairs customer-side practitioners with vendor experts in a private room, with invitation-only registration and a deliberately small group.
For brands planning a campaign
Brands should evaluate Etzler as a convener of small, partner-funded peer events rather than as a writer or keynote speaker. The format suits vendors seeking a curated room of named enterprise buyers in a specific city and topic area; the posts show the industries, job functions, and speaker mixes the series brings together.
The New York session focuses on what it takes to move agentic AI out of pilots and into secure, scalable production across financial services.
Read more
Named themes include governance and auditability, protecting sensitive financial data, preparing enterprise data for AI, managing infrastructure and AI costs, and identifying the use cases delivering the greatest business value. Attendees are listed as IT, engineering, data, and AI leaders from banks, insurers, asset managers, and consulting firms.
For brands planning a campaign
For brands selling AI governance, data readiness, or cost-management capabilities into regulated financial services, this framing speaks to buyers moving beyond experimentation and into production decisions. The named attendee list gives prospective sponsors a concrete way to assess whether the room matches their target accounts.
The Kansas City lunch-and-learn focuses on what the post calls the infrastructure supercycle: navigating cost, capacity, and vendor risk.
Read more
It targets enterprise technology leaders and pairs a security leader from Garmin with hybrid cloud, solutions architecture, and engineering speakers from HPE, Transcom, and Lightedge in an intimate group of about twenty.
For brands planning a campaign
This recurring subject area points to buyers weighing infrastructure economics and supplier exposure. Brands with a hybrid cloud, infrastructure, or vendor-risk proposition can use it as evidence that the event series reaches this audience with a topic already framed in buyers' language.
Steven Etzler's posts name Hewlett Packard Enterprise and NVIDIA as partners in the executive event series they promote.
Read more
Both appear in announcements for small, private-room peer learning events aimed at enterprise technology leaders. Ask whether the brands sponsor the programs, co-host them, or hire the organiser, and what role Etzler has in the business running them.
Hewlett Packard Enterprise
Disclosed partnership
Hewlett Packard Enterprise is named as a partner in two event announcements.
Read more
A Kansas City lunch-and-learn is billed as "our lunch & learn roadshow program with Hewlett Packard Enterprise GreenLake", covering infrastructure cost, capacity, and vendor risk for about 20 leaders.
A New York event is described as "our national peer learning roadshow program with Hewlett Packard Enterprise and NVIDIA", focused on moving agentic AI into production in financial services.
To assess the relationship, ask how HPE participates and what role Etzler has in the business running the programmes.
NVIDIA is named alongside Hewlett Packard Enterprise as a partner in the New York peer learning event "From Pilot to Production: Operationalizing Agentic AI in Financial Services", held in a private room for IT, engineering, data, and AI leaders from financial institutions.
Read more
Ask whether NVIDIA sponsors, co-hosts, or otherwise funds the programme, and what role Etzler has in the arrangement.
Steven Etzler's posts are short event notes, not long essays.
Read more
Start with the two that make the case for running a private executive dinner alongside a major conference, then read the two event announcements to see the format in practice.
Follow them for the host's view of B2B event marketing: choosing a night around a crowded conference agenda, keeping the room to roughly twenty invited executives, and bringing customer-side practitioners and vendor technologists together on a panel.
The New York and Kansas City events apply the format to agentic AI in financial services and infrastructure cost and vendor risk, two subjects the posts return to.
Conference executive dinnersEvent marketingEnterprise AI adoptionInfrastructure cost and vendor riskField and event marketingExecutive engagement programsInvitation-only executive dinnersPeer-learning roundtablesVendor and customer panelsEnterprise technology leadersFinancial services technology leadersB2B events and marketing teams
Joe Markert
Both argue that major conferences deliver more through relationships and small gatherings than session content.
Read more
Markert advises readers to network before arriving, skip sessions that will not move the business, and treat dinners and lobby conversations as the real meetings—the same case Etzler makes against building another conference session.
Markert writes from the attendee's side, offering a guide to meeting the right people and building a channel community, then applies that approach to a customer-success framework for MSPs. Etzler writes from the host's side: choosing the venue, timing the night around the official agenda, and gathering enterprise buyers for a vendor-funded panel.
Both treat conference and event marketing as a before, during, and after discipline, where scheduling and follow-through determine the result.
Read more
Adams names lead time, messaging cadence, and post-event follow-up as the three things that make an event work. Etzler covers the same ground, advising hosts to check the agenda before choosing a night and start recruiting several weeks out.
Adams makes a broad case for consistency in marketing and networking, aimed at professional-services firms, and points readers to a separate article. Etzler focuses on invitation-only dinners and peer-learning sessions for enterprise technology leaders, spelling out the logistics.
Both organise small, invitation-only gatherings around a larger industry conference and argue that visibility should start before the event.
Read more
Morris opens The Visibility Room for an interactive group ahead of the IFA conference and runs a Detroit gathering limited to fifteen women. That approach resembles Etzler's roughly twenty-person executive rooms, where fit matters more than headcount.
Morris focuses on personal-brand positioning, LinkedIn presence, and women in advisory and professional services. Etzler focuses on vendor-partner peer learning for IT, engineering, data, and AI leaders, with topics tied to enterprise buying decisions such as AI governance and infrastructure cost.
Steven Etzler's posts describe invitation-only peer-learning events for enterprise technology leaders: private executive dinners and lunch-and-learns tied to major conferences, covering topics such as agentic AI in financial services and infrastructure cost, capacity and vendor risk.
Read more
For a buyer planning executive dinners around conferences, the account offers a focused placement: a senior technology audience assembled in the conference city and kept small by design.
One Kansas City lunch-and-learn is described as an intimate group of about 20 leaders.
A New York financial-services session names speakers and guests from New York Life, UBS, Barclays, BNY, BNP Paribas, Capital One, Citi, Deutsche Bank, Morgan Stanley, MUFG, Nomura, Robinhood, State Street, TD, Fiserv, Google, KPMG, EY, Deloitte and others.
The LinkedIn account had 18,719 followers on 11 October 2026.
That figure measures account reach, not event attendance or audience composition.
The posts emphasize curation: walkable venues, guest lists of roughly twenty relevant executives, recruiting from conference speaker lists cross-referenced against a target account list, and outreach that starts weeks before the conference.
Because the groups are deliberately small, confirmed attendance quality matters more than follower totals.
Before committing budget, ask for recent confirmed results from comparable executive dinners and lunch-and-learns: invitations sent, confirmations and attendance; attendees' seniority and function mix (IT, engineering, data and AI leadership); the share from named target accounts; and institution type and city.
Ask for documented survey or platform demographic data covering geography, age or gender if those measures matter, and survey results for employer, occupation or job seniority.
LinkedIn followers
18,719
LinkedIn account record for the profile carrying the reviewed posts (account-level data, not from any post body) · 2026-10-11
Stated group size, Kansas City lunch-and-learn
about 20 leaders
Steven Etzler's own description of the planned event in the post · 2026-09-28
Etzler's posts document partnership work built around invitation-only peer-learning events for enterprise technology leaders: private executive dinners timed to major conferences and lunch-and-learn roadshow stops co-branded with technology vendors such as Hewlett Packard Enterprise and NVIDIA.
Read more
One post draws on firsthand experience running conference-adjacent dinners, and the event posts name vendor partners alongside panels of guest speakers from large enterprises. Ask directly about sponsorship terms, packages, pricing, and how to inquire; the posts do not provide those details.
Conference-piggyback executive dinner
Buyer requirement
Anchor the dinner to a major conference where your target audience is already gathered, and choose a venue within walking distance of the conference site or main hotels.
Asking executives to cross town after a full conference day adds friction.
The restaurant is part of the sell: look for a strong reputation, a private room, good food, and attentive service.
Check the official conference agenda before setting the date and time; receptions and vendor dinners compete for the same evenings.
Curate a group of roughly twenty relevant executives, keep formal programming limited, and leave most of the time for peer conversation.
Start recruiting several weeks out.
Cross-reference the conference speaker roster with your target accounts, then add qualified local executives who are not attending the event.
Co-branded lunch-and-learn or roadshow stop
Buyer requirement
The sponsored events in the posts are stops on a multi-city roadshow: a Kansas City lunch-and-learn with HPE GreenLake and a New York session with HPE and NVIDIA, both held in private rooms at well-known venues.
The vendor partner brings named speakers and a topic the audience cares about — here, infrastructure cost, capacity and vendor risk, and moving agentic AI from pilot to production in financial services.
The event includes the venue, hospitality, and invitation handling.
Expect an invitation-only room of roughly twenty enterprise technology leaders and registration by application rather than open ticketing, with capacity filling before the date.
Executive speaker panel slot
Buyer requirement
Both event posts list four to five named speakers from large enterprises and their vendors — for example, information security and cloud leaders from Garmin, Transcom, and Lightedge, and AI and engineering leaders from New York Life, UBS, and SHI.
For a client or your own executive to reach this audience, negotiate a panel slot, with the commitment to speak on the set theme rather than promote.
Confirm panel terms and any sponsorship cost directly; the posts do not list fees or a booking process.
Strong fit. Steven Etzler's posts describe exactly this need: private executive dinners timed to major conferences, plus co-hosted lunch-and-learns in conference cities, for roughly twenty enterprise technology leaders at a time. The posts spell out the method, rather than merely implying it.
Read more
Brief
A B2B event marketing agency wants to plan high-ROI executive dinners around major conferences. It needs a format to copy, a guest-list method, and a partner to run the room.
Reasons
The planning method is on the record. One post sets out six practices for piggybacking an executive dinner onto a major conference: choose a venue within walking distance of the conference or its main hotels; pick a restaurant that sells the experience on its own; cross-reference the conference speaker roster against your target-account list; check the official agenda before choosing a night, since receptions and partner dinners compete for the same evenings; keep formal content short and move quickly into peer conversation; and cap the room at roughly twenty well-matched executives instead of chasing headcount. The post also recommends adding qualified local executives who are not attending the conference and starting recruitment several weeks out.
The format is demonstrated, not just described. Two posts document private-room events in conference cities: a New York financial-services dinner co-hosted with Hewlett Packard Enterprise and NVIDIA, and a Kansas City lunch-and-learn with HPE GreenLake. Each features four to five named speakers from end-user companies and vendor partners. A planner can see how the topic is framed, who joins the panel, and how the invitation is handled.
The targeting method suits an agency approach. Cross-referencing a conference speaker list against an ideal-customer and target-account list is a concrete list-building step an agency can run and compare with its own approach.
The audience matches the brief. The New York post names IT, engineering, data, and AI leaders from banks, insurers, asset managers, and consulting firms; the Kansas City event pairs a security leader from a large enterprise with hybrid cloud and solutions architecture speakers. A brand selling into enterprise technology will recognise the room.
The topic framing speaks to buyers, not vendors. The discussion of agentic AI moving from pilot to production in financial services covers governance and auditability, protecting sensitive financial data, preparing enterprise data, managing infrastructure and AI costs, and prioritising use cases. It targets buyers making production decisions, not just experimenting. Infrastructure cost, capacity, and vendor risk speaks the same language to infrastructure buyers.
The posts show two co-branding models an agency can borrow: sponsor or co-host with a technology partner that supplies a named speaker and a theme, or add a client executive to a panel with a commitment to speak on the set topic.
What to confirm before committing
The posts show format and audience appeal, not outcomes. Ask for recent confirmed results from comparable dinners and lunch-and-learns: invitations sent versus confirmed versus attended, the seniority and function mix, the share of attendees from named target accounts, and the city and institution type. The posts do not state Steven Etzler's own role in these events, the wider event calendar, sponsorship pricing, or how an inquiry is handled, and the account's 18,719 LinkedIn followers say nothing about who attends the dinners. Treat the fit as a format and targeting match until attendance data is in hand.
When to choose a specialist
Poor fit. Steven Etzler's posts describe a small, invitation-only, in-person event model—not an ongoing publishing or video channel.
Read more
Brief
An enterprise software vendor wants an always-on paid creator program: a quarterly slate of sponsored posts and short videos aimed at a broad developer audience, with reach targets and per-post performance reporting.
Reasons
There is little publishable content to slot into a quarterly slate: four event announcements and one planning essay. The posts contain no long-form writing, video, or transcript material to support recurring sponsored posts or short videos.
Reach targets conflict with the documented design. The events are described as intimate groups of about twenty, with capacity limits and registration by application rather than open attendance. The only measured figure, 18,719 LinkedIn followers, is account reach, not audience delivery; follower totals do not establish who attends or reads.
There is no published commercial package to buy. Steven Etzler's posts contain no sponsorship policy, package specification, pricing, or inquiry route. A brand would be negotiating a new arrangement without a rate card or scope to compare against its media plan.
The posts provide no basis for performance reporting. They include no audience metrics for demographics, job function, geography, attendance, or engagement, so published data cannot support the per-post reporting this campaign requires.
The topic range is narrow by design. The reviewed events address agentic AI in financial services and infrastructure cost, capacity, and vendor risk. That is a strong match for enterprise technology buyers, but not for a broad developer-audience program.
What would change the assessment
The same vendor could be a good fit if it reframed the need as a single curated private event in one city, with a named client or vendor speaker on the panel and a target-account guest list. That means a smaller commitment, a tighter audience, and a format Steven Etzler's posts actually describe.
A worked campaign example
Angle
Turn one conference into a curated executive dinner with a written follow-up, using the six-point method as the operating plan and the co-hosted roadshow events as the template for partner support.
Example outreach
A short first message works better than a pitch: name the conference and date, state the theme in one line, name two or three confirmed panel voices, say the room is invitation-only and limited to about twenty senior technology leaders, and ask whether the person would like to be considered. Ask for one clear reply—interested or not—instead of a meeting.
How it would run
Choose the anchor conference where the client's target accounts are concentrated, and check the official agenda before setting a night; receptions and vendor dinners compete for the same evenings.
Build the guest list in two passes. First, cross-reference the conference speaker roster against the client's ideal-customer and target-account list, then invite the best fits. Next, add qualified local executives who are not attending the conference, a tactic the reviewed guidance recommends to expand the opportunity. Start several weeks before the event, since executive calendars fill early.
Choose a venue within walking distance of the conference site or main hotels, with a private room, strong food and service, and a reputation that helps sell the evening. The reviewed guidance identifies crossing town after a full conference day as avoidable friction.
Cap the room at roughly twenty relevant executives and make the invitation selective—by application or invitation, not open registration, as in the reviewed events.
Keep formal programming short and leave most of the time for peer conversation. The documented pattern is a short moderated discussion followed by networking; recreating a conference session is explicitly what not to do.
Use a peer-learning theme written in the buyer's language. For a financial-services room, focus on moving agentic AI from pilot to secure, scalable production, including governance and auditability, protecting sensitive financial data, enterprise data readiness, managing infrastructure and AI costs, and prioritising the use cases with the most business value. For an infrastructure room, focus on cost, capacity, and vendor risk.
Recruit speakers as the reviewed events do: four to five named panellists, mixing end-user practitioners from large enterprises with vendor technologists, all committed to the set theme rather than promotion.
Follow up in writing with the discussion points and a next-step ask, so the client can act on the dinner’s outcomes after the evening ends.
What would make this reproducible
Before repeating the model, get confirmed results from at least one comparable event: invitations sent, confirmed, and attended; the seniority and function mix of the room; the number of attendees from named target accounts; and the institution types represented. Ask who hosts and organises the events, since Steven Etzler's posts do not state their role, and whether panel terms or sponsorship costs apply, since their posts list no fees, package, or inquiry route.
Choose Joe Markert when the need shifts from producing a private dinner to working the conference floor, or when the buyer sells to managed service providers and channel partners rather than enterprise technology leaders.
Read more
One post is a practical field guide to a first conference: line up meetings on LinkedIn the week before, pick only sessions that move business, camp in a high-traffic spot such as the lobby or coffee bar, accept vendor dinners and happy hours, and treat the lobby or bar after the agenda as the place where useful conversations happen.
The other ties conference and industry relationships to a customer-success operating system for MSPs, organised around strategy, health, deliverables, process, people, and technology.
It argues that reliability is the price of entry, not the differentiator.
If the request is to help a smaller vendor or channel business get value from attending an event, or to frame the customer-success story behind a partner programme, Markert is closer to the task than a dinner producer.
The tradeoff is that Joe Markert's material focuses on attendee-side, one-to-many activity.
It offers no documented method for choosing a venue, building a guest list from a target-account list, recruiting named executive speakers, co-hosting with a technology partner, or capping a room at twenty.
A client who needs the dinner produced still has to solve the format, list, and partner model elsewhere.
Markert is the better answer to how an individual or small team should work a conference, not how to run a private room.
Choose Luke Adams when the campaign needs a longer runway around the event rather than a single evening.
Read more
One post lays out three event-marketing levers: lead time to get on calendars early, messaging cadence to stay visible without overwhelming, and post-event follow-up to turn attention into opportunity.
The strongest marketers, the post argues, build momentum before, during, and after—not only on the day.
The second post makes the case for consistency over cleverness in marketing and networking: repeat the core message until the market remembers you, show up when results are slow, follow up when it would be easier to move on, and let familiarity, reliability, and compounding relationships do the work.
An agency with the dinner format settled but in need of the surrounding outreach sequence, booth or sponsorship activity, and follow-up rhythm has reason to look here.
The tradeoff is that this is one-to-many event and brand marketing, not an intimate-room playbook.
There is no guest-list construction from a conference speaker roster, venue or capacity guidance, or co-hosting or panel-recruitment model.
Luke Adams shows a team how to time and sustain a campaign around a conference; the posts do not show how to fill twenty seats with the right executives or bring a technology partner into the room.
Choose Karyl Morris when a client needs to show up around a conference, or when the room should be small, invitation-only, and built around a specific community.
Read more
One post outlines a conference-visibility programme: how visibility works around an event, practical ways to start conversations through familiarity rather than introductions, how to be visible during the conference without being performative or glued to a phone, smarter post-conference follow-up, and using LinkedIn and digital presence to support—not replace—in-person networking.
The other documents an invitation-only gathering capped at fifteen women in advisory, consulting, professional services, and client-facing leadership roles.
Its stated goal is to get to know the people in the room rather than work it.
Among the other options described here, that is the closest match to the event's curated small-room principle, paired with a positioning method for the weeks before and after.
The tradeoff is scale and audience specificity.
Fifteen people in a room assembled for a defined professional community is a different instrument from twenty enterprise technology buyers gathered from a target-account list.
The posts do not cover cross-referencing a conference speaker roster against accounts, choosing a venue, co-hosting with a technology partner who supplies a panel speaker, or framing an enterprise-technology topic for the dinner.
Ask for those details if they matter to the brief.
Karyl Morris is the stronger choice when community, personal positioning, and pre- and post-event visibility drive the need; Steven Etzler is stronger when the job is the enterprise dinner itself.
This profile draws on four LinkedIn posts from Steven Etzler, captured 11 October 2026, all read in full.
Two are event announcements: a New York peer-learning dinner co-hosted with Hewlett Packard Enterprise and NVIDIA on moving agentic AI into production in financial services, and a Kansas City lunch-and-learn with HPE GreenLake on infrastructure cost, capacity, and vendor risk.
Two carry near-identical text setting out a method for piggybacking a private executive dinner onto a major conference, so that argument is treated as one repeated position rather than two.
The posts carry no publication dates and do not say what role Etzler had in the events, whether they had an employer, what their outcomes were, what sponsorship terms applied, or what pricing was offered.
No long-form writing, video, or transcripts were available.
Comparisons with other creators are based on posts by those creators and are used only for the specific similarities and differences described where they appear.