The old agency handoff was a staging URL, a Figma file, and a Slack thread nobody wanted to reopen. Diginomica published a deep dive on September 9, 2026 that names the replacement: Webflow Source is not just another site builder. It is an agentic environment agencies are meant to stand up, configure, and leave running for the client after the retainer ends.
That is a different product than a website.
Webflow Conf 2026 already put the pieces on the table on September 2: Source in limited research preview, Campaigns in beta for brief-to-landing-page work, Assets for on-brand creative, MCP 2.1 for deeper agent access, Releases for whole-site branching, Agent Instructions generation, and Agent Presence on the canvas. Diginomica's read a week later is the operator translation. The commercial object is no longer "we built your site." It is "we configured the workspace your marketers and agents will keep shipping from."
If you buy or sell digital work, that shift changes the SOW, the exit criteria, and who owns the mess when an agent publishes something dumb on a Tuesday.
What actually shipped
Source connects a codebase and a martech stack into one shared operating environment. Marketers, designers, developers, and agents get Views tailored to the jobs they own. Code stays the foundation so agents can take larger changes without living inside a brittle abstraction layer. Existing Webflow sites and external tools can compose into that layer instead of forcing a rip-and-replace.
Campaigns is the performance marketer product in that stack. Share a live site URL. An agent pulls colors, fonts, and UI into a brand system even if the main site is not on Webflow. Submit a brief. The agent helps refine audience, message, and channel. Then it generates a primary landing page, variants by audience or keyword, and ad creative you can push toward channels like Google Ads. Once live, it tracks conversions, connects to HubSpot or Salesforce for pipeline signal, and recommends iterative page updates. Campaigns is in beta now, with purchase expected next month per Webflow's Conf write-up.
Assets sits next to that. Agents adapt approved creative across channels using design system and performance context, not a one-shot image prompt with no brand memory. Assets enters beta in October.
Around the agents themselves, Webflow is shipping the boring controls operators actually need. MCP 2.1 expands what Claude, ChatGPT, and Slack-connected agents can do inside Webflow: GSAP interactions, richer CMS querying, and Webflow Cloud deploy error logs surfaced to coding agents. Releases branches an entire site including pages, CMS, components, assets, and locales before anything merges. Agent Instructions can now be generated from what the site already knows about brand, design system, assets, and CMS rules. Agent Presence shows where an agent is working on the canvas the way a teammate cursor would.
Diginomica's September 9 piece leans hard into the agency angle: Source is positioned as the environment partners configure and hand over. That matches Linda Tong's Conf framing that "builder" now includes marketers and agents, not only designers and developers. The platform bet is that craft plus amplification wins once code itself is cheap.
The mechanism operators keep missing
Most teams will evaluate Source as "Webflow but with AI." That is the wrong unit of analysis.
The unit is the configured workspace: which Views exist, which Agent Instructions are locked, which MCP scopes are allowed, which Releases gates sit in front of production, which Campaigns brand system was derived from which URL, and which activity log proves who asked for what before publish.
That package is what an agency can actually deliver as a durable asset. A pretty homepage is not. Anyone with a model and a weekend can fake a pretty homepage. Almost nobody leaves behind a governed agent surface the client can keep running without calling the shop every time paid search needs a new LP.
Campaigns makes the commercial pressure obvious. Organic discovery is getting harder while paid and owned still need pages yesterday. Webflow's own Conf copy says campaigns often ship weeks late. The product answer is agents that compress brief to live in hours. Diginomica ties that to a broader industry story: agencies and in-house teams both need a place where that compression happens under brand and CRM constraints, not in a random chat sidebar that forgets context every session.
So the handoff question becomes: when the agency leaves, does the client inherit a workspace with instructions, permissions, and measurement wired, or do they inherit a site and a PDF of "how we used AI"?
Only one of those survives the first holiday campaign.
Where operators get this wrong
First mistake: buying the demo, not the exit. Source in research preview will look magical in a partner pitch. Ask what gets transferred. Who edits Agent Instructions after month six. Who owns the brand system Campaigns derived. Whether Releases and roles survive the contract. If the answer is vague, you bought a show, not an operating layer.
Second mistake: treating Campaigns like a creative toy. The dangerous part is not the generated LP. It is the silent drift when variants multiply, HubSpot fields map wrong, and nobody reviews the agent recommendations that keep "improving" conversion copy into claims legal never cleared. Speed without a review gate is just a faster way to ship liability.
Third mistake: agencies pricing like 2022. If your value was hours in Webflow Designer, Source and Campaigns compress that labor. The durable sell is configuration, governance, and ongoing optimization of the agent layer. Shops that keep selling page builds against clients who can generate pages will lose on price and still own the cleanup when an agent goes live unsupervised.
Fourth mistake: stacking identity theater on top of an empty instruction set. We already covered coworkers with logins earlier this month. Logins without Agent Instructions, Releases discipline, and a real activity review loop are just more keys on a ring. Diginomica's agency-handoff framing only works if the handoff includes those controls as first-class deliverables, not appendix screenshots.
Fifth mistake: ignoring AEO while chasing LP velocity. Webflow says the median company in their 2,000-site look showed up in 16% of the AI answers they cared about and got cited 6% of the time. Content agents that draft into CMS from competitor citation gaps are part of the same Conf wave. If your Source workspace can ship paid LPs in hours but your answer-engine presence is still a spreadsheet, you optimized the channel that invoices weekly and neglected the channel that shapes consideration before the click.
Second-order effects
Agency margins move from production toward systems design. The scarce skill becomes knowing which Views to stand up, which instructions to freeze, and which MCP scopes to refuse. Junior production hours get automated first. Senior operators who can certify a workspace for a regulated brand get more expensive.
Procurement language has to change. "Deliverables include homepage, five inner pages, and CMS training" is obsolete for this stack. You want acceptance criteria around instruction coverage, role maps, release policy, CRM field contracts for Campaigns, and a documented agent review ritual. Otherwise you accept a black box with a nice canvas.
Liability gets weird. When an agency-configured agent publishes a claim, who is on the hook: the model vendor, Webflow, the agency, or the brand that clicked approve? Source's Agent Presence and activity log are not cosmetics. They are the audit trail you will wish you had when legal asks what changed at 11:40 p.m.
Vendor lock-in also changes shape. Leaving a CMS hurts. Leaving a configured agent workspace with years of instructions, Views, and Campaigns history hurts more. That can be fine if the operating gains are real. It is not fine if you never negotiated export of instructions, brand systems, and activity history into something you control.
Competitors will copy the narrative even if they cannot copy the surface. Expect every major DX and CMS player to sell "agent workspace handoff" as a partner motion. Diginomica writing this up on September 9 is early proof the story already travels beyond Webflow's own blog.
What to do this week
If you are in-house:
- Inventory every place an agent can already touch web, CMS, or ads. Map that against what Source-style Views and instructions would centralize.
- Write a one-page Agent Instructions draft for brand claims, legal phrases, and CMS rules even if you never touch Webflow. The format travels.
- For the next paid campaign, force a human review gate on every agent-proposed LP and ad variant before push. Time how long review actually takes. That number is your real Campaigns throughput, not the demo clock.
- Ask your agency, in writing, what a Source-style handoff would include if you started tomorrow. Compare it to your last SOW.
If you run an agency:
- Rebuild one sample SOW around workspace configuration, not page count. Price the governance, not the pixels.
- Pick a single client pilot for Campaigns-style brief-to-LP with explicit review SLAs and CRM field contracts.
- Generate and version Agent Instructions the way you version design systems. Put them in the repo clients can keep.
- Train account leads to demo Agent Presence and Releases, not only pretty output. Buyers who care about risk will ask.
If you are evaluating Source in research preview:
- Score the vendor on export, roles, activity log fidelity, and how Campaigns talks to your CRM, not on one wow demo.
- Refuse a pilot that cannot name the human who approves agent publishes.
- Schedule the Diginomica-style question in the first meeting: are we buying a site, or a configured agent environment we still own in twelve months.
The close
Diginomica did the industry a favor on September 9 by saying the quiet part. Source is an agency delivery vehicle for an agentic operating environment, wrapped in Webflow's Conf launches from September 2. Campaigns, Assets, MCP 2.1, Releases, and Agent Instructions are not feature confetti. They are the parts list for that environment.
The operators who win will not be the ones who generate the most pages this quarter. They will be the ones who can hand a client, or an internal team, a workspace that still behaves after the kickoff energy dies.
Your next deliverable is not a URL. It is a configured agent workspace with instructions sharp enough that you are willing to put your name on whatever it ships next Tuesday.
