A minimum marketable feature (MMF) is the smallest unit of new functionality that delivers enough standalone value to be worth announcing, selling or charging for. Where an MVP asks “what is the least we can build to learn?”, an MMF asks “what is the least we can ship that a customer would pay for or a sales team can lead with?” It packages scope by market value rather than engineering convenience: one coherent capability, complete enough to use in anger, small enough to ship in a release cycle.
The concept disciplines roadmaps in two directions. It prevents under-shipping — releasing fragments that technically work but change nothing for the buyer — and over-shipping, where teams gold-plate a capability long after its marketable core was done. Product organisations that think in MMFs sequence releases around value increments the market can absorb and reference: each one gets a name, a changelog entry, a pricing decision and a sales motion.
Commercial and contractual edges
MMFs surface in legal work through packaging decisions. Charging separately for a new feature raises pricing-and-terms questions for the installed base — does the existing subscription include “updates,” and what did the order form promise? Enterprise contracts with committed roadmaps or SLAs may treat a feature’s release date as an obligation, making the MMF cut line a compliance line. And in regulated products, the smallest marketable feature is sometimes defined by regulation rather than marketing: a payment capability is not marketable until the licence covers it, however small the code change was.
If this is on your desk
Templates and checklists are free in the Founder Academy; for a specific situation, book a 30-minute intro call.
Founder AcademyBook an intro call