Quaestor expands and improves its user authentication capabilities and user count with Stytch

Products used:

Key takeaways:

  • Time to value: One engineer, Anmol Maini, was able to independently stand up Stytch in one day
    • Within just a few months, upwards of 35% of users are logging in through Stytch, many of whom didn’t have access due to a lack of Google or Microsoft account
  • Developer experience: Stytch’s clear documentation and SDK were difference makers in their decision making process
  • Uptime: Stytch has been a reliable sign up and login provider for Quaestor thus far. This is in part due to Stytch’s built-in support of failover redundancy across multiple providers, ensuring low latency and high deliverability.

Quaestor is an automated data platform that enables financial transparency between startups and investors. With Stytch, Quaestor enables their customers to reach a broader range of their investor constituents, resulting in more end users on the Quaestor platform.

Challenge

When Quaestor initially launched, the only way an end user could log in was through a Google or Microsoft OAuth flow. This made sense as a starting point as their first clients just supported those platforms. But as the popularity of their product grew, they came up against companies who  either didn’t utilize Google or Microsoft login, or just weren’t comfortable with a password-based option. Because of this, there were important investors who simply could not log into Quaestor. This not only negatively affected Quaestor, since it limited who could access their platform, but it also frustrated Quaestor’s customers, as they had to maintain a separate flow to disseminate information to investors who couldn’t access Quaestor.

Quaestor quickly realized that they needed a secure, yet expansive, user authentication method that still relies on email as the primary factor while also emulating the passwordless experience that already existed with their existing OAuth flows.

Solution

After reviewing the available options in the market and deciding whether they should build a solution in-house or go with another provider, the Quaestor team ultimately decided to partner with Stytch to build out their ideal flow. The primary consideration point for them was the opportunity cost of their developers’ time, and Stytch enabled them to have very fast time to value. Additionally, implementing user authentication poorly has large downside risk and Quaestor could risk serious reputational harm. Finally, the team chose Stytch over other vendors because of Stytch’s intuitive documentation and focus on the overall developer experience. 

The full implementation took Anmol less than a day, and he was surprised that he didn’t have to bother his backend team for any help. 

“The docs were really good. I was honestly impressed with myself that I was able to get [Stytch’s] Python SDK running without needing to ping any of our backend engineers. All the Stytch integration stuff was very easy for me to do.”

The existing Quaestor user authentication flow was not something the team was super happy with, but they couldn’t afford to shut it off entirely to do a complete revamp without affecting their user base. With Stytch and the flexibility of their components and APIs however, Quaestor was able to have the best of both worlds.
By using Stytch’s React components and APIs, instead of ripping and replacing their existing flow, Quaestor was able to simply append a passwordless email authentication experience on top of what was already there. And because Stytch has an endpoint that enables customers to log in or create a user, Quaestor was able to modify both their Log In and Sign Up flows.

This let the Quaestor keep a user authentication flow in place while they built out a brand new onboarding flow that is just using the SDK to send out magic links, which will go live by the end of October 2021. Stytch’s products gave the Quaestor team the ultimate level of optionality and let them build what they needed, when they needed, all without disrupting their end users and letting them maintain control over their user experience.

Results

With Email Magic Links, Quaestor is no longer limited to only end users with a Google or Microsoft account, and they are able to expand access to its platform to anyone with an email address while still upholding their strong security. Anecdotally, the team found that end users tend to like using the magic links to login, and they were surprised at how many people gravitated towards that option despite not actively nudging end users towards it.

As of today, after having Stytch live for just a few months, Quaestor is seeing upwards of 35% of end users logging in through Stytch. Most importantly, Stytch has been a reliable partner for Quaestor and user authentication has not been something that their engineering team has needed to spend a lot of time on.

Profile photo of Anmol Maini

“The Stytch integration was very easy. The overall integration experience and docs were great; it was fast to get up and running with the Python SDK. And the user impact of the Stytch integration is substantial — previously, some people just weren’t able to login with our existing methods. Stytch has enabled more people to use the Quaestor platform.”

Anmol Maini, Full-stack engineer

Ready to get started?

Interested in trying Stytch out for yourself? You can sign up for free to start using our products. Or, you can read more about them in our API documentation. We can’t wait to see what you build with Stytch!