Challenge
A US company selling AI to sales teams was growing quickly, and like most growing companies, each team had built its own way of working. Go-to-market had its tools, customer experience had theirs, product and engineering had theirs. Each was reasonable on its own. Together they meant the company's knowledge lived in a dozen places that did not talk to each other.
The cost showed up at the seams. What customers told the support team reached product late, if at all. Releases went out without the people selling and supporting them knowing what had changed. Every new tool promised to fix one gap and opened another, and the company was paying for the sprawl in money, in time and in things falling between teams.
Solution
We built a company brain: one central system that holds how the company works and what it knows, on a single code base shared by every team. Instead of each team keeping its own version of the truth, the customer conversations, the product roadmap, the release notes and the go-to-market material all live in, and are built from, the same place.
That shared foundation is what made an agentic way of working possible. Agents can act across the whole company because the whole company is in one system: turning a customer issue into a product ticket, a release into updated help content, a roadmap change into what the sales team says next. The teams stopped handing work across tool boundaries and started working on the same thing.
Execution
Mapping how work moved between teams
We started by following the work, not the org chart: how a customer request travels from the support team to the product team, how a feature goes from idea to release, how a release reaches the people who sell and support it. Every handover between tools was a place where context was lost, and that map became the list of what the central system had to connect.
One code base instead of many tools
The core decision was to replace tool sprawl with one code base that every team works in, rather than adding integrations between more tools. Content, workflows and internal applications sit side by side, so a change in one place can update everything that depends on it. Fewer tools also meant fewer logins, fewer subscriptions and one place to look.
Connecting customer experience to product and engineering
Customer conversations feed straight into the product process: patterns in what customers ask become signals for the roadmap, and fixes flow back as updated answers. Engineering releases update the material the customer and sales teams rely on, so nobody learns about a change from a customer.
What runs on it
The central system is not an idea on a slide; the company runs on it every day. On it we built the help centre, every contact form and its connection to the CRM, and the partner portals where partners see their own accounts and numbers. Product updates no longer wait to be written up: each release is turned into tutorial videos and sent straight to customers, so they hear about a change from the company, not from finding it.
Designing for agents from the start
Because every team's work lives in one system, agents can be given real jobs rather than isolated tricks: drafting help content from a release, routing a customer issue to the right team, preparing material for a launch. People stay in control of what goes out; the agents do the joining-up that used to fall between teams.
