Building product strategy and scaling sales at Calendly

Executive overview

Calendly transitioned from a purely product-led business to blending sales-led growth while maintaining its core viral loop. The key insight is that clarity on target market and personas—not feature count—drives product velocity and business growth.

The company used a three-horizon strategy framework to guide work allocation and product decisions. As they shifted upmarket into enterprise, they restructured the product organization around clear user personas (sales teams, customer success, recruiting) rather than features, requiring cultural discipline to say no to requests outside their target market.

How product strategy shapes execution

• Strategy is an integrated set of choices defining where to play and how to win—not a wishlist
• Calendly's vision: become the best place to schedule, prepare for, and follow up on external meetings
• Three horizons with shifting resource allocation: Year 1 (70/30), Year 2 (50/50), Year 3 (30/60/10)
• Team structure organized around personas and outcomes, not features or departments
• Core team handles feature development and growth work for primary ICPs (sales, recruiting, customer success)
• Enterprise team serves IT admins and departmental leaders at scale
• Platform team owns integrations and APIs to embed Calendly into customer workflows
• Annual company OKRs cascade down with quarterly milestones and tightly mapped dependencies across departments

Finding and prioritizing the target customer

• Early Calendly served a broad, horizontal user base (solo users, educators, sales, recruiting, support)—which drove viral growth but made prioritization nearly impossible
• The shift to narrowing ICPs was a major unlock: teams can now prioritize ruthlessly because they know exactly who they're building for
• Example of deprioritization: rejecting a requested Venmo integration because it doesn't serve the target persona, despite small business demand
• Saying no is culturally difficult; Calendly's core value "focus wisely" is embedded in templates, OKRs, and product reviews to sustain the discipline

How Calendly organizes the product development lifecycle

• Four phases with clear commitment gates: discovery, solutioning, build, launch/measure/iterate
• Discovery and solutioning work are estimated and committed to (not just vague project dates)
• Estimation and delivery dates only promised once the solution is designed and scoped
• Quarterly roadmaps map to OKRs; three-year strategy guides multi-year investment bets
• Templates for OPA (opportunity/problem assessment) and PRDs reinforce target customer clarity

Managing the PLG-to-SLG transition

• When Calendly hired its first Chief Revenue Officer two years ago, ~99% of ARR was PLG
• SLG now represents ~20% of ARR and is the fastest-growing segment
• Early sales motions are inbound-heavy (PQLs and inbound leads), not outbound hunter profiles
• Sales team profile matters: hire people with experience selling to department heads (not CIOs or IT)—avoid Oracle-style sales reps in the early days
• Buyer evolves from department head → IT admin → CIO, but starting with the wrong profile slows growth

Building strong product-sales partnerships

• Sales teams are a product manager's biggest asset—they talk to 10X more customers than individual PMs
• At Box, deep field time with sales partners revealed customer problems at scale and how to solve them without building redundant features
• Treat sales as your voice of customer; lean on them for prioritization and problem understanding
• The transition from PLG to SLG changes everything: people, process, and product all need realignment

Calendly's first thousand users: the origin story

• Founder Tope (then sales professional) hired a Ukrainian development firm to build the product
• First 10 users came through the contracting firm itself—customer success agents using Calendly to schedule with parents for K–12 education
• Parents adopted it for parent-teacher scheduling, schools discovered it, and it spread organically
• The entire product started free because billing infrastructure wasn't built—a feature that turned into a growth advantage
• Viral loop + free tier + better UX than alternatives created exponential adoption

Why virality plateaus and what comes next

• Solo user PLG business eventually hits a growth ceiling (finite number of solo users willing to pay)
• Law of large numbers: hundreds of millions in revenue means growth naturally slows
• Calendly's next growth curve: teams and departments wanting to schedule together (faster growth than solo users)
• Unlike some companies, Calendly wasn't forced to invent the next growth lever—customers pulled them there through usage data

Why most companies struggle with saying no

• Clarity on target personas forces hard trade-off decisions
• Cultural difficulty: executives fear leaving "money on the table"
• In practice: building something amazing for a specific user beats building something mediocre for everyone
• If unclear about who you're building for, every customer request seems equally important

Product team practices and culture

OPA (Opportunity/Problem Assessment) meetings: PMs debate and spar about which problems to investigate or solutions to pursue; CPO deliberately absent to encourage psychological safety.

Competitive work aiming: quarterly rotation where assigned PM groups do deep SWOT analysis on competitors, present findings with prizes; keeps org aligned on competitive landscape without requiring all PMs to monitor all competitors.

Focus wisely principle embedded across templates, hiring rubrics, and product reviews.

Tools and systems

• Docs (Google Docs) and Slides for strategy and planning
• Miro for whiteboarding and brainstorming
• Confluence for documentation and project storage
• Aha and Airtable for roadmap and planning
• Jira for bug tracking
• Slack and Loom for communication
• Pendo for in-product user education during feature launches

Key advice for transitioning into product management

• APM programs: Google, Meta, and companies like Box offer formal paths; search Glassdoor.com for "associate product manager" to find opportunities at earlier-stage companies
• Internal transfer: express interest, partner closely with a PM, take on some PM work to demonstrate readiness
• Subject matter expert programs: pair with product teams to build depth in a specific area
• Join an early-stage startup where everyone does multiple roles

Successful transitions share traits: curious, passionate about product and customer problems, hands-on with side projects, willing to learn on the job.

Getting the CEO-CPO partnership right

Skip Community (founded by Nikhil, former CPO at Credit Karma, now VP Product at Meta) brings together ~23 CPOs and heads of product at late-stage growth companies.

Monthly meetups, Discord, podcast, and direct peer support for topics like managing CEO relationships, compensation, equity, avoiding burnout, and identifying next roles.

Starting point: follow Skip Community on LinkedIn and reach out to members.

Favorite tools and media

• Top SaaS products: Slack, Miro, Loom, Pendo, Confluence
• Books: Playing to Win, Good to Great, Hooked
• Podcast: 20VC with Harry Stebbings
• TV: Sing 2
• Interview question: "Tell me about your biggest product flop—what happened and what did you do about it?"—look for brutal honesty and learning

Calendly tips and new features

How to send a Calendly link without feeling awkward:

• Open the door: ask for their availability first before sending the link
• Add times to email: paste available time slots directly in your message to reduce friction
• Feature: Customize Once and Share—modify event type details (title, duration, dates) on the fly without creating a brand new event type