The Investor

The Convergence

Three events hit the creative software market simultaneously this week, and together they describe a structural break, not a temporary competitive blip. Adobe enters its customer summit down 30% YTD with CEO Shantanu Narayen departing — his worst possible exit timing. Canva launched AI 2.0, repositioning from design tool to the "visual execution layer" beneath every major AI assistant. And Claude Design demonstrated autonomous production-quality website generation, with an 18-minute tutorial by Viktor Oddy showing the capability is real, not vaporware.

The sell-side is noticing: BNP Paribas research described Canva's AI-powered design service as "beginning to rival Adobe's comprehensiveness." When sell-side analysts tell institutional clients that a private company matches the incumbent's product breadth, that's a procurement signal, not just a competitive note.

Canva's Data Moat Is Structural

The most investable detail from Canva's launch: its proprietary Design Model is trained not on final designs but on the actual sequence of edits — millions of design workflows capturing how humans iterate, refine, and decide. This edit-sequence data is structurally impossible to replicate without 265M+ monthly users generating it. Canva also uses a technique called "perturbation" — deliberately breaking designs to teach the model error recognition, enabling what they call "agentic editing."

CPO Cameron Adams confirmed that users don't care which model powers the tool — they want collaborative AI with control, not full automation. The copilot pattern wins; the autopilot pattern loses. This user behavior data should inform how you evaluate every AI application company's UX thesis.

The creative tools market just split into three layers: AI assistants handle ideation, a visual execution layer handles finishing and brand consistency, and professional tools handle precision. Adobe holds the third layer — the smallest and shrinking share of a much larger category.

The Three-Layer Architecture

Mike Krieger departing Figma's board after just 9 months to refocus on Anthropic is a revealed preference about where product value creation is migrating. The talent gravity has shifted.

Adobe's Compounding Problem

Adobe faces encirclement: Canva expanding up from prosumer, Claude Design pushing down from the AI layer, and no CEO to navigate. The summit (April 20-22) is the next catalyst — if AI announcements are incremental rather than transformative, expect another 10-15% drawdown. The barbell trade — short Adobe, long Canva pre-IPO — may be the highest-conviction pair in enterprise software right now.

Three Vectors of Compression

The AI application layer is being squeezed from three directions at once, and the timing is not coincidental — it reflects a structural phase change in where AI value accrues.

• From below (open-source): Alibaba's free Qwen3.6-35B-A3B outperformed Claude Opus 4.7 on spatial reasoning benchmarks while running as a 21GB quantized model on a MacBook Pro M5. A model you can run locally for free is beating a $25/million-token API on specific tasks.
• From within (hidden costs): Anthropic's new tokenizer may increase effective API costs by up to 35% depending on content mix. This won't show in published pricing — it's a silent COGS increase most portfolio companies won't catch until their next billing cycle.
• From above (platform expansion): Claude Design, HeyGen's open-source HyperFrames, and Canva AI 2.0 all eat into the application layer that startups built on top of foundation models.

Meta's $2B Manus Deal: The Definitive Comp

Meta paid ~$2B for Manus specifically for the agent harness technology — memory management, agent-to-agent protocols, skill orchestration, and compression infrastructure — not the underlying model. This is the clearest M&A price signal the market has produced for where AI value is migrating.

The harness architecture Meta acquired includes: Memory (working context, semantic knowledge, episodic experience), Skills (operational procedures, decision heuristics), and Protocols (agent-to-user, agent-to-agent, agent-to-tools). Between these sit sandboxing, observability, compression, and evaluation. Long-running agents routinely exceed token budgets, making compression a core unsolved infrastructure challenge.

Meta didn't pay $2B for a model — it paid for the harness around it. That single data point should reorder your entire AI infrastructure pipeline from model-first to orchestration-first.

The New Value Stack

The SaaS Existential Filter

Daniel Miessler's "fire of fires" framing is gaining traction among 1,500+ security practitioners who make enterprise buying decisions: if a SaaS product's core function can be replicated by an LLM plus a thin integration layer, it's on borrowed time. The filter is binary: does the company have proprietary data, network effects, or regulatory compliance requirements? Feature-layer tools (scheduling, forms, basic analytics) face critical substitution risk. Infrastructure platforms with scale economics and network effects — he specifically names Cloudflare — are consolidation beneficiaries.

The 950K+ AI practitioners absorbing the message that "using GPT or Claude out-of-the-box gives you zero competitive edge" accelerates this repricing as a self-fulfilling prophecy. Distribution, not model quality, is the emerging moat thesis — and it demands re-underwriting every AI deal in your pipeline.

Every CISO Sounds Defeated

Q1 2026 CISO conversations across RSA offsites, Slack channels, and practitioner networks reveal a universal pattern: every conversation ends on shadow AI, and every CISO sounds "a little defeated about it." Security controls for AI tiers are described as "wildly underfunded" — browser-layer DLP, agent inventory, ACL cleanup, and prompt injection testing don't make it into AI rollout budgets. The recommended fix: AI security needs its own budget line item with its own headcount.

That's not an operational recommendation — it's a TAM-creation event. When CISOs carve out dedicated budgets for a new category, it signals the same market-formation dynamics that created the cloud security category circa 2015. The parallels are precise: new technology adoption outpacing security tooling by years, CISOs acknowledging they're behind, and budgets being created from scratch.

Four Distinct Investable Vectors

Critically, blanket blocking drives usage underground — onto phones, personal devices, mobile hotspots. Organizations treating Copilot rollout like previous SaaS rollouts without adversarial testing are creating breach conditions. Most organizations find significantly more AI surface area than the CISO expected on first scan.

The Adjacent Structural Shift: VPN Appliances Are Being Eliminated

Five major vendors — Ivanti, Fortinet, Palo Alto, Cisco, F5 — have all shipped critical auth-bypass or RCE chains in their edge appliances in the last 24 months. The vulnerability class is architectural, not incidental — management interfaces built on CGI scripts and PHP with bugs baked into the codebase. The CISO recommendation has shifted from "patch faster" to "eliminate the appliance." That's a leading indicator of revenue decline at these vendors and structural tailwind for ZTNA providers (Zscaler, Cloudflare, Netskope).

Shadow AI security is the biggest greenfield category in cybersecurity since cloud security — CISOs are creating dedicated budgets, no vendor owns it, and the 12-18 month window to back category leaders is open now.

Portfolio Defense Implications

This isn't just deal flow intelligence — it's direct portfolio risk. If your portfolio companies are rolling out Microsoft Copilot without ACL cleanup, they're creating "a self-inflicted breach." If developers use AI coding assistants without private package namespace controls, they're exposed to automated supply chain compromise — AI coding assistants hallucinating package names that attackers actively squat on. A breach at a portfolio company from any of these vectors is both a reputational and valuation event. The Johns Hopkins ManyIH research showing frontier models fail at multi-tier privilege resolution adds an unresolved technical layer to this risk.