Haha, I'm working on my second SaaS for one person :)
The first is drfreezr.com , something I built for a friend who manages a bioresearch lab and had trouble enforcing diligent bookkeeping about what samples are stored where in what freezers.
He and his lab colleagues are very happy with it, and they use it on a daily basis. But now I have to start marketing it. So the typical thing I do is optimize the code/UX/data model instead of finding more customers.
And now I'm working on a small-scale CRM for my wife (prototype phase) and her colleague who's she's started a consulting business with :)
That's awesome, man! Congrats on launching a successful SaaS! Now get your butt in gear and start marketing that sucker :)
Jokes aside, this is exactly the point of Seven Day SaaS and why I challenged myself to build ONLY for a week, then focus on all the rest after that. I set a rule for myself: no more feature releases or UX tweaks (aside from egregious bug fixes). Marketing and outreach only from now on!
Don't build something new until you validate what you have built. It's like that analogy of the guy mining for diamonds: you have no idea how close you are to success.
Good question, but yes, he did. Their main issue with spreadsheets was the lack of roles and permissions.
The tool makes it easy to allocate fridge space to users, which in turn makes it easier for the users to keep track of things. Also, users can't touch other users' stuff.
Also, the data per fridge cell itself is more complex than what fits in a spreadsheet row.
All this adds up to a much more user-friendly (and manager-friendly) experience, which leads to higher uptake among users and ultimately cleaner data.
I'm really really amazed how creative and productive someone can be. Meanwhile I can't even find one ideas. It doesn't help that I'm not an app user. I keep my digital stuff minimal.
Here's the cheat code for you: look at what businesses are constantly spending money on, and you will find plenty of business ideas. There will be competition, most likely a lot of it, but don't let that deter you. Competition means there's money to be made in the market, and people are already aware of the problem so that you don't have to educate them on why they need a solution (you will have to clearly communicate why your product is better, though).
When going after existing markets, you basically swap an idea validation challenge with a sales and marketing challenge. Before launching my business, I had a misconception that if you're already solving a problem, you don't have to do much marketing and sales - WRONG! You still have to get in front of existing customers, repeatedly.
Going after an existing market doesn't mean you have to launch a carbon copy of an existing product. You can differentiate by a price (probably not a good idea), by a combination of features, or by having a polished UI/UX/Developer experience. If your competitors suck, you can differentiate by virtue of not being broken (e.g. "Product X just works" can be your shtick). You can also out-market your competition (here's the one thing they don't want you to know: better products don't usually win over better-marketed products).
Why businesses you might ask? Because they're not reluctant to part with their money if you can either save or make them money. You will have a higher average revenue per user (ARPU), which means you can spend more money on acquiring customers (CAC is the term-of-art) than if you were in B2C. You will also need fewer customers to reach your revenue goals, which will translate into less support.
If your goal is to build a sustainable business, I think this is the most optimal approach to take. Just make sure you're not in the winner-takes-all type of market.
This is a really good comment. I would only add, don't go into a market that is too mature unless you have a very unique or niche approach.
Examples include CRM and Data visualization. The CRM market is 20 years old so unless you are serving a vertical that is highly underserved for some bizarre reason you could build it but no one would come.
I built Chartly in the data viz market, but wish I would have instead spend the time on Webase [1] which, as a no-code platform, is way earlier in the market lifecycle.
My favorite tool for this example is Whimsical. How many mind mapping and flow chart tools are there?
Whimsical built a new one with way less features and I’m suddenly creating flowcharts again because of how refined it is. Refined because all the cruft has been stripped out.
Choose a business process AVD build the MVP of it. The key here is also that it has to be lightning fast with a modern a aesthetic. But use something like Tailwind and prioritize the speed of every user interaction and you have a winner.
Thanks for your post. If you're launching a new product, how do you compete with products that have loads of features?
At a previous startup I worked for we wrote tax software, which was a well established and entrenched market. Our big thing was really cloud-based, but acquiring customers was often really hard because we were always missing that one feature that people really cared about (and it's never the same feature).
By doing the one feature people care about well. Don't look at huge products, look at really small niche ones.
e.g., there are lots of small businesses that need to write up bids for work and email the resulting quote as a pdf. That's it!
A lot of the competition is stuff like Salesforce or JobBoss or other ERP tools that are gross overkill for the 20-person welding shop, not to mention way outside their budget.
Or, as I found out from browsing commercial lawn care forums, people want scheduling apps that can take before and after pictures of lawns to email to the homeowner. There's another fairly small project that's useful and saleable.
You'll find that if you go down this path, the biggest challenge is going to be marketing and customer acquisition, not building the product. I'm always tempted to build small apps like this, but I keep going back to embedded work because it's more fun!
It's fun because I like controlling the real world through software, especially making things move. I have my fingers in three motion control projects of various levels of complexity as we speak.
So one approach I have used is to launch a very opinionated product. Don't try to be everything to everyone - this is where all those features come from. Focus on what you feel is the best workflow and promote it unappologetically. This works really well if you are also a current (or emerging) expert in the field because it's viable for a single builder to codify their best practices. You marketing should then highlight both your skill as the thought leader and your product as the easiest, most effective way to put what you're promoting into practice.
This won't necessarily work in a domain like tax software where the feature requirements are well understood, but does work in areas that have a step learning curve because it helps people adopt them.
> My SaaS is so opinionated right now that only one person is using it.
Heh heh! Don't worry, you just have to find one more person like that, and then those two find two others & so on and so forth. 2^64 is the planet.
I'm in the same boat. I have a tiny handful of middle school kids religiously using my app, but their parents are like, why isn't it like khan academy, or beast academy, or ixl, or aops, or whatnot. And I'm like, yeah those things are great, but how come your kids are hanging out on my site and not over there ? Sometimes you just have to stick to your guns.
Few successful business start out with loads of features. They start out with the most important subset of features they need to get enough clients in the beginning to survive. Then come the enterprise contracts strong arming them into developing niche features that almost no one else needs, growth targets that requiring catering to lots of individual users who each need their own niche feature X and Y to sell it to their boss, and competitors that require them to differentiate just to stay shiny in customers' eyes. The general advice for startups is to find a niche. Even if they're VC funded, they're supposed to find a niche at first because thats a way of delaying all that expensive development they will have to do to catch up with competitors until they can afford it.
The key is that feature development productivity is inverse to company size and revenue. The bigger they are, the more customers they have, and the more money they make, the more time and effort they have to spend just keeping everyone aware of changes, let alone actually deciding how to move forward and executing. This is the complete opposite of almost every other industry where economies of scale dominate so unless your niche has extreme network effects like Google's Search business or Facebook's social network, there will always be room for more competition.
> If you're launching a new product, how do you compete with products that have loads of features?
One way to compete with incumbents, in the beginning, is by niching down, and offering things they can't.
Using your tax software example, it'd make sense to start with a single persona first (e.g. Tax Software for US-based freelancers). By building a tool for the specific audience, you can offer an experience a generic tool can't (i.e. a sole proprietor doesn't care much about corporate income taxes, excise taxes, etc.). You will also have less competition if you decide to go down the paid acquisition route.
FWIW, I have noticed that some subset of my customers only use a particular set of features, and don't care much about the rest.
Another advantage of focusing on a niche is that people with similar characteristics tend to congregate in a handful of communities, which makes it relatively easier to reach them. At some point, you can hopefully take advantage of word of mouth, and that is an incredibly powerful way of acquiring new customers.
Also, when you're the person who built the service, you can offer support to customers in a way your established competitors simply can't. Caring about things is a competitive advantage.
Make no mistake about it: it's going to be incredibly hard. However, by going after the existing market, you minimize chances of market mistake, which is costlier than a product mistake (i.e. you increase your odds of survival).
P.S. Having an existing audience makes things easier. People buy from people they know, trust, and like, even if your offering isn't the best out there.
If you are launching a new product you can't compete against entrenched competition in breadth of features. You need to compete against them by finding a small niche use case or feature and becoming the best piece of software for that niche. Using your tax software example, you would want to become the best tax software ever for pet store owners (random example), then you capture 100% of the pet store market and move out from there.
One thing that seems to affect my creativity levels is how much I'm consuming. You're either a consumer or a creator. You can't be both at the same time.
In this case, he's solving a real problem for a real person. This means you need to know people with problems, and recognize that they are problems (they may not think so!) and believe you can improve it.
Of course, you can make something way better than what they have, and they still not use it...
Most of these apps are basically just visualizing database data, with some very simple business rules for transforming the database. If you use the right framework, it becomes very easy and building an app is basically like filling out a template. Of course, if you start from the wrong framework, writing such an app can be a real challenge.
Start a development agency and advertise where non-tech people would look for you. Yellow pages, facebook page, fill out your details so they show up on google maps.
You'll have a ton of businesses contacting you looking to have their ancient specialised software replaced or improved upon. They wont have a budget to make doing it just for them worthwhile, but it will be a fountain of SaaS ideas that come with built in validation and a first customer to learn the specifics from and act as a reference.
tl;dr: I built a glorified spreadsheet app called Bicycle (https://usebicycle.com) in seven days. Now I'm refining it for one user's needs based on principles from Do Things That Don't Scale by Paul Graham and the 1000 True Fans theory.
Haha right? I seriously don’t get how Elon Musk pulled 120/hr weeks on the regular. Well, actually I guess I kind of do, a little... if you are super passionate and invested that makes a big difference.
Anyway, I did this as part of my Seven Day SaaS Challenge (https://sevendaysaas.com), where the goal is to constrain the amount of time behind a keyboard coding in order to force real world interaction with potential users, alongside marketing and the businessy (aka critical!) parts of building a SaaS. But, I’m an overachiever and I had high goals for this app, hence cramming a lot into one week. :)
Agreed that 90+ or 120 are just insanely difficult to do on the regular. I think I could have 1 such week per month, maybe once per quarter. One thing that might be a bit different in your example is if all 90 hours were for the same product. It might have been tougher for you to pay some time context switching between the two. Whereas, Elon Musk is doing all his hours for the same task. (Well, actually he's a terrible example because he probably has 100 tasks he does for 1 hour each week, but you get my point for the general case.)
As of right now, I'm planning on directly targeting enterprise users for access to projects with varying levels of permissions at a low monthly rate per user, something like $10 to $20/mo per user (possibly less, if that's too high). Enough that I'm making $$, but also not something an individual contributor couldn't just expense without turning heads. And then enterprise plans on top of that.
How much do you plan to spend on customer acquisition? Often with small SaaSes, this is overlooked or grossly underestimated. The problem is building it and almost nobody showing up.
This looks great, but just wondering if you have looked at something like Airtable (https://airtable.com/) to solve this? I had a couple custom tools that were similar, but I've been able to replace them w/ Airtable and it has been nice to not maintain those anymore.
The first is drfreezr.com , something I built for a friend who manages a bioresearch lab and had trouble enforcing diligent bookkeeping about what samples are stored where in what freezers.
He and his lab colleagues are very happy with it, and they use it on a daily basis. But now I have to start marketing it. So the typical thing I do is optimize the code/UX/data model instead of finding more customers.
And now I'm working on a small-scale CRM for my wife (prototype phase) and her colleague who's she's started a consulting business with :)