This website uses cookies to better the user experience of its visitors. Where applicable, this website uses a cookie control system, allowing users to allow or disallow the use of cookies on their computer/device on their first visit to the website. This complies with recent legislative requirements for websites to obtain explicit consent from users before leaving behind or reading files such as cookies on a user’s computer/device. To learn more click Cookie Policy.

Privacy preference center

Cookies are small files saved to a user’s computer/device hard drive that track, save, and store information about the user’s interactions and website use. They allow a website, through its server, to provide users with a tailored experience within the site. Users are advised to take necessary steps within their web browser security settings to block all cookies from this website and its external serving vendors if they wish to deny the use and saving of cookies from this website to their computer’s/device’s hard drive. To learn more click Cookie Policy.

Manage consent preferences

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Cookies list
Name _rg_session
Provider rubygarage.org
Retention period 2 days
Type First party
Category Necessary
Description The website session cookie is set by the server to maintain the user's session state across different pages of the website. This cookie is essential for functionalities such as login persistence, ensuring a seamless and consistent user experience. The session cookie does not store personal data and is typically deleted when the browser is closed, enhancing privacy and security.
Name m
Provider m.stripe.com
Retention period 1 year 1 month
Type Third party
Category Necessary
Description The m cookie is set by Stripe and is used to help assess the risk associated with attempted transactions on the website. This cookie plays a critical role in fraud detection by identifying and analyzing patterns of behavior to distinguish between legitimate users and potentially fraudulent activity. It enhances the security of online transactions, ensuring that only authorized payments are processed while minimizing the risk of fraud.
Name __cf_bm
Provider .pipedrive.com
Retention period 1 hour
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to support Cloudflare Bot Management. This cookie helps to identify and filter requests from bots, enhancing the security and performance of the website. By distinguishing between legitimate users and automated traffic, it ensures that the site remains protected from malicious bots and potential attacks. This functionality is crucial for maintaining the integrity and reliability of the site's operations.
Name _GRECAPTCHA
Provider .recaptcha.net
Retention period 6 months
Type Third party
Category Necessary
Description The _GRECAPTCHA cookie is set by Google reCAPTCHA to ensure that interactions with the website are from legitimate human users and not automated bots. This cookie helps protect forms, login pages, and other interactive elements from spam and abuse by analyzing user behavior. It is essential for the proper functioning of reCAPTCHA, providing a critical layer of security to maintain the integrity and reliability of the site's interactive features.
Name __cf_bm
Provider .calendly.com
Retention period 30 minutes
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to distinguish between humans and bots. This cookie is beneficial for the website as it helps in making valid reports on the use of the website. By identifying and managing automated traffic, it ensures that analytics and performance metrics accurately reflect human user interactions, thereby enhancing site security and performance.
Name __cfruid
Provider .calendly.com
Retention period During session
Type Third party
Category Necessary
Description The __cfruid cookie is associated with websites using Cloudflare services. This cookie is used to identify trusted web traffic and enhance security. It helps Cloudflare manage and filter legitimate traffic from potentially harmful requests, thereby protecting the website from malicious activities such as DDoS attacks and ensuring reliable performance for genuine users.
Name OptanonConsent
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonConsent cookie determines whether the visitor has accepted the cookie consent box, ensuring that the consent box will not be presented again upon re-entry to the site. This cookie helps maintain the user's consent preferences and compliance with privacy regulations by storing information about the categories of cookies the user has consented to and preventing unnecessary repetition of consent requests.
Name OptanonAlertBoxClosed
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonAlertBoxClosed cookie is set after visitors have seen a cookie information notice and, in some cases, only when they actively close the notice. It ensures that the cookie consent message is not shown again to the user, enhancing the user experience by preventing repetitive notifications. This cookie helps manage user preferences and ensures compliance with privacy regulations by recording when the notice has been acknowledged.
Name referrer_user_id
Provider .calendly.com
Retention period 14 days
Type Third party
Category Necessary
Description The referrer_user_id cookie is set by Calendly to support the booking functionality on the website. This cookie helps track the source of referrals to the booking page, enabling Calendly to attribute bookings accurately and enhance the user experience by streamlining the scheduling process. It assists in managing user sessions and preferences during the booking workflow, ensuring efficient and reliable operation.
Name _calendly_session
Provider .calendly.com
Retention period 21 days
Type Third party
Category Necessary
Description The _calendly_session cookie is set by Calendly, a meeting scheduling tool, to enable the meeting scheduler to function within the website. This cookie facilitates the scheduling process by maintaining session information, allowing visitors to book meetings and add events to their calendars seamlessly. It ensures that the scheduling workflow operates smoothly, providing a consistent and reliable user experience.
Name _gat_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _gat_UA-* cookie is a pattern type cookie set by Google Analytics, where the pattern element in the name contains the unique identity number of the Google Analytics account or website it relates to. This cookie is a variation of the _gat cookie and is used to throttle the request rate, limiting the amount of data collected by Google Analytics on high traffic websites. It helps manage the volume of data recorded, ensuring efficient performance and accurate analytics reporting.
Name _ga
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga cookie is set by Google Analytics to calculate visitor, session, and campaign data for the site's analytics reports. It helps track how users interact with the website, providing insights into site usage and performance.
Name _ga_*
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga_* cookie is set by Google Analytics to store and count page views on the website. This cookie helps track the number of visits and interactions with the website, providing valuable data for performance and user behavior analysis. It belongs to the analytics category and plays a crucial role in generating detailed usage reports for site optimization.
Name _gid
Provider rubygarage.org
Retention period 1 day
Type First party
Category Analytics
Description The _gid cookie is set by Google Analytics to store information about how visitors use a website and to create an analytics report on the website's performance. This cookie collects data on visitor behavior, including pages visited, duration of the visit, and interactions with the website, helping site owners understand and improve user experience. It is part of the analytics category and typically expires after 24 hours.
Name _dc_gtm_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _dc_gtm_UA-* cookie is set by Google Analytics to help load the Google Analytics script tag via Google Tag Manager. This cookie facilitates the efficient loading of analytics tools, ensuring that data on user behavior and website performance is accurately collected and reported. It is categorized under analytics and assists in the seamless integration and functioning of Google Analytics on the website.

