Annie Pearl on Product Focus, Enterprise Expansion and Hiring Product Leaders

Harry Stebbings welcomes Annie Pearl, then chief product officer at Calendly. Pearl originally intended to become a lawyer, but consulting with startups sparked an interest in technology. After passing the California bar she joined the founding team of a private-markets startup and took responsibility for product.

That first startup taught her the importance of focus before product-market fit. The team began with the acute problem of private-market liquidity but added ideas for fundraising, data rooms and networking too soon. Pearl says the breadth distracted from the initial problem; the lesson comes from her experience, not a rule that every expansion fails.

She recommends finding a clear product-market fit and making the first business repeatable before committing heavily to a second product. At the same time, waiting too long can leave a company behind because research, building and market adoption all take time. A second product need not be adjacent, but an existing distribution or data advantage can help.

At the time of the interview Pearl described Calendly’s first phase as a horizontal scheduling product serving many types of users. The next phase was to deepen use cases in externally facing roles such as sales, recruiting and customer success. She imagined a later expansion across the meeting lifecycle; that was a company executive’s future plan, not an established outcome.

Starting with a broad core can provide common functionality for multiple departments, Pearl says. As an example she describes scheduling involving several people inside an organization and an external participant. Calendly still has to decide whether a proposed feature is broadly useful or so narrow that it turns the product into a point solution for one role.

Pearl argues that many successful product-led companies eventually add enterprise sales. Her reasoning is that low-value self-service accounts can make high growth harder to sustain at scale, while wider deployments involve departmental and IT buyers. Her revenue-scale examples are experience-based heuristics, not a law that every company must follow.

Stebbings worries that founders move into enterprise too early. Pearl agrees that hiring salespeople without demand adds cost and noise. At Calendly she watched usage patterns, such as many sales representatives inside one organization, as a signal that a broader standardization conversation might be productive; she also asks whether the company itself is ready.

Enterprise expansion adds complexity within and across teams. Product must consider users, administrators and IT buyers; sales may need a new outbound motion; customer support may become managed accounts. Releases also need coordination across product, sales and customer success, and leaders must decide how to allocate resources between self-service and enterprise.

Security, compliance and scale work are necessary parts of serving large customers, but Pearl also finds new product questions in how teams and departments collaborate. She says the largest challenge is executive alignment: if leaders have not agreed on trade-offs between the two growth motions, employees cannot know which needs to prioritize.

Asked whether both motions are needed from day one, Pearl says a successful self-service product can in theory generate the resources to add sales later. She finds moving downmarket harder when an established sales team’s incentives conflict with self-service. At Glassdoor she recalls a customer signing up online and immediately receiving an upsell call, creating a poor experience.

For a product-led business, she sees the product experience itself as a form of marketing: one user receives value and introduces the product to another. As a company moves upmarket, a dedicated product-marketing function becomes more important for positioning, buyer segments and coordination. This is her framework, not the only way such teams can operate.

Pearl defines product management around two jobs: prioritize the right problems and build successful solutions that create business impact. She sees quantitative and qualitative evidence as particularly helpful in choosing opportunities, while product sense—curiosity, creativity and intuition—plays a larger role in shaping solutions. Both sides still use evidence.

The right first product hire depends on the company’s stage. Before fit, founders often work directly with engineers; after fit an early product manager may execute the founder’s vision; at greater scale a leader may build repeatable processes and a team. Later, a CPO may help open new products, markets or channels.

Stebbings asks whether scale forces a company to lose product craft. Pearl says it need not, but the founder and CPO must be clear about complementary roles. A visionary founder may need an operator, while a founder stepping back from product may need someone to shape the vision; hiring the opposite of what is actually needed can create conflict or a gap.

Before interviewing, she recommends writing the competencies required for the specific role and deciding how to assess them. A hiring-manager conversation checks experience, skills and interest, followed by a panel with assigned competencies. Without structure, multiple interviewers may ask similar questions and learn little that is new.

Her four broad areas are strategy and prioritization; product sense and the ability to describe a compelling solution; leadership, communication and execution; and analytical thinking about success measures and iteration. These are her hiring categories and should be adapted to the company and role.

To assess strategy, Pearl looks for how a person synthesizes information and makes decisions about markets, priorities and capabilities. Stebbings points out that an outsider cannot know Calendly as well as its employees. She agrees: candidates can draw on past experience or discuss a hypothetical where both sides begin on comparable footing.

For a later collaborative working session, a candidate can be given time to explore a more realistic problem, such as improving an onboarding flow. Pearl recommends clearly time-boxing preparation and acknowledging the effort. The session should help the candidate understand the actual work as well as help the company assess the candidate.

A common hiring error is misalignment about what the organization needs: a founder may recruit a visionary when they need an executor, or the reverse. Product managers also differ by stage. Someone who enjoys early ambiguity may feel constrained in a large company, while someone strong in a mature system may struggle without its structure.

Early in a product career, she recommends developing the fundamentals: problem prioritization, product sense, communication, storytelling and analytical measures of success. As a person progresses, the same skills must work at larger scope and with more autonomy, and the role may shift from execution toward owning strategy.

Resource allocation changes with the company’s stage. Before fit, finding it is the priority; after early fit, teams need repeatability; later they must fund future growth without neglecting the core. Pearl says a clear strategy lets leaders work backward from a future launch to research and design needed months earlier.

As organizations grow, she recommends deliberately protecting space for innovation through mechanisms such as sprints or hackathons. At Calendly she described a horizon framework: define the criteria for leaving the current phase, then the work required over the next several months. This was her account of the company’s process in 2022.

Pearl suggests a product vision and strategy may have a two- to three-year horizon, with quarterly reviews of data, customers, market and competition. A review does not require a quarterly rewrite. This cadence is her suggestion, and a different company or changing conditions may require a different one.

She pays attention to competitors but tries to anchor decisions in customers and her own strategy. A rival’s new feature may appear relevant even when the two products serve different use cases. She would reconsider if evidence materially challenged the strategy, rather than copying a launch merely because it appeared nearby.

At Box in 2012, Pearl helped launch an add-on product after customer research, market analysis and prototype validation. The team made aggressive revenue projections and missed its first-year internal target substantially, although she says it caught up to projections in years two and three. These are her retrospective account and internal planning comparisons.

The lesson was not simply that the product decision was wrong. A new product can take longer to affect the business, and a sales team that can meet quota with the established product may take the easier path. Pearl would set more realistic expectations and secure sales leadership’s commitment to enable and incentivize the new product earlier.

In the quick-fire round she says to listen to users while distinguishing a broad need from an edge case. She names product educators including Gib Biddle, Teresa Torres and Marty Cagan, and suggests a new leader work backward from the impact they hope to deliver in the first year to a 90-day and half-year roadmap.

She would welcome more movement into product management from customer success, support and product marketing, believing varied experience can improve teams’ thinking. Outside Calendly she praises Slack for changing much of her own email communication. These are personal observations, and her views about Calendly reflect her professional role.

Stebbings thanks Pearl for the conversation, and she thanks him in return. The available captions show a continuous interview from introduction to closing, consistent with a complete episode.