Comet Browser by Perplexity AI vs Zapier Agents

“The category is agentic browser automation — direct competitors are Anthropic's Computer Use, OpenAI Operator, and Arc's now-shelved Browse for Me, all of which have demonstrated the same core loop and hit the same walls: form auth, CAPTCHAs, and any site that detects non-human behavior. Comet breaks the moment a user wants it to handle a logged-in, dynamic SPA that rate-limits bots — which is most of the web that matters. What kills this in 12 months: OpenAI ships Operator to all ChatGPT users for free and Perplexity's differentiation collapses to brand preference. To earn a ship, Comet needs to demonstrate persistent session handling and a credible story for the 60% of high-value tasks that live behind auth walls.”

“The direct competitors here are Make (Integromat), n8n, and any engineer with a Claude MCP config and a few Composio or Nango connectors — and those alternatives don't charge you Zapier's per-task pricing at scale. The scenario where this breaks: any workflow that runs more than a few hundred times a month, where Zapier's task-based billing turns a 'simple' agent into a line item that triggers a procurement conversation. The thing that kills this in 12 months isn't a competitor — it's OpenAI or Anthropic shipping native tool-use registries that make the MCP middleman redundant, combined with Zapier's pricing model failing contact with power users who benchmark it against n8n self-hosted. To earn a ship, Zapier needs to show task economics that don't penalize success.”

“The thesis here is specific and falsifiable: by 2027, the browser tab is no longer a viewport you stare at — it's a task queue you delegate to. Comet is betting that the interface layer between humans and the web collapses from 'navigate and click' to 'state intent and verify result.' That's a real trajectory, and Perplexity is one of the few players with a live search index plus the intent-capture surface to make the delegation model feel natural rather than scripted. The second-order effect that matters: if Comet works, SEO as a discipline dies faster than anyone is modeling — the bot reads the page so the human doesn't, and click-through becomes irrelevant. The dependency that has to hold: users must be willing to hand over ambient browsing context to Perplexity's servers, which is a trust bet that sits on regulatory quicksand. Still, as a positioned bet on the trend of intent-first computing, this is early and credible rather than late and derivative.”

“The thesis here is falsifiable: within 3 years, MCP becomes the dominant protocol for AI-to-tool communication, and the entity that controls the most trusted, pre-authenticated MCP action surface wins disproportionate agent traffic — Zapier is betting it's them. What has to go right: MCP adoption accelerates in AI clients (Claude, Cursor, Copilot), and enterprises don't rebuild their own connector layers. What has to not happen: a well-funded open-source alternative (n8n already exists) commoditizes the connector layer before Zapier can lock in agent workflows as a habit. The second-order effect that's underappreciated: if Zapier's MCP server becomes the default tool-use layer for hosted AI clients, Zapier gains visibility into agent behavior at massive scale — that's a data asset for model fine-tuning and pricing intelligence that nobody's talking about yet. They're on-time to the MCP trend, not early, which means execution speed matters more than vision here.”

“The buyer is a Perplexity Pro subscriber who already pays $20/month — Comet is a retention and upgrade mechanism dressed as a product launch, which is actually smart distribution. The moat question is harder: browser distribution is a graveyard (ask Opera, Brave, Arc) and the switching cost of a browser is enormous for consumers but thin for Perplexity because users won't abandon Chrome for search features alone. The business survives model cost compression because Perplexity's value isn't the underlying LLM — it's the index and the task orchestration layer sitting on top of it. What worries me is the expand story: once you've automated the tasks a Pro user cares about, what's the upsell? There's no obvious enterprise tier with audit logs and admin controls mentioned at launch, which means the revenue ceiling is whatever the Pro subscriber count is. Viable, but not yet a standalone business thesis.”

“The buyer is a mid-market ops team or a SMB owner who already pays for Zapier and doesn't want to hire an engineer to build agentic workflows — that's a real, known, creditcard-holding customer with an existing budget line. The moat is distribution: Zapier has 6 million users who already trust it with their workflow credentials, and adding agents to an existing account is zero new procurement friction. The stress test is the unit economics question the Skeptic raises — task-based pricing doesn't scale with enterprise usage, and Zapier will need a seat-based or outcome-based tier before it can land serious enterprise deals. But for the SMB and prosumer segment, this is a genuine expansion of an existing product into a defensible new surface, not a pivot.”

“The job-to-be-done as stated is 'complete multi-step web tasks autonomously' — that sentence contains an 'and' hiding inside 'multi-step,' which means this product is trying to solve task delegation, context retention, and web navigation simultaneously before nailing any one of them. The onboarding reality: users join a waitlist, get access inside a Pro subscription, and then face the blank-slate problem of not knowing which tasks are reliably automatable versus which will silently fail halfway through. That's not a 2-minute path to value — that's a discovery tax. The product isn't complete enough to replace any existing workflow today because there's no task library, no failure transparency, and no way to audit what the agent actually did. Until Comet ships a defined set of tasks it handles end-to-end with high reliability and surfaces that clearly at onboarding, it's a demo with a waitlist, not a product.”

“The primitive is: a hosted MCP server that exposes 7,000 pre-built action triggers to any MCP-compatible AI client. That's actually a non-trivial engineering lift — building and maintaining those connectors is not a weekend project, and the MCP surface is the right bet for developer composability. The DX bet is that you never write an integration yourself, you just configure one; the complexity is pushed into Zapier's layer, not yours. The moment of truth is whether your target app's connector is maintained well enough to not break in prod — and that's historically Zapier's weakest point, fragile Zaps that silently fail. Still, for teams that already live in the Zapier ecosystem, the MCP server support is a genuine force multiplier, not just a marketing badge.”