When a developer resigns mid-project, critical project context including CMS architecture decisions, locale configurations, and component library rationale exists only in the departing developer's head, requiring manual reconstruction before the replacement can start. · Seen in: 2026-09-14-1012-sina-plancraft-besprechen-JqSi.md, 2026-09-15-0700-alignment-timeline-and-scope-related-l8Zx.md

A Claude agent triggered when a developer's last-day date is entered into the HR or project management system that reads all open project tickets assigned to that developer, extracts the CMS structure docs, Figma file links, and any Webflow MCP session logs, and generates a structured handover brief covering architecture decisions, known risks, and open dependencies.

Build a /dev-handover-brief skill that accepts a developer name and a list of active project IDs. The skill queries the ticket system for all open and in-progress tickets assigned to that developer, pulls linked Figma files and any attached architecture docs, and passes them to Claude with a prompt structured around four sections: CMS decisions made and why, locale and component library setup, known technical risks, and open questions for the replacement. The output is a Notion or Google Doc draft posted to the project channel with a checklist of items the departing developer must confirm before their last day. Wire a trigger into the HR offboarding flow so the brief is generated automatically when a last-day date is set.

Cam's last day is 14 October and the PlanCraft KW44 development start requires the replacement to understand a multi-locale CMS architecture that has not been documented; every day without a handover brief is a day the replacement starts cold on a €70K fixed-price project.

Clients who migrate their website to an AI-native builder like Lovable or internalize design at a C-level decision remove the Webflow dependency before Magier has any signal that the account is at risk, making the cancellation call the first warning. · Seen in: 2026-09-15-1201-weekly-telli-x-magier-LiLq.md

An n8n workflow that monitors subscription client LinkedIn pages and job boards weekly for signals of new engineering or design hires, new tool mentions in company updates, or job postings for in-house Webflow or design roles, and posts a churn-risk flag to the PM's Slack with the signal source and a suggested retention action.

Build a /churn-signal-monitor skill that runs weekly for all active subscription clients. The skill uses a Phantombuster LinkedIn scraper to check each client's company page for new hires in engineering or design roles and a job board API to check for open Webflow or design positions. Claude reads the signals and scores each client on a three-level churn-risk scale based on company size, subscription tenure, and signal type. Clients flagged as medium or high risk get a Slack card to the PM with the specific signal and a one-line suggested retention action such as scheduling a brand-system review call or proposing a design-system deliverable. Run the monitor every Monday morning before the weekly check-in.

Telli's cancellation was a C-level decision that Lorenzo had no advance signal of; with churn at 9.26 against a target of 8, one more undetected platform migration churn in the next quarter keeps the OKR in red.

When Max or Willi enters an enterprise Webflow deal negotiation, the Marketing Development Fund parameters and historical deal structures exist only in Willi's memory, requiring a manual ask before each negotiation and creating a delay when the sales rep needs the information before a client meeting. · Seen in: 2026-09-11-1107-julian-x-max-J2HO.md

A Claude agent that maintains a structured MDF deal log and generates a one-page deal brief on demand, covering the MDF ceiling for the current quarter, the last three deal structures where MDF was used, and a suggested negotiation framing for the specific prospect's company size and brand count.

Build a /mdf-deal-brief skill that reads a structured MDF log stored in Notion or a Google Sheet containing past deal amounts, conditions, and outcomes. When triggered with a prospect name and deal size, Claude generates a one-page brief with the current MDF ceiling, the closest comparable past deal, and a three-bullet negotiation framing tailored to the prospect profile. Willi populates the log with the last five deals in a one-hour session; after that, the log is updated by the sales rep after each deal closes. The skill is triggered via a Slack slash command so Max can call it from his phone before a client call. Seed with the Dr. Wolff Group as the first live use case.

Max is meeting the Webflow London team in two weeks and needs the MDF parameters before that meeting to position Dr. Wolff as a flagship European deal; without the brief, the negotiation lever is unused and the in-person client conversations OKR stays at 2 of 10.

Subscription clients with event-driven demand spikes open multiple high-priority tickets simultaneously, but the current subscription model has no mechanism to estimate whether the team can absorb the parallel load before the client commits to a timeline, leading to either missed SLAs or reactive hourly package upsells. · Seen in: 2026-09-14-1200-famedly-x-magier-fg5r.md, 2026-09-14-1029-keeunit-x-magier-check-in-oFEE.md

An n8n workflow triggered when a subscription client opens more than two tickets in a 48-hour window that reads the current team capacity from the ticket system, estimates the parallel delivery timeline based on ticket complexity tags, and posts a capacity card to the PM with a recommended response: absorb within subscription, suggest hourly top-up, or flag to Willi for a package conversation.

Build a /parallel-capacity-check skill that accepts a client ID and a list of open ticket IDs. The skill reads each ticket's complexity tag and the current designer and developer availability from the ticket system, then uses Claude to estimate whether the tickets can be delivered in parallel within the subscription SLA or whether a top-up is needed. The output is a Slack card to the PM with three options pre-drafted: a message to the client confirming delivery within subscription, a message proposing an hourly top-up with a price, or an escalation flag to Willi. Wire the trigger to fire automatically when a client's open ticket count crosses two within 48 hours. Use Famedly and keeunit as the first two pilot accounts since both surfaced the parallel-load constraint this week.

Famedly's peak is October and the ad-hoc 40-hour package was sold reactively after the client named the problem on the call; if the capacity check had fired when the second ticket opened, the upsell conversation would have happened before the client felt the friction.

When a new company is added to a directory by scraping, there is no automated workflow to notify the responsible person at that company, claim their profile, and route them into a warm sales sequence, requiring manual outreach for each of the hundreds of companies in the directory. · Seen in: 2026-09-15-1330-marc-andrew-and-maximilian-fleitmann-s6EN.md

An n8n workflow that runs after each batch of new companies is added to the Private Markets Forum directory, uses Apollo or Hunter to find the most likely marketing or growth contact at each company, sends a templated profile-claim email, and on claim submission routes the contact into a tiered outreach sequence with a Slack notification to Max or Whitley including the company's estimated sponsor tier.

Build a /directory-claim-router skill that accepts a list of newly added company names and domains. The skill queries Apollo for the most likely marketing or growth contact at each company, generates a personalized claim email using Claude with the company name and a one-line description of the directory's audience, and queues the emails in a sending tool such as Instantly or Lemlist. On form submission, Claude reads the company profile and assigns a sponsor tier based on company size, funding stage, and category, then posts a Slack card to Whitley and Max with the tier, the contact name, and a suggested first sales message. Wire the trigger to the directory CMS so it fires automatically when new companies are published. Seed with the first 50 companies Valeria has already added to the PMF directory.

Max described this exact playbook as the mechanism that generated warm inbound leads for VC Stack without cold outreach, and Marc confirmed the PMF directory is live and growing now; every week without the claim sequence is a week of warm leads going cold.