There is a wine club member at every winery who used to order every quarter, and then stopped, and nobody noticed for nine months. They did not unsubscribe. They did not complain. They just stopped. By the time the DTC manager runs a CRM report and sees the lapsed segment, the member is six months past the threshold where a personal note would have brought them back. Nobody dropped the ball on purpose. The ball was never being watched.
The Connector agent is the one that watches the ball. Every Sunday evening, it reads your CRM, flags the contacts who have gone quiet against the cadence you set, drafts a personal note in your voice for each one, and surfaces the networking opportunities for the week ahead. It also builds the content calendar that the Speechwriter writes against every morning. Nobody important goes quiet without you knowing.
This is the per-agent breakdown for the Connector in the Agent OS Webinar series. Week six of the 90-day install order. It comes after the Researcher, Speechwriter, Personal CFO, Executive Assistant, and Chief of Staff because the relationship work needs the most context to do well, and the upstream agents have spent five weeks building that context.
What the Connector reads (Inputs)
Five categories of input. The Connector is one of the most data-hungry agents because relationships are personal and local.
- Your calendar, past 90 days. Who you met with, who you missed, where you spent your time. The Connector sees patterns in your real time allocation, not in the time allocation you claim.
- Your contact and people notes. The Rolodex. Names, roles, last touchpoints, what they care about, the last 4 to 8 substantive interactions. The richer the notes, the better the agent.
- Customer activity data. Order history. Wine club status. Last contact date. Subscription tier. Net lifetime value. Any other behavioral signal your CRM tracks.
- Industry event calendars. Distributor conferences, wholesale summits, trade events, regional shows. The Connector uses these to spot networking opportunities you should be planning for.
- Your stated 30/60/90 day relationship goals. A document you write once a quarter, listing what relationships you want to deepen, what new ones you want to build, what business outcomes those relationships connect to.
The 30/60/90 doc is the input most winery leaders skip. The Connector cannot do networking strategy without knowing what you are trying to build. Without the goals doc, the agent is just a Sunday-night reminder service.
What it does with that material (Skills)
Five skills, each one more strategic than the last.
- Cadence tracking. For each named contact, the agent knows the right cadence for that relationship and watches the calendar against it. A wholesale buyer is a quarterly check-in. A key journalist is a monthly note. Your sister-in-law who runs a similar operation is the every-six-weeks coffee. Each cadence is set by you; the agent watches it.
- Quiet-contact detection. When a contact has been quiet past their cadence threshold, the agent flags them in the Sunday note. The flag includes a draft personal note in your voice. You read, edit, send. Five minutes for ten quiet contacts.
- Customer dormancy detection. Same logic, applied to your customer database. Wine club members who used to order and stopped. Top-decile lifetime-value customers who have not touched the brand in 90 days. The Connector surfaces them with one or two angles for re-engagement.
- Networking-opportunity surfacing. Upcoming industry events relevant to your 30/60/90 goals. For each event, the agent proposes who to introduce yourself to, what dossier the Researcher should prepare in advance, and what content the Speechwriter should be writing in the weeks leading up.
- Content calendar construction. Once a month, the Connector and the Speechwriter sit down together, figuratively, and draft the next month's content calendar. Which audiences to target on which days, which themes to run, which campaigns to align with the upcoming events on the calendar. The Speechwriter then writes against that calendar every morning.
What the Connector is not is a marketing automation tool. It does not send the email. It does not enroll anyone in a campaign. It writes drafts and proposes plans. You decide which ones ship.
The schedule (Scheduled Tasks)
The Connector runs on a weekly cadence with monthly and quarterly tasks layered on.
- Sunday 7:00 PM weekly. The relationships scan. Quiet contacts, customer dormancy, upcoming events for the week. One Sunday note in your daily folder by 7:30, with drafts attached for the quiet contacts.
- Monthly first-of-the-month, with the Speechwriter. Next month's content calendar. One document, ready before the first.
- Quarterly, end of the quarter. A 30/60/90 refresh. The agent reviews what landed and what slipped from the last quarter's goals doc, drafts the next quarter, surfaces relationships to add or remove.
- Event-triggered. When a relevant industry event lands on the calendar, the Connector creates a project file with the people to introduce yourself to, the dossiers to request from the Researcher, and the outreach drafts to write in the weeks before.
The Sunday cadence matters. Most GMs try to do networking during the week, when there is always something more urgent. Sunday evening is the one window when the relationship work is not competing with operational fires. Anchor the Connector there.
What lands on your desk (Outputs)
Three outputs, all consolidated in places your other agents already use.
- The Sunday note. Who got time this week, who did not, who is past cadence. Drafts attached for the quiet contacts. Customer dormancy flags with proposed angles. One document, in your daily folder, by Sunday 7:30 PM.
- The monthly content calendar. A markdown table or doc covering four weeks of content, by day, with audience targeting and theme arc. Sits in your content folder; the Speechwriter reads it every morning.
- The 30/60/90 roadmap. Updated quarterly. A working document that names the relationships you are building, the goals they connect to, and the cadence each one is on.
Nothing autonomous goes out. The agent drafts, surfaces, proposes. You decide and send.
The goal: nobody important goes quiet, networking on purpose
The Connector exists for two outcomes that connect. Nobody you care about goes quiet without you knowing. Your network grows on purpose, against goals you set, instead of by accident.
The second-order effect is sharp. Winery leaders with a Connector running for six months report a different relationship to time. The dormant wine club member you would have noticed six months too late is now in front of you on the Sunday she crosses 90 days quiet, with a draft note ready to send. The networking event you would have walked into cold is one you walk into with a plan, dossiers, and three names already on the call sheet. The relationships you said you wanted to build six months ago are the ones you built, because the agent kept surfacing them in the Sunday note until you did the work.
A worked example at Not Really Wines
At Not Really Wines, our fictional demo winery at NunnCurtis Labs, Jordan Miyake handles wholesale and on-premise. NRW makes premium non-alcoholic wine, vacuum-distilled from Sonoma fruit, and works with about thirty wholesale accounts across Sonoma and the East Bay. Jordan's 90-day goal this quarter is to grow wholesale in Oregon, where NRW currently has zero placements.
On a Friday in late spring, the Connector flags an industry event on the calendar. A wholesale-buyer summit in Portland in six weeks. Within an hour of the flag, a project file appears in Jordan's vault:
Project: Portland Wholesale Summit, June 12–14. Goal: 5 new buyer introductions in Oregon, two of which lead to follow-up tastings.
Buyers to target (pulled from event attendee list cross-referenced with your 30/60/90 goals): five names, with role, employer, prior contact with NRW, and the angle that would matter to each one — natural-wine focus, non-alcoholic category curiosity, restaurant-list compatibility, distributor relationship.
Pre-event dossiers (request from Researcher): For each of the five names, the last six months of their published content, the wines they have listed, the press they have done, the buyers they are connected to. Dossiers due June 5.
Outreach drafts (request from Speechwriter): For each name, a 100-word LinkedIn DM or email in Jordan's voice, sent the week before the event, asking for a 15-minute meeting at the summit. Drafts due May 29.
Content alignment (note for Speechwriter): Two LinkedIn posts in the two weeks before the summit, both about NRW's wholesale story and the non-alcoholic category opportunity for restaurant lists. The summit attendees should see Jordan's voice in their feed before he sends the cold DM.
Jordan opens the project file on Friday afternoon. He spends 20 minutes reviewing the five names and confirms or substitutes. The dossiers arrive from the Researcher by June 5. The outreach drafts arrive from the Speechwriter by May 29. By the time Jordan flies to Portland on June 11, he has done one hour of high-leverage editing, not 30 hours of low-leverage research. He walks into the summit with five planned conversations, two of which become follow-up tastings within a month.
The Connector did not make any of the decisions. It surfaced the opportunity early enough that the work was possible, sequenced the request to the other agents, and assembled the project plan. Jordan brought the judgment.
How the Connector demonstrates Interview
The Connector is the strongest example in the shadow team of the Interview teaching move. The agent interviews your CRM, your calendar, your 30/60/90 doc, and surfaces the questions you would not have surfaced for yourself.
Three of those questions show up in every Sunday note:
- Who, on your priority contact list, has been quiet longer than the cadence you set?
- Which top-decile lifetime-value customers have not touched the brand recently enough to count as engaged?
- What is coming up on the calendar in the next 30 days that connects to a stated relationship goal but is not yet planned for?
You did not ask the agent these questions. The agent asked them, against your data, and put the answers in front of you in time to act.
Why this is week six of the install order
The Connector comes sixth because relationship work is the most context-hungry of the agents. The Connector needs the Researcher for pre-event dossiers, the Speechwriter for outreach drafts, and the Executive Assistant for the recent inbox and calendar context. Build the Connector first and the agent has none of those upstream inputs. Build it sixth and it inherits five weeks of compounding context.
Two more reasons:
- The 30/60/90 doc is the hardest input to get right, and CEOs who have lived with the other agents for five weeks have already practiced the kind of structured-document writing the goals doc demands.
- The Connector's outputs are the most strategic in the shadow team. Putting it in week six means the CEO has built enough trust in the system to treat the Sunday note as a working artifact rather than another inbox to ignore.
Build this one in week six. The webinar recording and the rest of the Agent OS series live at nunncurtislabs.com/webinars.