What specific contributions and value moments should be named in a year-one acknowledgment message?

The contribution worth naming is not the highest-volume contribution — the member who posted the most questions, the member who attended every office hours session, the member with the highest reaction count. It is the contribution with the most specific observable impact on another member: a reply in a goal-track channel that the original poster explicitly applied and followed up on; an introduction the member made in #intros that produced a DM exchange and a follow-up post from one of the connected members; a live event moment where the member described a methodology or decision and other members asked follow-up questions in the channel after the session. The specificity matters more than the magnitude. A contribution named as 'your contributions to the community have been valuable' is a performance of appreciation. A contribution named as 'in March, you replied to Taiwo's question about certification pathway design and she mentioned two weeks later that she had restructured her program based on what you described' is evidence that the operator saw something specific. The same principle applies to the value moment: not 'I hope you've been finding value here' but 'the conversation you had with Obinna in September about content modular design — the one where he shared the sequencing approach his team uses for onboarding academies — seemed to be the kind of thing you were describing when you joined.' The member knows immediately that this is not a template because it names something that only they and the operator could both have observed. If the operator cannot identify a specific contribution or value moment for a particular member, that is itself diagnostic: a member who has been active for twelve months without a single observable contribution or received value moment is a member who has been in peripheral engagement, and the question for that member is different from the question for an actively engaged member. The message structure can be adapted: 'I noticed you've been following the work happening in [goal-track channel] without posting much — I'd like to understand what's been most useful and what hasn't, before we head into year two together.' This is a contribution gap survey framing rather than an acknowledgment framing, but it serves the same function of opening a specific conversation rather than sending an inert renewal prompt.

What do you do when a member made no visible contributions — they were a 'reader' who posted rarely or never?

A member who reached month twelve without a single post, reply, or publicly visible contribution is not necessarily an unengaged member. Some members in paid professional communities are deliberate readers: they joined to learn from others' questions and cases rather than to contribute their own, they attend every live event without speaking, they read every goal-track channel carefully without posting. These members can be genuinely satisfied and genuinely retained. The problem is that the year-one acknowledgment message as written — naming a specific contribution — cannot be sent to them because there is nothing to name. The adapted approach: lead with the value moment instead of the contribution, and change the forward question to give the reader framing an explicit name. The message might read: 'You've been in the community for a year — I know you tend to read more than post, and I want to make sure the year has been worth it. The conversations in [goal-track channel] about [specific recent topic] have been among the best we've had; I'd like to know if that's the kind of thing that makes the community useful for you, or whether there's something else you'd want more of in year two.' This version still demonstrates observation — the operator knows this member reads more than posts, knows which channel they have been following — without manufacturing a contribution that did not exist. The message is honest about the asymmetry in the member's engagement pattern without framing the asymmetry as a problem. For reader members, the most common forward-question answer is a request for more content in a specific sub-topic, more access to a specific type of practitioner, or a specific programming format they have not seen yet. These answers are more useful to the operator than 'I want to contribute more' because they are honest descriptions of what the member actually wants, not aspirational descriptions of what they think a good community member should want. Reader members who receive an adapted acknowledgment message retain at a higher rate than reader members who receive nothing, primarily because the message is the first evidence many of them have ever received that the operator knows they are there.

Should the year-one acknowledgment message include an annual billing offer, or should that be a separate message?

The year-one acknowledgment message should not include an annual billing offer. The two serve different functions and introducing the billing offer into the acknowledgment message converts it into a retention pitch — which is precisely what makes it stop working. The acknowledgment message works because it is structurally disinterested: it does not ask the member to do anything that benefits the operator. It names something the member did, names something the member received, and asks what the member wants from year two. The forward question is the only ask, and it is the member's agenda entirely. Introducing an annual billing offer into this message changes its apparent purpose: the member reads the acknowledgment as the setup for a sales argument, which immediately reduces the credibility of the specific observations that preceded it ('the operator noticed my contribution because they were setting up a pitch, not because they were actually paying attention'). The timing that produces the highest annual billing conversion from the year-one cohort is a separate message sent approximately ten to fourteen days after the acknowledgment, referencing the conversation that the acknowledgment produced. If the member replied to the acknowledgment with something specific — described what they want from year two, named a problem they are still working on, mentioned a type of peer they want to connect with — the annual billing offer sent ten to fourteen days later can reference that specific reply: 'You mentioned two weeks ago that you want to go deeper on [specific topic] in year two — that's exactly what I want to build into the programming this year. The annual membership removes the monthly renewal decision from the equation and locks in the current rate; I wanted to offer it specifically to founding cohort members before the year-two price comes in.' This version works because it is a logical continuation of a specific conversation rather than a standalone offer. The member who agreed to continue engaging at the end of the acknowledgment message is in a materially different decision state than the member who received a cold annual billing offer at Day 195. The sequence — acknowledgment, specific reply, annual offer as a follow-on — consistently outperforms a single combined message because it creates two separate moments of engagement rather than one.

