Back office ops · Production

Assembled builds a company-wide AI operating system with Dust, achieving 95% internal adoption across 120+ employees

The problem

Assembled's hypergrowth exposed severe knowledge fragmentation: company information was scattered across Google Drive, Slack, Notion, Linear, Cursor, Snowflake, and more, search was broken, rapid product releases made knowledge quickly obsolete, and individual AI tool usage was siloed with no shared workflows.

First attempt

Individual automation setups using Relay, Zapier, or personal Claude MCP configurations did not scale because each workflow was tied to a single employee's account and required technical setup most staff could not do.

Workflow diagram · grounded in source
1
CEO pilots Dust in Slack
trigger
“Ryan began experimenting with Dust inside a Slack channel, using it to test small internal workflows”
2
Unified cross-tool search
ai_action
“With a single query, teams could pull information from: Notion, Google Drive, Slack, Gong, Salesforce”
3
Teams build specialized agents
ai_action
“Marketing built competitive intelligence and content automation agents. Sales created follow-up and account research agents. Customer Success built Zendesk and product feedback agents. Engineering added code-base search and SQL query age…”
4
AI Collective knowledge sharing
feedback_loop
“Assembled created an internal AI Collective, which is a monthly gathering where employees share agents they've built and collaboratively troubleshoot new ideas”
5
Employee self-serve retrieval
output
“It used to be: ask marketing or CS where something is. Now it's: ask Dust. Everyone can self-serve”
Reported outcome

Dust achieved 95% internal adoption across 120+ employees without extensive training, saved hundreds of hours through unified search and AI agents, reduced cross-team interruptions so employees self-serve information, and accelerated new-hire onboarding.

Reported metrics
Internal adoption rate95%
Hours saved overallhundreds of hours
Hours saved from search alonehundreds of hours
Reported stack
DustZendeskLinearSnowflakeRelayZapier
Source
https://dust.tt/customers/part-1-assembled-ai-operating-system
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

Dust achieved 95% internal adoption across 120+ employees without extensive training, saved hundreds of hours through unified search and AI agents, reduced cross-team interruptions so employees self-serve information,…

What tools did this team use?

Dust, Zendesk, Linear, Snowflake, Relay, Zapier.

What results were reported?

Internal adoption rate: 95%; Hours saved overall: hundreds of hours; Hours saved from search alone: hundreds of hours (source-reported, not independently verified).

What failed first in this deployment?

Individual automation setups using Relay, Zapier, or personal Claude MCP configurations did not scale because each workflow was tied to a single employee's account and required technical setup most staff could not do.

How is this back office ops AI workflow structured?

CEO pilots Dust in Slack → Unified cross-tool search → Teams build specialized agents → AI Collective knowledge sharing → Employee self-serve retrieval.

Related back office ops cases