Do you add social login to your SaaS, or stick with email and password?

Question

I recently launched a small SaaS and noticed a surprising drop-off at the signup page. Right now I only support the classic email + password flow.I&rsquo;m debating whether adding social sign-in (Google, GitHub, Apple, etc.) would meaningfully improve conversion, or just add complexity and support overhead.For context: the product is LogoSmith, a lightweight AI logo generator I built for indie devs. Instead of random AI prompts, it uses a simple wizard (fonts, colors, style) and generates instant logos. I&rsquo;ve seen interest, but the signup completion rate isn&rsquo;t where I&rsquo;d like it to be, which makes me wonder if login friction is part of the problem.Curious how others here have handled this:Did you see a noticeable bump after adding social login?Any unexpected issues (abuse, vendor lock-in, user confusion)?Is it something you&rsquo;d recommend prioritizing early, or waiting until later?Would love to hear real experiences from other SaaS builders.

emiliog07 · Accepted Answer

Always github

mtmail · Answer

We saw slight drop in fake email (disposable, temporary email addresses) signups but it became clear many login-with-google also use their secondary or spam aliases. In B2B the big customers, those actually paying, rarely use social logins.
Issues: Users don't remember which login method they used so next time they might try to create an account with email&password. login-with-google actually is the same as register-with-google, it doesn't tell you ahead if the user already has an account with your website. Some users expect to convert their login method to email&password. The flows for password change or forgot password are different.
That said you can solve each as it happens, it doesn't matter with a small number of users. I'd still implement it later, it's likely not the reason why people bail during signup.