Loading...
Answers
MenuHow do you know when your SaaS product is ready to launch and start getting paying customers?
Answers
I believe in MVP (Maximum Validated Product). The more you get customer/user validation, the more robust and complete the product becomes. It's smart to begin testing immediately to collect data that can help road mapping for the next product build improvements. Launch early with a few lighthouse customers to get the following (but not exhaustive) information:
• Validate improvement over previous product iterations
• Validate visual fit as a lightweight QA process
• Supplement quantitative A/B testing to investigate user preference from a qualitative perspective
• Identify missed usability issues or awkward product flows
• Show use cases of a product in multiple environments (Desktop vs. Mobile)
• Collect user feedback and hear their opinions, suggestions, and desired features lists
You are too late. You should have validated the buyability of your idea before you went further building it.
Having built and stabilized it, you should have already launched. Everyday, as you hesitate, you are loosing
Customer Insights
Marketing Insights
Product Insights
Mind Share
In any endeavor its about the momentum. If your competitor is on to it and is seeing momentum. You are staring at extinction.
Get it Launched. Now.
Worked in and around SaaS businesses for the last 10 years.
This is a careful dance. Obviously you want the product of high enough quality that it has utility for your users, but you could play that game in perpetuity. If you have customers using the product and getting value from it, release it and start charging. Paying customers often behave different than free users and will give you the real feedback you need. Maybe there are features your paying customers need that your free customers haven't surfaced.
It depends on how many prospective customers you have.
Do you only have 3 high profile customers that you think you can sell to, or are there 100s.
If there are 100s, simply write a few of them and ask them if they want to try out your product for free, since you identified them as "high profile" clients. (don't add the "" of course;))
If there are only 3, polish for another 1-2 months.
Related Questions
-
How can I manage my developers' performance if I don't understand IT?
Whenever you assign them a task, break down the task into small chunks. Make the chunks as small as you can (within reason, and to the extent that your knowledge allows), and tell your devs that if any chunks seem large, that they should further break those chunks down into bite size pieces. For instance, for the overall task of making a new webpage, _you_ might break it down as follows: 1) Set up a database 2) Make a form that takes user email, name, and phone number and adds them to database 3) Have our site send an email to everyone above the age of 50 each week When your devs take a look at it, _they_ might further break down the third step into: A) Set up an email service B) Connect it to the client database C) Figure out how to query the database for certain users D) Have it send emails to users over 50 You can keep using Asana, or you could use something like Trello which might make more sense for a small company, and might be easier to understand and track by yourself. In Trello you'd set up 4 columns titled, "To Do", "Doing", "Ready for Review", "Approved" (or combine the last two into "Done") You might want to tell them to only have tasks in the "Doing" column if they/re actually sitting at their desk working on it. For instance: not to leave a task in "Doing" overnight after work. That way you can actually see what they're working on and how long it takes, but that might be overly micro-manager-y At the end of each day / week when you review the tasks completed, look for ones that took a longer time than average (since, on average, all the tasks should be broken down into sub-tasks of approximately the same difficulty). Ask them about those tasks and why they took longer to do. It may be because they neglected to further break it down into chunks as you had asked (in which case you ask them to do that next time), or it may be that some unexpected snag came up, or it may be a hard task that can't be further broken down. In any case, listen to their explanation and you should be able to tell if it sounds reasonable, and if it sounds fishy, google the problem they say they encountered. You'll be able to get a better feel of their work ethic and honesty by how they answer the question, without worrying as much about what their actual words are. Make sure that when you ask for more details about why a task took longer, you don't do it in a probing way. Make sure they understand that you're doing it for your own learning and to help predict and properly plan future timelines.LV
-
How important is coding knowledge in starting a SAAS business? Should I start by learning code or just get started on the idea? Book suggestions?
I started a large SaaS Company for B2B where perfection in code is as importante as it gets. So here is my advice, DON'T CODE until you know what the Saas Really is. First start understanding what the problem REALLY is. Interview people and actually spend 100% of your time doing Customer Discovery. (This sounds easy but it is a skill you'll have to develop far more important than coding). Once you understand what the problem is, come up with a value proposition. Still no code. Then make a sell. If you can actually find things already existing that you can Hack and put it together then use that. Then make another sell. If you can sell it to at least 50 people if you are B2C, or if you are B2B you should have at least 1 customer. Once you do that then start automating some parts of the solution that you have hacked and so on. But THE most important thing is to be in constant conversations with your customers and hot leads. Remember you are a customer making machine not a coding machine, the first one is where the money is. Hope this helped you, if you want to talk more about customer discovery and customer development, just give me a call.JC
-
What are the SaaS B2B expectations when paying annually - annual paid annually or annual paid monthly? Is a discount necessary (i.e. 20%)?
Most Software as a service vendors generally don't book annual deals except in highly specialized cases. Most customers prefer to be able to cancel/change anytime they choose. Also, deals done "offline" end up actually often being more trouble than they are worth to administrate especially for a $2988 ticket. Generally, companies don't view prepaying for SaaS products a year in advance as a "convenience" (to them) so if the debate is internal (not customer driven), I'd set this debate aside until it's requested by the customer. Most customers will request a discount to pre-pay annual service. Happy to talk this through with you in a call, to work through the specifics of your situation in more detail.TW
-
Does anyone know of a good SaaS financial projection template for excel/apple numbers?
Here is a link to a basic model - http://monetizepros.com/tools/template-library/subscription-revenue-model-spreadsheet/ Depending on the purpose of the model you could get much much more elaborate or simpler. This base model will help you to understand size of the prize. But if you want to develop an end to end profitability model (Revenue, Gross Margin, Selling & General Administrative Costs, Taxes) I would suggest working with financial analyst. You biggest drivers (inputs) on a SaaS model will be CAC (Customer Acquisition Cost, Average Selling Price / Monthly Plan Cost, Customer Churn(How many people cancel their plans month to month), & Cost to serve If you can nail down them with solid backup data on your assumption that will make thing a lot simpler. Let me know if you need any help. I spent 7 years at a Fortune 100 company as a Sr. Financial Analyst.BD
-
For a SaaS, I find that Stripe is not available to Indian companies. What are other Stripe-like payment gateway options for Indian companies?
there is Balanced, Dwolla, Braintree but none of them seem to work in India yet.HJ
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.