Category: Loyalty Sommelier

Your members choose, write, and host, three behaviors your program treats as service traffic instead of information. Rank their substitutions, surface their sentences at the point of purchase, and record the dinners they host. The winery that reads what members do grows where the other plateaus.

Consider two subscription programs at premium wineries of comparable size, with comparable tenure on the list and comparable retention. Both send four shipments a year. Both have members who talk about the wine without being asked. Three years on, one of them can tell you what its list chose last cycle, which sentences its members wrote about the current release, and how much of its volume went to other people’s tables. The other cannot answer any of the three, and its growth line shows it.

Neither program bought anything the other did not. One of them decided that what members do inside the program is information; the other has been treating it as service traffic.

The channel is not helping either of them. DTC shipments fell 15% in volume and 6% in value in 2025, the steepest decline since the series began in 2010 (Sovos ShipCompliant and WineBusiness Analytics, 2026). Growth this year comes from the list you have.

The Three Systems

System 1: The Choice Signal

Your members make a purchase decision every cycle when they edit, or decline to edit, what arrives. Those substitutions are handled one at a time as service requests and never read in aggregate. The system is a reading habit: rank what was swapped in and out per cycle, track the share of members who changed anything at all, then send that ranking to the release planning meeting and to the member currently choosing, by ordering your customization list by what the list actually took. If your members cannot edit at all, that is the first move, and there is a number attached to it: members who can edit their packages show 20.7% higher average order value and roughly 50% lower churn, across 1.4 million memberships at 17,000 programs (Commerce7 Data Drop, June 2026). That is an observed association across a very large sample rather than a controlled experiment, which is worth saying out loud before anyone repeats it upstairs.

System 2: The Member Note

Every word at your point of purchase was written by the party with something to sell, and your members price that in when they read it. The system moves member-written language to the surfaces where decisions happen, using material you already hold. Harvest replies, post-shipment notes, and the free-text on your pause and rejoin flows, searching for specifics rather than praise. Ask permission in writing, quoting the exact sentence and offering the naming choice, which is usually first name and city. Then place one sentence per wine beside that wine, in the allocation offer, the customization list, and the release email, rather than on a testimonial page nobody opens while deciding. There is no credible published figure for what this does to conversion in our category, and you should refuse to carry one into a meeting. The argument stands without it.

System 3: The Shared Table

Members buy your wine for dinners they host, and the transaction records one person where the evening had nine. The system gives that lane a shape and a record without turning it into a referral ask: a quantity built for a table, a delivery window tied to the date rather than to your fulfillment calendar, and a card that travels with the wine. Then an occasion field on the order, and an optional, host-controlled way for the table to find you afterward. The reason the record matters is visible in where records come from: point of sale is 55.2% of DTC transaction volume and 47% of all new customer records (Commerce7 Data Drop, “The Tasting Room Effect”). Transactions create records. This transaction has never been given the chance.

How the Three Connect

Run separately, these are three good habits. Together they close a loop around the one asset a Loyalty Sommelier program has in surplus and has never instrumented: what members do in relation to each other.

The Choice Signal tells you what the list wants. The Member Note puts the list’s own language where the next decision is made. The Shared Table turns a member’s own table into a commerce event you can see. Break any link and the other two lose footing: a ranked demand signal with no member language beside it is a spreadsheet, and member language with no occasion attached is decoration.

This is the same pattern behind a subscription program we operate: 11,600 subscribers, a 48% engaged-subscriber-to-buyer conversion rate, and roughly a 5% response rate, sustained for more than four years. Those are our own results and not an industry benchmark. Four years of that comes from reading what members do, not from a better campaign.

Why This Fits a Loyalty Sommelier

Your retention is the strongest thing about your program, and nothing here asks you to defend it again. Annual retention in this category runs roughly 64% to 77%, with about 40% of members cancelling in year one (Silicon Valley Bank, State of the US Wine Industry 2026), and you are not the winery with that problem.

The exposure is on the other line. Retention compounds; gross adds do not follow automatically, and a Director who can defend retention brilliantly and cannot defend growth is in a specific kind of trouble at review. All three systems move the growth line without a referral ask, without a migration, and without asking your most loyal members to spend social capital on your behalf. Each produces an artifact: a ranked demand list, a set of member sentences with written permission, and a count of how much volume is already going to other people’s tables.

Where to Start

If you cannot say what your list swapped out last cycle, start with the ranking; it is an afternoon with an export you already have. If your offer copy has never contained a member sentence, start with one quarter of replies and three permission requests. If you suspect a meaningful share of your volume is already going to hosted dinners, start by flagging last quarter’s oversized orders and calling three of those members.

The three-minute archetype assessment identifies which of the three will move your number first.

P.S. Of the three, the swap ranking is the one to do this week, because it needs nobody’s approval and no member’s permission. The member sentences need three people to write back, and the hosted-occasion lane needs a conversation with fulfillment about delivery windows. The ranking needs an export and an afternoon, and it is the one that changes what gets said in the next release meeting.

A member buying wine for a dinner they are hosting is a transaction your system records as one person, though eight drank it. Give the hosted occasion a shape, a table-sized quantity, a delivery window tied to the date, a card that travels with the wine, and an occasion field, and it becomes a commerce lane you can see.

Somewhere on your list this month, a member is buying six bottles for a dinner they are hosting. Eight people will drink your wine that evening, most of whom have never bought from you, several of whom will ask what it was. Your commerce platform records that evening as one transaction, one member, one shipping address. Every other place in your business where a group of strangers tastes your wine has instrumentation around it: the tasting room has a reservation system, an event has an RSVP list, a trade pour has a rep and a report. This one has nothing, and it happens more often than all of them.

It is worth saying clearly what this is not, because the category it gets filed under is the reason nobody has built anything around it. It is not a referral program.

The Shared Table

The Shared Table treats the member-hosted occasion as a commerce lane with its own shape rather than as an ordinary reorder that happens to be larger. Nobody is recruited, no introduction is requested, and no member is asked to spend social capital on your behalf. Three components.

Component 1: Name the occasion, not the referral

The framing decision comes first and determines whether the rest works.

A referral ask puts the member in the position of vouching, which costs them something real and which your best members ration carefully. That is precisely why referral volume plateaus in programs with excellent retention: the pool of people willing to make introductions is finite and gets used.

A hosted occasion asks nothing of the relationship. The member is having people over. They were going to serve wine. The only question in front of them is whose, and how much, and whether it arrives in time. You are competing with a supermarket run on a Thursday, not asking for access to anybody’s address book. Hold that distinction in the copy as strictly as you hold it in your own thinking, because the moment the offer smells like recruitment, it collects the same resistance the referral ask collects.

Component 2: Give it a transaction shape

Right now this purchase has no shape, so it defaults to the shape of a normal order and performs like one.

Three elements give it a shape. A quantity built for a table rather than for a person: six bottles across two wines is a dinner, twelve is a party, and a member planning either should not have to assemble it bottle by bottle from a list designed for personal consumption. A delivery window tied to the date rather than to your fulfillment calendar, since arriving two days after the dinner is a complete failure of an otherwise perfect order. And something that travels with the wine to the table: a card with the wines named and one line about each, in your voice, that the host can read out or leave on the sideboard.

