🏷️ Maximizing Partnerships: A Deep Dive into Integrations with PriceWell’s Matt Reid
Unpacking PriceWell's approach to prioritizing, building and implementing integrations
Hi friends!
Welcome to the latest in our series where we delve into the world of integration strategies with some of the industry's most forward-thinking individuals and teams. Our aim is to highlight the growing significance of integrations in today's digital realm, examine their contribution to overall business objectives, and provide actionable insights for your integration endeavors.
In this edition, we have the pleasure of talking to Matt, co-founder of PriceWell, a SaaS platform that simplifies the integration of Stripe subscriptions to your website.
Throughout this interview, Matt shares invaluable insights about PriceWell's integration strategy, their approach to building new integrations, and how they support their customers through the implementation and use of these new integrations.
Here's a snippet of our conversation:
Hi Matt! Tell us more about you and PriceWell. How do integrations contribute to your overall business strategy and goals?
I’m Matt, co-founder of pricewell.com. We take the pain out of adding Stripe subscriptions to your website. I’m a software engineer who has built and sold multiple SaaS businesses. One thing I found frustrating while building previous businesses was spending weeks setting up billing when I wanted to be focused on the business itself.
Integrations are a huge part of our customer acquisition strategy. There are hundreds of website builders out there. Most of them lack a solid Stripe integration. Integrating with other tools helps get the word out about PriceWell through cross-promotion and discovery via listings on plugin marketplaces.
When it comes to integrating new services with PriceWell, how do you prioritize which integrations to build?
We listen to our customers first and foremost. They tell us which tools they are using and those become our priorities for an integration. We’re a small team so we can act fast when we hear a need for a new integration. When choosing to develop a new deep integration (like a plugin) we first take a look at the Total Addressable Market of that plugin (e.g. a niche tool with a small market might not be worth it). Then we look at the developer documentation for building such an integration. Ideally, we’d like to be able to build a plugin without ever contacting support for the tool (these types of contact can really elongate the process)…
Stay tuned for more stories from SaaS leaders on their integration approaches in our upcoming issues. As always, if you have any questions or would like to share your own integration journey, don't hesitate to reach out.
Until our next deep dive!
Cheers,
Lola