7
2 Comments

How much custom code have you written to support basic SaaS workflows?

Hi all!

I started my start-up (www.outseta.com) back in 2016 largely because the equivalent of Stripe Billing didn't exist at the time—Stripe offered great APIs, but it was still way to difficult do deliver the basic table stakes functionality that nearly all SaaS products require.

While Stripe Billing now exists (and is a killer product), I still hear near constant frustration from developers in terms of the sheer amount of custom code still needs to be written to manage very basic workflows in the content of a SaaS business.

This stuff is not unique—why are we still reinventing the wheel when this stuff comes with a significant opportunity cost—developer time spent building non-core product?

What other workflows have you invested time building yourself that you'd like to see offered out-of-the-box when you launch your next SaaS business?

https://www.outseta.com/developer-workflows

on October 24, 2022
  1. 1

    The main reason to build your own subscription system is that Stripe charges heavily for them but is very cost-efficient for one-off payments. At a certain scale everyone tends to roll their own.

  2. 2

    This comment was deleted 3 years ago

    1. 1

      How so? What are the add-on products you are selling—are they additional subscriptions? One-time products? What's tough to manage today?