Pricing and checkout optimization·

The 'Tell Us About Your Team' Step Is a Signup Leak: A Before/After Teardown of Pricing-Gated Onboarding

The 'Tell Us About Your Team' Step Is a Signup Leak: A Before/After Teardown of Pricing-Gated Onboarding

You rewrote the pricing page. You swapped the CTA from "Get Started" to "Start Free Trial". You even added a trust bar with customer logos. Yet the biggest drop-off in your funnel is still right after the email confirmation.

Chances are, you're not leaking on the signup form or the pricing page. You're leaking on the onboarding step that asks "Tell us about your team" – the pricing-gated qualification form that appears before a user has felt any product value.

I've audited this exact pattern in dozens of SaaS flows. It consistently destroys signup completion. And it's fixable without touching your pricing model.

The anatomy of a pricing-gated onboarding leak

Here's the pattern: a user clicks "Start free trial" on your pricing page, enters their email, and expects to land in the product. Instead, they hit a screen like this:

  • "Company size?"
  • "How many seats do you need?"
  • "What's your monthly budget?"
  • "Which role best describes you?"

Every one of these fields is an extra decision. Every decision is a chance to lose the user. But the real damage isn't friction – it's the message these fields send: you care more about qualifying me than helping me.

Users who haven't unlocked the "aha" moment have no commitment to your product. Asking for billing-related information before that moment is like asking a stranger to commit to a date before you've said hello.

Why this step violates the trust and clarity heuristics

Nielsen's usability heuristics aren't just for UI errors – they apply to entire flow sections. This step fails two of them:

  • Clarity and guidance: The user doesn't know why you're asking for team size. Is it to build a quote? To route them to the right plan? If you don't explain, they infer the worst. They think you're a sales-led tool and they're not ready.
  • Friction and user control: A required multi-field form with no "Skip" option removes user control. The user feels trapped, so they leave.

Classic checkout friction patterns – like preemptive upselling or asking for unnecessary billing details – have the same effect when applied too early in the signup flow. The principle is the same: only ask for what you need at that exact moment, and only when the user clearly understands the benefit.

Before/after: rewriting the "Tell us about your team" step

Here's a real example from a recent audit (details masked).

Before (the leak):

Welcome to AcmeSaaS! Before we get started, tell us a bit about your company.

  1. Company size: [Dropdown]
  2. Number of employee accounts: [Number field]
  3. Expected monthly spend: [Dropdown]
  4. How did you hear about us? [Dropdown] (bonus leak)

[Continue] [No thanks, take me to my dashboard] ← buried link at the bottom

The user feels like they're filling out an insurance application, not trying a product. The "No thanks" link is present, but it's weak and buried.

After (the fix):

Your workspace is ready. We just need one thing to set it up:

"How large is your team?" (This lets us pre-size your workspace and skip the manual invite step.)

[Start with 1–2 seats] [Start with 3–10 seats] [I'm not sure yet]

(All options lead to the exact same product experience. You're only using the answer to personalize the dashboard, not to gate access.)

The difference? The after version asks a single, optional-feeling question. It explains the benefit ("pre-size your workspace"). It gives the user control with a "not sure yet" option. And it doesn't ask about budget or sales readiness.

This isn't about being anti-data. It's about asking the right data at the right time. If you really need company size for a quote, ask it after the user has activated and cares about upgrading.

A mini playbook: P0/P1/P2 for your pricing-gated step

Apply these in order:

  • P0 – Remove every field that isn't strictly required for the product to run. If you can start a trial without a company size, delete the field. If you can't, make it optional.
  • P1 – Defer the question to a later stage. Move "team size" to the first billing-address step, or to the upgrade flow. Users who then see the question understand why you're asking.
  • P2 – If you must ask at signup, add a "Skip for now" and a one-line benefit. For example: "We'll use this to pre-configure your workspace. You can change it anytime."

And stop asking for "monthly budget" during onboarding. That's a sales question, not a product question.

The better alternative: let pricing find your users, not your forms

Your pricing page and your onboarding step are two different tools. The pricing page targets informed buyers. The onboarding step should gear up new users, not filter them.

If you can't fix the step by editing copy, consider a bigger change: decouple plan selection from signup. Let all users land in the product on a free tier, and show pricing only when they hit a usage limit. This is the pattern behind the most successful product-led SaaS companies I've seen, and it consistently reduces signup drop-off.

Of course, the fix depends on your specific flow. That's why I run a free audit on your signup flow – you'll get a prioritized list of leaks like this one, mapped to the exact steps that are costing you users.

The bottom line

The "Tell us about your team" step is a pricing-gated onboarding leak because it asks for commitment before value. Treat it like a checkout step, and you'll lose the user. Treat it like a personalization prompt, and you'll keep them.

Fix the form, fix the copy, or kill it entirely. Then watch your signup completion curve move in the right direction.