Loading...
Answers
MenuFor Initial Users: Sell User License or make it into SaaS?
For initial users we believe selling individual user license are better until we know issues that we will have to deal with if we go SaaS.
Should we go SaaS? or Sell Individual License?
Can someone list hosting related problems (bandwidth, outage etc.) and how to tackle with them while selling SaaS?
Answers
SaaS. Always.
I am a founder of a Startup about to launch our first product (mobile app). We looked at this very question. In the end we looked at the impact the decision would have on our company's valuation. Based on my initial, informal discussions with funders in my area (Canadian Atlantic Region) with single point of sale revenue a healthy technical start up is worth approximately 4-6X annual revenue whereas the same company with a subscription or SAAS model is worth 10x and up.
Always default to SaaS and only offer one-off licenses in exceptional circumstances.
Is your product for individuals, SMB's or larger enterprise?
I've spoken with many entrepreneurs who have sold products on a per-license and all of them are either in the process of transitioning to, or are already, selling their product under a new SaaS model.
The cloud infrastructures in place today make launching a SaaS product much, much easier for the average developer. The common term for these is "PaaS" or "Platform As A Service" and they vary from very 'generic & flexible' cloud platforms like Amazon Web Services (AWS) or Digital Ocean, to more specialised services like Heroku (Ruby on Rails), MongoHQ (MongoDB databases), PagadoBox (PHP).
All of these services have some kind of free tier for getting a new app started and for development, and then have very granular pricing for slowly scaling the cost of your cloud hosting with the size of your offering.
Nearly all platforms offer redundancy once you're on a paid tier, meaning if their physical hardware has a failure, your app will automagically be moved to a new piece of phsyical hardware and thus you'll have minimal/zero downtime. As you scale up, you can make this even more sophisticated with the right sys admin team working on it for you.
If you're launching a pretty simple B2B SaaS app like a project management or invoicing app, then your hosting costs will be negligible compared to your scale & revenue (excluding employee cost to manage). If you're launching something that involves media (pictures, videos, MP3's) then even on cloud PaaS, your hosting costs will still be quite significant, and you should have a chat with someone to estimate your costs first.
I built a SaaS product (KeepMeBooked) which was specifically targeted at people using traditional installed software (owners of guesthouses and B&Bs using Outlook or some other old-school calendar system installed on their PC to manage their guests and reservations).
It sounds like you are considering this problem from the point of view of what’s best/easiest for you. Might I suggest that you look at it from the customer’s point of view?
For the customer, is your product more useful as an on-premise installed product, or as SaaS tool?
(I’m assuming, by the way, that when you say ‘individual user licence’ you mean the user installs and hosts the software on their own computer(s). So we are comparing SaaS with on-premise software here, is that right?)
In my experience, almost all software solutions work better for the customer if they are SaaS: no installation issues; access from any internet-connected computer; everything safely backed up in enterprise-grade data centre; no version control problems; etc.
The few exceptions to this are typically where you need fast data-entry and rapid processing. For example, I use Google Spreadsheets for simple little spreadsheets, but go back to Excel if I need some hard-core number-crunching. Waiting a few milliseconds after each action in Google Spreadsheets slows things down too much for me.
Or where the customer is extremely sensitive about their data and won’t countenance it being controlled by someone else, however safely and carefully you look after it.
So, I’d suggest, you outline how a SaaS solution for your product would work and talk to your customers about whether it will solve their problem better than an installed product. They might not know, of course, so you’ll have to ask some careful and probing questions. As Henry Ford said, if you ask the customer what they want they’ll tell you to build a faster horse.
You’ll need to find out if accessing the product from any computer is useful to them, for example (do your customers work from an office and from home? Do they often change / upgrade their computers?) And what backup solution do they have with your installed product? Is that backup solution safe and reliable? Would your SaaS solution be better from that point of view? And so on.
If it turns out that a SaaS solution would be better for your customer, then it “just” comes down to you figuring out how to implement it.
Hosting and bandwidth shouldn’t be too much of an issue these days. There are plenty of wel-established cloud platforms (like Amazon EC2 and Heroku) where you just pay for the computing power and bandwidth as you need it, and you don’t worry about the details of the physical infrastructure. I’m no sysadmin expert, so can’t really advise on pros and cons of having your own hardware in Rackspace compared to running a load of EC2 instances. But I’m sure you can find someone on Clarity who is. In my businesses we’ve used BrightBox (a managed hosting provider in the UK), Amazon and Heroku, all of which were excellent. We also used NewRelic and Pingdom to keep an eye on everything 24/7 and troubleshoot performance / availability issues.
Hope that helps. Happy to take a call if you'd like to speak further.
Related Questions
-
What is the point of having multi-year contracts in SAAS if the customer does not pay upfront for the 2nd year?
If you have an enforceable contract, the client is obligated to pay for the services received. As a business owner, I would be very concerned if a SAAS was demanding upfront payment for 2 years.SN
-
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
-
Will moving my website to another web host / server affect my google rankings?
Typically just moving from one server to the next has no issues at all so long as you're not making any other changes to the site, such as changing URLs in a re-design process. Just make sure its a quality, respected server. If the server has issues then, yeah, you'll inherit them. But otherwise you'll be fine.SD
-
What's the best way to sell a SaaS prior to launching?
I was involved with a SaaS product that launched a landing page and made clear that the product was still in development, but that we would give earliest access to people who pre-paid for the product. We also allowed people to choose what they paid, and promised them that payment would stay in-effect for several months. We generated revenue the first day of posting the landing-page publicly and increased revenue month-over-month. However, we discontinued the product as it was simply not big enough of a market for us to justify continued time and energy. But I would encourage you to pursue a similar model in that it's a great way to test and validate the pain others experience for the problem and a great way to ensure you're building the product to satisfy real customers. Happy to talk this through in more detail in a callTW
-
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
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.