Feb 26, 2023 · 1h 1m · lennys-podcast
Behind the scenes of Calendly’s rapid growth | Annie Pearl (CPO)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this episode, Calendly Chief Product Officer Annie Pearl shares actionable frameworks on scaling product-led growth into enterprise sales, organizing high-performing product teams, and executing disciplined product strategy. She provides deep operational insights into prioritization frameworks, internal product rituals, and navigating product management careers from entry-level to the executive suite.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 29.1% of the talking time here. How this is scored →
Lenny as informed peer 3.6 Guest teaching 5.1 Guest disagreement 0.1 Lenny pushing back 0.3
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 22:55 Pearl pushes back on broad horizontal expansion
Pearl candidly challenges the conventional executive reluctance to say no, arguing that trying to satisfy everyone yields mediocre products rather than excellence for high-value ICPs.
Hardest push from Lenny ▶ 11:42 Lenny questions the rarity of APM programsLenny challenges why more companies don't launch APM programs given their obvious talent pipeline benefits, prompting Pearl to explain the high overhead and organizational capacity required.
Biggest teaching moment ▶ 41:19 Pearl reveals Calendly's unusual agency-based viral originPearl details how Calendly achieved its first 1,000 users through the Ukrainian development agency's other client CSMs and free access, surprising Lenny with a counterintuitive bootstrap growth story.
Lenny holds their own ▶ 44:54 Lenny analyzes the limits of viral PLG curvesLenny demonstrates his product growth expertise by diagnosing why organic viral PLG motions inevitably plateau under the law of large numbers without an expansion into multi-seat B2B teams.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Tactical Etiquette for Sharing Calendly Links | 4 | 5 | 0 | 1 | Lenny asks how to avoid the etiquette problem of Calendly links feeling like a power move. Pearl gives clear tactical recommendations (opening the door first, pasting times directly into the email), which Lenny validates with his own habit. | |
| Pathways and Strategies for Breaking into Product Management | 5 | 6 | 0 | 1 | Lenny asks for advice on transitioning into PM from non-technical backgrounds. Pearl outlines four concrete paths (APMs, internal job boards, shadowing/SME programs, early startups). Lenny synthesizes the paths and brings in his own observations from Airbnb regarding the high investment cost of APM programs. | |
| Calendly's Product Organization Structure and Design Alignment | 4 | 5 | 0 | 1 | Lenny probes how Calendly structures its product, design, and research orgs under a single leader. Pearl explains how uniting product and design ensures holistic end-to-end user experience and details Calendly's team taxonomy across core, enterprise, and platform. | |
| Evolving OKRs into an Integrated Company-Wide System | 3 | 5 | 0 | 0 | Lenny inquires about making OKRs practical. Pearl traces Calendly's evolution through three distinct stages, from no OKRs to siloed product OKRs to company-wide integrated OKRs with cross-functional dependency mapping. | |
| Narrowing Target ICPs and Transitioning Beyond Horizontal Growth | 4 | 6 | 1 | 1 | Pearl explains why transitioning from broad horizontal usage to focused target ICPs (sales, recruiting, customer success) was essential for prioritization. Lenny highlights the fear founders feel when intentionally saying no to potential revenue. | |
| Calendly's Viral Loop and Building a Sales-Led Growth Engine | 4 | 6 | 0 | 1 | Pearl reveals that 70% of Calendly's signups stem from its viral loop and explains the mechanics of layering an inbound-driven sales-led growth engine on top of product-led adoption. Lenny digs into the hiring profile adjustments needed for sales reps. | |
| Fostering Product Empathy and Collaboration with Sales | 3 | 5 | 0 | 0 | Lenny asks how product teams can build great partnerships with sales. Pearl reframes the sales team as a product manager's biggest asset to 10x customer empathy, drawing on her enterprise PM background at Box. | |
| Frameworks for Prioritization: Playing to Win and Three Horizons | 4 | 6 | 0 | 0 | Pearl introduces Lafley & Martin's 'Playing to Win' framework and illustrates how Calendly shifted resource allocation across three horizons over three years. She gives a crisp counterexample of rejecting a Venmo integration because it does not serve their core B2B personas. | |
| Calendly's Product Development Lifecycle and Delivery Milestones | 4 | 5 | 0 | 0 | Pearl outlines Calendly's gated product development lifecycle (Discovery, Solutioning, Build, Launch/Iterate) and explains why teams only commit delivery dates once discovery and solutioning are complete. Lenny clarifies the quarterly roadmap cadence. | |
| Strategy Artifacts and the Internal Product Tool Stack | 3 | 4 | 0 | 0 | Lenny asks about internal strategy artifacts and documentation tools. Pearl walks through company 3-year docs, slides, PRD templates, and their tooling stack (Confluence, Aha, Airtable, Jira, Pendo). | |
| Calendly's Origin Story: Ukraine Agency and the First 1,000 Users | 4 | 6 | 0 | 1 | Pearl shares the origin story of founder Tope Awotona using his 401(k) to hire Railsware in Ukraine, where the contractor's other clients became Calendly's first users. Lenny notes his own Ukrainian roots and highlights how rare it is for outsourced agencies to succeed as startup incubators. | |
| The Growth Frontier: Shifting from Solo Users to Multi-Department Teams | 4 | 5 | 0 | 0 | Pearl explains that multi-user team scheduling is expanding much faster than solo users, driving enterprise expansion. Lenny observes that organic PLG virality eventually plateaus due to the law of large numbers, requiring intentional multi-seat motions. | |
| Product Culture Traditions: OPA Reviews and Competitive Wargaming | 4 | 5 | 0 | 0 | Pearl describes Calendly's OPA (Opportunity Problem Assessment) reviews—which she deliberately avoids attending so PMs can debate freely—and quarterly competitive wargaming exercises. Lenny contrasts OPA with hostile product reviews at gaming studios like Zynga. | |
| Cultural Tenet: 'Focus Wisely' and Strategic Trade-Offs | 3 | 5 | 0 | 0 | Pearl discusses how Calendly operationalizes the cultural tenet 'Focus Wisely' in remote PRD templates, reviews, and strategic trade-offs when transitioning from horizontal breadth to vertical depth. | |
| Comparing Career Lessons: Box, Glassdoor, and Calendly | 3 | 5 | 0 | 0 | Pearl contrasts career learnings from Box (solving underlying problems scalably without bloating features) and Glassdoor (consumer growth funnels and A/B testing) with applying both models at Calendly. | |
| The SCIP Community for Product Executives | 3 | 4 | 0 | 0 | Pearl explains the mission and activities of the SCIP peer community for late-stage CPOs and Heads of Product, discussing Sunday meetings, executive hiring experiments, and Discord support for product leaders. | |
| Lightning Round: Book Recommendations, Media, and Calendly Pro Tip | 3 | 4 | 0 | 0 | In the lightning round, Pearl recommends 'Playing to Win' and 'Hooked', names her favorite interview question regarding product failures, and gives a Calendly pro tip on the 'customize once and share' feature. |
Statements from this episode (19)
Pearl: Offer your availability first to reduce scheduling friction
“I think at a high level, I think I recommend first really just kind of opening the door for the person you're trying to schedule time with to share their availability first, right? So instead of just sending the link, I usually start the email with something l…”
Pearl: Best internal PM transfers start doing product work beforehand
“So some of the kind of best PMs that I've brought over to product from kind of other functions, they really start by expressing interest in product and then like start partnering closely with the product manager and maybe even doing a little bit of product wor…”
Calendly grew from 150 to 600 employees in two years
“When I joined about two years ago, I think the company was about a 150 people, and I think we're about 600 now, and then the product team, we're about, there were about 15 product managers and designers when I joined again about two years ago, and I think we'r…”
Calendly focuses on sales, customer success, and recruiting as core ICPs
“While a lot of the feature work that we'll do to support our target personas of sales teams, customer success teams, recruiting teams will impact folks who are not in those personas. Those are the core ICPs that we're going after.”
Pearl: 70% of Calendly signups come through viral loops
“70% of our signups come through that viral loop that you referred to”
Pearl: PLG represented 99% of Calendly ARR two years ago
“When I joined two years ago, we just hired our first CRO, and the PLG business really represented, you know, 99% of our ARR.”
Pearl: Sales-led growth represents 20% of Calendly ARR
“Our SLG motion, our sales-led growth motion, now represents about 20% of our ARR, and it's actually the fastest-growing segment”
Pearl: Early PLG-to-sales transitions need inbound growers, not hunters
“When you're making that transition from PLG to adding in the sales-led motion because you're starting from PLG, it tends to be much more inbound in nature, right? You've got these sales reps who are working leads who have usually proactively reached out, inter…”
Pearl: Early PLG sales motions target department heads over CIOs
“When you transition from kind of PLG to sales led or, you know, adding this direct sales motion, the buyer is usually just the department head, right? It's the head of sales. It's the head of RevOps. It's the head of recruiting. And it's not, you know, a senio…”
Calendly shifted engineering horizons allocation from 70/30/0 to 30/60/10
“Now, the year one that I was here, the percentage of resources we spent on sort of that first horizon and the second horizon was about a seventy-thirty split, and we put zero percent of our resources on horizon three. That was too far out in the future, and we…”
Calendly deprioritized Venmo integration to focus on sales, recruiting, and CS
“There's lots of small businesses and solopreneurs who would love us to have a Venmo integration. We have a PayPal integration, but you know, our target market that we're really trying to go after as our primary, you know, persona are As I've mentioned, these s…”
Calendly commits to engineering dates only after finishing discovery and solutioning
“Something we've done over the last year is, is really kind of moved to a model of, Talking about dates and promising and committing to dates that are within our control. And so if you think about kind of the product development lifecycle, you know, we can comm…”
Calendly's first 10 users came through its contract development firm
“The first 10 users were actually customer success agents at a company in an educate, in the education space that contracted with the same firm That Tope was using to build Calendly. So he really found his first set of users through the firm that he was using t…”
Calendly launched for free partly because it lacked billing infrastructure
“The entire product was free. Some of this came from honestly not being able to actually build the billing infrastructure that would be required to actually charge. So it came a little bit out of necessity, but it was also free.”
Pearl: Calendly's team business is growing much faster than solo business
“And I think people would be surprised to learn that our team's business, so multiple users in an organization who want to collaboratively schedule together is growing much faster than our solo user business.”
Pearl: Calendly CPO skips early PM reviews to encourage open debate
“Actually, part of the reason I don't go to the meeting is that I really want everyone to be able to be open and transparent and provide feedback and not feel like there's any sort of Judgment from me or any sort of needing to act a certain way because I'm in t…”
Pearl: Calendly conducts quarterly competitive wargaming across product teams
“Another fun one we do is something we call competitive wargaming. So, you know, on a some sort of time interval, at times it's been quarterly, we'll have assigned people into groups for the quarter to own a competitor, and their job is to essentially, you know…”
Rachitsky: Harry Stebbings inspired the creation of Lenny's Podcast
“Harry is responsible for this podcast. I was on his podcast and he's like, Lenny, you should be doing it.”
Pearl: The best PM candidates are brutally honest about product failures
“People being brutally honest around how bad it was and why it failed. You know, the rest of the interview, they're trying to tell you all the wonderful things they did and all the accomplishments they had, and so I think the rawer the answer in terms of how ba…”