2 ms·
This doesn't directly answer your question, but it may give you insight on whatever steps you need to take: It costs whatever it does to build something in whi
by joshmn 6y ago
This doesn't directly answer your question, but it may give you insight on whatever steps you need to take:
It costs whatever it does to build something in which you can have someone pay you for and receive value in exchange. Nothing more.
That value is not a SaaS. You don't need build out a "teams" feature or "multiple accounts" feature; you don't need to even build out recurring billing, seat management, or whatever combination of tiered usage you can think of.
You need to give the ability to receive value for something.
I see so many people burn themselves out on doing so and they never talk to customers because all they're doing is fixing edge cases in their billing features.
Once you have your idea's guts, build out the most bare minimum payment model: accept their credit card, store it, charge it, and make a reminder that you need to go into Stripe/Braintree/whatever and charge their card again in a month. Manually create an invoice if your provider can't give you an invoice for them for some reason.
Once managing your customers manually becomes a chore, you can then start to invest in automating it and building out the "boring" infrastructure that has nothing to do with your core idea. Granted, there are SaaS starter kits all over the place for many languages and frameworks. There are also platforms that handle all the recurring billing/seat management stuff for you, too.
But the odds are you might even not get there. The time you would spend building out that infrastructure is not valuable to a customer, and so it's not valuable to you.
Your chances of succeeding are not as closely correlated with subscription management as they are learning about your customer's needs. Take the time you would otherwise invest perfecting a SaaS setup and invest that into talking to customers.
Build your idea, forget that you're building a SaaS. Build the SaaS-y part of the SaaS after you have a customer. Without customer, you're missing the S in SaaS: service. All you have is software.
Build the software.