None of that is a discount, and the discount instinct is the thing to resist. A member hosting a dinner is not price-sensitive on the day; they are logistics-sensitive and pride-sensitive. Solve those two and the order grows on its own.

The other thing a shape does is make the purchase askable. Right now there is no moment in your calendar where it would be natural to raise this, because an unnamed thing cannot be offered. Once it has a name and a shape, it has obvious placements: the release email in the weeks before the holidays, the confirmation after a visit where somebody mentioned an anniversary, the note to a member whose last three orders were all larger than their allocation. None of those is a campaign. They are places where a sentence about a dinner now fits and previously did not.

Component 3: Record the second party as a party

This is the component with the longest tail, and it is a data decision rather than a marketing one.

Look at where records actually come from in this category. Point of sale accounts for 55.2% of DTC transaction volume, and 47% of all new customer records are created there (Commerce7 Data Drop, “The Tasting Room Effect”). Records follow transactions. The hosted dinner is a transaction that creates none, because the system has one field for a person and the evening had nine.

The fix is modest and entirely within your control. Add an occasion field to the order: what it was for, and roughly how many people. That alone changes what you can ask of the data later. Then give the host an easy, optional way to bring the table into contact with you on their terms, which almost always means something the guests take rather than something you take from the guests: a card with a link to the wines they drank, a small allocation held for that address for a fortnight, an invitation the host can pass on. You are not collecting the room. You are making it possible for the room to find you.

What This Produces

The first output is visibility, and it arrives immediately, because the occasion field tells you within a quarter how much of your volume is already going to other people’s tables. Most Directors are surprised by the number, and it’s one nobody at your winery has ever had.

The second is basket size, and the mechanism is the same one behind the clearest verified finding in this part of our business: members who can edit their packages show 20.7% higher average order value and roughly 50% lower churn, across 1.4 million memberships at 17,000 programs (Commerce7 Data Drop, June 2026). That is an association rather than an experiment, and the lever underneath it is agency. A hosted occasion is agency with a date attached, which is why it behaves like the strongest version of it.

The third is slower and is the reason this belongs in a growth conversation rather than a service one. Annual retention in this category runs roughly 64% to 77%, with about 40% of members cancelling inside their first year (Silicon Valley Bank, State of the US Wine Industry 2026). A member who has served your wine to their own guests, by name, at their own table, has made a public statement about your winery in front of people whose opinion they care about. That is a different relationship from one that consists of four deliveries a year, and it does not require them to introduce anybody to you.

The Objection You Will Hear Internally

Somebody will say this is a referral program with the serial numbers filed off, and that you are dressing up an ask.

The test is whether the member has to do anything relational for you to get paid. In a referral program they do; the introduction is the product. Here the transaction completes whether or not a single guest ever contacts you, and everything downstream is optional and host-controlled. If your implementation drifts so that the member is chasing guest details on your behalf, you have rebuilt the referral program and you will get referral-program fatigue.

A second objection will come from operations, and it is fair: date-certain delivery is harder than it sounds, and a missed dinner is worse than no program. Start with the window you can actually hold, in the states you ship to most, and say no to dates you cannot make. One late arrival at a member’s own dinner party will cost you more than a quarter of this will earn.

This Month’s Action

Pull last quarter’s orders and flag every one that was larger than that member’s normal order and shipped to their own address. That rough filter catches most hosted occasions, and the count is your baseline.

Then call three of those members and ask what the order was for. Not a survey; three calls. You will learn what shape the offer needs, and you will hear the occasion described in the member’s own words, which is where the copy for it should come from.

P.S. The three ideas from this week share a shape. Each one takes something your members are already doing, choosing, writing, or pouring for other people, and gives it a record. Friday’s email puts them together and shows what a program looks like when all three are running.

Put your members’ own words at the point of purchase. The sentences they already wrote to you, in replies, post-shipment notes, and pause flows, read as information where your own copy reads as a claim. Harvest them, get written permission, and place one under each wine where the decision actually happens.

Open the four surfaces where a subscriber decides something: the allocation offer, the customization screen, the reorder page, and the email that carries the release. Now ask who wrote the words on them. The answer at almost every winery of your size is some combination of you, the founder, the winemaker, and whoever owned the templates three years ago. Every sentence at the moment of decision comes from the party with something to sell, which your members know, and which they price into how they read it. That is not a criticism of the copy. Most of it is good. It is a structural limit on what any amount of good copy can accomplish.

Meanwhile, the people who bought the wine, opened it, and wrote to you about it have produced sentences you are not allowed to compete with, and those sentences are sitting in a folder.

The Member Note

The Member Note is a harvest and placement routine. It puts member-written language at the point of decision, using material you already hold, and it requires no new campaign, no platform, and no request to your members for content. Three components.

Component 1: Harvest what already exists

Start with what has already been written to you, because the volume is larger than anyone expects and the material is better than anything solicited.

Four places are worth searching. Replies to your shipment announcements, which most teams triage for questions and then archive. Post-shipment notes, the ones that begin “we opened the ’22 on Saturday.” Whatever free-text field sits on your cancellation or pause flow, which contains the most honest writing in your entire business. And the reason people give when they rejoin, which is rarer and more useful than all of it.

Search on a quarter at a time. You are looking for specifics rather than praise: the occasion, the food, the person they opened it with, the thing they were surprised by. Praise is not usable and will not persuade anyone. A sentence naming a Tuesday, a dish, and a bottle is.

Discard more than you keep, and discard on a rule rather than on taste. Three go straight out. Anything that reads as a review, because a verdict invites the reader to disagree with it, while a description of an evening does not. Anything that praises you rather than the wine, which is warm to receive and useless at a point of purchase. And anything comparing you favorably to a named competitor, which creates a problem you do not need. What survives that filter is usually one sentence in twenty, which is why you search a quarter rather than a week.

Component 2: Get permission properly

This is the component that gets skipped and the one that can actually hurt you, so do it first and do it in writing.

Write to the member, quote the exact sentence you want to use, say precisely where it will appear, and ask how they would like to be named. Offer the choice explicitly: first name only, first name and city, or full name. Most people pick first name and city, and that form carries more weight than a full name because it reads as a person rather than as a credential.

Anonymous attribution is not a safe middle ground; it removes the entire mechanism. The sentence works because a specific person said it, and an unattributed quotation returns the reader to the assumption that you wrote it. If a member declines, thank them and move on. In practice, the ask itself lands well, because being quoted is a form of recognition that costs your winery nothing.

Keep a simple record: the sentence, the member, the date they agreed, the surfaces covered, and how to reach them if they want it removed. Ten rows in a spreadsheet is a sufficient system.

Component 3: Place it where the decision happens

Placement is where most of the value is won or lost, and the default placement is wrong almost everywhere.

The standard destination is a testimonial page, which is visited by people who have already decided and by nobody at the moment of choosing. The useful destinations are the four surfaces you audited: one member sentence beside the wine in the allocation offer, one in the customization list next to the bottle it describes, one on the reorder page, one in the release email under the wine rather than at the bottom under a heading.

The constraint that keeps this honest is one sentence per wine, attached to that wine. A block of quotations is decoration and gets skimmed. A single line under the bottle a member is looking at is information delivered at the moment the question is live.

