Your Buyer’s AI Is Pitching YOUR Product (Badly) | Adrian Rosenkranz, CRO @ Webflow

Key Takeaways

• AI tools boost efficiency but reduce reps’ customer time
• 20% of Webflow traffic now originates from AI bots
• Centralized GTM engineering prevents fragmented AI hacks
• Narrative‑driven enablement outperforms feature‑by‑feature training
• Living markdown knowledge bases power AI agents with fresh context

Pulse Analysis

The surge of AI‑powered workflows inside revenue teams has created what Adrian Rosenkranz calls the “efficiency trap.” Managers showcase custom call‑prep bots, yet the key metric—more time with customers—often falls. By turning senior salespeople into part‑time rev‑ops engineers, firms sacrifice the human interaction that drives deals. Rosenkranz’s fix is a structural re‑org: merge marketing, sales, post‑sales and rev‑ops into a single GTM engineering group that builds cross‑functional agents, while keeping reps focused on conversations. This restores alignment and ties AI spend to real revenue outcomes.

Simultaneously, the external discovery layer is being rewritten by large language models. Webflow reports AI bot traffic rising from under 1 % to nearly 20 % of visits, with 43 % acting as live agents for human buyers. This “agent experience optimization” (AEO) replaces SEO clicks with citations inside LLM responses. Companies must treat LLM visibility like search rankings—optimizing schema markup, markdown content, and structured metadata so agents retrieve accurate pages. Ignoring AEO means disappearing from the primary source of B2B buyer information.

The final piece is a living knowledge base that feeds every AI agent with fresh context. Instead of static decks, Rosenkranz builds weekly‑refreshing markdown files that combine deal data, call transcripts, and market insights, serving as ground truth for coaching, ICP, and objection‑handling bots. Paired with a strong strategic narrative, this dynamic content turns context into a moat, while walled‑garden tools that hoard data become liabilities. CROs should centralize AI engineering, monitor AEO performance, and replace stale documents with self‑updating knowledge files to keep reps on the phone.