Live data from Hacker News

One-man SaaS, 9 Years In

blog.healthchecks.io

121–130 of 221 posts

Re: One-man SaaS, 9 Years In

#121
post #86

Earlier quoted context omitted.

Stealing ideas is a lot of work.

Right. And it is even more work to, you know, actually (as in real life deploy) implement the copied business idea, and then to keep it running on an ongoing basis, showing up daily, even if not for a mad number of hours. This is the point where most of the glib talkers would fail, early.

Also, I totally agree with what sharmi says here:

https://news.ycombinator.com/item?id=41106276

Re: One-man SaaS, 9 Years In

#122
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 and it's ok to just not work some days.

- finding a niche is hard, but they can be surprisingly basic. You're just saving someone time, effort, worry etc.

- lean on global cloud services for reliability. Let them do that.

Re: One-man SaaS, 9 Years In

#124

Do you do marketing as well? I'd assume not based on the no JS-analytics so I'm curious what your customer acquisition methods are, as in how they find out about your business?

Author here, I think most new signups are through traffic from search engines and through word of mouth, Healthchecks.io gets regular mentions in Reddit /r/selfhosted. I've dabbled with paid ads (Google search, Reddit, Twitter, EthicalAds) but without analytics it was shooting in the dark.

Re: One-man SaaS, 9 Years In

#125

Earlier quoted context omitted.

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…

That is not answering the question. How do you do to get alerted of your service going down when: - you are in the wilderness, ouside or with little cell coverage - drunk and dancing in a wedding with music at full blast These are just 2 small examples out of many others. Also it means you need to stay connected when taking a plane, be able to stop and/or swap drivers if your are in a long driving trip so that you ca…

Even Google has outages sometimes. The chances of an outage happening at that exact moment when you are "drunk and dancing at a wedding" are probably lower than "catastrophic deployment failure at FAANG, multi-hour outage", especially because you are certainly not deploying any changes at that time. And if the outage is due to a third-party dependency failing then you can blame it on them and there's not much you could do even if you were online anyway.

Re: One-man SaaS, 9 Years In

#126

I wish the best for OP but I really wonder if advertising your one-man-SaaS to the wider world is a good idea. Especially on a forum like HN where competent people are few clicks away from stealing your idea.

90% of the difficulty in booting a competitor is unrelated to copying the product. It's in finding and then convincing customers to spend money with you.

Re: One-man SaaS, 9 Years In

#127

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.

Re: One-man SaaS, 9 Years In

#128
If anyone wants some one-man-SaaS ideas, here's a few which I desperately want. Somebody please build these and let me know! I already have my own startup so I don't have time to build these other ideas.

- A cheaper and simpler version of visualping.io, they used to be really good but now they're too expensive and enterprise-y. Would be easier and better with AI.

- AI-based email assistant which instantly brings up the entire history of contact I had with a person (even if they used a different email or sent to a different inbox) and can quickly be used to draft replies based on that history and a set of canned response templates. Note that I don't want a full email client, I want to use my own email client, I just want an assistant that is plugged in via API/whatever. Yes I've already tried all the alternatives in this space like Mailbutler/Spark/Superhuman but they're all crappy and force you to be locked in to their client.

- An Apple TV/Android TV app for the Anki memorization app. Lots of people have made successful Anki plugins and little hardware devices and made good money, like AnkiRemote.com. TVs are extremely well suited to laid-back studying and memorization, so you could easily promote this within the Anki student community if you made one.

Re: One-man SaaS, 9 Years In

#129

Inspiring! 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?)

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.

I swear to god that this is the future.

Re: One-man SaaS, 9 Years In

#130

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…

150k users supported by one man holy shit! This is obviously a B2C freemium app, right? Would love to see a writeup on how you handled the devops/deployment for this. Load balancers, serverless, or just one baremetal server?
Post reply on HN