Canopy

Canopy builds infrastructure software for fintech companies, providing the API layer that powers payment processing, compliance checks, and transaction monitoring for some of the fastest-growing financial technology startups. Headquartered in San Francisco with a hybrid workforce of 200 employees, Canopy has tripled in size over the past two years—and their internal processes had not kept pace with that growth.

The company is organized into roughly 20 cross-functional teams spanning engineering, product, design, sales, and customer success. Each team operated with a high degree of autonomy, which was great for speed but created significant alignment challenges. By mid-2024, the company had developed what VP of Engineering David Park calls a “meeting culture problem”—one that was quietly eroding the engineering velocity that had made Canopy successful in the first place.

Before Intelo, Canopy relied on a familiar stack: Google Workspace for documents and email, Slack for real-time communication, Zoom for video calls, Linear for engineering project management, and Notion for wikis and documentation. The tools worked fine individually, but there was no connective tissue between them—and meetings had become the default way to bridge that gap.

The numbers painted a stark picture. Canopy averaged 14 recurring meetings per team per week. For engineers, this meant losing entire afternoons to syncs, standups, backlog grooming sessions, cross-team alignment meetings, and ad-hoc “quick calls” that were never quick. A time audit conducted by the engineering leadership revealed that the average Canopy engineer spent only 52% of their work week writing code. The rest was consumed by meetings, context-switching, and the preparation and follow-up work that surrounded those meetings.

The root cause was a lack of shared context. Most of these meetings existed purely to share status updates that could have been a written summary—but nobody had time to write those summaries because they were too busy attending meetings. It was a vicious cycle. Product managers were spending 60% of their time synthesizing information from various sources and communicating it outward, leaving precious little time for the customer research and strategic thinking that was supposed to be their primary job.

Several teams attempted to break the cycle by adopting async practices—written standups, Loom videos, Notion updates—but these efforts fizzled out within weeks. The problem wasn’t willingness; it was the overhead of actually producing and consuming async updates. Writing a good status update took almost as long as attending the meeting it was supposed to replace.

Canopy’s engineering leadership brought Intelo on board with a specific, measurable goal: reduce meeting load by at least 30% within 60 days without sacrificing team alignment. Ivo was deployed to all engineering and product teams first, with a phased rollout to sales and customer success over the following month.

The implementation focused on three core capabilities. First, Ivo was configured to monitor Slack project channels and Linear boards, automatically generating daily digests that summarized what had changed, what was blocked, and what decisions needed attention. These digests replaced the daily standup meetings for most teams. Second, Ivo began pre-populating meeting agendas for the meetings that remained, pulling in relevant context from Slack threads, Linear tickets, and Notion documents so that attendees arrived already informed. Third, Ivo generated post-meeting summaries with clear action items and owners, eliminating the “wait, who was supposed to do that?” problem.

The cultural shift happened faster than anyone expected. Within weeks, teams began canceling their standing syncs on their own—not because they were told to, but because the syncs had become redundant. The meetings that remained became shorter and more focused because Ivo had already surfaced the context everyone needed before the meeting started. David Park describes it as the moment Canopy’s async culture finally clicked: “We had been trying to go async for a year. Ivo is what actually made it work.”