Inside monday.com’s transformation: radical transparency, impact over output, and their path to $1B ARR | Daniel Lereya (Chief Product and Technology Officer)

Episode Summary

Executive Summary: Daniel Larea, Monday.com’s CPTO, explains how the company scaled from a small team to a $1B ARR platform by obsessing over impact, radical transparency, and bold, time-boxed bets. He argues that competitors can be a useful gift, that speed comes from reframing problems rather than working harder, and that teams must continuously reinvent themselves as the company grows.

Main Topics: Using competition as a catalyst for change (Priority: 5/5): Monday realized competitors were shipping dramatically faster, which exposed their own execution bottlenecks and pushed them to rethink product architecture, team operating model, and ambition. Impact-driven product management (Priority: 5/5): Daniel defines great PMs as relentless on validating customer impact, not just shipping features. Teams must work backward from measurable goals and focus on whether a release changes user behavior or business outcomes. Radical transparency and shared accountability (Priority: 5/5): Monday shares extensive company and product metrics broadly, believing transparency creates partnership, surfaces issues faster, and puts everyone’s brain on the challenge instead of centralizing knowledge. Bold, time-boxed product bets (Priority: 4/5): The company uses aggressive deadlines and ambitious targets to force different thinking, cut scope, and avoid overbuilding. This led to rapid launches like new columns, AI blocks rollout, and enterprise offerings. Scaling requires letting go of prior strengths (Priority: 4/5): Daniel says the habits that made leaders successful early on can become liabilities at scale. He emphasizes adapting leadership style, communication, and decision-making as the company and org evolve. Turning infrastructure pain into strategic advantage (Priority: 4/5): Performance and scalability crises prompted Monday to build MondayDB and other foundational systems, transforming a problem into a long-term competitive edge for enterprise-grade usage. AI as a productivity and productization challenge (Priority: 3/5): Daniel shares practical AI use cases, from interpreting medical results to researching pricing and competitors, and stresses that the real challenge is productizing AI so customers can access its value.

Key Arguments: Competitors can provide a valuable forcing function: seeing others do something you thought impossible removes excuses and can unlock step-change improvements. A great PM is defined by impact validation, not activity; shipping many things is irrelevant if you cannot point to a specific customer or business outcome. Transparency makes teams stronger, not weaker, because it creates trust, shared context, and faster problem detection across the company. Ambitious goals are not about working longer hours; they force smarter thinking, better architecture, and elimination of fake speed. Many product problems are actually visibility or accessibility problems; sometimes the highest-impact move is making existing value easier to discover and use. As a company scales, the leader’s job changes; strengths like deep detail ownership can become constraints if they are not intentionally adapted. When core systems break, the right response may be a strategic investment rather than a patch, especially if the issue affects long-term product differentiation. Customer feedback must be interpreted in context; early paid-user feedback is often a better signal than broad feedback, and complaints can be a sign that people care. AI has immense capability, but the real leverage comes from packaging it into workflows customers can actually use. Culture and operational cadence are central to scale; Monday treats culture as an active system, not an abstract value statement.

Data Points: Customers: 250,000 - Monday’s current paying customer base discussed in the interview ARR: $1 billion - Monday recently announced it crossed this annual recurring revenue milestone Company size today: 2,500 employees - Approximate current size of Monday.com Company size when Daniel joined: around 40 employees - Daniel joined early in Monday’s growth journey Company size during the competitor-shipping moment: around 150–200 people - Estimated scale when the team realized it was moving too slowly Early ARR at join time: around $4 million ARR - Monday’s revenue scale when Daniel joined Original board columns: 5 columns - Monday had five board column types before the redesign Competitor launch comparison: 30 new columns - A competitor launched 30 columns, triggering Monday’s shift Time to build one column originally: about 4 months - Previous development cycle for a new column type Columns hacked in the new approach: 25 columns in one month target - Aggressive goal used to force a new way of working Columns delivered after the shift: 30 columns in about a month and a half - Result of the rapid re-architecture and hackathon approach AI blocks rollout: 98% of customers - Monday opened AI blocks to nearly all customers within two weeks AI adoption comparison: a few thousand accounts out of 250,000 paying companies - Low initial AI usage prompted action to expand access Non-tech customer share: 70% - Daniel notes most Monday customers are non-technical Team/org size under builders org: 700 people - Current engineering, product management, and product design org scale Performance issue response: three major iterations/episodes - Repeated performance spikes eventually led to MondayDB investment MondayDB investment window: last 3 years or so - Underlying data infrastructure built to address scale and performance

Pivotal Quotes: "We received a gift from our competitors. They showed us that it's possible." — Daniel Larea: On the moment Monday realized competitors were shipping much faster and used it as a catalyst for change "We really want everyone's brains in the challenge and not just one centralized brain and a lot of working hands." — Daniel Larea: Explaining Monday’s radical transparency philosophy "A great PM basically for me is someone that is relentless until he gets this impact, until he validates that this impact is in place." — Daniel Larea: Defining product management around measurable outcomes rather than output

Implications: For product teams, the episode argues for measurable outcomes, transparent operating systems, and bold bets that force new thinking. For scaling companies, it shows that growth requires continual reinvention and that infrastructure, culture, and AI adoption must all be treated as strategic priorities.