Funnily enough, I was about to cite the example of Freshworks (in that building SaaS companies from India gives one an unfair pricing advantage; and also that focusing on one product for a large but under-served (read: small companies) market that can be sold "repeatably" (read: feature set everyone needs) is the "key" before moving "upmarket" to large enterprises [0]) but it looks like you are an ex-employee and so you'd know all of this already!
That out of the way, a few follow-ups:
> ...we "assumed" people who used our competitors would use our product too. And when we were not able to sell, we thought It was because of lack of feature.
I mean, I'd naively think it to be true as well-- that not being able to sell (to target customers) would be usually be due to lack of features. If not that, what, you think, were some reasons Marketfox couldn't?
> At some point we blindly started copying features, without thinking why we need to build it.
You mean Marketfox didn't know if a missing feature (that a competitor had but Marketfox didn't) was important / critical but expended engineering resources on it anyway? If so, what you'd have done in its stead? How else you'd approach figuring out what to build?
Also, I am assuming Marketfox had access to founders/mentors who had done SaaS before... why you'd think that didn't make a difference (given your analysis that the mistakes you enumerated were avoidable)? What'd you, in the light of that, do differently?
Thanks.