The signup problem.
Signup forms have a specific failure mode: they were designed by the team that built the product, not by the visitor who is about to use it for the first time.
The team that built the product knows why they need your company name, your role, your team size, and your phone number. The visitor doesn't. They see a wall of fields between them and the thing they came to try, and a meaningful percentage of them leave.
Across Levri's dataset, the median SaaS signup form has 7.4 fields. The median form with a conversion rate above 40% has 3.1 fields. The difference between those two numbers is a measurable revenue gap — and most of it is recoverable in an afternoon.
The field count baseline.
The relationship between field count and signup conversion is well-established and consistent: every additional field reduces completion rate, with diminishing but non-zero impact at each step.
The typical impact of reducing from 7 fields to 3 fields: +18% to +26% signup completion.
This doesn't mean every field beyond three is removable. It means every field beyond three needs a specific, defensible reason to be there at signup rather than collected later.
What to ship
Audit each field on your signup form against three questions:
- Is this required to create the account? If no, defer it.
- Can this be collected after the first session? If yes, defer it.
- Do we actually use this data? If the answer involves "eventually" or "for enterprise," defer it.
Fields that almost never need to be on a signup form: company name, phone number, team size, role/job title, how you heard about us, billing address.
Fields that often need to be there: email, password (or magic link), name (sometimes). For SSO flows: nothing — the IdP handles it.
The right time to ask for company name, team size, and role is during onboarding — after the account exists, when the value of collecting that data is clearer to both sides.
Typical impact: high — the highest-ROI signup change available to most SaaS products.
Deferred trust asks.
The card requirement is the single biggest conversion blocker in trial-based SaaS — and in most cases, it's a policy decision masquerading as a UX requirement.
Card-required trials convert at roughly one-third the rate of no-card trials on equivalent products at equivalent price points. The visitors who complete a card-required trial are higher-intent and convert to paid at a higher rate — but the volume loss almost always outweighs the quality gain unless your product has extremely high paid conversion rates.
What we see on scans
- Card required at signup for products with a 14-day or longer trial period.
- Card required for trials where the primary value is delivered in the first session.
- No explanation of when the card will be charged or what cancellation involves.
- Card field positioned before the user has seen the product or understood the value.
What to ship
If you can't remove the card requirement entirely (infrastructure costs, fraud prevention, business model constraints), there are two mitigations:
Option A — Move the card ask to day 7 of a 14-day trial. The visitor activates, experiences value, then gets a well-timed card request. Typical lift vs card-at-signup: +12% to +22% on trial starts.
Option B — Make the commitment reducer explicit and prominent. "14-day free trial. Cancel anytime before [exact date] and you'll never be charged." Position this directly adjacent to the card field — not in the footer, not in small print. Typical lift from repositioning: +6% to +11%.
Typical impact: high — card removal or deferral is typically the single largest signup conversion lever for SaaS.
SSO and OAuth friction.
Single sign-on ("Continue with Google," "Continue with GitHub") consistently outperforms email/password signup on completion rate — but it's frequently implemented in a way that reduces rather than improves conversion.
What we see on scans
- SSO options positioned below the email/password form, below the fold.
- SSO buttons with low visual contrast, small font, or a design treatment that makes them look secondary.
- Three SSO options (Google, GitHub, Microsoft) that create a secondary choice before the visitor has even started.
- No SSO option at all — email/password only, on a product where the target audience has strong OAuth preferences.
What to ship
If you offer SSO, it should be the primary path — positioned above the email/password form, high contrast, singular (choose your most-used IdP and lead with it, offer others below).
If you don't offer SSO and your audience includes developers or Google Workspace users, adding "Continue with Google" as the primary CTA will typically outperform an email field as the first input.
For most B2B SaaS products, the ideal signup form is: one SSO button (primary) + email/password as the secondary option below a divider.
Typical lift from repositioning SSO as the primary path: +9% to +17% on signup completion.
Typical impact: medium to high — depends heavily on your audience's IdP habits.
Error handling.
Signup forms have a specific error pattern that most teams don't monitor: the user completes the form, hits submit, encounters a validation error, and leaves. Not because the product failed them — because the error message did.
What we see on scans
- Generic error messages ("Something went wrong. Please try again.") that give the user no actionable information.
- Email validation errors that appear after submit rather than inline during input.
- Password strength requirements that aren't communicated until after the user has already typed a non-compliant password.
- "Email already in use" errors that don't offer a "Log in instead" path, forcing the user to navigate away.
What to ship
Three specific fixes with high impact and low implementation cost:
-
Inline validation on email and password fields — validate format on blur, not on submit. Show the error at the field, immediately, before the user has moved to the next input.
-
Password requirements visible before input — show the requirements in a tooltip or inline note when the password field gains focus, not after a failed submit.
-
"Email already in use" → login link — when this error fires, show a "Log in to your account instead →" link inline. Users who already have accounts and are trying to re-sign up are high-intent. Don't lose them to navigation.
Typical lift from all three error handling fixes: +3% to +7% on form completion.
Typical impact: medium — small per-fix, significant in combination.
The post-signup drop.
The most underestimated conversion leak in SaaS isn't on the signup form — it's immediately after it. The moment between account creation and first meaningful action is where a significant percentage of trial users are permanently lost.
Most teams treat "completed signup" as a conversion event. It's not. It's the start of a conversion event. The conversion is first value delivery — the moment the user understands what the product does for them.
What we see on scans
- Generic "Welcome to [Product]" pages with no clear next action.
- Onboarding flows that ask for company name, team size, and role before showing the product — the friction that should have been deferred from signup is now collected as a wall between the user and activation.
- Empty product states with no guided action ("You have no projects. Create your first project →" in a text link in an empty container).
What to ship
The post-signup page has one job: get the user to the moment where the product makes sense. Everything between account creation and that moment is friction.
The single highest-ROI change for most SaaS products: replace the generic welcome page with a single, specific action that demonstrates the core value of the product.
If your product scans URLs, the post-signup page should have a URL input and a single button. If it analyses data, it should have a file upload or a connect-your-data flow. If it generates content, it should generate something — immediately, with no configuration required.
Time-to-first-value is the metric that matters. Every second between signup and that moment is a second in which the user can leave. Minimise it.
Typical lift from replacing a generic welcome page with a value-first activation step: +14% to +28% on trial-to-active conversion.
Typical impact: high — this is often the largest conversion lever in the entire trial funnel.
How Levri spots signup friction.
Levri analyses signup forms for field count, trust ask timing, SSO positioning, error handling patterns, and post-signup flow clarity — and ranks each finding by its estimated impact on trial start rate and time-to-first-value.
The output is specific: "Your signup form has 8 fields. Removing company name, phone number, and role and deferring them to onboarding is estimated to increase signup completion by 18–26%." Not "consider simplifying your form."
Fix these first.
In order of typical impact:
- Audit every field on your signup form. Remove or defer any field that doesn't need to exist at account creation.
- If you require a card at signup and your trial is 14+ days, move the card ask to day 7 or add a prominent commitment reducer adjacent to the card field.
- If you offer SSO, make it the primary path — above the email/password form, high contrast, singular.
- Add inline validation on email and password fields. Add an inline login link to the "email already in use" error.
- Replace your post-signup welcome page with a single, specific action that delivers first value immediately.
Ship steps 1 and 5 in the same deploy. They address opposite ends of the same funnel and together account for the majority of trial start and activation lift.
Frequently asked.
How many fields should a signup form have?
As few as possible to create the account. The median signup form with a conversion rate above 40% has 3.1 fields. Every field beyond what's strictly required to create the account should be deferred to onboarding or collected progressively after activation. Email, password (or magic link), and sometimes name are usually sufficient.
Should I require a credit card for a free trial?
Only if you have a specific reason that outweighs the conversion cost. Card-required trials convert at roughly one-third the rate of no-card trials on equivalent products. If you must require a card, move the ask to day 7 of a 14-day trial — after the user has experienced value — or add a prominent commitment reducer adjacent to the card field stating exactly when and how they'll be charged.
Does "Continue with Google" improve signup conversion?
Yes, typically by 9–17% on signup completion when it's the primary path. SSO should be positioned above the email/password form, at high contrast, as the default option — not tucked below as an afterthought. For B2B SaaS with a Google Workspace audience, leading with "Continue with Google" consistently outperforms leading with an email field.
What is time-to-first-value and why does it affect trial conversion?
Time-to-first-value is the duration between account creation and the moment the user first experiences the core benefit of the product. It's the single metric most predictive of trial-to-paid conversion. Users who reach first value within the first session activate and retain at dramatically higher rates. Every screen, field, or choice between signup and that moment is friction on the highest-value conversion in your funnel.
Why do users abandon signup forms?
The three most common causes are field overload (too many inputs before the user has experienced any value), trust friction (card required or unclear commitment), and error handling failures (generic error messages or validation that only fires on submit). Inline validation, SSO as the primary path, and removing non-essential fields address all three.