How do you send year-one acknowledgment messages when thirty or more members are hitting their first anniversary in the same month?

The year-one acknowledgment message does not scale in the way a newsletter or broadcast message scales. It scales in the way a Day-0 DM or a Day-75 renewal conversation scales: the template provides the structure, the operator fills in the specific observations, and the time per message is determined by how much the operator has been paying attention. For operators who have been watching their goal-track channels and running their weekly community review, the specific observation for each member takes two to four minutes to identify: scan the member's post history for a reply that produced follow-up, recall a live event where they contributed, identify a goal-track thread where they received substantive help. For operators who have not been maintaining that practice, it takes fifteen to twenty minutes per member because they are doing four months of retrospective observation in the moment. The practical threshold at which the year-one acknowledgment becomes a bandwidth problem is approximately thirty to forty members hitting their anniversary in the same month. At that volume, the operator faces a choice: (1) stagger the sends over two to three weeks, sending ten to fifteen per week; (2) identify which members in the cohort have the clearest observable contribution or value moment and send the full acknowledgment to those members, sending the adapted reader-member version to members with less visible engagement; or (3) delegate the specific observation research to a community manager or assistant if the community is at a scale where that role exists, with the operator writing the final DM from the research notes rather than doing the observation work from scratch. The stagger approach is the most common and the most effective: a member who receives their acknowledgment message one week into their anniversary month reads it as an individual message rather than as a mass campaign, because nothing else in that period has signaled to them that the operator sent the same message to thirty people on the same day. The acknowledgment's credibility depends entirely on its perceived individuality; the stagger preserves that perception without reducing the number of messages sent.

Paid community retention

Her founding-cohort members were hitting month twelve. She sent nothing. Eight of fifty cancelled in October and November. A peer with a comparable founding cohort had 2.3% year-one churn. The difference was one message. Named concept: the year-one acknowledgment.

Nkechi Adewale launched The B2B SaaS Customer Education Leaders Network in November 2024. Her first fifty members joined in October and November 2024. By November 2025 — month twelve — eight of them had cancelled in the preceding two months, a year-one monthly churn rate of 7.6%. She had sent nothing specifically to that cohort at their twelve-month mark. No anniversary message. No acknowledgment of the year. At a December 2025 operators roundtable, Folake Adesanya — running The B2B SaaS Revenue Enablement and Readiness Network ($119 per month, 280 members, $33,320 MRR, 2.2% monthly churn) — described a message she sent to every member at their twelve-month anniversary. Her founding-cohort year-one churn: 2.3%. Named concept: the year-one acknowledgment — a personal DM sent at the twelve-month mark that names one specific contribution the member made and one specific value moment they received, then asks one forward-looking question about year two, without making a retention argument. The acknowledgment works where a renewal pitch doesn’t because the member’s forward-commitment decision is answered by evidence from year one, not by the operator’s argument about year two.

The community at month twelve

Nkechi launched The B2B SaaS Customer Education Leaders Network in November 2024 — a paid Slack community for Customer Education Managers, Learning Experience Designers, Instructional Designers, and Heads of Customer Education at B2B SaaS companies with 500 or more customers. The community addressed the operational and strategic problems that surface when a B2B SaaS company’s customer education function matures past a one-person program into a team with multiple delivery formats, an internal stakeholder map, and pressure to demonstrate ROI: building curriculum that scales across onboarding cohorts without accumulating technical debt; designing modular content architectures that accommodate both self-paced and live delivery without maintaining two separate programs; measuring the relationship between customer education completion rates and product adoption, renewal likelihood, and support ticket volume; and navigating the internal positioning work required to maintain a customer education budget when the CFO is treating it as a line item without a clear revenue attribution. $99 per month.

