A Factor box waiting on a front porch in late afternoon light
Factor+ · HelloFresh · 2026

Making a second subscription worth paying for

Factor delivers prepared meals through a weekly subscription. Factor+ added free shipping and premium meal credits for a separate fee.

I led product design from exploration to launch, designing how customers joined, used their benefits and managed their membership. I also helped shape the experiment that would guide its expansion.

+30.5%

More orders per customer in the observed data

+12.6%

Higher predicted net customer value over 52 weeks

−7.4%

Lower meal subscription cancellation, relative to control

Results for customers offered Factor+ versus control, among customers with 2–10 previous boxes. Source and methodology.

Role
Lead Product Designer
Team
Gen AI Startup Squad
Scope
Strategy → shipped MVP
Partners
Product · Engineering · Data · Finance · Brand
Reuse
Recommended as a starting point for HelloFresh+
Status
Shipped · wider rollout recommended

Strategy

Customers were already paying us

Factor+ cost $24.99 every four weeks or $99 a year. The offer was straightforward: pay a membership fee to save on shipping and premium meals.

But Factor already had a Rewards program. I initially argued for bringing the benefits into that program, rather than asking customers to understand another one. The team chose a standalone membership that we could price and test independently.

That left two things to resolve: would customers see enough value to join, and would their ordering change enough to justify the benefits?

Design

Make the value easy to see and use

I worked with a small product and engineering team in HelloFresh’s Gen AI squad, using Claude to explore ideas and prototype in code. We kept the first release focused. Tiering and gifting could wait until we understood the basic membership.

I concentrated the experience around three moments:

  • Joining. Make the price, billing schedule and benefits clear before customers commit. The cart experience shows what joining would save on the order they already have.

  • Using the membership. Apply benefits automatically and give customers one place to see their credits, savings and expiry dates.

  • Leaving. Show what happens to the remaining benefits and confirm when billing stops.

Factor+ membership hub showing active member status, free shipping usage, premium meal credit, and benefit expiry
Fig. 01The membership hub as shipped: what’s included, used and saved, and when benefits expire.

The membership hub shipped as the place to manage that relationship. The cart and cancellation demos below recreate those journeys using Factor’s production components and sample data.

  1. 01
    The offer, in the cart
    What joining would save on this order, right above the button that pays for it.
  2. 02
    One sheet to join
    Two plans, the card on file, and the terms in a sentence.
  3. 03
    Savings, applied
    The new total, before the order is placed.
Fig. 02Joining from the cart. Recreated for this page with Factor’s production components; prices and meals are sample data.
The first cancellation screen: Hold up, you still have benefits to use, showing $131.96 saved since joining, a Keep my bonuses button and a Cancel Anyway button
What you’d give up
What you’ve saved so far, with the way out on the same screen.
A short survey sheet asking why you are cancelling, with Not using the benefits selected, and buttons to go back or submit and cancel
One question
Why you’re leaving, then submit. Or go back.
Confirmation that the membership is cancelled: no more charges, and free delivery and premium meal coupons continue to the end of the billing cycle
Cancelled, and clear about it
No more charges. Benefits run to the end of the term.
Fig. 03Leaving, in three screens. Same components and sample data.

Experiment

Include the customers we were worried about

The original brief planned to exclude highly loyal customers. They already ordered regularly, so we risked giving them discounts without getting any additional orders.

I argued to include them in a separate test group. Excluding them would avoid the immediate risk, but it would also leave us guessing about whether the membership could work for them.

I documented the concern during launch week. We read the results by previous order history and compared everyone offered Factor+ with control, including people who never joined. Comparing members alone would favour customers who were already more engaged.

Results

The results supported a wider audience

In the target group, customers offered Factor+ averaged 2.408 orders, compared with 1.845 in control. Their predicted net value over 52 weeks was $353.80 versus $314.14, a difference of $39.66 per customer.1

Meal subscription cancellation was 67.24% versus 72.63%: 5.39 percentage points lower, or a 7.4% relative reduction.

The loyal customers were the surprise. Predicted value remained above control much further into that group than our initial concerns suggested.

Predicted value vs control

+12.6% −1.3%1

Predicted net value over 52 weeks per customer offered Factor+, by previous order history. LL indicates previous box count.

  1. LL2–10+12.6%Target cohort
  2. LL10–15+5.0%Expand
  3. LL15–20+3.7%Expand
  4. LL20–30+4.5%Expand
  5. LL30–50+1.7%Monitor
  6. LL50+−1.3%Paused
Fig. 04Predicted net value remained above control through LL30–50, and below control at LL50+.

Overall adoption reached 9.96%, although the target group’s adoption was lower at 6.52%. By week 34, 45,609 weekly active Factor customers were members, representing roughly 9% of the active customer base.

The August recommendation was to expand to LL10–30, monitor LL30–50, and keep LL50+ paused while the benefit structure was reviewed.

The original plan would have excluded these loyal customers together. Testing them gave us evidence to include some and reconsider the offer for others.

  1. Source: PM performance read, August 28, 2026. Order actuals and value forecasts use W18–W31 allocation cohorts; cancellation covers all-time allocations. Net value includes membership fees and modeled reactivation discounts and acquisition costs. Forecasts are not observed annual returns. The readout provides no confidence intervals or significance tests. An app bug affected control exposure until May 27; earlier LL2–10 analysis used web data for that period, but the August read does not restate the filter. Customer reach is from W34.