Glean Actions vs Comet Browser by Perplexity

“Glean already owns the search index in enterprises where it's deployed, so Actions isn't a cold-start problem — it's an upsell on top of data access they already have. The direct competitors are ServiceNow's AI layer, Microsoft Copilot for M365, and frankly just Slack + a well-configured Workato flow. Where this breaks: any company whose HR and IT data isn't cleanly indexed in Glean already, which is most companies in year one of a Glean deployment. My 12-month prediction: this either becomes table stakes for Glean's renewal motion or it gets cannibalized when Microsoft ships the same workflow triggers natively in Copilot Studio — Glean's bet is that enterprise search context beats platform incumbency, and that's a real but narrow window.”

“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 buyer is the CIO or CHRO who already wrote a Glean check — this is pure expansion revenue with essentially zero new sales motion required, which is a beautiful thing. The moat is the existing index: once Glean has crawled your Workday, ServiceNow, and Confluence, the switching cost to rip it out and replace it with Copilot is genuinely painful. The risk is that this is an enterprise feature expansion masquerading as a product launch — if it's gated behind an additional SKU with a separate SOW negotiation, adoption will be slow enough that competitors close the gap before Glean gets the case studies.”

“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 primitive here is: natural language → workflow action dispatch, using Glean's existing knowledge graph as the intent resolver. That's a defensible idea. But the entire blog post is marketing copy with a screenshot at the bottom — there's no API surface documented, no SDK, no mention of how custom actions are defined or what the action schema looks like. If I'm an IT engineer at a 5,000-person company who wants to add a custom action for our in-house provisioning tool, I have no idea how to do that from anything published. The DX bet is entirely opaque, and a tool that lives inside enterprise deals with no developer-facing documentation is a platform I have to adopt wholesale on someone else's timeline — exactly what I'm tired of.”

“The job-to-be-done is clear and singular: let an employee resolve an HR or IT need without opening a new tab or filing a ticket manually. That's a real, high-frequency frustration in any company over 500 people, and Glean is solving it at the right layer — the search interface where employees already go to find answers. The completeness question is the real test: this only works if your company's Glean deployment is mature, your HR and IT data is actually indexed and current, and your IT team has configured the action integrations. For a new Glean customer, this is a 6-month-away feature, not a day-one capability — which means it's a retention play, not an acquisition hook. Still a ship because the job is real and the placement is right.”

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