Company Product Fit
A framework by Manik Gupta arguing that the prior question to product-market fit is whether a product belongs in the company’s portfolio at all.
The argument
Every company has unique structural strengths and weaknesses. A product that would be excellent at one company becomes a distraction at another, regardless of its market potential. The test Gupta proposes: assuming this product succeeds, does it serve the right place in the company’s existing portfolio, and does it play to the company’s structural advantages?
Companies that build products because a competitor is building them fail the company product fit test almost every time. The competitive reactive impulse is precisely what the framework is designed to resist.
Relationship to product-market fit
Company product fit is the prerequisite: before asking “will users want this?” ask “should this company be building this?” A product that passes company product fit has the organisational infrastructure, data, distribution, and trust to execute. One that fails it will struggle regardless of market validation.
Where mainstream views differ
The dominant product discourse focuses heavily on user discovery, PMF, and growth mechanics — all of which assume the product already belongs in the portfolio. Gupta’s framework inserts a strategic question upstream. Critics might argue that structural advantage is itself mutable, and that some of the best products were built by companies where it was not obvious they “should” build them (e.g., Amazon building AWS).
Related
- Consumer Stack — the operational framework that follows once company product fit is established
- Manik Gupta on the Consumer Stack, Company Product Fit, and Building Consumer Products — source episode
- Manik Gupta — speaker page