Earlier quoted context omitted.
That's how essentially 99% of businesses get started. The obsession with PMF and being "unique" is a very strange affectation specific to software startups.
Being unique is important if you actually want to dominate the market. A product like his has captured a piece of the pie, but someone with equal distribution can easily eat into that since he has no moat.
One-man SaaS, 9 Years In
71–80 of 221 posts
Re: One-man SaaS, 9 Years In
#72Re: One-man SaaS, 9 Years In
#73Inspiring! 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…
This is so true. To me, finishing writing the code means releasable code. I have done the testing along the way.
Re: One-man SaaS, 9 Years In
#74Earlier quoted context omitted.
That's how essentially 99% of businesses get started. The obsession with PMF and being "unique" is a very strange affectation specific to software startups.
Unlike regular businesses, software scales infinitely and delivers immediately. You absolutely must have a "unique" selling point, even if it's just being cheaper. Otherwise, your competitors are just a click away. I'd argue the author HAS found PMF, just not the kind that gets you to $1b.
I don't think you have to have a unique selling point all the times. You can make an exact product as the market leader and layer on top a distribution that you own or you sell the product to a underserved groups. It will work too. In fact, this way of doing business happens a lot to non software products.
Re: One-man SaaS, 9 Years In
#75Earlier quoted context omitted.
Being unique is important if you actually want to dominate the market. A product like his has captured a piece of the pie, but someone with equal distribution can easily eat into that since he has no moat.
His moat is his price. And it absolutely is a moat because most bigger competitors would not bother competing in the segment with even lower prices, as there’d be no upside
His moat is a combination of pricing + cost structure + time spent to cumulate the customer base.
If someone were to enter the market and try to take his business, they will have to consider if their conditions can result in the same offerings. I don't think it's easy to match the same offerings.
Re: One-man SaaS, 9 Years In
#76Inspired beyond belief. Personally I'd rather commit suicide than work for the slave drivers at apple and google who screwed my life over then gave me jobs proving their guilt.
Or you could, you know, have a normal job.
It's unbearable to have to work for someone imo.
I wish to be in charge of my life as much as possible.
Re: One-man SaaS, 9 Years In
#77Re: One-man SaaS, 9 Years In
#78Earlier quoted context omitted.
Literally every software I have ever used or company I worked for has had multiple competitors doing the exact same thing.
I really doubt "literally" every software you used or worked for has multiple competitors doing the "exact" same thing. VC money can temporarily prop up multiple competitors doing the same thing, but over time, winners definitely spring up. A lot of software that on the surface does the "exact same thing" often has different nuances, either to the business or the product that makes them appeal to different niches in…
They could all be replaced and do 90% of the job immediately and a week later figure out the last 10%.
As as for work, coinbase is not the only exchange, square is one of many, meta is another social media site.
Re: One-man SaaS, 9 Years In
#79Inspiring! 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?)
If you’re not pushing code/changes the likelihood of incidents is significantly less. Also, not having a few enterprise contracts that make up most of the revenue, helps ease customer support load.