Set a refresh cadence at the same time you set the placement, because the failure mode here is not a bad sentence; it is a sentence that has been sitting under the same wine for three years. One line per wine per release keeps the material current and keeps the harvest habit alive; a sentence about a vintage two releases back tells a member reading it that nobody has looked at this page since. Put the refresh on the release checklist, rather than relying on someone’s memory, next to the item about updating the tasting note, since it is the same job done by a different author.

Why the Same Words Land Differently

The mechanism here is not that members write better than you. Often they do not. The mechanism is that the reader assigns a different evidentiary status to the same sentence depending on who is understood to be speaking, and no improvement in your own writing closes that gap.

Be careful about what you claim for this, including internally. There is no credible published figure for how much member-written language lifts conversion in our category, and anyone quoting one to you is repeating something invented. Do not carry a number you cannot source into an ownership meeting, because the moment somebody asks for the source, you have spent credibility you needed for the rest of the year.

The defensible version is stronger than a borrowed statistic anyway. The channel has less tolerance for vagueness than it did: DTC shipments fell 15% in volume and 6% in value in 2025, the steepest decline since the report series began in 2010, and the average bottle price rose 11% for reasons the report attributes to mix shift as lower-priced buyers left the channel, not to anyone trading up (Sovos ShipCompliant and WineBusiness Analytics, DtC Wine Shipping Report 2026). In a channel contracting that way, the wineries holding their lists are the ones whose members can picture the bottle on a table. Your members describe that better than your tasting notes do, and the material costs nothing.

The Objection You Will Hear Internally

Somebody will say that member language is inconsistent with the brand voice, and at a heritage estate the person saying it may well be right to raise it.

Handle it by separating the two jobs rather than arguing about taste. Your voice does the describing: the vineyard, the vintage, the intent, the house style. The member sentence does the witnessing, and a witness is not supposed to sound like the brand. Placed under your own copy rather than in place of it, the two do not compete; the contrast between them is what makes the second one legible.

There is a second objection worth pre-empting, which is that this looks like a review system and reviews invite the bad ones. It is not a review system. You are quoting what members chose to write to you, with their permission, which is an editorial decision rather than an open channel. If you later want an open channel, that is a separate project with a separate risk profile.

This Week’s Action

Search one quarter of replies for the word “opened.” It is the single highest-yield search term, because it is how people describe the moment the wine actually entered their life.

Pick three sentences. Write to those three members this week with the quote, the placement, and the naming question. By the end of the month, you can have one member sentence under each of your next release’s wines, which is more member language than your point of purchase has carried in its history.

P.S. Both of this week’s ideas are about members influencing what other members buy. There is a third version that is not influence at all but an actual transaction, and it is happening in your program right now without a record. Wednesday’s email is about the purchase your members make for other people’s tables.

Your subscribers tell you what to ship every cycle in the substitutions they make to their own packages. Read those swaps in aggregate and they become the only unprompted statement of preference your program produces, at no cost, from exactly the people whose spending you are forecasting. Members who can edit their packages show 20.7% higher order value and roughly half the churn.

Pull the substitution records for your last three shipment cycles and read them as one ranked list: what members took out, what they put in, how many made a change at all, and how many left the default alone. Most DTC teams have never looked at that list in aggregate, because the platform presents substitutions one member at a time, as service requests to be fulfilled rather than as information to be read. Filed that way, each swap is an exception someone handles. Stacked up, the same swaps are the only unprompted statement of preference your program produces, and they arrive on a schedule, at no cost, from exactly the people whose spending you are forecasting.

That is not a reporting complaint. It is a signal that exists, has a known shape, and currently terminates in a fulfillment queue.

The Choice Signal

The Choice Signal is a reading habit, not a system purchase. It turns the substitutions your members already make into a ranked demand statement, then puts that statement in front of the two audiences who can act on it. Three components.

Component 1: Turn the choice on

Some programs do not produce this signal at all, because members cannot change what arrives. If that is your situation, the first move is not analysis; it is giving members the ability to edit.

There is a real number attached to that decision. Members who can edit their packages show 20.7% higher average order value and roughly 50% lower churn, measured across 1.4 million memberships at 17,000 programs (Commerce7 Data Drop, June 2026). That is the largest, most recent, most directly relevant figure available on this question, and it is worth being precise about what it does and does not say. It is an observed association across a very large sample, not a controlled experiment, and it does not promise that switching the setting on produces those deltas at your winery next quarter.

What it does support is the direction and the size of the prize, which is enough to move an internal conversation. The common objection is that editing will collapse the allocation plan as everyone takes the same two wines. That is a fulfillment constraint, and it is solved the way every allocation is solved: caps, windows, and a default that stays good. It is not a reason to keep members silent.

Component 2: Read the aggregate, not the individual

The individual swap is a service event. The aggregate is a forecast.

Build one list per cycle with four columns: wine swapped out, wine swapped in, count, and share of members who changed anything at all. That fourth number matters more than people expect. A cycle where 6% of members touch the package and a cycle where 30% do are telling you two completely different things about how well the default is landing, and neither reading requires you to know which member did what.

Read it against the constraint rather than in isolation. The DTC channel fell 15% in volume and 6% in value in 2025, the steepest decline since the report series began in 2010, and wines above $50 now account for 71% of DTC value, up from 52% in 2020 (Sovos ShipCompliant and WineBusiness Analytics, DTC Wine Shipping Report 2026). In a channel shaped like that, the question of what your existing members will actually take is worth more than it was five years ago, and you are the only person who can answer it for your list.

One cut is worth making and no more: split the ranking by tenure, first-year members against everyone else. Those two groups are usually reaching for different things, and the difference is the most actionable thing in the whole exercise, because the first-year cohort is the one you are most likely to lose and the only one whose preferences you have almost no history on. Beyond that split, resist the urge to segment. A ranking cut five ways stops being a signal and becomes a research project, and research projects do not survive a busy quarter.

Component 3: Send the signal back in both directions

A ranked list that stays in your file is half the exercise. The signal has two destinations.

The first is the allocation and release plan. Bring the ranking to the meeting where next cycle’s contents are decided, as a document rather than an opinion. A Director who can say “38% of the list swapped out the white last cycle, and two-thirds of them took the same red” has changed the nature of that conversation, and it will be the first time most of the room has seen member preference stated as a quantity.

The second destination is the member who is choosing right now. Somewhere in your customization flow there is an ordered list of what a member can select, and that order is currently set by your commerce platform or by whoever configured it. Ordering it by what the list actually chose last cycle costs nothing and changes what a deciding member sees first.

Keep that second destination aggregate. The temptation is to turn the ranking into a per-member recommendation, and that is a different project with a different cost, a different failure mode, and a much longer path to anything shippable. What you are doing here is simpler and needs no model: showing the list what the list did. Ordering a page is a configuration change; predicting an individual is a program.

What the Aggregate Will Tell You

The first finding usually arrives inside one cycle and is uncomfortable: the default is carrying less agreement than anyone assumed. That is not a failure of the winemaking. It is the difference between a package designed to represent the estate and a package designed for what this particular list drinks, and the two were never the same document.

The second finding is about who changes things. Members who customize are not the difficult members, which is how substitutions get discussed when they live in a fulfillment queue. They are the members who cared enough to open the window before it closed. Reading the log by tenure usually shows the habit concentrated in the members you would least like to lose.