Minimal Marketable Product vs Minimum Loveable Product: Building Upon an MVP

  • 31718 views
  • 9 min
  • Aug 15, 2017
Irina M.

Irina M.

Copywriter

Oleksandra I.

Oleksandra I.

Head of Product Management Office

Tags:

MVP

Share

Many of us are familiar with the concept of a Minimum Viable Product (MVP) and its benefits for startups. An MVP helps you deliver your idea to early adopters and gather feedback to make improvements. But did you know that you can create an easily sellable product by building a Minimal Marketable Product (MMP) or a Minimum Loveable Product (MLP)?

Sure, an MVP is perfect to convey your product’s basic features and value to customers and investors. However, it doesn’t display everything your product can be. An MVP is a base upon which you can develop an MMP or an MLP, depending on your goals and resources.

Let’s find out more about these two concepts and what advantages they offer your business.

Minimal Marketable Product

To understand what a minimum marketable product is, we need to look at the origin of this term. Imagine you’ve developed the first version of your MVP. You’ve tested your idea, gathered feedback, and iterated. This cycle can go on for a while until you arrive at a version of your product that potential customers will want to buy.

Think of it this way: an MMP is a combination of several versions of your MVP. As you improve upon each version, an image of the most efficient and compact form of your product is built.

MMP structure formula

So how exactly is an MMP different from an MVP? The purpose of an MVP is to validate your business idea and determine which problems need to be solved to make users willing to pay money for the product. A minimum marketable product is an MVP that has been repeatedly improved until becoming a sellable product.

Advantages of an MMP

The most uncertain thing about a product under development, and at the same time the most important, is its future. No amount of market research can predict how a product will do after its introduction to users. A minimum marketable product can help minimize losses in case of failure and ease the lack of comprehensible market development foresight

It’s possible to look at MMP as a safety cushion in a number of ways:

  • An MMP reduces time to market, which in turn allows you to adjust to user needs and respond accordingly instead of trying to guess what customers want.
  • With an MMP, development is cheaper, which increases return on investment in case of success.
  • An MMP’s minimalism reduces financial investment, which mitigates risk – less money is lost in case of underperformance.   

How can we ensure that our MMP comes with all of these advantages and that its first version is a sellable product? This is where building upon the MVP concept comes into play.

The incorporation of several versions of an MVP in an MMP comes with two key benefits:

  • Each MVP refines a final MMP version by acquiring feedback and making room for improvement. 
  • Customer retention is increased since users are involved in product development and experience improvements firsthand.

Ensuring a smooth transition from MVP to MMP

We’ve already established that building an MMP on the basis of an MVP can lead to more efficient results. Now we want to highlight the essential points for making an effective shift from MVP to MMP that secures your product’s successful release.

  • Reliability. Make sure to iron out any potential glitches in your product before its release. Although you can rely on an MVP to catch issues during beta testing, don’t rush to give users access to your MMP too early. It has to be ready for use when it’s introduced to the market.
  • Scalability. Assuming your product is useful and effective, you might experience an inflow of users upon release. You need to prepare for accelerating number of signups with a scalable platform that can handle increasing traffic.
  • Performance. The speed of your product is essential, even if it isn’t web-based. Any delay in response can lead to the loss of customers. Test your product performance repeatedly and in different ways before its release to market.

At this point, don’t forget that just like an MVP, your minimum marketable product has to solve a problem. Achieving excellence in product performance and durability doesn’t ensure usefulness to prospective customers.

Always remember that the most important criteria upon which your product will be judged are its value and the effectiveness of its solutions.

Minimum Loveable Product

Similar to an MVP and an MMP, a minimum loveable product is the simplest version of a sellable product that can be introduced to the market. But while an MVP is a bare product stripped of non-functional elements, an MLP strives to be a product that can delight customers to the point where they praise it and recommend it to their friends.

