Build vs. buy AI agents: What 1,000+ enterprise deployments taught us about the real costs
Companies deploying AI agents consistently underestimate the true cost of building in-house, facing hidden burdens in time-to-value, compounding maintenance, and opportunity cost diverted from core business.
Doctolib's internal ChatGPT-based tool DoctoGPT rapidly attracted 800 active users but became unsustainable as feature requests overwhelmed the team. Wakam's data science team built a working RAG chatbot prototype but found that keeping pace with the AI market would require tripling team size.
Companies that adopted Dust achieved rapid deployment and broad employee adoption: Wakam hit 70% adoption in two months with 136 agents deployed and 50% reduction in legal contract analysis time; Ardabelle evaluated 50% more deals in the same timeframe; CMI Strategies achieved 95% adoption with 60-70% time savings on commercial proposals.
Show all 17 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
Companies that adopted Dust achieved rapid deployment and broad employee adoption: Wakam hit 70% adoption in two months with 136 agents deployed and 50% reduction in legal contract analysis time; Ardabelle evaluated 5…
What tools did this team use?
Dust, GPT-4, ChatGPT, RAG, Zendesk, Slack, Notion, GitHub, Salesforce, JIRA.
What results were reported?
Wakam employee adoption: 70%; Wakam AI agents deployed: 136; Wakam contract analysis time reduction: 50%; Ardabelle analyst queries per week: 150+ (source-reported, not independently verified).
What failed first in this deployment?
Doctolib's internal ChatGPT-based tool DoctoGPT rapidly attracted 800 active users but became unsustainable as feature requests overwhelmed the team.
How is this legal document review AI workflow structured?
Leadership faces build-or-buy decision → Internal AI prototype built → Feature demand overwhelms team → Company adopts Dust platform → Business outcomes delivered.