I have a similar style of business, ~10K customers, ~150k users, ~7yrs. The key points are: - offer email support, but don't offer phone, video calls or remote support. This works for most people and forces them to properly phrase questions instead of just "jumping on a call" (so you can then effectively train them over the phone, which doesn't scale). - offer as much self-service as possible - work at your own pace…
One trick I may or may not have invented for the enterprise PO problem (manual processes etc) was to offer an Azure Marketplace subscription for the product. That way they can just go to azure and subscribe to the license that way, without needing any azure resources etc, it's just a billing mechanism. They can then bundle that into their usual Azure spend and even do manual POs etc that I never have to deal with.
One-man SaaS, 9 Years In
171–180 of 221 posts
Re: One-man SaaS, 9 Years In
#172Earlier quoted context omitted.
I also have a one man show Saas with 34 companies paying that pays my bills. It runs on namecheap shared hosting. If it goes down, I trust namecheap to fix it asap. If it goes down and someone called me, I don't really know what I would do anyway.... In 6 years it has never been a problem. PHP and jQuery. I use phpmyadmin via cpanel to manage the database.
Care to share the product here?
Re: One-man SaaS, 9 Years In
#173Are there any solutions for one-man SaaS to handle payments from enterprise customers? I'm assuming that the preferred mode of payment here is through wire transfers after some kind of PO process.
Re: One-man SaaS, 9 Years In
#174How long did it take you to find your first paying customer and which channels did you find to be most successful in acquisition? I've just launched my own SaaS as a Solopreneur ( https://msgdrop.io ) and and trying to figure out where to invest most of my limited free time to grow it now.
Nice looking page? Did you design it? If so, where did you get the graphics? My design work looks like a kindergartener drew it with a fat crayon on Big Chief paper! ;-)
Re: One-man SaaS, 9 Years In
#175How long did it take you to find your first paying customer and which channels did you find to be most successful in acquisition? I've just launched my own SaaS as a Solopreneur ( https://msgdrop.io ) and and trying to figure out where to invest most of my limited free time to grow it now.
Paid advertising or organic marketing with reels/shorts and blog posts that are SEO optimized,lastly, a bit of luck.
Re: One-man SaaS, 9 Years In
#176Massive respect for the no growth approach. We’re different in that we’re a consultancy rather than a SaaS but 14 years into running our “micro agency” (my wife and I). We’ve had plenty of opportunities to take on staff but have always chosen not to in favour of working with trusted freelancers. Net result is an extremely contented life spent living by the sea in Cornwall and a gently profitable business. We'll never…
Re: One-man SaaS, 9 Years In
#177Earlier quoted context omitted.
I have the same problem. When I see the kinds of simple products printing HNers money I think “people pay for THAT?” Any ideas I do have I convince myself nobody needs, wants, or will pay for.
What blows my mind is that people tolerate paying monthly for what is a static service. A service routine monitor doesn't need to be updated every month to function, so why would anyone pay every month to use it?
Re: One-man SaaS, 9 Years In
#178How long did it take you to find your first paying customer and which channels did you find to be most successful in acquisition? I've just launched my own SaaS as a Solopreneur ( https://msgdrop.io ) and and trying to figure out where to invest most of my limited free time to grow it now.
Billing was ready in December 2015, and the first customer ($5 MRR) was in March 2016.
Re: One-man SaaS, 9 Years In
#179Inspiring! How do you handle on-call / customer support, particularly around vacations? (In other words, if you want to go away for awhile, how do you make sure any outages get resolved?)
One man army apps are generally dead simple to maintain and bug-fix. You write all the code, so when someone pings you with a problem you know exactly what caused it without any need to check for anything. I’ve maintained apps like that for years and have sometimes pushed a code change directly on the GitHub app on the phone and just checking if the site is fixed after. Another point is if you’re also your own produc…