Kollab vs Comet Browser by Perplexity AI

“The primitive here is a shared prompt-and-context registry with a workflow runner bolted on — which is a real problem, but the DX bet is squarely on the no-code crowd, not engineers who'd actually compose this into something. The Skills layer sounds like saved prompts with parameters, and there's no public API, no SDK, no repo to audit — so the 'full participant' positioning is marketing until I can call an agent from my own code. The moment of truth is building your first Skill, and if that's a form with dropdowns rather than a function signature, I'm out.”

“The direct competitors here are Notion AI with its database integrations, and more pointedly, Microsoft Copilot Pages — both of which already sit inside workflows teams actually use daily, backed by companies that own the productivity stack. The specific scenario where Kollab breaks is at the organizational scale: persistent memory across sessions sounds great until you have 200 employees, conflicting contexts, and no audit trail for what the agent 'remembered.' What kills this in 12 months isn't a competitor — it's that Slack and Notion each ship a native Skills-equivalent, and the integration layer Kollab's Bots occupy evaporates overnight.”

“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 buyer is a team lead or ops person at a 10–100 person company spending real hours rebuilding the same AI prompts across tools — that's a real budget line (productivity software) and a real pain point with a clear before/after. The pricing architecture is smart: credits scale with usage, the free tier is genuinely usable, and $20/month per user is a no-brainer procurement decision that bypasses IT entirely. The moat is thin against platform consolidation, but the Skills-as-shared-org-memory angle creates genuine workflow lock-in if they can get three or four critical workflows embedded — teams don't migrate away from things baked into their daily rhythm.”

“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 job-to-be-done is clean and singular: stop rebuilding AI context every time a new person on your team needs to use it. The Skills layer nails this — one person builds the investor-update workflow, everyone else invokes it without touching a prompt. The incompleteness risk is the knowledge base: if documents go stale and agents cite outdated context, the product actively makes work worse, not better, and there's no visible mechanism for freshness signaling. But the onboarding path — connect a tool, build a Skill, deploy a Bot — has a credible three-step value arc that most AI workspaces bury under configuration screens.”

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