Joe Pettersson joins the podcast, to talk all things devrel at banked.com. Banked is a global payments network, and if you’ve ever tried to order anything online, you’ll know that the payments systems used by various websites are far from perfect. Banked is on a mission to fix that. They want to get users through payments systems as smoothly as possible. As Joe puts it, the payments industry is big, but old-fashioned. So the question for him and the team at Banked became “how would we build Visa, or Mastercard if we started in 2023?”
Alongside all of this, Joe and his team have also made waves in the devrel space, and we were excited to hear about their innovative new system for measuring developer relations. At banked.com, their sales process is developer-enabled. It comes down to whether you’re selling directly to developers, or trying to avoid the developers “nope”-ing your product when it’s put before them.
Joe explains that a huge part of banked.com’s success has been down to their focus on the developer experience. From his perspective, payment systems are already complex enough without needing to pass that complexity onto developers. For Richard, this represents a huge leap in efficiency from the days when he spent hours trying to integrate a credit card payment provider with a website, and had to personally calculate the encryption hash. PTSD, anyone?
Joe tells us that accounting for the developer experience while designing your product can be directly translated into increased revenue. Developers won’t always be choosing the products they use, but they are often given the power to say no. But how exactly do you measure the benefit of time and money invested into devrel? Joe and his team have a system that involves finding out what percentage of your prospect’s developers have heard of your project. It sounds simple, but we think this system is a gem that will soon be spreading to other companies. Listen to Joe explain HOW they implement this system.