Claude for Google Sheets & Docs vs Perplexity Comet Browser

“The primitive here is straightforward: an Apps Script bridge that routes cell or document content to the Claude API and returns the response in-place. The DX bet is correct — billing through an existing API account means no new credential surface, no second dashboard, and no per-seat pricing negotiation. The moment of truth is formula-based invocation like =CLAUDE(A1, "summarize") or a sidebar panel in Docs; if that works on first install without needing to touch OAuth scopes manually, the DX clears the bar. This is not something a competent engineer couldn't replicate in a weekend with Apps Script and a fetch() call, but the GA status means Anthropic is owning the maintenance burden of the Google OAuth dance and add-on review process, which is genuinely not trivial. Ships because it removes a class of annoying glue code from teams that would otherwise build and maintain this themselves.”

“Direct competitors are the existing third-party Claude add-ons already in the Google Workspace Marketplace, plus GPT for Sheets and Docs which has had this exact positioning for two years. Anthropic going GA native removes the trust problem those third-party tools carry — you're no longer routing your spreadsheet data through an unknown intermediary — and that's a real differentiator worth naming. The scenario where this breaks is enterprise: IT admins blocking third-party add-ons, data-residency requirements, or organizations already paying for Gemini Advanced inside Workspace who aren't going to pay twice. What kills this in 12 months is Google shipping Gemini deep enough into Sheets and Docs natively that the install friction disappears entirely — Google controls the distribution here, and Anthropic does not. Ships because the trust gap it closes is genuine, but it's a clock-ticking position.”

“The direct competitor here is Arc Browser plus any AI extension, or just Chrome plus the Perplexity extension that already exists — and Perplexity already ships that extension. The specific scenario where this collapses is enterprise adoption: IT departments don't swap default browsers for waitlist products, and consumers don't either without a compelling reason beyond 'the sidebar is better.' The prediction: Google ships Gemini natively into Chrome at a depth Perplexity can't match within 18 months, and the browser angle becomes indefensible. For this to earn a ship, Comet needs a capability that is literally impossible to replicate in an extension — and form-filling and summarization are not that.”

“The job-to-be-done is singular and honest: run Claude on your data without leaving the document, which is the right scope. Onboarding requires installing from the Workspace Marketplace and connecting an API key — that's two steps with one friction point, which is acceptable for a power-user tool but will lose casual users who don't already have an Anthropic API account. The completeness question is where this earns its score: for teams already in the Anthropic API ecosystem, this actually replaces the copy-paste-to-Claude.ai workflow entirely for document tasks, meaning it's a full substitute rather than a half-product requiring dual-wielding. The opinion baked in is clear — the model runs in your context, not in a separate chat thread — and that's the right call. The gap is discoverability for new Anthropic users who encounter this before they have an API account; the install flow should handle account creation, and if it doesn't, that's the specific product decision that needs fixing.”

“The job-to-be-done is specific: execute multi-step web tasks without juggling tabs, extensions, and copy-paste loops — and that is a real job that knowledge workers hire for daily. The onboarding question is the one I can't answer from waitlist access, but the make-or-break moment is whether a user can complete a real task in the first five minutes without reading docs, because agentic products that require prompt engineering upfront die in onboarding. The completeness problem is that this requires switching your entire browser, which is a massive ask — Perplexity would have shipped a stronger product by nailing the extension first and using that install base as the migration funnel into Comet rather than leading with the browser. The specific product opinion I'd give them credit for: making the agent persistent and context-aware across the session, not just per-page, is the right call and meaningfully different from extension-based competitors.”

“The buyer here is a knowledge worker or team lead who already has an Anthropic API account, which is a small and self-selecting population — this is not a product that creates new Anthropic customers, it's a retention and expansion play for existing API users. The pricing architecture is API pass-through with no add-on margin, which means Anthropic isn't building a separate revenue line here, they're defending against churn to GPT for Sheets. The moat is brand trust and Anthropic's ownership of the add-on listing, but Google can revoke distribution or preference Gemini in search rankings at any time, which means the moat is rented. What happens when Google makes Gemini formula invocation the default in Sheets with no install required? This product disappears from the consideration set entirely. Skips from a business strategy standpoint — it's a defensive move dressed up as a launch, and the unit economics don't justify treating it as a standalone business bet.”

“The buyer here is unclear in a way that should worry everyone: consumers don't pay for browsers, and enterprise won't deploy an unapproved Chromium fork from a company best known for a search sidebar. The pricing architecture is almost certainly 'bundled into Perplexity Pro,' which means the browser is a retention mechanic, not a revenue line — that's fine until you realize the cost of maintaining a browser fork is not trivial and the ROI has to be measured in churn reduction, not new ARR. The moat question is the real problem: Chromium is open, the AI agent layer is replicable, and the switching cost for a browser is extremely high to create but fragile once created. This survives if Perplexity gets acquired by a platform player who needs an AI browser story; as a standalone business decision, the unit economics don't pencil.”

“The thesis here is falsifiable: the browser is the last surface layer a model provider can own before cloud platforms commoditize the query layer, and whoever owns ambient web interaction owns the monetization stack that replaces the search ad. The dependency that has to hold is that users adopt a second browser for AI tasks — a behavior that has actually happened before with Arc, Brave, and Opera, so it's not implausible. The second-order effect nobody is talking about: if Comet's agent can observe full browsing context across sessions, Perplexity builds a behavioral dataset that no API-layer competitor can replicate, which is the real moat. The trend is browser-as-OS-layer, and Perplexity is early — not on-time, early — which means the execution risk is high but the position is genuinely differentiated.”