This is what I'll check before building a SaaS product.

This is what I'll check before building a SaaS product.

1/ Is there a common issue frequently discussed in the help centre communities of major tech platforms?

For example, in Shopify, there's a limitation where you can't import products with columns that match your custom meta fields, and there's no manual option available in the bulk editor.

This can be incredibly frustrating, especially for those managing a large inventory.

Shopify might mention that they may consider building a solution for this in the future, but in the meantime, they'll suggest using a Shopify app (like Matrixify) to address the issue.

So Shopify would be your sales team.

2/ Is there a well-liked website, app, or community that everyone's itching to replicate, but it needs a specific set of development skills?

For instance, Product Hunt reigns supreme among tech startups, and many folks are keen to craft their own version.

Yet, the upvote system was notably absent in most website builders tailored for non-techy founders.

Then came Jetboost just when everyone was eager to recreate Product Hunt. It made it possible for anyone to whip up a replica in mere hours using Webflow, allowing them to mimic the exact design of Product Hunt or even improve upon it.

3/ Are there enough freelancers, agencies, or consultants available who can market and sell my product along with their services locally?

For instance, understanding your industry is crucial, and knowing which services are most commonly hashtag#outsourced within that sector will greatly impact your success.

Let's take an example: if you're developing a revenue management tool for the hospitality sector, the abundance of revenue and commercial consultants in that field is a positive indicator for finding potential partners.

Similarly, if you're creating a marketing tool, the presence of numerous marketing agencies can be advantageous. So you won't struggle to find resellers, guest writers and influencers.