By November 2025 (month twelve): 220 active members, $21,780 MRR. Bilateral activation — the share of all members who had ever joined and both posted and received a substantive reply from a peer they had not previously known, within their first seven days — was at 72%. Monthly churn was 3.3%. Both numbers were within the ranges she had been working toward since launch. The community had been growing steadily across the year: a combination of content traffic from blog posts she had been publishing since month three, referrals from active members, and conversions from a waitlist that had accumulated 190 leads by month ten.

What was not working was the founding cohort. The first fifty members had joined in October and November 2024 during her pre-launch and launch period. These were the members who had signed up earliest — people who had found the waitlist through her newsletter, through a Twitter thread she had written about customer education measurement, through word of mouth from the two or three community operators she knew personally before launch. They were the members who had experienced every version of the community: the channel structure before she restructured it in month three, the first three live events before she changed formats in month four, the original Day-0 DM and onboarding checklist before she switched to Foothold’s conditional routing in month five.

By October and November 2025 (months eleven and twelve), she had 42 of the original 50 still active. That was not unexpected — some founding cohort attrition over twelve months was normal. What was unexpected was the rate at which the remaining founding cohort members were cancelling: seven had cancelled in October and November combined, a 7.6% monthly churn rate among the founding cohort over that two-month window. The rest of the community was running 3.3% monthly. The founding cohort was running more than twice that.

What the founding cohort data said

She ran the analysis in late November 2025. When she segmented by tenure band — the tenure decomposition diagnostic she had read about in a December 2024 operators roundup — the shape was immediately visible: months one through three at 1.9% monthly; months four through six at 2.6% monthly; months seven through eleven at 4.1% monthly; founding cohort (months twelve and beyond) at 7.6% monthly. The founding cohort was the binding churn band. It was generating approximately 60% of her total monthly cancellations from less than 20% of her membership.

She had been treating the founding cohort as her most secure members. They had been around for twelve months. They knew the community well. They had seen it evolve. She had assumed that twelve months of continuous subscription represented twelve months of satisfied membership, and that satisfied members who had been around that long would continue by default. The data said otherwise. The founding cohort was not the most secure segment; it was the most at-risk.

When she looked at the exit DMs from the seven October and November cancellations, the pattern was not dissatisfaction. Five of seven said some version of “I’ve got a lot going on and I need to cut some subscriptions.” Two said they had moved into roles where the community’s focus was less directly relevant. None said the community was bad. None mentioned a specific programming failure or a negative experience. What they had in common was not a reason to leave but the absence of a specific reason to stay. After twelve months, the community had become part of their background infrastructure — something they were aware of without actively using — and when a subscription audit came, it was an easy line item to remove.

What most operators send at month twelve

Nkechi had not sent anything specific to the founding cohort at their twelve-month mark because she did not have a practice for doing so. Most paid community operators do not. The standard alternatives are: an automated Slack workspace anniversary notification (which is not an operator message and does not function as one), a generic “it’s been a great year” broadcast sent to all members simultaneously (which is functionally a newsletter, not an individual acknowledgment), or nothing.

Operators who do send something at the twelve-month mark typically send one of two things: a renewal pitch or an NPS survey. The renewal pitch is a Slack DM or email that makes an argument for continued membership — names a few highlights from the year, describes what is coming in year two, includes a link to the annual billing option or a discount code for one month free. The NPS survey is a request for a satisfaction rating, usually with a one-question format and an optional comment field.

Both fail at the same point: they confirm the operator’s agenda rather than the member’s value. The renewal pitch is visibly about retention — the operator wants the member to continue paying. The NPS survey is visibly about measurement — the operator wants a data point. Neither starts from the question the member is actually trying to answer at month twelve, which is not “is this operator trying to retain me?” but “has this community been worth it, and will it continue to be worth it for the next twelve months?” The renewal pitch and NPS survey are answers to different questions than the one the member is asking.

The year-one acknowledgment

At the December 2025 operators roundtable — a monthly virtual session for a loosely organized group of paid Slack community operators who had been meeting since the previous spring — Nkechi described her founding cohort problem. Folake Adesanya was in the same session. Folake had launched The B2B SaaS Revenue Enablement and Readiness Network in October 2024, one month before Nkechi. By December 2025 (month fourteen for Folake): 280 members, $33,320 MRR, 2.2% monthly churn, 73% annual billing conversion.