The third takes a year and is the one that pays. Once you have four cycles of rankings, you can compare the swap rate with what happened next: who renewed, who lapsed, who moved up. Annual retention in this category runs roughly 64% to 77%, with about 40% of members canceling inside the first year (Silicon Valley Bank, State of the US Wine Industry 2026). Those are the odds you are playing against, and a member who actively chose their last three shipments is a different proposition from one who simply did not cancel.

The Objection You Will Hear Internally

Somebody will say that members do not know what they want, that the point of a curated program is the curation, and that ranking bottles by popularity is how a premium program becomes a supermarket shelf.

That objection is worth taking seriously rather than talking around, because the person raising it is protecting the thing that makes the program worth joining. The answer is that the signal informs the default; it does not replace it. Nobody is proposing that the list votes on the blend. The claim is narrower: when you build a package, you are making a prediction about what this list will keep, and you currently make that prediction without looking at the last three answers.

The second objection is quieter and comes from whoever runs fulfillment, who will point out that every substitution is a pick, a pack, and sometimes a phone call. That is true, and it is the reason substitutions get framed as a cost center in the first place. Put the two ledgers side by side rather than arguing from principle. On one side sits the handling cost of the swaps, which your operations lead can quantify in an afternoon. On the other sits the order-value and retention difference associated with members having the choice at all. You do not need the second number to be precise at your winery to know which side of that comparison is larger, and framing it as a comparison rather than as a complaint is what gets the conversation to a decision.

This Week’s Action

Export the substitution records for your last three cycles and build the four-column ranking. It is an afternoon in a spreadsheet, and the export already exists in your commerce platform.

Then take one number from it, the share of members who changed anything at all, and bring it to the next release planning meeting. Not a recommendation, just the number. The conversation it starts is the point.

P.S. There is a second thing your members produce that nobody reads: the sentences they write back to you. Somewhere in your reply folder is a description of your wine that will outperform anything written in-house, for a reason that has nothing to do with how good the writing is. Monday’s email is about that.

Most subscription referral programs run one mechanic — a code and a quarterly reminder — where three connected systems belong: advocate currency, sponsored onboarding, and a first-referral pipeline. Alone, each helps a little. Connected, they compound: currency gives an advocate something worth spending, onboarding makes that spend worth repeating, and the pipeline recruits the next advocate from behaviors your systems already record.

Picture two subscription programs of comparable size in comparable appellations, both of which would tell you they have a referral program. The first has a code, an incentive, and a reminder that goes out each quarter. The second treats advocacy as an ecosystem with a supply side, a conversion step, and a replenishment mechanism. Over three years, the gap between them widens steadily, and it is not explained by the wine or the enthusiasm of the base.

It is explained by the fact that the first program built one mechanic where three systems belong. This week covered all three.

The Three Advocate Systems

System 1: Advocate Currency

Your best subscriber has nothing to hand a friend except a discount code, which recasts them as a promoter rather than a host. Advocate currency replaces the code with transferable assets: a named, finite guest allocation the recipient could not otherwise buy, and an unconditional plus-one seat at subscribers-only pours. Critically, the capacity is issued with membership rather than earned after a referral, so the ask stops being a request for a favor and becomes a reminder that something unspent is about to expire. Programs that issue currency rather than codes may see warmer introductions rather than simply a higher count, and margin is protected either way, because you spend inventory and hospitality capacity rather than your price architecture.

System 2: Sponsored Onboarding

A referred subscriber joined a person before they joined a program, and standard onboarding erases that immediately. Sponsored onboarding names the sponsor in the first message, pairs the sponsor’s and new subscriber’s first shipment with an invitation to open it together, and routes the first year alongside the sponsor’s calendar. The research is directional but consistent: referred customers show roughly 16 to 25% higher lifetime value and about 18% lower churn (Schmitt, Skiera and Van den Bulte, Journal of Marketing, 2011, studying a German bank rather than a winery). That advantage is a starting condition, not a permanent property, and roughly 40% of subscription members cancel within the first year against standard-club retention of 64 to 77% (Silicon Valley Bank, State of the US Wine Industry 2026). Programs running referred subscribers through a generic sequence may spend the advantage inside precisely that window.

System 3: The First-Referral Pipeline

Advocacy is depletable, and a flat referral total can hide a pool running dry. The pipeline counts first-time referrers as a separate metric, triggers invitations off the behaviors that precede a first referral rather than off the calendar, and keeps the first ask deliberately small because a first referral carries social risk a repeat no longer does. The timing lever is measurable: triggered emails click near 5% against 1.5 to 2% for batch sends (Klaviyo and GetResponse benchmarks, 2024). Programs that trigger on behavior rather than the calendar may see the pool refill at roughly the rate it draws down.

How the Three Compound

Separately, these are three sensible tactics. Connected, they form a loop that feeds itself. The currency gives an advocate something worth spending, so the introduction is warm rather than promotional. Sponsored onboarding makes that spend visibly worthwhile, which is what makes the advocate willing to spend again. And the pipeline recruits the next advocate from the behaviors your systems already record, so the pool refills at roughly the rate it draws down.

Break any one link, and the loop opens. Currency without onboarding produces introductions that get processed like cold traffic, and the advocate quietly stops. Onboarding without a pipeline treats a handful of referrals beautifully while the source dries up. A pipeline without currency recruits new advocates and then hands them a coupon.

This is the same principle behind the program we operate with 11,600 subscribers, which has sustained a 48% engaged-subscriber-to-buyer conversion rate for more than four years at around a 5% response rate. Those are our own results rather than an industry benchmark, and what makes them durable is not a larger list or a better offer. It is a coordinated loop that keeps bringing new people into active participation instead of extracting more from the same responsive core.

The KPIs This Addresses

A Loyalty Sommelier Director defends three numbers, and this system is built around them without inventing any of them. Annual churn is the first: standard-club retention sits near 64 to 77% with roughly 40% canceling in year one (SVB 2026), and sponsored onboarding is aimed squarely at that first-year window. Subscriber value is the second: there is no credible published dollar band for wine subscriber lifetime value, so the honest framing is the referral effect itself, directionally higher value and lower churn for referred subscribers. Referral-attributed new subscribers is the third, and the pipeline is what keeps that share from decaying as your original advocates exhaust their reach.

Where to Start

If your subscribers are willing but nothing happens, the currency layer is empty. If referrals arrive and then churn like any other acquisition, the onboarding layer is empty. If your referral total is flat and the same names keep appearing, the pipeline is empty, and the plateau is already underway.

Most programs have one of the three, occasionally two, almost never all three. The three-minute archetype assessment is built to identify which layer is missing in yours and which one will move your numbers first.

P.S. The most common self-diagnosis is that the incentive is too small, and it is almost always wrong. Raising the reward pulls harder on the same depleting pool and produces a visible spike that masks the underlying decline for another quarter or two. The assessment is designed to tell you which layer is actually empty, so you stop paying more for the referrals you were already getting.

Advocacy is depletable: a flat referral total often hides a shrinking pool of first-time referrers, while the same enthusiastic few are asked again and again. The First-Referral Pipeline counts first-time referrers as a separate metric, triggers a specific invitation off the behaviors that precede a first referral — a guest brought to a visit, a gift order, a forwarded message — and keeps the first ask small. Triggered emails click near 5% versus 1.5-2% for batch sends (Klaviyo/GetResponse, 2024).

