Dust.tt Enterprise vs Perplexity Assistant for Enterprise

“The buyer here is crystal clear: it's the IT or security team that's been blocking the AI project the line-of-business team has been begging for. SSO, RBAC, and audit logs aren't features — they're the unlock code for enterprise procurement. The wedge is smart: land with one Slack agent, expand into every department's knowledge base. The risk is that the 'contact sales' pricing wall means we have no idea if the unit economics survive a real enterprise deal with professional services and compliance reviews baked in. If they can hold a $30-50 per seat number without collapsing into custom contracts, this is a real business.”

“The buyer is a VP of Sales or RevOps, and this competes directly against budget already committed to Salesforce licenses, Gong, and internal BI tools — that's a brutal procurement fight with no obvious wedge. The pricing architecture is a black box behind 'contact sales,' which means the unit economics only work if ACV is high enough to justify an enterprise sales motion, and Perplexity doesn't have the enterprise sales muscle to close those deals at scale yet. The moat question is the real problem: Salesforce and HubSpot can each flip a switch and ship 80% of this natively inside their own platforms, and Perplexity's web search differentiation means nothing to a CRO who just wants clean pipeline data.”

“The direct competitors are Glean, Guru, and — increasingly — Microsoft Copilot Studio, which ships with the SSO and audit logs already baked into a tenant most enterprises already pay for. Dust wins if and only if the no-code agent builder is genuinely more capable than what IT admins can stand up in an afternoon with Copilot. The scenario where this breaks is a Fortune 500 with a Microsoft EA — the IT admin has Copilot Studio free in the bundle and zero incentive to add another vendor. What kills this in 12 months is not a competitor, it's platform consolidation: Microsoft and Salesforce both ship 80% of this natively and enterprises stop evaluating point solutions.”

“The category here is enterprise AI search with CRM grounding, and the direct competitors are Glean, Guru, and honestly just Salesforce Einstein with a decent prompt. The specific scenario where this breaks: a sales team actually tries to use it during a live deal — the CRM sync lag, permission scoping across Salesforce orgs, and hallucinated contact history will crater trust in week two. What kills this in 12 months is Salesforce shipping Agentforce deeper into their own interface and making a third-party conversational layer redundant; Perplexity's web search moat doesn't translate into enterprise data trust, and that's the only thing that matters here.”

“The primitive is an agent-scoped RAG pipeline with an enterprise auth layer bolted on — that's a real thing, but the 'no-code' framing immediately raises the question of what happens when the agent needs to do something the drag-and-drop builder didn't anticipate. The DX bet is that IT admins, not engineers, are the deployers, which means the API surface for developers who want to compose this with their own tooling is probably an afterthought. There's no public API docs linked from the blog post, no mention of a SDK, and 'scoped to internal knowledge bases' tells me nothing about how document ingestion actually works at scale. I'll change my verdict the day there's a repo or a curl example in the docs.”

“The job-to-be-done is precise: let a non-technical team deploy an AI assistant over internal docs without giving up on compliance. That's one job, and the SSO plus audit log bundle is exactly what makes that job completable — without those two things, no enterprise IT team signs off. The onboarding question I can't answer from the announcement alone is whether a new user can go from SAML config to a deployed Slack agent in under 30 minutes, or whether there's a professional services call hiding in the middle. The specific product decision that earns a ship is scoping agents to internal knowledge bases by default — that's an opinionated choice that removes the biggest enterprise objection before the customer even raises it.”

“The job-to-be-done is clear and singular: let a knowledge worker ask one question and get an answer that draws on both live web context and internal CRM records without copy-pasting between tabs. That's a real, daily friction point for account executives and analysts, and no incumbent solves it cleanly. The concern is completeness — if the Salesforce integration requires admin setup, OAuth approval chains, and field-mapping configuration before a single query works, the onboarding buries the value and this ships as a demo product, not a workflow replacement. The opinion baked in — conversational over dashboard — is the right one, but it only holds if the data freshness and permission model are tight enough that users trust the answers.”

“The thesis here is falsifiable: by 2028, enterprise knowledge workers will interact with their business data through natural language interfaces rather than BI dashboards and CRM UIs, and the company that owns the query layer owns the workflow. The dependencies are real — this only works if Perplexity can maintain lower hallucination rates on grounded enterprise data than GPT-based competitors, and if enterprises actually grant third-party tools the deep OAuth access required rather than retreating to walled-garden vendor solutions. The second-order effect nobody is talking about: if this works, CRM data quality becomes a competitive differentiator for the first time — companies with clean Salesforce hygiene get dramatically better AI answers than those with garbage pipelines, which reshuffles who benefits from the same tool. Perplexity is on-time to this trend, not early, and that's the risk.”