When a client host blocks bots, the migration workbench returns an unhelpful error and the team has no documented fallback, forcing manual workarounds that vary by person. · Seen in: 2026-06-12-0800-migration-workbench-intro-83Ga.md

A fly.io worker or n8n flow that detects a bot-block response during sitemap fetch, triggers a structured CSV intake form sent to the client via email, parses the returned CSV into the workbench schema, and posts a Slack notification to the project channel when the import is ready for review.

Extend the migration workbench's existing sitemap fetch logic with a bot-block detection branch. On detection, the tool renders an in-app banner with step-by-step instructions and triggers an n8n flow that emails the client a pre-filled CSV template with the required columns: page name, URL slug, title tag, meta description. When the client returns the CSV, the n8n flow parses it, validates the schema, and pushes the rows into the workbench via its existing API. The Ariba project is the first live test case and the CSV template columns are already known from the session.

Every enterprise client with bot-blocking hits this gap on the first sitemap fetch, and without a documented path the team improvises differently each time, creating inconsistent project starts that affect SEO handoff quality.

When a prospect's key decision-maker is not yet in role, the window between first contact and their onboarding closes before magier can get a tailored pitch in front of them. · Seen in: 2026-06-15-0800-sync-moritz-willy-mustafa-Ptb3.md

A Claude agent that accepts a call transcript and a prospect company URL, extracts the stated pain points and tech stack, and generates a one-page PDF brief tailored to the incoming decision-maker's domain, including relevant case studies, a positioning paragraph, and a suggested first-meeting agenda.

Build a /prospect-brief skill that takes a Granola transcript basename and a company URL as inputs. Claude extracts pain points, tech mentions, and decision-maker domain from the transcript, then firecrawl-searches the company site for additional context. The output is a structured markdown brief with four sections: their situation as heard, relevant magier case studies matched by industry and tech stack, a positioning paragraph for the decision-maker's domain, and a suggested agenda for the follow-up call. The brief is rendered as a PDF via a fly.io worker and posted to the relevant Slack sales channel. The Vays case is the first pilot: Niklas is CMO-domain, so the brief should lead with AI-augmented marketing and web, not design subscription.

The Vays deal is warm but structurally paused until Niklas signs, and the portfolio pack Willi committed to sending needs to land before the notary date, not after, or the first impression defaults to whatever the other pitches say.

Every new ebook or editorial deliverable requires a style definition round from scratch because magier has no reusable editorial layout system, consuming the buffer before copy even arrives. · Seen in: 2026-06-15-1202-weekly-telli-x-magier-FDOA.md, 2026-06-17-1259-george-x-willi-wbhs.md

A Claude agent that accepts a client brand profile JSON and a content type tag such as ebook or one-pager, generates two Figma-ready style frame specifications covering typography scale, grid, color application, and section templates, and posts them as a structured brief to the relevant Many Requests ticket before copy is received.

Build a /editorial-style-frame skill that reads the client brand profile JSON from the clients folder and a content-type parameter. Claude generates two style direction specs: one conservative applying the existing brand system directly, one more expressive pushing one brand element such as color or typography. Each spec includes: type scale, grid columns, primary and accent color usage rules, and three section templates described in enough detail for a designer to build in Figma without a reference call. The output posts as an internal ticket note in Many Requests. The Telli ebook is the first pilot since copy is arriving this week and the style gap is already blocking parallel work. The brand profile JSON infrastructure being built for the brand guidelines agent provides the shared input layer.

Telli has a hard Tuesday June 23 deadline for a 30-page ebook with no style precedent, and every day spent on style definition after copy arrives is a day removed from design execution time.

Team members are granting Claude connectors access to client Figma files and live websites before a data policy exists, creating untracked exposure that varies by individual judgment. · Seen in: 2026-06-17-0800-claude-basics-intro-eS0D.md

A Claude agent that runs as a weekly audit, reads the list of active Claude connector permissions across the team, flags any connector granted to a client-tagged project without a corresponding approved-use entry in the shadow IT rulebook, and posts a summary to a designated Slack channel for Willi and Gabriel to review.

Build a /connector-audit skill that reads a team-level connector registry maintained as a markdown file in the magier Claude folder, cross-references each entry against an approved-use list in the shadow IT rulebook, and generates a weekly diff showing new connectors added since the last audit, their granted scope, and whether they have rulebook coverage. The audit runs as a scheduled task in the Claude desktop app every Monday morning and posts to a private Slack channel. The approved-use list starts with the four interim rules Willi stated in the workshop and expands as the rulebook is built. The first run uses the connectors Alessa and Vincent already have active as the baseline.

The team is already using Claude on client work without guardrails and the rulebook does not exist yet, meaning every week without the audit is a week of untracked exposure that grows as more team members activate connectors after the workshop.

Multiple OTP projects stall for days waiting on client-side inputs such as copy approval, CMS content, or partner section details, with no automated follow-up and no visibility into how long each project has been blocked. · Seen in: 2026-06-16-0801-otp-pulse-check-jP0Y.md, 2026-06-12-0659-weekly-check-in-2QpM.md

An n8n workflow triggered by a Many Requests ticket status change to On Hold that starts a countdown, and if the ticket remains On Hold for more than 48 hours without a client reply, automatically sends a templated follow-up message to the client via the ticket activity feed and posts a Slack alert to the project manager.

Build an n8n flow triggered by the Many Requests webhook on status change to On Hold. The flow records the timestamp and sets a 48-hour timer. If no client activity is detected in the ticket within 48 hours, Claude drafts a follow-up message using the ticket title, the last PM comment, and a one-sentence prompt asking the client for the specific missing item. The draft posts as a pending message in the ticket activity feed for PM review before sending, not automatically to the client. A Slack notification goes to the assigned PM with a one-click approve-and-send button. JetBlend, DeliWell, and Lead and Security are all currently in this state and would have triggered this flow if it existed.

JetBlend was blocked for a week on clarification questions that had to route through Sina before reaching the client, and DeliWell is stalled on a script with slow client comms, meaning the cost of each day of delay is direct margin erosion on fixed-scope projects.