Folake asked how many of the founding cohort cancellations had come within thirty days of the member’s twelve-month anniversary. Nkechi went back and checked. Five of seven had cancelled within three weeks of the month in which they had originally joined. The founding cohort was not cancelling randomly across the year; they were cancelling at their renewal anniversary.

Folake described a practice she had started at month twelve of her own community — October 2025, one month earlier — after noticing the same founding-cohort elevation in her own tenure decomposition. She had read about the pattern in a peer forum and had decided to test a specific message at the year-one anniversary rather than wait to see whether the problem materialized in her own numbers. She called it the year-one acknowledgment: a personal DM sent to every member at their twelve-month mark that (1) named a specific contribution the member had made to the community, (2) named a specific value moment the community had delivered to that member that Folake had directly observed, and (3) asked one forward-looking question about what the member wanted from year two. No retention argument. No annual billing offer. No discount code. No NPS survey.

The structure of the message

Folake’s message had three components in a fixed sequence. The sequence mattered. Any reordering changed the apparent purpose of the message and reduced its effectiveness.

Component one: specific contribution observation. The first sentence or two named what the member had contributed. The standard is not the highest-volume contribution — the member who posted most frequently, the one with the most reactions. It is the contribution with the most specific observable impact on another community member. A reply in a goal-track channel that the original poster explicitly applied and followed up on three weeks later. An introduction in #intros that produced a DM exchange and a follow-up post. A live event moment where the member described a methodology and other members asked follow-up questions in the channel after the session. The specificity is what does the work. “Your contributions to the community have been genuinely valuable” is a performance of appreciation. “In April, you replied to Olumide’s question about onboarding academy certification pathways and he mentioned two weeks later that he had restructured his program design based on what you described” is evidence that the operator saw something specific.

Component two: specific value moment observed. The second section named something the community had delivered to the member that the operator had directly observed. Not “I hope you’ve been finding value here” — which is a hope, not an observation — but a named event: “The conversation you had with Taiwo in September about modular content architecture — the one where he shared the sequencing approach his team uses for reducing onboarding academy rebuild frequency — seemed to be the kind of thing you were describing when you said you were looking for peers who had already been through the scaling transition.” The member knows immediately that this is not a template because it names something that only they and the operator could both have seen. It demonstrates that the operator has been watching carefully enough to recall a specific exchange from month ten. That demonstration is itself the evidence the member needs for the forward-commitment evaluation: an operator who noticed this in October will notice things in March of next year. The community is run by someone who is paying attention.

Component three: one forward-looking question. The final element was a single question about year two. Not “are you going to renew?” Not “do you find the community valuable?” Those questions put the member in the position of either confirming the operator’s retention agenda or disappointing them. The question Folake used was: “What would make year two more valuable than year one for you?” This question presupposes continuation without asking for a commitment. It treats the member’s continued presence as the default and asks only what would make the default more worth having. Members who are genuinely satisfied answer it with specific programming requests, with types of peers they want to connect with, with formats they want more of. Members who are genuinely considering leaving answer it honestly — because the question is not asking them to justify staying, it is asking them what staying would need to look like. Both answers are more useful to the operator than a renewal pitch response.

Folake added an optional fourth element that she sent to approximately half of her anniversary messages: a referral ask embedded naturally after the forward question. “Is there a revenue enablement professional in your network who is working through the challenges you were tackling when you joined a year ago? I’d want to make the same kind of introduction for them that [peer name, if one was made in the first month] made for you.” The referral ask was conditional: she only included it when she had a genuine peer connection to reference, or when the member’s contribution observation named an expertise area that naturally implied a network of peers with similar problems.

Why the acknowledgment works where the retention pitch does not

Month twelve is the first fully conscious renewal evaluation most members make. The first eleven monthly renewals in a paid community are passive: the billing cycle fires, the payment clears, and the member continues. For many members, months two through eleven have not involved a deliberate decision to continue — they have involved the absence of a decision to cancel. Month twelve is different. Something about reaching a full year triggers a reflexive evaluation: I have been paying for this for a year. Has it been worth it? Will it be worth it for another year?

The forward-commitment question — will this be worth it for the next twelve months? — is answered by what the member can recall specifically about year one. Not by the operator’s characterization of year two. Not by a discount offer. The member who can recall two or three specific moments where the community delivered something concrete — a conversation that clarified a decision they had been stuck on, a peer who became a reference they still use, a live event that gave them a methodology they applied the following week — answers the forward-commitment question from evidence. The member who cannot recall anything specific, or whose most recent memory of the community is an automated newsletter, answers from optimism. Optimism-based forward commitments cancel at a materially higher rate than evidence-based ones.

