All work

Doubling Payment Integration Adoption

How rethinking when and where users discover a paid feature helped turn customer intent into action.

Company

Calendly

Role

Senior product designer

focus

Growth experimentation, monetization, onboarding, product strategy

year

2025

Booking-page customization with a forest-green and cream Coffee Chat preview and a Callie customization card.

2x

As many payment integrations in test as control

256

Users connected payments in test

120

Users connected payments in control

As the lead product designer on the Growth team, I led a series of high-impact A/B experiments focused on increasing activation and retention at Calendly.

One area of focus was the adoption of Calendly's payments feature. In the first week of testing, 256 users connected a payment integration in the test group, compared with 120 in control.

Rather than building a new feature, we explored how to help users discover and activate an existing capability at the moment it was most relevant to them.

The opportunity

Leadership asked the Growth team to increase adoption of Calendly's payments feature: allowing users to connect Stripe or PayPal and charge for meetings.

I framed this problem into two questions: how do we identify which users actually want to collect payments, and how can we meet them in the moment to make setup feel effortless?

To answer the first question, I introduced a simple onboarding prompt asking users about their goals.


Users could select "Collect payment" as one of their goals. That gave us an early signal of intent, but the experience didn't immediately help them act on it.

The question became: How might we turn expressed user intent into meaningful product activation?

Our hypothesis

I hypothesized that users would be more likely to connect a payment integration if we made the opportunity visible at a moment when they understood its value.

During onboarding: Users had just told us they wanted to collect payments. Their intent was fresh, and we could immediately guide them toward setup.

After onboarding: Users were beginning to explore Calendly and create their scheduling experiences. We could introduce payments within the context of what they were already doing.

The experiment

I designed an A/B experiment to explore whether introducing payment integrations at different points in the user journey could increase adoption.


The experiment at a glance

Control

Variant A

Variant B


Control: the existing onboarding experience

Users selected their goals during onboarding, including whether they wanted to collect payments.

However, selecting that goal didn't immediately lead to payment setup. Users continued into Calendly, where they would need to discover and connect an integration independently.

This gave us a baseline for understanding how users behaved without additional guidance.

The limitation: We knew what users wanted to accomplish, but weren't using that information to help them take the next step.

Variant A: Act on intent immediately

The first approach introduced a personalized payment setup experience during onboarding.

When users indicated they wanted to collect payments, we surfaced a dedicated step explaining how Calendly could help them get paid for meetings.

Instead of asking users to navigate through the product, we gave them direct options to connect Stripe or PayPal.

Why this approach: I wanted to explore whether reducing the distance between expressing intent and taking action would make users more likely to activate the feature.

The experience was designed to feel like a helpful continuation of onboarding rather than an unrelated promotion.

Variant B: Introduce value in context

The second approach introduced payment integrations after onboarding, directly within the Scheduling experience.

A prominent banner highlighted the value of getting paid before client meetings and provided a clear path to explore integrations.

Unlike Variant A, this approach didn't require users to make a decision during account setup.

Instead, it introduced the capability once users were inside the product and beginning to engage with their scheduling workflow.

Why this approach: I wanted to test whether contextual discovery could be more effective than asking users to configure an additional capability during onboarding.

The design decisions behind the experiment

While the interfaces themselves were relatively simple, the decisions behind them were intentional.

  1. Personalization over generic promotion: Rather than presenting every user with the same feature recommendation, the onboarding approach used a goal users had already expressed. The intention was to make the experience feel relevant and helpful, not promotional.

  2. Reduce the distance between intent and action: In Variant A, users could connect Stripe or PayPal directly from the personalized setup experience. This removed the need to navigate to integrations independently and gave users a clear next step.


Results

The first week of testing showed a substantial increase in payment integration connections within the target cohort.

These early results suggested that making payment integrations more discoverable and actionable could meaningfully increase adoption.

The experiment reinforced an important hypothesis: users may already recognize the value, but still need help understanding how and when to get started.

What I learned

Adoption isn't always a feature problem

We didn't need to introduce new functionality to create value. The opportunity was to make an existing capability easier to discover and activate.

Small design decisions can create meaningful business outcomes

The changes we explored weren't particularly complex. But they addressed an important gap in the user journey. For me, this reinforced that impactful growth design is about identifying where users are getting stuck and removing the friction between their goals and taking action.