I currently run two profitable SaaS products, ResumeMaker.Online and aiCarousels.com. They serve different purposes, but there is some overlap (design-focused), and they share a lot of front-end and under-the-hood AI stuff. And although it has some cons, I couldnāt recommend this approach enough.
First: platform risks. You build something on top of LinkedIn, Twitter, YouTube, or whatever platform thatās trending today, and youāre at their mercy. They change something, youāre screwed. Having two products has been my safety net.
But this safety net has extra benefits. It keeps you level-headed. Youāre not freaking out when a product churn spikes one month. You can make smarter decisions, not panic moves.
Youāve got options. You can experiment, try things out, and not have to worry about āthis product has to work or Iām screwed.ā
I used to have a 9to5 job. It felt secure until it wasnāt. When I got fired, it was stressful AS HELL. I only had one product at the time, and I knew I couldnāt rely on just that. Thatās why, after being let go, I decided to build aiCarousels, the first AI carousel generator (I documented the whole ride on YouTube).
Iāve been running ResumeMaker.Online as well, which helps people create resumes, theyāre different products, but because of the shared codebase, I can swap and improve features between the two easily.
The big challenge is probably finding two products that can share a codebase. But even if they canāt share everything, at least sharing the front end is worth it.
Iām not big on giving adviceā¦ I donāt know your personal goals, your market, or what you want out of this. But having two products lets me stay calm, make smarter decisions, and grow both without the constant fear of a single point of failure.
Yes, there are some cons (splitting my focus makes me feel like neither product is getting enough attention or growth it could), but I would recommend you AT LEAST give it a thought.