Lenny's PodcastBehind the scenes of Calendly’s rapid growth | Annie Pearl (CPO)
CHAPTERS
- 4:09 – 6:04
Calendly invite etiquette: sending links without the “power move” vibe
Lenny opens with a practical question: how to send a Calendly link without making the recipient do extra work or feel pressured. Annie shares specific phrasing and a built-in Calendly feature that reduces friction.
- •Ask the other person for their availability first, then offer your link as an easier option
- •Use “add times to email” to include selectable times directly in the message
- •Reduce clicks and perceived burden to make scheduling feel collaborative
- •Calendly has guidance (blog content) dedicated to this exact scenario
- 6:04 – 9:53
Breaking into product from a non-technical background (Annie’s paths + what works best)
Annie explains how she moved from law into product, then lays out the most common routes she’s seen for others. The emphasis is on demonstrating real product skills before you officially have the PM title.
- •Four entry paths: APM programs, applying to junior PM roles (often internally), shadowing/SME partnering, or joining an early startup
- •Internal transfer is most common in Annie’s experience—relationships + proof of work matter
- •Use SME (subject matter expert) programs to embed with a product squad
- •Traits that stand out: curiosity, customer-problem obsession, and side projects that show PM thinking
- 9:53 – 13:26
APM programs: where to look and why they’re rare
The conversation zooms in on Associate Product Manager programs—where they exist and why more companies don’t run them. Annie and Lenny discuss the operational burden of doing these programs well.
- •Well-known programs: Google APM, Meta APM; smaller companies can have them too (e.g., Box built one)
- •Tip: search “Associate Product Manager” roles on Glassdoor to find programs/openings
- •APM programs are rare because they require heavy investment (interviewing, training, clear graduation paths)
- •Companies need enough scale and capacity to run them responsibly
- 13:26 – 14:50
Calendly’s org growth and product team structure (core, enterprise, platform)
Annie shares how Calendly scaled from ~150 to ~600 employees and expanded the product org significantly. She explains the leadership structure and how teams are organized around personas and problem spaces.
- •Product/design/research org grew from ~15 to ~60 (PMs, design, research) with ~20 PMs
- •Product leadership includes heads of Design, Research, Product Ops plus PM leaders across Core, Enterprise, Platform
- •Team grouping is largely persona/problem-based rather than purely feature-based
- •Core serves external-facing roles (sales, recruiting, CS) and also owns PLG funnel work
- 14:50 – 19:07
Why design reports into product—and the Head of Design hire
Annie explains why Calendly has design, product, and research under a single leader focused on end-to-end UX. She also shares that one of her earliest moves was hiring a Head of Design to scale the function.
- •Unifying product + design can improve holistic decision-making around the end-to-end experience
- •Calendly already had strong design ICs but lacked design leadership at the time
- •Hiring a Head of Design helped build the design function and partner effectively with product leads
- •This structure becomes more common as companies scale and need tighter integration
- 19:07 – 21:20
OKRs maturity: from unclear priorities to integrated company planning
Annie describes Calendly’s evolution in goal-setting and execution. The biggest improvement was moving from siloed OKRs to tightly connected company-level objectives with cross-functional dependency mapping.
- •Phase 1: lots of work, but unclear measurement and how it fit together
- •Phase 2: product OKRs existed but departments operated with siloed OKRs
- •Phase 3: a small set of company OKRs with integrated cross-company plans and dependency mapping
- •Linking OKRs top-to-bottom improved alignment and execution
- 21:20 – 23:44
Execution unlock: narrowing the ICP (and why saying ‘no’ is hard)
Annie explains that Calendly’s broad horizontal user base made prioritization difficult. The team improved speed and decision quality by explicitly focusing on core ICPs and accepting trade-offs.
- •Calendly served many segments (freelancers, education, sales, recruiting, CS), making prioritization hard
- •Strategy work clarified markets, segments, and personas—especially target ICPs
- •Saying no enables building something great for the most important users vs. ‘okay’ for everyone
- •Focus improved both prioritization rigor and value delivered to target personas
- 23:44 – 25:15
From PLG to adding sales: cultural, process, and product changes
The episode shifts into how Calendly layered a sales motion on top of a historically PLG business. Annie emphasizes that moving upmarket changes people profiles, processes, and culture—not just pricing or packaging.
- •When Annie joined, PLG was ~99% of ARR; the CRO was just hired to build sales
- •Moving upmarket requires tighter cross-functional integration vs. siloed PLG optimization
- •Sales-led motion forces changes across people, process, product, and culture
- •The shift intersects with ICP focus: teams must align on who the real buyer/user is
- 25:15 – 26:16
Calendly’s growth engine: the viral loop + PQL-driven expansion
Annie breaks down how most sign-ups still come from Calendly’s viral sharing loop. Then she explains how usage expands inside companies and becomes sales opportunities via product-qualified lead signals.
- •~70% of sign-ups come from recipients encountering Calendly links (viral loop)
- •Users often start solo, then invite teammates; teams adoption creates internal momentum
- •PQL (product-qualified lead) data helps identify accounts/teams to pursue
- •Sales then expands usage from teams to broader org deployments
- 26:16 – 29:23
Early sales team strategy: hire for inbound motion and the right buyer
Annie shares two key considerations for early sales hiring when transitioning from PLG to SLG. Inbound-heavy leads and departmental buyers require a different sales profile than enterprise IT/CIO selling.
- •Early PLG-to-sales motion is mostly inbound/PQL-driven—more ‘grower’ than ‘hunter’
- •Assess reps by prior selling motion experience (background matters more than personality)
- •Early buyers are typically department heads (Sales/RevOps/Recruiting), not CIO/IT
- •Avoid hiring only CIO-oriented enterprise sellers too early; buyer maturity evolves over time
- 29:23 – 31:57
Product–Sales partnership: treat GTM as your customer empathy engine
Annie argues that sales and GTM functions can be a product team’s biggest asset. She illustrates with her Box experience: sales talks to far more customers, accelerating product learning and decision quality.
- •Start with empathy: see sales as an asset, not an interruption
- •Sales provides scaled customer insight (far more conversations than PMs can do alone)
- •Field time and sales partnership helped Annie build better enterprise products at Box
- •Strong collaboration improves both discovery and prioritization
- 31:57 – 35:31
Prioritization and strategy: ‘Playing to Win’ + horizon-based investment allocation
Annie explains her prioritization approach anchored in product strategy: where to play, how to win, and what not to do. She then shares how Calendly allocates resources across three horizons that evolve year to year.
- •Use ‘Playing to Win’ to define winning aspiration, where to play, and how to win
- •Clarity on where NOT to play is essential for prioritization
- •Calendly vision: best place to schedule, prepare for, and follow up on external meetings
- •Resource allocation shifts across horizons over time (e.g., 70/30 → 50/50 → 30/60/10 across horizons 1/2/3)
- 35:31 – 38:14
Roadmaps & commitments: planning by phase (discovery → solutioning → build → launch/iterate)
Annie details Calendly’s planning cadence and how they avoid overcommitting too far out. The key tactic: commit to phases you can control (like discovery) and only commit to delivery dates after solution clarity and estimation.
- •Company OKRs measured annually with quarterly milestones for progress tracking
- •Roadmaps support key results and are planned with quarterly breakdowns
- •Commit to discovery/solutioning phases earlier; commit to ship dates after design + estimation
- •Defined lifecycle: discovery, solutioning, build, launch/measure/iterate
- 38:14 – 40:26
Strategy artifacts and product stack: how the work is documented and managed
Annie describes the layers of strategy documentation—from a company-wide 3-year strategy to team OKRs to project templates. She also shares the tooling stack used to plan, track, collaborate, and launch features.
- •Company-level 3-year strategy lives as docs + slides; becoming part of new-hire onboarding
- •OKRs and plans start in docs and often convert to slides for broader communication
- •Confluence-heavy culture with templates for different work types
- •Tooling includes Aha!, Airtable, Jira, Slack, Loom, MURAL, Pendo, Google Docs/Slides
- 40:26 – 43:37
Origin story: how Calendly got its first users (contractors, education, and viral spread)
Annie recounts a surprising early-growth story validated with the CEO. Calendly’s first users came through the external dev firm building the product, creating an organic viral chain from education customer success to parents to schools.
- •Founder Tope knew scheduling pain from sales and saw weak solutions on the market
- •He funded early development by raiding his 401(k) and used a Ukrainian dev firm
- •First ~10 users were customer success agents at another company working with the same firm
- •Education use case spread to parents and schools; free tier (partly by necessity) accelerated adoption
- 43:37 – 52:07
New growth levers, culture rituals, and ‘focus wisely’ in practice
Annie explains what’s changing in Calendly’s growth mix: team and department usage is outpacing solo usage. She also shares cultural rituals (OPA and competitive war-gaming) and how ‘focus wisely’ is reinforced through templates and reviews.
- •Teams/departmental Calendly is growing faster than solo use—and is a major future growth driver
- •At scale, viral solo growth slows; next curve comes from org-wide deployments
- •Rituals: OPA (Opportunity/Problem Assessment) debate forum; competitive war gaming with prizes
- •‘Focus wisely’ is reinforced via documentation/templates and consistent customer/persona framing
- 52:07 – 1:01:48
Career lessons from Box & Glassdoor, Skip Community, and lightning round (books, tools, tips)
Annie reflects on what she learned from enterprise (Box) and marketplace/consumer growth (Glassdoor) and how both inform Calendly’s hybrid PLG+sales model. She then describes the Skip Community for CPOs and closes with a lightning round including her favorite interview question and a new Calendly pro tip.
- •Box: learn the ‘why’ behind customer requests; build scalable solutions without harming UX
- •Glassdoor: funnel optimization, growth discipline, data/AB testing for consumer-scale products
- •Skip Community: peer support for Heads of Product/CPOs; LinkedIn entry point + Discord + programming
- •Lightning round highlights: books (Playing to Win, Good to Great, Hooked), flop interview question, stack, and “Customize Once and Share” Calendly feature
