Plate Lickers: How to Spot Them Before They Register (and What They Really Cost)
Every advisor who runs dinner seminars knows the type. They arrive on time, order the surf and turf, nod thoughtfully through your presentation, compliment the venue on the way out, and would sooner enter witness protection than sit down for an appointment. The industry calls them plate lickers, and if you run events in the same market for long, you will get to know some of them by name.
In my practice's most recent campaign, 10 of 106 registered households were flagged as plate lickers before the events. Just under one in ten. That ratio has been fairly stable for us, and it is worth taking seriously, because plate lickers are not a punchline. They are a line item.
What a plate licker actually costs
Three costs, and only the first one is obvious:
The meal. A dinner seat at a decent venue runs real money, and a couple occupies two of them. That is the cost everyone jokes about.
The displaced prospect. This is the one that actually hurts. Most seminars have a capacity, and most decent campaigns overfill it. Every seat a serial diner occupies is a seat a genuinely curious household did not get. In my last campaign, every attending household represented $225 of all-in campaign cost, but the real value of a seat was far higher: the campaign has produced over $1,300 in gross revenue per attending household so far. That is what a wasted seat costs. Not the steak. The household that never got the steak.
The poisoned numbers. Plate lickers wreck your analytics quietly. They register, they attend, they never book, and every metric downstream absorbs the distortion: your show rate looks fine while your appointment rate looks broken, and you start diagnosing the wrong problem. I wrote about this in the show rate piece: they belong in their own bucket, out of your denominators entirely.
How to spot them at registration
The signal is history, which means you can only see it if you keep history. Patterns that flag a registrant in my practice:
- They have attended before, more than once, and never booked. One prior attendance with no appointment is a person who was not ready. A pattern of them is a hobby.
- They register for everything. Different topics, different venues, same household. Someone interested in your retirement tax seminar and your estate planning seminar and your Social Security seminar within a few months is usually interested in dinner.
- The registration recurs across campaigns but the phone never answers. Serial diners are reliably unreachable between events, because there is nothing to reach them about.
None of this is visible if each seminar lives in its own spreadsheet, which is how most offices track. The registrant looks brand new every time because, on that spreadsheet, they are. Detection requires one continuous database across all your events, where the new registration lands on top of the household's full history, and the pattern is staring at you at review time.
How to handle them without being a jerk
My process: every registration lands on a pending list, and nothing goes out until it is reviewed. At review, a household with a plate licker history gets flagged, and flagged registrants are filtered out of the event by default, with a deliberate override if I want to allow someone anyway.
That override matters more than it sounds. Two judgment calls come up constantly:
The borderline case. A household that attended once eighteen months ago and did not book is not a plate licker; they are a slow prospect, and slow prospects close all the time. The flag is for patterns, not for anyone who ever ate without buying. Be honest about the difference, because the failure mode in the other direction, treating every non-booker as a moocher, costs you real future clients.
The room-filler case. Sometimes an event is undersold and a warm body is genuinely useful: a fuller room presents better and costs the same minimum either way. If you had to guarantee the restaurant a minimum spend anyway, seating a known diner in an otherwise empty seat costs you nothing and keeps the energy up. The point is not that plate lickers must never attend. The point is that their attendance should be your decision, made knowingly, instead of a surprise you discover when the appointment sheet comes back with their row blank.
And when you do decline someone, the mechanics are gentle: they simply are not confirmed for this event. Waitlists exist for a reason. Nobody needs a speech.
The one-line summary
Plate lickers are a data problem wearing a dinner napkin. Keep continuous history across every event, review registrations before your confirmation sequence fires, flag the patterns, and make room decisions on purpose. The dinner they eat is the smallest thing they cost you.
Full disclosure: the pending-review workflow, household history, and plate licker flagging described above are all features of SeminarEV, the system I built for my own practice. But the principle works on any stack that keeps permanent, cross-event history, which is exactly the thing single-event spreadsheets cannot do.