Referral programs follow a predictable arc. Strong first quarter, decent second, then a long slow flattening that nobody can explain. The usual response is to raise the incentive, redesign the email, or run a campaign reminding everyone that the program exists.

None of that addresses what is actually happening, which is arithmetic rather than motivation. A person has a finite number of people they can credibly introduce you to. Your most enthusiastic subscribers spent that capacity early, in the first two quarters, because enthusiasm is exactly what makes someone act fast. What looks like declining engagement is usually a small group of advocates who have already introduced everyone in reach, being asked to do it again.

Advocacy is depletable. Almost no program treats it that way, and the measurement is where the blindness starts.

The Metric That Hides the Problem

Nearly every referral dashboard reports total referrals per period. That number can hold perfectly steady while the underlying health of the ecosystem collapses, because a shrinking group of repeat referrers producing more each can mask a complete absence of new entrants.

The number to put beside it is the count of subscribers who made their first-ever referral in the period. That single addition changes what you can see. Total flat and first-timers flat means a healthy, replenishing system. Total flat and first-timers falling means you are drawing down a pool with nothing refilling it, and you are one or two quarters from the decline showing up in the headline number where ownership will notice it.

For a Director, this is also the more defensible metric to carry into a review, because it describes the capacity of the program rather than the output of a single campaign.

There is a simple way to build it without waiting on a reporting project. Export your referral events for the last eight quarters, tag each one with whether that subscriber had any prior referral event, and count the untagged ones per quarter. That is a spreadsheet afternoon rather than a data initiative, and it produces the one chart that tells you whether your program is a system or a harvest.

The First-Referral Pipeline

The pipeline exists to move subscribers from never having referred to having referred once. Three components, and deliberately no tier structure: ranking your base by advocacy is a different system with different problems, and it is not what replenishes a pool.

Component 1: Identify the pre-referral behaviors

A first referral is almost never the first social act. It is preceded by smaller ones that your systems already record, and nothing currently reads:

• A subscriber who brings a guest to a visit or a pickup. They have already made an introduction, in person, with no code involved.
• A subscriber who places a gift order shipped to a different address. They are putting your wine in someone else’s hands and attaching their name to it.
• A subscriber who forwards a message, visible as a distinct open or click from a new address, or who replies asking whether a friend can buy something.
• A subscriber who asks a question on behalf of someone else. “Do you ship to Oregon?” from a subscriber who lives in Napa is rarely a logistics question.

Each of these is a person demonstrating that they are willing to spend social capital on you. None is captured by a referral program that sits waiting for a code to be used.

Component 2: Trigger the invitation off the signal

When one of those behaviors fires, send a specific invitation within days, while the act is recent. Not a campaign, and not a promotion: a short message that acknowledges what they did and offers the currency to do it properly next time.

The timing advantage here is measurable and citable. Triggered emails click near 5%, while batch sends run near 1.5 to 2% (Klaviyo Email Benchmarks 2024; GetResponse Email Marketing Benchmarks 2024). A quarterly referral blast to your whole base is a batch send with all the performance that implies. An invitation that fires because a subscriber just brought a guest to a Saturday pour is a triggered message, arriving at the one moment the request makes obvious sense to the person receiving it.

Component 3: Make the first ask smaller than the second

A first referral carries social risk that a repeat referral has already discharged. The subscriber does not yet know how you will treat the person they send, which is precisely the uncertainty Friday’s sponsored onboarding is designed to answer.

So the first ask should be the smallest possible version: one guest seat, one named allocation, one person. Not “share this with your network.” The narrower the request, the lower the perceived risk, and a first referral is largely a risk-management decision on the subscriber’s part. Once they have done it once and watched their friend get treated well, the second is a different and far easier act.

Why Raising the Incentive Makes It Worse

The instinct when referrals flatten is to increase the reward, and it is worth understanding why that reliably produces a short spike followed by a steeper decline.

A larger incentive does not create new social capacity. It pulls harder on the subscribers who already refer, which accelerates the depletion you were trying to reverse. The subscriber who would have introduced two people over the coming year introduces them this quarter instead. Your total looks excellent for one reporting period, and the following year that person has nobody left in reach and a higher price expectation attached to the act.

The second cost is harder to measure and probably larger. Raising the reward moves the act from social to transactional in the subscriber’s own understanding of what they are doing. Someone who was introducing a friend because the friend would enjoy the wine starts weighing instead whether the payout justifies the ask, and those are different decisions with different answers. In a program whose entire competitive position is relationship depth, converting your most relationally motivated subscribers into commission-seekers is a strange trade to make on purpose.

The pipeline runs the other way. It spends no additional incentive and instead widens how many people participate at all.

What the Pipeline Produces

Programs that add first-time referrers deliberately, rather than waiting for enthusiasm to produce them, may see the plateau flatten out later or not appear at all, because the pool refills at roughly the rate it is drawn down. The compounding is worth naming: today’s first-time referrer, if their referred subscriber is onboarded well, becomes next year’s repeat referrer, and their referred subscriber becomes a candidate for their own first referral.

This is the pattern behind the program we operate with 11,600 subscribers, which has held a 48% engaged-subscriber-to-buyer conversion rate for more than four years at around a 5% response rate. Those are our own numbers rather than an industry benchmark, and the durability is the interesting part: sustaining that for four years is not a campaign result; it comes from continuously bringing new people into active participation instead of extracting more from the same responsive core.

A caution on expectations is fair here. This is a slower mechanism than an incentive push, and it should be presented that way internally, because a system abandoned in quarter two for underperforming against a spike was never going to survive long enough to compound. Set the expectation on the first-time-referrer count, review it quarterly, and let the total follow.

This Quarter’s Action

Run one query. Of the subscribers who referred someone in the last twelve months, how many had never referred before? Split that by quarter and look at the trend line rather than the total.

If first-time referrers are declining while your total holds steady, you have found the plateau before it arrives in the headline number, and the fix is a trigger rather than a bigger incentive. Start with the single easiest signal to capture, which for most programs is the gift order, since it is already a distinct transaction type in your DTC commerce platform and needs no new tracking to detect.

P.S. The reason this rarely gets built is that it produces no visible win in its first quarter. You are adding first-time referrers whose value shows up a year later, in a cohort nobody is tracking, while the incentive increase your peers chose produces a spike everyone can see immediately. The spike is drawn from the same depleting pool. The pipeline is the only one of the two that is still working in year three.

A referred subscriber’s welcome sequence erases the reason they joined when it treats them identically to a paid click, discarding trust a real person already vouched for. Sponsored Onboarding fixes this with three moves: naming the sponsor in the first message, pairing the sponsor’s and new subscriber’s first shipment, and routing the first year of invitations alongside the sponsor’s calendar. Referred customers show 16-25% higher lifetime value and about 18% lower churn (Schmitt, Skiera & Van den Bulte, 2011).

Consider what actually happened in the moments before a referred signup reaches your system. Someone with no commercial interest in the outcome put their own credibility behind your program, in front of a person whose opinion they care about. That is the most expensive form of endorsement in marketing, and you did not pay for it.

