This doesn't directly answer your question, but it may give you insight on whatever steps you need to take:<p>It costs whatever it does to build something in which you can have someone pay you for and receive value in exchange. Nothing more.<p>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.<p>You need to give the ability to receive value for something.<p>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.<p>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.<p>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.<p>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.<p>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.<p>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.<p>Build the software.
It depends a lot on what your product does, so it's hard to give an estimate. I've built SaaS products that only took a few weeks. I've built ones that took 6 months.<p>One way to save significant time/money is by using a SaaS starter kit. There's one for just about every stack these days: <a href="https://bullettrain.co" rel="nofollow">https://bullettrain.co</a> (Rails), <a href="https://divjoy.com" rel="nofollow">https://divjoy.com</a> (Node/React), <a href="https://saaspegasus.com" rel="nofollow">https://saaspegasus.com</a> (Django), <a href="https://spark.laravel.com" rel="nofollow">https://spark.laravel.com</a> (PHP/Laravel). Ideally you're not wasting any time on this boilerplate.
If you're a dev who doesn't value your time it's free!<p>Otherwise it costs you many hours of market research to see if your product is viable. Many hours of design and testing to determine if your product is useful/liked by customers.<p>In comparison, the running costs are orders of magnitude less than what you will waste building and launching the product.
This is a pretty broad question. A big question is what does your SaaS do, and how much functionality does your SaaS need to have? And are you a developer who can build something end to end? I built a basic recruiting app for maybe $20K in 2010, but I was focused on a very specific feature set to keep the cost down.
It depends. We're developing our machine learning platform. We're a boutique consultancy and the opportunity cost is high as we're not affordable for most organizations.<p>However, the product is for ourselves and what it avoids us down stream is huge.<p>Machine learning projects are expensive and seldom succeed, and this is taxing on morale, retention, hiring, etc. and our platform addresses these problems.<p>In other words, spending time to make a wheel means it's time you're not spending moving forward, but a round wheel is much better than a square wheel and you make it up in no time when you have it.<p>Huge costs, but huge benefits that compound.
When you're not yet paying yourself, your costs are your living costs and opportunity costs (in addition to the given fixed and variable dev and prod deployment cloud costs).<p>Early feedback from actual customers on an MVP can save lots of development time. GitLab Service Desk is one way to handle emails as issues from users who don't have GitLab accounts.<p>A beta invite program / mailing list signup page costs very little to set up; you can start building your funnel while you're developing the product.
Less than $100 to just launch the saas, assuming technical (co)founder.<p>Less than $1k if you also incorporate in a standard way, e.g. stripe atlas.<p>Less than $10k if you also need a lawyer and/or CPA for taxes.<p>I can't say the cost for non-technical founders, i.e. outsourcing development. I'd guess with $10k you can already get something simple up and running.<p>Edit: of course I'm assuming cost of your team time = $0.
This is a weird ambiguous question. Please be specific and respond here so we can help you instead of creating a cesspool of unrelated and unorganized responses.<p>What you're really asking is "How to create a SaaS app?" which is extremely broad.
It depends on many different factors, e.g., what’s the SaaS business? do you value your own time? Do you count the opportunity cost? Do you have some existing foundations to build on, e.g., reuse old code base / customer relationship...