The image below demonstrates the difference between an MVP (left) and an MLP (right). As you can see, a viable product is only developed to be functional, while a loveable product incorporates a bit of functionality along with reliability, usability, and emotional design. 

MVP vs MLP pyramids

How can you know if the product you’re building is loveable? The following characteristics will help you differentiate an MLP from an MVP or MMP: 

  • Your MLP must be unique, meaning there are no products like it on the market – not necessarily in terms of its function, but in terms of its appeal. This avoids competition and possible analogues, providing customers with a one-of-a-kind experience. 
  • An MLP is a marathon, not a sprint. Customer love is developed over time. At the testing stage, gaining your audience’s interest will be enough. Once you have their attention, you can gradually build toward receiving their love. 
  • After introducing your product to the market, people will start contacting you to gather as much information as possible about your MLP: release date, functionality, and so on. 
  • Prospective customers will display visible emotions when you’re describing the product to them, either positive or negative. Don’t be afraid of negative reactions; the most important thing is to avoid neutrality or disinterest. 
  • If your product is loveable, you’ll be eager to use it yourself and look forward to adding new features. 

Creating an MLP means creating a product the users love instead of tolerate. 

MLP image

Benefits of an MLP

What sets a minimum loveable product apart from a minimum viable or a minimum marketable product? To answer this, we must highlight the advantages of creating an MLP based on your idea:

  • The product becomes customer-oriented. When a team is working on a loveable concept, they’re thinking about users and how to serve them. With viable and marketable products, ideas are business-oriented, leaving customer accountability on the sidelines.

  • User involvement is drastically increased. As the product’s lovability goes up, so does the emotional interaction with customers. Small details that center on the user promote loyalty at every step of the experience.

  • The team is kept on the same course. By eliminating multiple versions of the product, the team focuses on the original strategy, perfecting it along the way. The steady application of customer expectations ensures successful realization of the idea.

  • The product reflects your company’s image. When you’re releasing viable products onto the market, you most likely aim to convey their functionality. With an MLP, you tie the product to your company’s strategy and vision to create an emotional connection with the customer. An MVP is replaceable, but an MLP is an integral part of your organization.

While an MVP is a fast way to get your product to market and an MMP is a sellable product by the time it’s finished, an MLP combines these ideas. It’s fast because of the team’s focus and it’s sellable because it was developed with customers’ needs in mind.

How to shift from an MVP to an MLP

Unlike an MMP, a minimum loveable product doesn’t include several versions of an MVP; it simply improves upon its viable concept. You don’t even need to finish an MVP to start creating an MLP; all you need to do is determine your product’s value and focus on its minimal features to then move on to achieving lovability.

Let’s go over how you can start building your MLP step by step: 

  • Establish a timeframe
  • Assemble a group of the most enthusiastic and efficient people in your organization and assign them to the project. Then create a workshop where you can map out your path to success from start to finish. In addition, put constraints on your time and budget.

    By setting a deadline for each stage of the project and limiting financial investment, you reduce the scope of work. This means that you and your team will be forced to come up with a fast and cost-effective solution. You’ll also have to adjust to restrictions and learn to build a compact MLP without sacrificing its value. 

  • Decide on one idea and start working on it
  • Determine a clear purpose for your product and focus on making a feature that can help you achieve this purpose perfectly. Ideally, the final concept should solve a customer’s problem as well as convey the product’s unique value to users.

    The founders of Waze, John Boudreau and Steven Rice, say “Fall in love with the problem, not with the solution,” meaning that as long as you know every aspect of the issue, you’ll be able to come up with a superior solution. 

  • Add an element of surprise to impress users
  • Imagine a plain cake: no decorations on top, just some bare layers and frosting here and there. Yes, it serves its purpose, but it leaves the customer underwhelmed. Then take the same cake but heavily frost it and decorate it with fresh fruit. Now it has character and evokes positive emotions.

    Apply the same strategy to your product to make it appealing. 

  • Make an effort to gain a following
  • Once your product has been released to market, it will start to acquire customers. You need to hook those customers and develop a sense of community associated with your MLP.

    You can start by setting up a social media page dedicated to your product. Make it as friendly and engaging as possible, and soon your customers will become active and add unique content that will speak to other prospective users.

Incorporating the concept of lovability into your product helps your idea stand out. Most likely, your target market is filled with viable products that solve the same problem. By adding a little extra thought to the product’s appeal you can disrupt a stable market and catch attention.

Now that you’re familiar with the concepts of a minimal marketable product and a minimum loveable product, you can correlate them with your goals and pick the one most suitable for you. Once you’ve chosen your strategy, the RubyGarage team can assist you with bringing your idea to life.

CONTENTS

Tags:

MVP

Authors:

Irina M.

Irina M.

Copywriter

Oleksandra I.

Oleksandra I.

Head of Product Management Office

Rate this article!

Nay
So-so
Not bad
Good
Wow
2 rating, average 5 out of 5

Share article with

Comments (0)

There are no comments yet

Leave a comment

Subscribe via email and know it all first!