Then the record lands in your DTC commerce platform, and everything that follows is identical to what a paid click receives. Same welcome email, same generic sequence, same offer. The single most valuable attribute of that acquisition, the fact that a specific person vouched for you, is stored in a field and never used again.

We covered the attribution side of this in an earlier set: tracking the referral at join and closing the loop back to the referrer. This is the other half, and it is the half almost nobody builds. Once you know a subscriber was referred, what does their first year actually look like?

The Sponsored Onboarding Sequence

The design principle is simple to state and rarely implemented: a referred subscriber joined a relationship, so the onboarding should keep that relationship in the room. Three components, all configured inside the email automation platform and DTC commerce platform you already operate.

Component 1: Name the sponsor

Capture permission at the time of referral with a single checkbox in the sharing flow, then reference the sponsor by first name in the first message the new subscriber receives. Not “you were referred by a member,” which reads as a database lookup. The actual name, in the actual sentence, the way a person would say it.

This does one specific job. A new subscriber’s earliest impression of a program is whether it is a machine or a place with people in it. When the first message names the friend who brought them, the program immediately inherits some of that friend’s warmth. When it does not, the borrowed trust starts converting back into ordinary consumer skepticism from day one.

Component 2: Pair the first shipment

Put the same wine in the sponsor’s and the new subscriber’s first cycle together, and say so to both, with a brief suggestion that they open it in the same week and compare notes. This costs you nothing beyond an allocation decision, and it converts the first shipment from a solitary delivery into a shared occasion.

The reason this matters more than it sounds is that first shipments are when new subscribers form their verdict, and a verdict formed in isolation is fragile. A bottle opened alone produces an opinion. A bottle opened in conversation with the person who recommended it produces a memory, and memories are what people renew for. You are not adding an experience; you are refusing to waste one that the referral already created.

Component 3: Route the first year alongside the sponsor

For the first year, bias invitations toward the events, pickups, and release windows the sponsor is already attending. If the sponsor attends the spring pickup, the new subscriber’s invitation is timed and framed around it. Where a pairing is impractical, the fallback is to route both into the same cohort at least, so the touchpoints stay parallel.

The first year is where this either holds or evaporates. Roughly 40% of subscription members cancel within their first year, and standard-club annual retention ranges from 64% to 77% (Silicon Valley Bank, State of the US Wine Industry 2026). A referred subscriber routed into a generic first-year cadence is exposed to exactly those numbers, with none of the social structure that produced the join still operating.

There is a practical version of this for programs where pairing calendars is genuinely impossible. Bias the content rather than the logistics: if the sponsor is a Cabernet buyer who attends library tastings, the new subscriber’s first year of recommendations and invitations leans that way rather than defaulting to your general calendar. The sponsor’s revealed preferences are a better predictor of a referred subscriber than your baseline is, because the referral itself was an act of matching. Someone decided these two people would like the same thing, and they were usually right.

Where This Breaks in Practice

Three failure modes account for nearly every implementation that stalls, and all three are worth deciding in advance rather than discovering in production.

The first is permission. Some sponsors do not want to be named, and a program that names them anyway has damaged the relationship it set out to honor. The checkbox is not a formality; it is the difference between an introduction and an exposure. Default it to unchecked, phrase it in plain language, and accept that a meaningful share will decline. Those referrals fall back to a warm generic welcome, which is what every referral gets today anyway.

The second is the anonymous arrival. A shared link forwarded three times has no identifiable sponsor by the time it converts, and no amount of configuration recovers a relationship the data never captured. This is where the attribution work earns its keep: capturing the source at the join, rather than reconstructing it later, is what makes sponsored onboarding possible at all. Without it, you have a well-designed sequence and nobody to run it on.

The third is the lapsed sponsor. Naming someone who canceled two months ago is worse than naming no one, because it advertises churn to a subscriber during their most impressionable weeks. Add a status check to the trigger condition: if the sponsor is no longer active, the new subscriber is quietly routed to the standard sequence.

None of these are reasons to skip the build. They are reasons to settle the edge cases at design time rather than while debugging a live sequence in front of your warmest acquisitions.

What Sponsored Onboarding Protects

Research on referred customers is consistent and worth citing accurately: they show roughly 16-25% higher lifetime value and about 18% lower churn than customers acquired through other channels. That work comes from Schmitt, Skiera, and Van den Bulte in the Journal of Marketing (2011), and it studied a German bank rather than a winery, so treat it as directional evidence about referral as a mechanism rather than as a wine-specific benchmark.

Read carefully, though, that finding is a warning as much as an encouragement. The advantage is not a permanent property of the subscriber; it is a starting condition. It comes from the fit and trust that the sponsor supplied at the point of introduction, and it decays exactly as fast as the program lets that relationship go quiet. Programs that route referred subscribers into the same generic onboarding as everyone else are spending an advantage they were handed for free, and they will never see it on a report, because nothing in a standard dashboard shows you the retention you failed to keep.

It is worth being precise about what this does and does not claim. Sponsored onboarding does not make a subscriber more valuable than the research already suggests; it prevents you from discarding an advantage you were given at no cost. That is an unglamorous framing, and it is the accurate one. The gain is defensive; it shows up as churn that did not happen, and defensive gains are notoriously hard to see in a dashboard built to celebrate acquisition.

For a Loyalty Sommelier program, the stakes are higher than for the other archetypes. Relationship depth is the entire competitive position. A referred subscriber is the one acquisition that arrives with depth pre-installed, which makes generic onboarding a more expensive mistake here than anywhere else in the business.

This Week’s Action

Pull the referred subscribers who joined in the last two quarters and read the first three messages each of them received. Not the ones you intended to send: the ones that actually went out. Then ask whether any of them would look different if the subscriber had arrived through a paid ad.

If the answer is no, you have found an unbuilt system rather than a broken one, and the cheapest component to build first is the sponsor name, because it is a permission checkbox and a merge field. The paired shipment and the shared calendar can follow once the first message no longer treats your warmest acquisition as your coldest.

P.S. There is a second beneficiary here that the reporting will never attribute correctly. A sponsor who watches their friend get treated well becomes far more willing to spend their next introduction, and a sponsor who watches their friend get processed will quietly stop referring without ever telling you why. Sponsored onboarding is a retention system aimed at new subscribers and an advocacy system aimed at existing ones, which is exactly the question that Monday’s email addresses.

Advocate currency — a named guest allocation and an unconditional plus-one seat, issued with membership rather than earned — gives a subscriber something transferable to hand a friend instead of a discount code. The framework has three parts: a finite allocation tied to one release, a plus-one seat at subscriber-only pours, and capacity issued with membership rather than earned. DTC shipments fell 15% in volume in 2025 (Sovos/WineBusiness Analytics, DTC Wine Shipping Report 2026), making your existing base the most reliable growth channel.

Here is a question worth putting to your own program this week. A subscriber who genuinely likes what you make wants to bring someone in. They are sitting at dinner, the wine is open, and a friend asks where it came from. What, concretely, does that subscriber have to offer in that moment?

For almost every mid-tier subscription program, the immediate solution is a discount code. Fifteen percent off a first order, or twenty off a case. That code is the whole inventory. And a code is a strange thing to hand a friend, because it recasts the relationship: your subscriber is no longer someone sharing a discovery; they are someone passing along a promotion. Generosity is replaced by a transaction, and most people can feel the difference even when they cannot name it.

