Whenever an entrepreneur shares their idea with me, the following question always comes up, “is this a feature or a product?” Occasionally, it’s clear that this is a feature with product and platform potential, but most products, especially minimum viable products, start out as a feature solving a simple problem.

At Pardot, version one of our software tracked individual page views of prospects (micro web analytics) and captured web forms. Over time, email marketing, landing pages, scoring, grading, automation rules, drip programs, and more were added. At first it was a feature and then over the course of several years became a product.

Here are a few questions on the feature vs product debate:

  • How valuable is this functionality as a standalone application?
  • How much more valuable is this feature as part of a broader set of features?
  • How much of a nice-to-have vs a must-have is this functionality?
  • Are there existing products in the market that should add this feature? Why or why wouldn’t they do that?
  • Where is the market headed? More standalone features or products that combine features?

The feature vs product debate is ongoing, but one of the main takeaways is whether or not an ecosystem and industry gets built around the business (a product/platform) or if the business runs in more of a silo and offers a more limited, but highly focused, feature.

What else? What are some other thoughts on the idea of a feature vs a product?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.