Signup case studies: Dropbox, Slack, Stripe, Notion, Shopify, Airbnb, Figma

THE DECISION

Double-sided referral loop built into the post-signup onboarding.

THE NUMBER

A 60%+ permanent increase in signups per Sean Ellis's writing and Andrew Chen's analysis of the Dropbox growth playbook.

SOURCE

Sean Ellis on growthhackers.com; Andrew Chen's essay 'How Dropbox got its first 10 million users' (andrewchen.com, 2014).

THE TRADE-OFF

The viral loop worked brilliantly in the 2009-2012 era. As the internet became more spam-aware and storage became cheap from competitors, the referral loop's social value declined. Dropbox eventually shifted to paid acquisition and enterprise as the primary growth driver. The pattern was time-limited but pioneering.

THE LESSON

A referral loop attached to a real product value (free storage) creates genuine word-of-mouth with economic incentive. The key was the double-sided structure: sender and receiver both got something. One-sided referral schemes (only the sender benefits) convert at much lower rates.

THE DECISION

Email-only signup, no OAuth, no password at signup time. Magic link for authentication.

THE NUMBER

Slack reached 1 million daily active users in 2015 with email-only signup. First Round Review 2016 write-up details the product design reasoning.

SOURCE

First Round Review, 'From 0 to $1B - Slack's Founder Shares Their Epic Launch Strategy' (2016); Slack engineering blog.

THE TRADE-OFF

Email-only makes sense when the work email is the team identity anchor. It adds friction vs OAuth for consumer-oriented products. Slack later added Google Workspace SSO for enterprise accounts - a different path for a different user tier.

THE LESSON

The auth method choice should serve the product's identity model. Slack wanted the work email to be the identity. OAuth would tie users to personal accounts. Email-only was a product decision, not a default. Know what identity means to your product before choosing your auth method.

THE DECISION

Multi-screen signup asking for business details, banking information, and identity verification in sequence.

THE NUMBER

Stripe processes hundreds of billions in payment volume annually. Their multi-step signup is a deliberate product decision that has remained through multiple design iterations.

SOURCE

Stripe's own design commentary, Patrick Collison interviews on product philosophy, Stripe engineering blog.

THE TRADE-OFF

Multi-step signup costs conversion compared to a single-form minimal approach. Stripe accepts this trade-off because the product is one where trust is the value proposition. An account that takes three minutes to create signals that the product treats money seriously. For Stripe's target market, this is a feature, not a bug.

THE LESSON

Friction earns its keep when the product's value depends on trust. A payments company that makes signup too easy creates doubt about its identity and compliance controls. Know when your users want to feel friction - it signals you take their business seriously.

THE DECISION

Magic link as primary auth method. Email only at signup. Workspace name set inside the product.

THE NUMBER

Notion reached 30+ million users in 2024 with magic link as the primary authentication. Internal teams cite the signup conversion lift from removing password friction.

SOURCE

Notion engineering blog, product team interviews, Ivan Zhao (Notion CEO) on product design philosophy.

THE TRADE-OFF

Magic link as primary auth means every login requires checking email. For a tool where users return multiple times per day (Notion is a daily driver for many teams), this can be friction. Notion offers passkey setup inside the product as an alternative login path.

THE LESSON

Magic link removes password friction at signup but shifts friction to repeat login. It works best for invite-heavy products where new users often sign up from a link (the link is already a context switch to email). Consider the repeat-login UX when choosing magic link as primary.

THE DECISION

Shop URL and email at signup. Everything else collected inside the admin dashboard at the relevant moment.

THE NUMBER

Shopify has 4+ million active merchants as of 2026. The minimal signup is explicitly cited in product design commentary as a conversion optimisation at scale.

SOURCE

Shopify Partners Blog, Shopify engineering blog, Tobi Lutke interviews on product philosophy.

THE TRADE-OFF

The two-field signup means Shopify has minimal lead-qualification data at the point of signup. They compensate with behavioural signals inside the admin to route merchants to appropriate support, trial, and sales follow-up tracks.

THE LESSON

Progressive profiling at scale means you may have less data at signup, but behavioural signals inside the product are often more reliable than self-reported fields. What users do tells you more than what they say they will do.

THE DECISION

When compelled to add Apple Sign In for App Store compliance, Airbnb audited the downstream impact on email relay.

THE NUMBER

Airbnb's post-implementation audit (referenced in iOS developer community discussions) found that Apple's Hide My Email relay created significant downstream issues for their customer service and transactional email flows.

SOURCE

iOS developer community documentation, Airbnb engineering blog commentary, Apple developer forums.

THE TRADE-OFF

Apple Sign In's email relay means customer service cannot look up users by email address in the standard way. Transactional emails (booking confirmations, support tickets) sent to the relay address may not reach the user if they disable the relay. For marketplaces where email communication is core to the product, this is a significant operational cost.

THE LESSON

Apple Sign In is required for App Store compliance if you offer other OAuth options. Build the operational infrastructure to handle relayed emails before you launch it. Apple provides APIs to check relay status and send to the canonical address. The compliance requirement is real; the operational preparation is optional but necessary.

THE DECISION

Email, name, and a role dropdown at signup. Role drives personalised onboarding template and feature highlighting.

THE NUMBER

Figma has 4+ million active users in 2026. The role-personalised onboarding is cited in Figma's design talks and product team writing as a driver of time-to-first-value.

SOURCE

Figma Config conference talks, Figma product team blog posts, Dylan Field interviews on product design philosophy.

THE TRADE-OFF

Adding any field beyond email adds friction. The role dropdown adds approximately 2-4pp drop per HubSpot benchmarks. Figma accepts this because the personalisation it enables reduces time to first meaningful action, which the product team believes improves long-term retention more than the signup conversion delta costs.

THE LESSON

The only field worth adding at signup beyond the minimum is one that immediately and directly improves the user's first experience. A role that routes to personalised templates passes this test. A role that sits in a database field nobody reads does not.