This is not a motivation problem. Your subscribers are willing. It is a supply problem: you have not given them anything worth giving.

The Advocate Currency Framework

Advocate currency is the set of transferable assets a subscriber holds and can spend on someone outside the program. Three components, all built from allocation and reservation capacity you already control.

Component 1: The guest allocation

Set aside a named, finite share of a release that each subscriber may pass to exactly one person outside the program. Not a discount on your general offering: a specific wine, in a specific quantity, that the recipient could not buy on their own.

The mechanics matter more than the size. It has to be named, so the subscriber can say what it is. It has to be finite, so spending it is a real decision. And it has to be tied to the subscriber’s own record, so the person receiving it is receiving something from them rather than from your marketing calendar. A subscriber who says “I have one of the reserve allocations, and I want you to have it” is doing something a coupon can never do.

Component 2: The plus-one

The second currency is a seat rather than a bottle. Every subscriber-only pour, pickup, or release event carries a small number of guest seats issued to the subscriber, spendable on whoever they choose, with no requirement that the guest sign up for anything first.

The unconditional part is the part programs get wrong. The moment a guest seat requires the guest to join, provide a card, or sit through a pitch, the subscriber knows they are delivering a prospect rather than bringing a friend. Almost none of them will do it twice. A seat with no strings costs you a pour and buys you the only introduction that reliably converts: an in-person one from someone the guest already trusts.

Component 3: Issued, not earned

This is the component that separates advocate currency from a referral program. The capacity arrives with membership. It is not a reward unlocked after someone refers; it is a standing part of what it means to be a subscriber, replenished on a schedule you set.

The behavioral consequence is significant. When the capacity is a reward, every ask is a request for a favor performed in advance. When the capacity already exists, the ask changes shape entirely: it becomes a reminder that the subscriber is holding something unspent, and that it expires. You are no longer asking them to do you a service. You are telling them about an asset they own.

Deciding who holds currency, and how often it refills

Two configuration questions determine whether this works or quietly becomes another unused benefit. The first is who receives capacity. Issuing to your entire base on day one dilutes the thing that makes it feel like standing: pick a tenure threshold, communicate it plainly, and let newer subscribers see it as something arriving rather than something withheld. The second is replenishment cadence. Capacity that never refills gets hoarded, and capacity that refills constantly stops being scarce enough to spend deliberately. An annual or per-release rhythm, announced in advance and expiring on a stated date, produces the behavior you want: a decision, made on purpose, before a deadline.

Expiry is the part programs flinch at, and it is doing real work. An asset with no end date is a permanent option, and permanent options do not get exercised. A named allocation that expires at the close of a release window forces the subscriber to answer a question they otherwise defer indefinitely: is there someone in my life who should have this?

The Objection You Will Hear Internally

Someone in the room will point out that you are giving away inventory, and that deserves a straight answer rather than a deflection. You are. The question is what you get in exchange, and against which alternative.

A discount-led referral program acquires subscribers by lowering the price of entry, and in practice that discount does not stay at the entry point. It anchors expectations, it reappears at renewal, and it follows the relationship for years. You have not spent inventory; you have spent your price architecture, which is the one asset in a contracting channel that is hardest to rebuild.

Advocate currency spends a bottle and a seat instead. Both are things you already produce; both are capacities you have already committed to; and neither affects what you charge. If the guest never converts, the cost is a pour. If they do, they enter at full price with a relationship already attached, and your pricing sits exactly where it was. Framed that way, the conversation with ownership stops being about generosity and becomes a straightforward comparison of which asset you would rather spend.

What the Framework Produces

Programs that issue currency rather than codes may see a different quality of introduction, not simply a higher count. The person who arrives via a guest allocation or a plus-one arrives with a specific wine or evening attached, and with a named person standing behind the introduction. That is a materially warmer starting position than clicking a shared code, and it shows up later in how those subscribers behave.

The industry context is what makes this worth your quarter. DTC shipments fell 15% in volume and 6% in value in 2025, the worst year since the report series began in 2010, and the rise in average bottle price is explicitly due to mix shift rather than premiumization (Sovos ShipCompliant and WineBusiness Analytics, DTC Wine Shipping Report 2026). Meanwhile, the spread between operators widened: top-quartile wineries grew DTC revenue by 22%, while the median was flat and the bottom quartile fell by 13% (Silicon Valley Bank, DTC Wine Report 2026). The channel is not growing everyone equally, which means the base you already have is the most reliable acquisition asset on your list.

There is a margin argument too, and it is the one to bring to ownership. A discount-led referral program buys new subscribers by permanently lowering the price of entry, and the discount tends to follow the subscriber for years. Access-led currency spends inventory and hospitality capacity instead, which you are already producing, and it leaves your price architecture untouched. You are trading a bottle for a relationship rather than trading your pricing for a signup.

This Month’s Action

Take your next allocation and carve out a guest tier before you announce it. Give every subscriber above a tenure threshold you choose one named guest allocation, communicate it as something they hold rather than something they earn, and put an expiry on it. Then measure only one thing: what share of the issued allocations is spent.

That single number tells you whether your subscribers lacked motivation or lacked inventory. In most programs it turns out to be inventory, and the finding reframes the entire referral conversation. No new platform is required; this is allocation configuration inside the DTC commerce platform you already run, plus one message from your email automation platform.

Two secondary readings are worth capturing simultaneously. Note which subscribers spend their allocation in the first week against those who let it drift toward expiry, because urgency of spend is a useful proxy for how socially active someone is around wine. And note what share of the guests subsequently buy anything at all, at full price, without a further offer. Those two readings give you the honest shape of the mechanism inside your own program rather than in a framework description.

P.S. Watch who spends their allocation first. It will not always be your highest-spending subscribers; it is usually the ones with the most social exposure to other wine buyers, which is a completely different segment and one your revenue reporting has never surfaced. That list is the real starting point for everything else in this week’s sequence, and Friday’s email is about how to find those people before they refer rather than after.

A pre-event priming sequence turns the days between RSVP and arrival into the highest-leverage stretch in your event calendar. Three components — segmented pre-arrival tracks for first-timers versus tenured members, a pre-commit wine allocation opening 72 hours before the event, and a 24-hour logistics confirmation — may lift event-attributed AOV and reduce no-show rates without changing the event itself.

Segmented tracks, a pre-commit window, and show-rate protection: the days before the door.

Here is the gap almost every event program leaves open. The reservation comes in, gets counted, and then nothing happens until the member walks through the door on the day. The space between the RSVP and the arrival, often a full week or more, is treated as dead time. It is not. It is the single most underused stretch in your entire event calendar, and it is where attendance quality and pre-committed revenue are actually won or lost.

For a Loyalty Sommelier program, this matters more than it does for anyone else. Your advantage is relationship depth, and an event is the highest-bandwidth relationship moment you have all quarter. Walking a member from “I said yes” to “I arrived already invested” is the difference between an event that fills a room and an event that moves your retention number.

The Pre-Event Priming Sequence

The sequence is a digital wrap around the physical event, built from systems you already run: the reservation system that holds the RSVP, the email automation platform that carries context, and the SMS platform that handles the final logistics. Three components do the work.

