Teardown · October 2023 · Growth strategy · Privacy software

Built as a case study exercise using public information. Not a client engagement.

Proton: launching a twelfth product without confusing the eleven you have

The situation

Proton Contacts would join an ecosystem that already included Mail, Drive, VPN, Calendar and Pass. The persona: a 36-year-old US software engineer, tech-savvy but not an ideologue, who buys on word-of-mouth and expert opinion and responds to companies with a mission.

Adding a product to a bundle is not the same as launching a product. Every new tile makes the pricing page harder to read and gives an existing subscriber one more thing to not understand.

This one is a growth brief rather than a positioning brief: funnel, conversion and monetisation rather than category and message.

Products in the bundle

Feature gate

Jobs it does

The analysis in three numbers.

What I built

A full funnel from awareness to advocacy. Awareness through the channels the persona actually trusts (TechCrunch, TechRadar, Engadget, Wired), plus expert reviews, G2 and Trustpilot presence, and Reddit community engagement rather than paid social. Consideration through product landing pages with technical depth, comparison content, and use cases matched to a software engineer's actual day. Loyalty through pre-launch MVP access for power users and Customer Advisory Boards. Advocacy through in-product referral.

Then the problems, named rather than assumed: user overwhelm, resource allocation, technical integration, user trust, support load, and cannibalisation, which I raised and then dismissed with a reason specific to contacts rather than waving it away.

The judgment call

One feature gate doing three jobs.

Contacts ships inside Proton Free: no acquisition friction, it strengthens the free tier and gives the ecosystem another reason to exist. But creating groups requires Plus or Unlimited. Hitting that wall does two things at once: it presents the upgrade at the exact moment the user has demonstrated intent, and it triggers a drip campaign that surfaces paid features across the rest of the ecosystem.

So a single gate handles acquisition, conversion and cross-sell. In a bundle business the new product's real job is often to sell the other eleven, and the monetisation design should reflect that rather than trying to make the twelfth product profitable on its own.

What I'd do differently

I'd have specified the drip campaign's exit conditions. A sequence that keeps surfacing paid features to someone who has decided not to upgrade is a churn risk in a product whose entire brand is we don't manipulate you. Getting that wrong costs more at Proton than it would anywhere else.