Comet Browser by Perplexity vs Zapier Agents

“The direct competitors here are Arc Browser's AI features, Dia from The Browser Company, Google's built-in Gemini integration in Chrome, and frankly just using Perplexity in a tab. The scenario where Comet breaks is the moment a user hits a site with aggressive bot detection, a multi-step OAuth flow, or a form that requires human verification — and that's the majority of 'book an appointment' use cases in the real world. My prediction for what kills this in 12 months: Google ships Gemini-native task execution in Chrome and the 3.5 billion people who already have Chrome installed don't download a new browser for a feature they get for free. For Comet to earn a ship, it needs to demonstrate autonomous task completion on a real-world benchmark — not a curated demo set — and show completion rates above 70% on genuinely complex multi-step workflows.”

“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 Comet is betting on: within three years, the browser's primary job shifts from rendering documents to executing intentions, and whoever owns the execution layer owns the session data that trains the next generation of personal agents. The dependency that has to hold is that users will switch browsers — which historically requires extraordinary activation energy, but smartphone-generation users have shown less browser loyalty than desktop users, and Perplexity already has distribution through its search product. The second-order effect that matters most isn't the time saved booking appointments; it's that Comet positions Perplexity to capture behavioral clickstream data at a scale that currently only Google holds, which becomes the actual moat. This is riding the trend of 'intent graph beats knowledge graph' and Perplexity is approximately on-time — not early enough to be alone, but not late enough to be irrelevant.”

“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 here is the existing Perplexity Pro subscriber who is already paying $20/month and now gets a reason to make Perplexity their primary browsing context, not just a search tab — that's a defensible expansion play into a relationship they already own. The moat question is harder: browser switching costs are real but the moat isn't the browser itself, it's the behavioral data and the agent memory that accumulates over sessions, which is the right answer but requires years of retention to materialize. The stress-test that concerns me most isn't Google — it's that Perplexity's own unit economics depend on query costs, and an agentic browser that runs multi-step tasks is dramatically more expensive per session than a search query; if they can't make the margin work at scale, the Pro pricing doesn't hold.”

“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 'browse the web and get things done without context-switching to an AI tool' — which is one coherent job, so the focus is there. The problem is completeness: a browser only works as a daily driver if it handles 100% of browsing tasks, and Comet launching without extension support, established sync infrastructure, password manager integration, and a mature dev tools panel means users will dual-wield Chrome and Comet for months, which is the death state for browser adoption. The product has a clear opinion — AI executes, human approves — but the onboarding question I need answered is whether a new user reaches a successful autonomous task completion in under five minutes or spends that time granting permissions and watching it fail on a CAPTCHA.”

“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.”