> The Bonjoro upgrade experiment that led to Plandalf: a feature-led offer, an in-product payment flow, and a reported lift from a 10–12% baseline to 16.6%.

Source: https://plandalf.com/blog/2025-02-19-how-bonjoro-increased-saas-conversions-by-40-with-low-code-checkout-flow
Last modified: 2026-09-24

Checkout

# How Bonjoro increased SaaS conversions by 40% with checkout experiments

The Bonjoro upgrade experiment that led to Plandalf: a feature-led offer, an in-product payment flow, and a reported lift from a 10–12% baseline to 16.6%.

**Plandalf Team**February 19, 20253 min readUpdated September 24, 2026

_Originally published in February 2025. This account describes an internal Bonjoro experiment; the figures below were reported by the original team and have not been independently audited. We reviewed the article in September 2026 and removed an obsolete installation snippet._

Plandalf began with an upgrade problem at Bonjoro. The product team wanted to test new offers and checkout experiences, but each change competed with feature work for engineering time. A small experiment became a way to put the upgrade flow back in the hands of the people working on conversion.

## The problem with the existing upgrade path

Bonjoro had a standard, multi-plan upgrade journey. Someone using a particular feature had to leave their work, compare plans, pay, and find their way back. That interruption was especially costly when an upgrade appeared during template creation: users could lose the context of what they were making.

The team wanted to answer a more focused question: would a feature-specific offer, shown where the need arose, work better than sending every user through the same plan comparison?

## Three changes to the flow

### 1\. Lead with the feature the customer wanted

The first test focused on Rollups, Bonjoro’s group video sending feature. Instead of opening with every plan and every feature, the upgrade explained Rollups and showed one clear next step. The aim was to make the purchase decision about the task already in progress.

### 2\. Keep the upgrade in the product

An in-product upgrade experience let users pay and return to what they were doing. This mattered most for someone partway through a template. It also gave the team a place to test offer copy, supporting proof, and how monthly and annual choices were presented.

### 3\. Test relevant variants

The team could vary the offer for solo and team users, and distinguish a first paid purchase from an upgrade by an existing customer. Those were the initial segments. The point was to learn from a few meaningful differences before adding more targeting rules.

## What the first test reported

The original account put Bonjoro’s free-to-paid baseline at **roughly 10–12%** and the new badge upgrade workflow at **16.6%**. It described the result as a **40% uplift**. That percentage is a rounded relative comparison against a baseline near the upper end of the reported range; it is not a 40 percentage point increase. The source did not publish sample sizes, a test window, or statistical confidence, so treat the result as a team-reported experiment, not a general conversion benchmark.

The result changed how the team approached upgrades. Instead of waiting for an occasional redesign, they could iterate on each moment of intent: which feature prompted the offer, what the customer saw, and whether the experience returned them to their original task.

## What they learned beyond conversion

Feature-level upgrade events also helped the team ask better questions about pricing and packaging. Which features led to paid plans? Which attracted annual purchases? Did solo and team customers respond to the same offer? Those questions are useful even when a test does not lift conversion.

The durable lesson from this early Plandalf story is to connect the offer to the customer’s immediate goal, preserve their work through payment, and measure the whole journey. Explore [Plandalf Checkouts](https://plandalf.com/products/checkouts) and the [integration catalog](https://plandalf.com/integrations) for the current product; the old JavaScript installation shown in the 2025 post is no longer current guidance.

Filed under[Checkout](https://plandalf.com/blog/tag/checkout)[Conversion](https://plandalf.com/blog/tag/conversion)[Case study](https://plandalf.com/blog/tag/case-study)

Written by Plandalf Team

The team building Plandalf.

Where this lives in Plandalf

[**Checkouts**The branded sales flow for launches with moving parts.See Checkouts](https://plandalf.com/products/checkouts)

Keep reading

## More from the blog.

1.  [May 15, 20261 min readCheckoutThree things every checkout should do before you optimize anythingBefore you A/B test button colors, get the fundamentals right: page weight, address autofill, and a payment method customers actually want to use.](https://plandalf.com/blog/2026-05-15-checkout-conversion-fundamentals)
2.  [September 3, 20243 min readCheckoutFive checkout handoffs worth getting right with StripeChoose the right plan, prepare customers for payment, connect checkout sessions to purchases, deliver the upgrade, and return people to their work.](https://plandalf.com/blog/2024-09-03-the-hidden-levers-of-stripe-checkout)
3.  [September 15, 20243 min readPaywallWhat Canva's 2024 paywall gets right about upgradesA close look at Canva upgrade screens captured in 2024: premium feature cues, contextual offers, product previews, and a clear path back to the work.](https://plandalf.com/blog/2024-09-15-canva-paywall-masterclass)

[All posts](https://plandalf.com/blog)

Newsletter

## Get new posts by email.

Checkout teardowns, pricing notes and product updates. Only when there is something worth reading.

The team

## Built by a team obsessed with conversion.

![Aaron](https://plandalf.com/images/faces/aarongorn.png)![Bilbert](https://plandalf.com/images/faces/bilbert.png)![Buildo](https://plandalf.com/images/faces/buildo.png)![Foundo](https://plandalf.com/images/faces/foundo.png)![Legoli](https://plandalf.com/images/faces/legoli.png)

15\+ years building SaaS businesses together. Every part of Plandalf comes from a real checkout problem we’ve had to solve ourselves.

[Start your 14-day free trial](https://admin.plandalf.dev/signup)

No credit card required. Nothing to migrate.
