Capchase Case Study

Capchase has been one of the most advanced FinTechs for over 6 years now. They started using DevinAI soon after it launched in 2024, adopted Cursor in that same year, and by January 2026 the Tech team was migrating to Claude Code. Despite that, the team of ~30 engineers felt it was falling behind.

During April, Tech and Product leadership had a conversation with Desplega Labs aimed to understand what truly meant to become AI Native. Everyone in the org was using Claude, ChatGPT, and multiple other solutions heavily, but the team wasn't upskilling fast enough. How would you continuously upskill a company?

It's no secret that we worked together in the past, and that experience made us confident a short in-person 20 hour workshop would yield great results. The workshop had a single objective: develop an organizational blueprint on how to become AI Native. Together with that blueprint, we would define a Tech roadmap meant to sustain that evolution. In a single quarter, agent-swarm went from a PoC to 44 active users, 10k+ tasks weekly and 26 agents. All due to Capchase doing something differently than most.

Organizational alignment

A clear mandate from the CEO resulted in a dedicated Tech Lead, Daniel Füvesi, and multiple cross-functional leaders across Product, Risk, Operations, Customer Support, Sales, etc, all focused on rapid adoption. The results speak for themselves. In 6 weeks, they rocketed from ~15 tasks/wk to ~7,000 tasks/wk. They integrated with their CRM, gsuite, notion, helpdesk, observability platform, data-warehouse, and more. Daniel reflects on how the tech team stopped investing hours on triaging, data collection and synthesis. In fact, those periodic reports (payment status, customer report, enterprise discovery, etc), and automatic internal support tasks (think of Linear, Pylon and Slack messages) moved entirely to the swarm. That gave Tech a chance to implement key features like Automated security patches with superagent.sh, also in the swarm, key in days of escalating cyberattacks.

Why?

Because 30% of agent-swarm users at Capchase are non-Tech. They are asking the swarm those Data, Tech, Product and IT questions that used to consume the Tech team. They are able to build their own workflows, currently Capchase has 17 automated workflows, with the confidence that the underlying system is at the level Capchase needs.

When asked about agent-swarm, Daniel states clearly:

Why the swarm?

"The swarm gives us three things. It is platform agnostic, so no single vendor can lock us in. It moves workflows (and skills) from individual laptops to the cloud, where they run day and night. It centralizes our company knowledge and skills in one system instead of scattering them across the team. When a provider goes down, we just flip a switch."

Why not build it yourself?

"Many well-funded teams are out there 100% focused on delivering OSS for the agentic world. Building an agent platform from scratch would have pulled our engineers away from the product, and a closed platform would have put our AI roadmap in someone else's hands. Open source is the third option. We self-host it, we own the infra, we can read every line, and when we need something we build it and contribute it back. We get the velocity of a dedicated team and the ownership of an internal tool."

How do you see the increasing cost challenge?

"We are in the transformation phase, where adoption has priority over efficiency. The swarm helps us maximize the utilization of our AI investment, and we actively monitor AI cost per employee. Looking ahead, we are experimenting with self-improvement loops that optimize token usage and cost per task."

What would happen if you turned off the swarm now?

"If we turned off the swarm, all the operational burden it has been taking care of would suddenly land back on people. Months of automated workflows would sit idle while people redo their output by hand. Capchase would not break. It would slow down. Given that we own the memory/historical knowledge, we would adopt a comparable solution."

We are most proud of having Daniel as a key collaborator in our Agent Swarm community. He contributed 29 PRs, out of 49 PRs from Capchase, and we look forward to keep working with Capchase and others to help them reach the provider agnosticism they deserve.