I remember a time when I only wanted one big revenue stream. The idea of having multiple products and services sounded exhausting. But these days, I'm all about it. And not just for the excitement of it — diversifying revenue streams is always smart, and it's particularly so when there's talk of a recession.
So I've been thinking a ton about how to expand my offerings. Luckily, a lot of indie hackers are already clearing that path, so I looked into what they're doing. Here's what I've found. 👇
First off, it's worth mentioning that I've seen folks arguing both for and against starting multiple companies. Some of the most common reasons for doing it were:
All of that sounds great, so why not do it? The most common answer that I saw here on IH was that splitting focus means that each product gets less juice — all the products will take longer to become successful than if you were to just focus on one. And that's fair enough. Like Ron Swanson said, "Never half-ass two things; whole-ass one thing."
That's why timing it right is important, which I'll get to in a bit. You can actually mitigate that risk a bit.
@dohertyjf: Focus on the one that brings in the most revenue until you have a team mostly running that business, then you can put more time into the smaller one.
So here's how to do it effectively.
The trick is to be very strategic about what you build and what you don't. That means validating before you build a thing (via a landing page). And then building an MVP and validating with that. In other words, step-by-step validation so that the risk of starting a new business is minimized.
And there's more to it than that. Here's what some indie hackers had to say:
@tonydinh: I want to use my own products, so I can make them perfectly fit my workflow. I have a lot of ideas that I would build for myself, but I only build ones that have the potential to also get paying customers. It’s the sweet spot between “what I want” and “what people want” that allows me to build for myself and sell to other people.
Yes, step one is to make sure people will pay.
@dohertyjf: Pick one customer and build multiple things for them.
That's huge. You want each product to be within the same market and the same area of expertise. This will also help you grow your personal brand as an expert in that space.
@tonydinh again: Build products that require low maintenance effort.
Tony goes on to say that SaaS products require a lot of upkeep, while downloadable apps and info products are much easier. This is why he only has one SaaS, but multiple other products.
In addition to maintenance, it's important to consider the length of time that it'll take to build in the first place. In case it's helpful, here's a list of the fastest products to build.
Make sure the timing is right before you get started. As I mentioned above, it's gotta be validated. Beyond that, it really depends on your capacity and your other responsibilities. It's generally best if your first product is (at least partially) on auto-pilot. So bring it to that point first.
dohertyjf: Think hard about it, and make sure you are not doing it simply because you are bored, or because you're in the middle of something big and it feels hard. You don't want to be distracted and starve both businesses of growth. It's better to push through that hard patch or figure out how to make your current thing less boring.
Only once you've stabilized that first business and have a team running it, including an operator with strong business ops experience, should you look to start another business.
Most of us won't be bringing on teams like John did, but it is possible to automate processes and get the product into a good spot where it can coast for a bit. And that's what I'd suggest doing before you start building another product.
Ultimately, though, if you feel ready and you've got time, do it. Here's John again:
@dohertyjf: But there's also never a good time to start something like a new business. There are just those of us who don't let that hold us back.
And of course, all of this assumes you aren't doing something like a 12x12, in which case, the right time is as soon as you launch your previous product.
Ok, so let's say you moved forward and now you're building multiple products simultaneously. It's hugely important to be strategic about your prioritization — you'll need to know which task for which product needs your attention first.
There are about a million methods for prioritizing, and most are good in one way or another. My take is that the "DIE" method is best for indie hackers. But "Value vs Effort is" great in a pinch because it's quick and easy. I've noticed that "RICE" is very popular among indie hackers. Prioritizing by constraints is good if you have a specific constraint (in this case, probably time). And then, of course, there's going with your gut, which I'm a big fan of. 😎
Let's break them down:
It's worth noting that, in general, it's best to prioritize one product over another — have a primary product and a secondary product. Of course, priorities may shift as important tasks come and go, but an 80/20 approach favoring the product with the most potential can be a good idea.
@felix12777: I break down my roadmap and goals so that they're as small as possible. This makes it so I can see my progress and bring things together gradually.
It goes without saying that when you're rocking multiple products, you're going to need to be hyper-efficient. I like efficiency, so I've researched it a ton in my day.
A big part of efficiency is lifestyle. Take care of yourself! Eat healthy, sleep, exercise, stay hydrated, limit caffeine (counter-intuitive, I know) and alcohol, meditate, relax, and spend time with loved ones. Don't burn out — that won't make your products successful any faster! Prioritize work-life balance.
Then there's your mentality. Be okay with doing less! Say no. Focus on results; not hours. And set realistic expectations.
Set up an environment that lends itself to efficiency. Remove distractions and clutter, organize your space and make it a pleasant place to spend your time, and play focus music (or whatever gets you going).
And then there's your workflow. Break tasks into small pieces, batch similar tasks, and avoid multi-tasking. I'm a huge fan of using todo lists and/or project management software to keep things organized. Set a timer — the Pomodoro technique is fantastic. If something comes to mind that needs to get done, right it down, then keep doing what you're doing and circle back later. Accountability buddies can be a godsend (check out the tools below). Outsource when possible, and automate everything!
@tonydinh: The management can become very messy, real quick if you are not careful. Mixed revenue reports, shared accounts, email support, partnerships, multiple payment accounts, etc. — it took me quite a while to find a workflow to consolidate all this and I still have to improve it day by day.
This is a bit part of efficiency, but it deserves its own section. How you structure your day will determine how good you are at juggling projects. Here are a few tips:
If you create a schedule and it just isn't working for you, it can be a good idea to list what you do each day, what you should be doing, what you shouldn't be doing, and what you want to be doing, then restructure it. More on that here
@robhope — It's super difficult to shift attention so many times a day. Without a schedule, I can blink and I haven't posted on Email Love in 2 weeks.
Lastly, tools are your friend.
If you need some advice on solid project management tools to keep you on track, here's a post that breaks down some of the best.
As far as setting up business entities, I'd wait until you have some decent revenue. Not a lawyer, but that's my two cents.
If you already have an LLC, you can sell the new product under that. You can even create a DBA (doing business as), allowing you to set up a business bank account for your product and take payments. I wrote a post on this recently if you'd like to learn more.
I'm curious, how do you juggle it all?
Subscribe for more tips, how-tos, and case studies 👇
I think building multiple products is especially useful if you can somehow connect them. For instance, I'm building feez.ws and hosting it on stormkit.io. So it's a very nice opportunity for me to dogfood my own product and improve the user experience. Also, if Feez becomes popular, it's a win for Stormkit as well!
feez.ws is realliy smart and interesting. Can i talk about it on my newsletter ? The landing pre-sale is brillant. I want to present ways to pre-sale an idea. Have you thinked of making a template of your landing ? Think about it. Thank you.
Tried to check out your newsletter but the link on your Twitter isn't working. Just a heads up :)
Thanks for the kind words! I'd be super happy if you could mention it :) I actually wrote a blog post about the template here: https://vsk.me/blog/programming/all-in-one-ssr-ssg-spa-api but it's a template for tech people. But you're right, maybe I could provide ready-to-use landing page templates on Stormkit, thanks for the idea 🙌🏻
Yeah, that's a great point! And I agree with @mrehouri_a — solid landing page for validation/pre-sale.
Thank you @IndieJames for sharing such amazing info.
I will say this post has helped me gain a better understanding of the importance of having a clear strategy and vision when building multiple products.
In the past, we were in the trap of multiple projects but all did not provide a good result because of the multiple factors.
Then we started focusing on the one SaaS project which is helping membership businesses to reduce customer churn Churnfree customer retention tool.
Thank you for sharing the project management tools which you're using to increase productivity.
My pleasure! We’ve all been there :)
What a post! 👏🏼
Thanks! 😀
this is in sync with the "portfolio of small bets" approach by @dvassallo, which is in sync with my own approach of multiple small projects :-)
i think there is no better way if you are starting out and trying different things, building MVPs, etc. It is not only a matter of finding your "product market fit", but also about discovering your own strengths and weaknesses along the way and focusing on the intersection of what you can do best, and what the market wants.
Awesome post, as always @IndieJames !
Couldn't agree more. I think I've heard that called "product-founder fit" and "founder-market fit". So many "fits" to consider! 😅
Super interesting section about strategical work prioritize!
Will definitely get some inspiration from that for my product launch platform.
Thank you for posting such qualitative stuff James!
Glad it helped!
What a great post!
As a venture studio builder (I worked for one and am starting a mini venture studio) - this is exactly my approach.
To make it easier for myself, I've picked an audience I'd like to serve (in this case start-up founders) and implement this strategy:
Phase 1 - Build an audience I can co-create (and test) ideas with. This is my Twitter + newsletter.
Phase 2 - Create mini products as my MVP to test demand for the ideas. Let the ideas compete with each other for my time & money.
Phase 3 - Iterate by giving more growth fuel to the more promising ones. Kill the others.
Hit me up if anyone here wants to do similar things and share ideas.
Sounds like a good plan, good luck!
Great post. I hope you don't mind I've shared this post in my community of SideHustlers.com: https://www.sidehustlify.com/post/building-multiple-products-how-and-when-to-do-it-1674223241331
👍 Thanks for sharing
I like the idea of slicing attention to products 80/20.
If you do 50/50 you never have a clear decision which one to focus on.
I use RICE prioritization because it helps to unveil something important about new product ideas: Quite often the result is that the products I am already working on are the better "bet to place" then the new product ideas.
We slightly modified our prioritization framework from RICE though to make it better reflect product goals.
Nice, how did you modify it?
Yeah, I bet current products are the better bet most of the time! But sometimes you've gotta throw caution to the wind too 😎
Hi IndieJames, please excuse the late reply.
Here is the modification:
Remove confidence: it does not bring so much value in our context, we just try to estimate the other values as good as possible (not perfectly - just good enough to move forward). We aim to establish the an equal level of confidence for each other value, while accepting that it is never 100%.
Add Distribution channel:
A score for the availability of the distribution channel. Because depending on the product you already might have a distribution channel, or you need to build up a new one to reach your customer segment, which is additional time and effort and should not be underestimated (it's not a 'no' for a product, its just something you want to take into account when comparing alternatives).
If you have a new product which reuses the same distribution channels, thats much easier.
When you just use 'Effort' it might get blurry what is actually hidden behind that, and people tend to consider the technical effort only.
But I would say it depends on everyones own context whether such modification helps.
What do you think of those modifications, especially of the second one?
This definitely sounds like an interesting approach. Lots of low maintenance products vs one big one. It's also great for testing MVPs
How does one deal with customer support when they're all related to different queries?
I guess since they're low maintenance, they probably don't have too many queries.
I'm more of a build one product type of guy though. That's the main reason why I co-founded Evoke lol
Yeah, it really depends on what type of product you create. If you do one SaaS and some low-maintenance products, the lion's share of support will come from your SaaS. And regardless of product type, support won't usually get out of hand until you have a lot of customers... and that's a good problem to have! In the case that you have lots of support tickets for 2+ products, you might consider outsourcing it to a helpdesk or, even better, implementing some proactive support (FAQ, documentation, tutorials, tool-tips, user community, etc.)
I guess if you have lots of customer support questions coming in, it might mean a successful product.
In that case, it might help to drop the other ones and focus on that one :)
Some good advice this article. I'm still struggling with marketing, and by extension, product validation. That's something I'm working on...
I have multiple projects on the go. Roughly 50% of my work time goes to contract work (where most of the work comes from), then I have one main project that takes up the bulk of the remaining time. Then I have one side project, or two... and lots of ideas that are just going to have to wait.
Yeah, product validation can be tough! Splitting contract work and projects is smart though. Sounds like you've got a lot on your plate - good luck! 💪
Thanks for the timeivy.com mention, (and this is another gem of a post!).
I think it's typical for certain personality types to lean more towards this kind setup. Personally, I have always been working on different projects at the same time and most of those points align with my experience.
Not a lot to add, but I cannot emphasize enough the part about "compartmentalizing" things.
What has worked for me is to have scheduled blocks of work, that I stick to every day, (yes, with my own app ;) while also keeping part of my day open for unstructured work. That way, I can :
Well said!
That's funny, I actually just started blocking out my mornings for deep work, then my afternoons are unstructured. As a new father trying to build a few businesses, it's been working really well for me.
This is an amazing post! I debate the "half-ass" vs. "whole-ass" in my mind often. I have built up to 4 products at the same time and spent most of the time putting out fires/context switching most of the time.
I am currently building 2 products simultaneously. For me, I have found my "optimal" tech stack and built a solid wireframe to quickly spin up frontend, backend, DB. I try to stick to that as much as possible, so I can spend as much time building vs. juggling technologies.
Hah, yeah the "half-ass / whole-ass" dilemma is a tough one to figure out. It's crazy how much additional time context-switching takes. You think it'll take 30 seconds but in reality, it's way more than that somehow.
That's awesome that you've found your optimal stack and process. That's huge!
I just don't see how someone can effectively do two at once. Maybe after the first has a whole team and you can remove yourself... but until then, you're just losing focus.
I guess throuples just aren't for me. I'm a one-product kind of guy.
Yeah, I've always wanted to start another project but I don't know where I'd find the time. Maybe one day. I think Tony nailed it though — one SaaS, then a bunch of little products.