A field event dinner is not a thank-you party. It is a tightly produced, 10 to 12 person working session with named target accounts, timed to a conference or city tour, that gets a buying committee into a room with your executives and a peer customer. Done well, more than 60 percent of accepted invites convert into a sales-accepted meeting inside two weeks. Done poorly, you spent a four-figure venue bill feeding the people who already like you. This guide walks the full motion end to end, owned jointly by Field Marketing and the VP of Sales.
Time: 4-6 weeks lead time
The field dinner does not stand alone. It attaches to an anchor moment that gives invitees a reason to already be in town: a major industry conference, a user group, a regional roadshow stop, or a dense cluster of named accounts in a single metro. Pick the date to land either the night before day one of the conference or the night after day one, never the final night when invitees are catching flights home. If you are running a city tour without a conference anchor, pick a Tuesday or Wednesday and give at least four weeks of notice so calendars can clear. Confirm the anchor moment before you book the venue, because an empty seat on the wrong night is a four-figure write-off.
The invite list is the whole product. Start from the Field Marketing and VP Sales joint target account list for the city, filter to accounts in an active or near-active buying window, and pick the 25 to 35 names you will invite to seat 10 to 12. Every invite is a specific person at a specific account, not a generic distribution. For each name, the owning AE writes a one-line reason this seat is worth a dinner slot (open opportunity, stalled deal, new executive, strategic logo). If the AE cannot write the line, the name does not go on the list. Overweight accounts where the economic buyer and one coach can both attend, because the dinner compounds when two people from the same org go back to the office together.
The invite comes from the AE or the executive host, personally, on their own calendar and email domain. It is a short note, not a designed email. It names the city, the date, the restaurant, the format (10 to 12 person dinner, hosted conversation, peer customer attending), and one sentence of personal reason this specific person is being invited. Send the first wave four weeks out, follow up at two weeks and one week, and have Field Marketing track accept and decline status in the CRM against the invite list so the AE knows which doors to re-knock. A branded marketing email to the same list will convert at a fraction of the rate because it reads as a cattle call, not a seat held for them.
The venue is a working tool, not a flex. Book a private room (not a corner of a loud restaurant), with a single long table or a square of two tables that puts everyone in eye contact, and acoustics that let one person speak and the whole table hear. Confirm a fixed menu with two to three choices per course so the night does not stall on 12 people reading menus one at a time, and a wine pour that is generous but not sloppy. Walk the room yourself or send the Field Marketing lead to walk it the week before the dinner. Confirm the AV if the host will do any kind of structured opening, confirm the private room is actually private (no walkthrough traffic, no shared door with a louder party), and confirm the final guest count with the venue 48 hours out.
A field dinner is not a free-form meal. It is an 80 to 100 minute structured conversation with a loose dinner wrapped around it. The spine is four blocks. First, a 10 minute reception with drinks while late arrivals land. Second, a 10 minute seated icebreaker where the host welcomes the room, names why everyone is here, and runs one go-around question that gets every voice in the air before food arrives. Third, a 25 to 30 minute facilitated panel where the host interviews the peer customer with 3 to 4 prepared questions that surface the real operator story, followed by 20 to 25 minutes of open Q&A that pulls the rest of the table into the conversation. Fourth, dessert and open conversation for the last 30 minutes, which is where the AE works the room and books follow-ups. Write the agenda down, time it, and run it.
Seating is not first-come first-served. Build a seating chart with the Field Marketing lead and the AE for each account the day before the dinner. Put the peer customer in the center of one long side so the whole table can hear them during the panel. Put the executive host directly across from the peer customer or at the head so they can run the conversation. Alternate buyers with Strkr team members around the rest of the table so no account cluster becomes a side-conversation island. Separate attendees from the same competing accounts if that will create awkward tension. Print the seating chart, name cards included, and hand it to the host 30 minutes before guests arrive. Reseating 12 people on the fly in a busy restaurant is how the structured conversation never starts.
The dinner is wasted if the follow-up stalls. The SOP runs on a fixed 48 hour clock. Within 24 hours, the AE for each attending account sends a personal thank-you referencing a specific moment from the conversation (what the peer customer said about a problem the attendee is also facing, a question they asked, a side comment from the Q&A). Within 48 hours, the AE books the next working meeting on the attendee's calendar, with a draft agenda that moves the conversation from dinner-table to deal-mechanics. Field Marketing logs every attendee as a dinner touchpoint in the CRM against the account, flags the follow-up task, and tracks sales-accepted meeting conversion from the dinner as the primary success metric. The target is 60 percent or better of accepted invites converting into a sales-accepted meeting inside two weeks.
Inside two weeks of the dinner, the AE pod lead, the Field Marketing owner, and the executive host run a 30 minute debrief. Pull the data: invite accept rate, show rate, sales-accepted meeting conversion, and pipeline influenced inside 90 days once the window has run. Pull the qualitative signal: what the peer customer said that landed, what fell flat, which questions pulled the room in, which seat changes to repeat, which to drop. Write the debrief as a one-page memo and store it in the shared Field Marketing playbook so the next dinner in the next city starts from the current best version, not a cold start. The field dinner is a repeatable motion, not a one-off hero project. The debrief is what makes it compound.
Ten to twelve seated attendees is the operating range. Below eight the conversation feels thin and the economics do not justify the venue. Above fourteen the single-table dynamic breaks, the room splits into side conversations, and the peer customer story cannot be heard end to end. If you need to serve more than twelve, run two dinners on different nights, not one bigger table.
A well-targeted list with personal AE invites typically converts at 35 to 45 percent to accept and 70 to 85 percent of accepts to actual show. Plan the invite volume accordingly: to seat 10 to 12 buyers, invite 25 to 35 named contacts. A branded marketing-email blast to the same list will land in the single digits.
Jointly. Field Marketing owns the logistics (venue, menu, invite production, follow-up tracking, debrief memo). The VP Sales owns the target account list, the AE invites, the follow-up SOP, and the sales-accepted meeting conversion metric. If one of those two owners is absent from planning, the dinner becomes either a logistics exercise with no pipeline or a sales push with no production quality.
Sales-accepted meeting conversion inside two weeks of the dinner is the operating metric. The target is 60 percent or better of accepted invites booking a working meeting with the owning AE. Downstream, track pipeline influenced inside 90 days against the attendee cohort. Vanity metrics like attendance count and social photos do not predict pipeline and should not steer the budget decision.
Yes, in almost every case. The peer customer carries the credibility that no vendor can carry about themselves, and the hosted panel format gives the room a reason to listen to one voice at a time instead of fragmenting. If the right peer customer cannot attend, delay the dinner or substitute a credible industry analyst or operator who can speak candidly about the problem space, not a second vendor.
Four weeks of lead time is the floor for a city dinner tied to a conference anchor, with follow-ups at two weeks and one week out. For a city tour without a conference, give at least four to six weeks so executive calendars can clear. Last-minute invites inside two weeks will fill with people who happen to be free, not with the named buyers you built the list to reach.
Strkr lets Field Marketing and the VP Sales share one named account list, one invite funnel, and one follow-up SOP so every dinner attendee is tracked against the deal they are tied to and the sales-accepted meeting target is visible to both teams in real time.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