The acknowledgment message does not make the case that the community is valuable. It surfaces specific evidence of value that the member may have experienced but not consciously retained as evidence. The member who received Taiwo’s modular architecture advice in September knows they had that conversation. What the acknowledgment does is name it back to them in a way that makes it retainable: now they have a specific, labeled moment to point to when they are answering the forward-commitment question. This is the mechanism. The acknowledgment does not create value; it makes experienced value legible at the moment when the member needs to describe it to themselves.

The referral chain at the year-one mark

The year-one acknowledgment creates a secondary effect that most operators who run it describe as unexpected: a significant portion of the members who receive it make a referral within thirty days, without being asked in most cases. The mechanism is straightforward once described: a member who has just had their specific contributions and received value moments named back to them has a fully articulate narrative for why the community is worth joining. They did not have this narrative before the acknowledgment — they knew the community was useful, but they could not necessarily describe to a peer what specifically made it useful for them. The acknowledgment does the work of crystallizing the narrative, and a crystallized narrative is exactly what a referral act requires.

The referral ask embedded in the acknowledgment message — when included — converts at a consistently higher rate than referral asks sent at other points in the member lifecycle. The referral timing gap concept names this: referral intent is highest when a member has just experienced something specific enough to describe to a peer. The acknowledgment message is not a high-value interaction in the sense of a peer connection or an expert response — it is a high-specificity moment for the member’s self-understanding of their own year. That specificity drives referral behavior in the same way that a peer connection that moved or an expert response with acknowledgment drives it: the member who has just had their year crystallized into two or three specific moments has those moments in the foreground of their thinking, which is exactly when “is there someone in your network who would benefit from the same kind of experience?” produces an immediate answer rather than an abstract evaluation.

Folake’s data across seven months of acknowledgment messages (October 2025 through April 2026): of 47 members who received an acknowledgment with the referral ask included, 29 named a specific prospect (62% named prospect rate). Of those 29, 23 prospects received operator-facilitated introductions, 18 of whom joined (78% join rate from named prospects). The 18 referral-cohort members from the acknowledgment period had a 90-day retention rate of 94% — the highest of any acquisition cohort she had tracked. The retention rate was consistent with the event-triggered referral pattern: members referred by a referring member who had just had a year of value crystallized arrive with a highly specific, evidence-based reason for joining.

Folake’s data across seven months

By April 2026, Folake had sent year-one acknowledgment messages to 68 members in total — everyone who had hit a twelve-month anniversary since October 2025. The aggregate results:

Reply rate: 89% (61 of 68). The reply rate was notably higher than any other Slack DM she sent, including the Day-75 renewal conversation (71% reply rate) and the Day-28 value-crystallization check-in (68% reply rate). The year-one acknowledgment generated the highest reply rate of any message in her member lifecycle sequence. Her explanation: the message asks a question that most people genuinely want to answer. “What would make year two more valuable than year one?” is an invitation to have a specific conversation about what the member wants — and most people, when invited to describe what they want from something they are already paying for, reply. It is not a retention pitch they need to deflect; it is a question they can answer honestly.

Year-one anniversary cohort monthly churn: 2.3% across all 68 members in the month following the acknowledgment message, compared to an estimated 7–9% for comparable communities without a specific year-one touchpoint (her own founding cohort was running 7.6% before she implemented the practice). The churn reduction persisted: the 68 anniversary-acknowledgment recipients were running 2.1% monthly churn in months thirteen through fifteen, compared to 3.9% for her cohorts that did not receive the message (pre-October 2025).

Annual billing conversion from anniversary cohort: 71% across all 68 members, measured as the share who converted to annual billing within sixty days of the acknowledgment message. This was not because the acknowledgment included an annual billing offer — it did not. It was because Folake sent a separate annual billing message ten to fourteen days after the acknowledgment, referencing the specific reply the member had made to the forward question. Members who had described what they wanted from year two were in a materially different state for receiving an annual billing offer: they had already agreed, implicitly, to have a year two. The offer removed the monthly renewal decision friction for members who had already made the continuation decision. Her overall annual billing conversion before implementing the acknowledgment: 44%. After seven months: 73%.

