My Webflow Scope Ledger: What I Added and Removed This Week

The week of May 19 through 22, 2026 carried five meaningful announcements: Webflow Code Embed props on May 19, Webflow Gemini-based Localization on May 20, OpenAI's C2PA and SynthID launch on May 20, Webflow AEO GA on May 21 alongside the Google Core Update at 8:43 AM Pacific Time, and Anthropic's Project Glasswing initial update on May 22. That is a dense week even by 2026 standards.

This is a first-person reflection on what I am adding to my Phoenix Studio retainer scope and what I am removing as a direct result of these announcements. It is structured as a scope ledger: one entry per change, with the reasoning. The pattern is intentional because retainer scope discipline is how a solo Webflow Partner stays profitable through churn.

What Changed in the Week of May 19-22 That Actually Affects Scope?

Five things at the scope level. AEO GA changes what I offer Enterprise clients. Code Embed props change my implementation patterns. Glasswing changes security expectations for B2B SaaS. The Core Update changes SEO reporting cadence through June 4. Gemini Localization changes my multilingual recommendation defaults. Each entry below is one of those five.

The discipline I am applying is one in, one out. Every retainer scope addition needs a matching removal. That keeps the scope honest and the retainer hours predictable. Without the discipline, retainer scope drifts upward over months without the price moving, and the Partner ends up subsidising the client. I learned that lesson in 2022. It still holds.

Why Am I Adding AEO Phase Zero Audit to Every New Retainer This Week?

AEO GA on Webflow Enterprise creates a concrete deliverable I can ship that did not exist last week. The AEO Phase Zero audit is a 30-day measurement-only run that establishes a baseline citation footprint across ChatGPT, Gemini, Perplexity, and Claude. It is six hours of scoped work and produces a deliverable retainer clients can actually use.

The reason it goes on every new retainer is the baseline matters for any subsequent AEO work. Without a baseline, every later citation report is impossible to interpret. I covered the AEO GA detail in my AEO GA read. The Phase Zero audit ties into that framework directly without creating a new vendor relationship.

Why Am I Removing Ad-Hoc Copy Generation From My Scope?

Webflow AI credits make copy generation table stakes for any Premium-or-above client. There is no longer scope-worthy value in me writing one-off copy variants when the client's own Webflow Designer can generate them in the editor. Removing this from scope frees four to six retainer hours a month per client to reallocate to higher-leverage work.

The replacement is editorial review and brand voice consistency, which the client cannot do themselves. That keeps me in the value chain on copy without trying to compete with a built-in feature. Retainer clients prefer the new framing because it positions me as the senior reviewer rather than the junior generator. The hourly value goes up.

What Is My Position on Whether AEO GA Justifies the Enterprise Jump?

For most Series A and early Series B B2B SaaS clients, no. AEO alone does not justify the Enterprise pricing gap from Premium or Team. The justification requires data residency, dedicated support, or named-region hosting on top. The exception is clients already evaluating Enterprise for other reasons, where AEO becomes a real line item that previously did not exist.

I am telling three retainer clients explicitly this week that they should not upgrade just for AEO. That is a counter-revenue recommendation because Webflow Partner commissions improve on Enterprise upsells. The Partner integrity argument is the recommendation is genuinely correct for those three. The commission would be short-term revenue and long-term reputation cost.

How Do I Read the Glasswing 10,000 Vulnerability Update as a Marketing-Site Partner?

As a credible reason to add a security advisory page to every B2B SaaS retainer's scope. Glasswing changes the disclosure expectations for downstream vendors, which includes any SaaS marketing site that depends on third-party scripts. A public security advisory page demonstrates procurement maturity at low build cost and high credibility yield.

The Phoenix Studio scope addition is one new CMS Collection, a hub page, and a footer link, plus a documented monthly review cadence. Total build effort is four to six hours. The retainer scope addition is the monthly review at one hour. That is a small but meaningful expansion of the work I do. The patterns I covered in my Glasswing piece describe the deliverable in full.

Am I Shipping Code Embed Prop Refactors as a Paid SOW or a Free Upgrade?

Free upgrade for retainer clients. The Code Embed prop refactor is a 30-minute win per cluster of repeated embeds and the cumulative time saved by the maintenance reduction pays back the upgrade work within the first sprint after. Charging for it would be the kind of nickel-and-dime move that costs trust over months.

For non-retainer clients who ask about it, the refactor is a paid SOW. The pricing difference is not the work, it is the relationship. Retainer clients get the upgrade because the retainer is built on shared upside. Project clients get the SOW because we have no shared upside. The same pattern applies to every product update of similar magnitude.

When Do I Tell a B2B SaaS Founder to Wait on the May 2026 Core Update Fallout?

Until June 4 at the earliest. The Core Update rollout window goes through June 4 and any structural changes before then risk fighting the algorithm rather than working with it. The honest framing for retainer clients is the next two weeks are observation weeks, not action weeks. That holds even when the dashboard shows scary numbers.

The exception is forensic audit on individual pages that drop out of top ten on primary queries after Day 10, which I covered in my Core Update action plan. Page-level investigation after Day 10 is fine. Site-wide restructuring before Day 14 is not. The discipline of waiting is the high-leverage move.

Why I Am Still Skeptical About Generative Video for B2B SaaS Heroes

Generative video looks impressive in demos and falls apart on close inspection at hero scale. The B2B SaaS buyer who watches your hero video on a 27-inch display sees the artifacts in skin texture, hand positions, and lip sync that demos hide. Brand trust costs more to rebuild than the cost of human-shot footage.

The exception is ambient background video where motion is the message and detail is irrelevant. For those, Kling 3.0 and Runway are now genuinely good enough. For featured customer testimonials, product demos, or founder talks, the answer remains human footage with conservative editing. My take has not moved with the May releases. The output quality has improved. The buyer scrutiny has improved more.

What I Am Telling Bengaluru-Based Founders About DPDP Phase II

Start the consent stack build in July. November 13 is six months out and the build takes two to three months to design and ship cleanly. Founders who start in October will be late. Founders who start in July will have time for one round of iteration based on the accredited Consent Manager list, which will stabilise through Q3.

The specific recommendation for Bengaluru-based SaaS is to staff the Phase II work with local Indian counsel rather than imported templates. The DPDP Rules have India-specific subtleties around consent withdrawal mechanisms and Privacy Notice translation that templated solutions from US or EU vendors do not handle well. I covered the broader timeline in my DPDP Phase II piece.

The One Thing I Would Do Differently If I Started a Webflow Practice in May 2026

I would build the security advisory page muscle from day one. In 2024 I treated security as a Q3 concern for any retainer client. Glasswing makes it a Q1 concern. A Webflow Partner who can credibly demonstrate security maturity to a Series B procurement team has a real edge over Partners still pitching fast pretty sites.

The corollary is I would specialize harder. Security advisory pages, AEO Phase Zero audits, and DPDP Phase II consent builds are three deliverables that did not exist as scope items eighteen months ago. Each one is a credible specialization that compounds. The generalist Webflow Partner is getting squeezed from both ends. The specialist who picks two or three named deliverables has the leverage. That is the move I am making this quarter.

If you want a Phoenix Studio scoping conversation on which scope changes from this week actually apply to your specific stack, drop me a line. Let's chat.