Component 1: Segmented pre-arrival tracks

A first-time attendee and a member three years into the relationship should not receive the same pre-event email. The first-timer needs orientation: where to park, what the format is, who they will meet, what to expect. The tenured member needs depth: what is being poured, why this vintage, what is different about this gathering from the last one they attended.

Route the two groups the moment the RSVP lands. Your reservation system knows join date and attendance history; that is enough to branch the sequence. The first-timer track is designed to reduce the anxiety that keeps new members from showing up at all. The tenured track is designed to raise anticipation, because for this cohort the event is a renewal of belonging, not an introduction.

Component 2: The pre-commit window

Open a small allocation tied directly to the event wine, 72 hours before the event, to attendees only. This is the component most programs miss entirely. A member who purchases before arriving has crossed the line from prospective buyer to committed buyer, and they arrive in a completely different posture.

The window works because it is scarce, specific, and time-bound: a named wine, a held quantity, a closing date that lands before the event itself. It is not a discount. It is early access as a reward for the RSVP. Members who buy in this window attend as participants who already have a stake in the wine on the table.

Component 3: Show-rate protection

The final touch fires 24 hours out: a single SMS that confirms logistics and nothing else. Time, place, parking, what to bring. No upsell, no pitch. The goal is to make arrival feel frictionless, because the most common reason a confirmed member does not show is not a change of heart; it is a small logistical uncertainty that tips a busy evening toward staying home.

For remote members, the same three-component sequence runs against a shipped tasting kit, so the digital attendee gets a genuine parallel experience rather than a passive feed of an in-person room.

What the Sequence Produces

Programs that prime before the door, rather than waiting for arrival, may see two numbers move together. Event-attributed AOV rises, because a meaningful share of attendees arrive having already purchased through the pre-commit window. And no-show rates fall, because the segmented tracks and the 24-hour logistics confirmation remove the friction and uncertainty that quietly erode attendance.

Both improvements come without touching the event itself: the venue, the pour, the format, and the staffing are unchanged. The lift is entirely in the wrap around the event, which is why the return on the configuration time is high. You are not spending more on the event; you are capturing more of the value the event was always capable of producing.

There is a second-order effect worth naming. A member who buys in the pre-commit window has handed you a behavioral signal: this person responds to event-linked scarcity. That signal feeds everything downstream, from how you sequence their next invitation to how you weight them in your retention model.

This Month’s Action

Take your next scheduled event and build only the pre-commit window. Skip the segmentation and the SMS for now; just open a small, named allocation tied to the event wine, 72 hours out, to confirmed attendees. Measure two things: what share of attendees purchase before arriving, and whether their on-site or post-event spend differs from attendees who did not. That single data point will tell you whether the full sequence is worth building, and it usually is.

Configuration for the full sequence is a few hours across your reservation system and email automation platform. The pre-commit window alone is often live within an afternoon.

P.S. The pre-commit window quietly solves a problem most Directors do not associate with events: it pulls revenue forward into a measurable, attributable moment. Instead of hoping attendance converts to purchases at some vague later date, you have a dated transaction tied to a specific event and a specific member. That makes the event legible in your reporting.

The 72 hours after a winery event are when membership value is captured or lost. A structured post-event sequence — recognition within 24 hours that names what the member specifically did, an event-linked wine allocation closing within days while sensory memory is still vivid, and a rebooking prompt before the afterglow fades — may produce higher event-attributed repeat purchase and a measurable retention lift that the same outreach sent weeks later cannot replicate.

Recognition, an event-linked allocation, and a rebooking prompt, all inside the window that closes fast.

The most expensive mistake in winery events is not a low turnout or a high catering bill. It is letting the 72 hours after the event pass without a deliberate sequence. The wine is poured, the room is reset, the team moves on to the next thing, and the single most valuable stretch of the entire event quietly elapses unused. The attention you spent weeks and real dollars to create peaks the moment the member walks out, and then it decays, fast.

For a Loyalty Sommelier program, this is the window where the event either becomes a retention event or stays a nice evening that shows up only as a cost line. The difference is not the quality of the gathering. It is whether a structured digital sequence is waiting on the other side of the door.

The 72-Hour Post-Event Window

Three components, all built on the email automation platform, SMS platform, and DTC commerce platform you already run. The constraint that makes them work is time: each fires inside a window measured in hours and days, not weeks.

Component 1: Recognition within 24 hours

The first touch is not a sell. It is an acknowledgment of what the member specifically did. If they worked the sorting table, name it. If they built a blend in a small group, reference it. If they attended remotely against a tasting kit, acknowledge the format. The detail is the entire point: a templated “thanks for coming” reads as automation, while a specific recognition reads as attention.

This touch closes a psychological loop. The member took the time to show up and participate; the recognition confirms that the participation was seen. For the relationship-driven members who form the core of a Loyalty Sommelier base, being seen is the currency that retention is actually built on.

Component 2: The event-linked allocation, closing fast

Within the same window, open the wine they tasted as a held allocation for attendees, with a close date a few days out. This is distinct from the pre-commit window in Monday’s sequence: that one captured intent before arrival, this one captures it while the sensory memory is still vivid. A member who tasted a wine on Saturday and can purchase it on Sunday, while the impression is fresh, converts at a rate that the same offer sent a month later never reaches.

The speed is not a gimmick. It is matched to how attention actually behaves. The allocation closing in days, rather than sitting open indefinitely, respects the reality that the window is short and gives the member a reason to act inside it.

Component 3: The rebooking prompt

Before the afterglow fades, offer the next gathering. The second commitment is dramatically easier to secure inside the window than it is in a cold invitation weeks later, because the member is currently holding a positive, concrete memory of the last one. A single attendance is a data point; a rebooking is the start of a pattern, and patterns are what move retention.

For remote attendees, all three components run against their kit and their digital experience, so the follow-up never depends on whether someone was physically present. Geography decides where a member sits, not whether they get worked through the window.

What the Window Produces

Programs that run a structured 72-hour window, rather than an ad-hoc thank-you whenever someone gets to it, may see event-attributed repeat purchase rise and a measurable retention lift among attendees compared with non-attendees. The mechanism is timing, not new spend: the same recognition, the same wine, and the same invitation produce far more when they land inside the window than when they trickle out afterward.

The retention lift is the number that matters most for this archetype. An attendee who is recognized, who acts on a fresh allocation, and who rebooks before leaving the afterglow has just compounded three small commitments into a meaningfully deeper relationship. That depth is what defends the 4-7% annual churn band that distinguishes a strong Loyalty Sommelier program from the roughly 18% industry baseline.

This Week’s Action

Audit how long your current post-event follow-up takes to reach an attendee. Pull your last event and find the timestamp of the first message that went out afterward. If it is more than 24 hours, or if there was no structured follow-up at all, that gap is your fastest available win. Build the recognition touch first: it is the simplest to configure and the one that sets up the allocation and the rebooking prompt that follow.

Total configuration across the three components is a few hours, all on platforms you already operate.

P.S. The component Directors underestimate most is the rebooking prompt. The cost of securing a member’s next attendance inside the afterglow is a fraction of the cost of re-earning their attention from cold weeks later. If you build only one piece of this window, build the one that turns a single event into a habit.