Nkechi’s January 2026 implementation

Nkechi sent her first batch of year-one acknowledgment messages in early January 2026 — one month late for the members who had hit their anniversary in November and December 2025. She sent messages to the 42 founding-cohort members still active after the October and November cancellations. The delay mattered, she found: the specificity of the value moment reference was slightly harder to make vivid when naming an exchange from September or October rather than from the prior two weeks. She adapted by using the most recent high-value interaction she could identify for each member rather than a year-one retrospective framing, and by making the lateness explicit in a few cases where the most recent interaction worth naming was more than four months old: “I’ve been meaning to say this since we passed the year mark last month — I wanted to wait until I had something specific to point to rather than a generic ‘thanks for a great year.’”

She spent the first week of January identifying the specific contribution observation and value moment for each of the 42 members. For 31 of them, this took two to four minutes per member: she knew her community well enough that scanning the member’s recent channel history surfaced a specific interaction without extended research. For eight members she was less certain about, the observation took ten to fifteen minutes to identify — members who had been in peripheral engagement for months four through twelve, whose most recent visible interaction worth naming was from month two or three. For three members she could not identify any specific contribution, and she sent the adapted reader-member version: an acknowledgment that they had been following the work in the community carefully without posting much, and a question about what they had been finding most useful.

She included the referral ask in 28 of the 42 messages — those where she had a specific peer connection or expertise area to reference. For the other 14, she omitted it, primarily because she did not have a natural referral frame that felt genuine rather than mechanical.

Reply rate: 87% (37 of 42). The three non-replies were all members she had already classified as elevated churn risk based on declining open rates and no channel activity in the prior eight weeks. Of the 37 who replied, 24 described a specific year-one value moment that the acknowledgment had surfaced — exchanges they remembered but had not retained as evidence for the forward-commitment question until the message named them. Eleven described a specific programming addition they wanted from year two. Nine said some version of “I hadn’t thought about whether this was worth renewing until you asked, and writing the answer helped me realize it is.”

Of the 28 messages that included the referral ask, 19 of 28 named a specific prospect (68%). Fourteen of those 19 prospects received outreach. Eleven joined in January and February 2026. The referral-cohort join rate — 79% from named prospects — was consistent with Folake’s data.

Results by April 2026

By April 2026 (month seventeen for Nkechi’s community): founding cohort monthly churn had dropped from 7.6% in October–November 2025 to 2.9% in January–February 2026, running at 2.4% by March–April 2026. Overall monthly churn had fallen from 3.3% to 2.4%. Annual billing conversion, which had been at 22% for her founding cohort before the acknowledgment, was at 54% by March 2026 — driven by the follow-on annual billing messages sent ten to fourteen days after the acknowledgment replies, referencing each member’s specific forward-question answer. For cohorts beyond the founding cohort, she had implemented the acknowledgment as a standard Foothold trigger at Day 365, and their annual billing conversion was tracking at 61% by April 2026.

MRR: $21,780 (220 members, November 2025) to $38,610 (390 members, April 2026). The growth came from two compounding sources: reduced churn from the founding cohort and subsequent anniversary cohorts, and the eleven referral-cohort new members from January–February plus ongoing referral activity from the founding cohort members who had named prospects in January. The founding cohort, which had been generating 60% of her total monthly cancellations in October and November 2025, was generating less than 10% of her total monthly cancellations by April 2026. The same forty-two people who had been her highest-churn segment were her highest-referral segment.

Nkechi described the secondary effect she had not anticipated at the December roundtable: the acknowledgment changed how she ran her community review. Because she knew she would be writing specific observations for every member at their anniversary, she started noting observable contribution and value moments in a running document during her weekly review — not for the acknowledgment specifically, but because noticing specific things became a practice rather than a task. By April 2026, she was running her community with a significantly clearer picture of which members were generating value for which other members, and which members were receiving value from whom. That picture was what made the member directory meaningful beyond its static profile data: she knew who was connected to whom, not from the directory, but from twelve months of paying attention.

Foothold’s Day 365 trigger, which she had not known existed when she sent her January 2026 messages manually, fired automatically for every member who hit their anniversary after February 2026, using the goal-track and engagement data from the member’s profile as the scaffolding for the specific observation. She still wrote the observations herself. The trigger just made sure she did not miss anyone. Start your free trial to see how the anniversary trigger works in practice.