Strategy is Choices:
Playing to Win at Calendly

Annie Pearl

Chief Product Officer, Calendly
Former CPO, Glassdoor

PRODUCT STRATEGY

Framework

Strategy = An Integrated Set of Choices

"Strategy is really just an integrated set of choices that outline how you're going to win in whatever marketplace you choose."

Framework from Playing to Win by Roger Martin
Forces clarity: where you WILL play AND where you won't
Defines markets → segments → personas → winning approach
Strategy without exclusions is just a wish list

The Horizon Model

How Calendly Allocates Resources Across Time

Calendly's Winning Aspiration Become the best place to schedule, prepare for, and follow up on your external meetings.

70→30

H1 investment shift Yr1→Yr3

Horizon 3 spend in years 1 & 2

Strategy defines where you play and where you don't — Venmo integration declined despite demand because it falls outside target ICP
OKRs measured annually with quarterly milestones for tracking progress
Roadmap work allocations should map directly back to company-level key results
Commit only to dates within your control: discovery end-dates, not shipping dates

PLG → Sales Motion

How Calendly Layered Sales onto a Product-Led Foundation

"The product itself creates a viral loop — when you send a Calendly link, you are in effect marketing Calendly to everyone you meet with."

The Grower vs. Hunter distinction

Early PLG→Sales reps must be growers — they expand accounts where Calendly already has organic usage. Hunter-profile reps (outbound, cold) are the wrong hire at the start. Match rep profile to your actual go-to-market motion.

Target buyer evolution

Early sales closes with the department head (Head of Sales, Recruiting, Rev Ops) — not the CIO. Don't hire reps who only sell into IT. Buyer persona will graduate toward IT over several years.

Playbook

Breaking Into PM (4 Real Paths)

APM programs — Google, Meta set the standard; Box-sized companies also run them. Search "associate product manager" on Glassdoor for the full universe
Internal junior PM role — works best if you're already in a product-adjacent function (CS, sales engineer, implementation)
Shadow & partner up — express interest, volunteer for PM work before having the title; become an official SME embedded in a product squad
Join an early-stage startup — everyone gets their hands dirty; easiest place to try the role without a formal title

The traits that close the deal Curiosity, genuine passion for solving customer problems, willingness to show work before having the title. Side projects help. Internal transfers succeed most when PMs already know the relationships.

Contrarian

Annie Pearl's Counterintuitive Takes on Product & Growth

✗ Sales teams distract PMs from real product work INSTEAD → ✓ Sales is your biggest asset for customer empathy. A sales rep talks to 10× the customers you can in a week — treat them as the voice of the customer, not a distraction.

✗ Build for everyone and you'll capture the biggest market INSTEAD → ✓ A real strategy forces you to say NO. Calendly declined a Venmo integration with real user demand because it fell outside the target ICP — clarity on who you're NOT building for is the strategy.

✗ Commit to ship dates to build stakeholder trust INSTEAD → ✓ Only commit to dates within your control: the end of a discovery sprint, not a release date. Ship dates depend on what you learn. Promising them erodes trust faster than it builds it.

✗ Design should report separately to stay independent INSTEAD → ✓ Consolidating product and design under one CPO forces end-to-end user experience thinking. When PMs own the problem and designers own the solution, they need one integrating leader — not separate silos.