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.

How to Build a Minimum Viable Product (MVP)

  • 185399 views
  • 9 min
  • Jan 02, 2020
Viktoria K.

Viktoria K.

Copywriter

Vlad V.

Vlad V.

Chief Executive Officer

Tags:

MVP

Share

What should you do if you have an idea for a product but you aren’t sure if you can successfully implement it? Bringing a new product to market is always a big risk. But to reduce the risk, you can first develop a minimum viable product (MVP). Have you heard about Airbnb and how they got started?

Back in 2008, when Airbnb was founded, there were two guys who couldn’t pay the rent. So they decided to transform their living room into a bedroom with air mattresses for three people. After they had earned some money renting out their living room, they built a simple website to offer their service on the internet. This first website didn’t have all the features of Airbnb’s current website, but it could still provide accommodations.

Based on the story of Airbnb – and other startups that began the same way – we can define an MVP as a product that provides only the single most important service (its core functionality). After this product is launched, you can test it on real users, learn from them, and continue improving and developing your MVP. One day, this MVP will become a fully-fledged product.

Now that we’ve established what a minimum viable product is, let’s figure out how to build an MVP in five steps.

Step #1 — Figure Out What Problem You’re Solving, and For Whom

The first step of successful minimum viable product development is evaluating your business idea. Start by asking yourself two questions to try to put yourself in your customer’s shoes: Why do I need this product? and How it can help me? Answering these questions will help you understand the main goal of your product and find the best solution to your future customers’ real needs.

We can call these “future customers” your target audience: the group of people who you’re hoping will buy and use your product. But why would they use it? You need to find a problem you can solve for your target audience. The best way to find a problem that needs a solution is to think about your personal challenges. Is there anything that you personally could do better if you only had the right tool? And can you actually create this tool? If you can’t find a problem this way, you can always look for problems within a particular segment of the market.

If we, for example, look back at how Uber started, we can see that it was initially an app to request premium black cars in a few metropolitan areas. Despite the fact that the usual meaning of ‘premium’ is expensive, Uber wasn’t expensive at all. Its service was aimed at an underserved customer segment, e.g. people who can’t afford to order a premium black car from a traditional taxi service because it’s too expensive. In the same way, you can find your own problem within a particular segment of the market and offer a solution.

Just imagine that you want to build an application that will help people save money. Saving money is a pretty obvious goal for many people. Nearly everyone would like a little extra money in their pockets. To save money you might use coupons and look for discounts on food, shoes, gifts, and other goods or services. These coupons and discounts can be found on the websites of shops, delivery services, etc.

But sometimes people don’t have time to look all over the web for these discounts, and as a result they pay more money than they need to for goods and services. Therefore you might develop an app that helps people search for discounts and coupons in an easier way and, most importantly, helps them save money. The primary goal of this product, therefore, would be to allow users to search for discounts (to save money) easily.

Step #2 — Analyze Your Competitors

It’s obvious that you have to conduct a competitor analysis if there are already similar products on the market. But sometimes, entrepreneurs ignore competitor analysis because of a pure faith in their product’s uniqueness. Keep in mind that even if you don’t think you have any direct competitors, your faith in the uniqueness of your product is not sufficient grounds for confidently bringing your product to market. Competitor analysis is important no matter what.

There are various tools available that can help you investigate your competitor's websites or apps and get some insights about their monthly traffic, sources of traffic, website or app rank (globally and within a particular country), geographical location of users, and other helpful information. Keep in mind that all of this data will be within a small margin of error. One of the most popular free service of this type is Similar Web. With Similar Web, all you need to do is copy-paste a link to a site or even just set up an extension in your browser.

Analyze Your Competitors for building MVP
[Source: This data was displayed by the SimilarWeb extension for Google Chrome]

Other popular free tools you may consider are App Annie, Ahrefs, Follow, and QuantCast. If you’re ready to pay, then check out SensorTower or MOZ.

Additionally, you can find and analyze feedback about your competitors’ products. Analyzing customer feedback about your competitors’ products can help you build an MVP for your own product that addresses the shortcomings of existing solutions! To sum up, don’t hesitate to adopt good ideas from your competitors and also learn from their mistakes. Once we’ve determined the problem we’re solving for our target audience and have analyzed the competition, we can move on and define the main user flow.

Step #3 — Define the User Flow

We’re sure you’re familiar with Zappos, one of the most outstanding online shoe stores. Zappos also started with an MVP. Let’s consider the Zappos user flow. Remember that when you start defining the user flow for your future product, you should focus directly on its primary goal. As Zappos is an online shop that sells shoes, its main goal is to allow users to buy shoes online.

To define the main user flow we should first define process stages. This is actually quite easy, because all you need to do is explain the steps required to reach your product’s primary goal. At this point you should think less about particular features and concentrate more on basic tasks such as: “find shoes,” “buy shoes,” “manage orders,” and “receive orders.” These are the types of goals your end-users will have when they use your product. As soon as all these process stages are defined, we can then define features for each stage.

Step #4 — List All Necessary Features and Prioritize Them

As soon as you’ve defined all the steps your customer should take while using your product, you can start creating a list of particular features for each stage. You might highlight all the features you think are ‘nice-to-have,’ but not strictly necessary. When you have a list of features for each stage, you then need to prioritize them. To prioritize features, do the following:

  1. Ask yourself: What is the single-most important action that I want my users to accomplish? (Note: this will be your main feature);
  2. Ask yourself: What other features do I want to offer? (Explain why you need each of these features, then cross out the least important ones.)
  3. Now categorize all the remaining features under the categories ‘must-have,’ ‘nice-to-have’, and ‘don’t care.’ The Story Mapping technique might make this process easier. You can build a matrix where you have a horizontal row showing main process stages (our user flow) and under each stage a number of features dedicated to this stage.
  4. List of features
  1. Once you’ve added all the stages and features for each stage, you can draw a downward vertical arrow going from ‘high priority’ at the top of the column to ‘low priority’ at the bottom. Now, you’re ready to start arranging features by their priority. Move stories which are crucial up the column, and other stories down. Always focus on the whole process.
  2. Downward vertical of features
  3. When you’ve prioritized all the features, you may define their scope for the first version of the product and move to building an MVP. If you want to see what your future product will look like, you can first create an MVP's prototype. Here at RubyGarage we create UX and UI prototypes of our clients’ products in InVision and Moqups. For one of our recent projects, Shopperations, we first created a prototype, then the project received investment, and then we proceeded with development. Here’s what the prototype looked like:
How to Build a Minimum Viable Product (MVP)

Step #5 — Build, Test, and Learn

When the first scope of work is defined, we move to the development stage. And when product development is almost completed, the product needs to be tested. The first testing stage is conducted by our Quality Assurance engineers, who work to improve the quality of the product when it’s not yet released. They ensure that a product is ready for alpha or beta testing.

Alpha testing can also be called a Friends & Family release, because you generally give an alpha build of your product only to a limited focus group, in most cases to friends and relatives. You may conduct alpha testing first and then move to beta one, or may proceed directly to beta testing. As soon as the product passes alpha testing it’s ready for beta testing. When we talk about beta testing, we mean that the product is going out into the real world to be tested by real users. The beta testing period varies, but it usually takes 1–2 weeks to get sufficient feedback. Based on feedback from beta testing, you may consider implementing changes in the following versions of your product. Keep in mind that only crucial changes should be made immediately.

Your users are the only people who can define what features your product lacks and what features aren’t needed. After you collect user feedback, you can start improving your product again and then test, and learn, and build again, and test again, and learn again.

Improving your MVP

If you’re curious how much MVP development costs, you should know that in most cases the cost for building a product depends on a great many factors. One of the most significant is project complexity. The approximate cost of building an Airbnb-like website ranges from $38,430 to $225,750. You can find out more details about the MVP product development in our article dedicated to the cost of building a minimum viable product for an Airbnb-like website.

If you have any questions or want us to help you develop an MVP or minimum viable product UI/UX design, don’t hesitate to contact us.

CONTENTS

FAQ

  1. The first step of successful minimum viable product development is evaluating your business idea. Start by asking yourself two questions to try to put yourself in your customer’s shoes: Why do I need this product? and How it can help me? Answering these questions will help you understand the main goal of your product and find the best solution to your future customers’ real needs.
  2. One of the most popular free service of this type is Similar Web. With Similar Web, all you need to do is copy-paste a link to a site or even just set up an extension in your browser. Other popular free tools you may consider are App Annie, Ahrefs, Follow, and QuantCast. If you’re ready to pay, then check out SensorTower or MOZ.
  3. To define the main user flow, first define process stages. All you need to do is explain the steps required to reach your product’s primary goal. As soon as all these process stages are defined, you can then define features for each stage.
  4. When making a list of must-have features, think about a single-most important action that helps users accomplish their goal.

Tags:

MVP

Authors:

Viktoria K.

Viktoria K.

Copywriter

Vlad V.

Vlad V.

Chief Executive Officer

Rate this article!

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

Share article with

Comments (0)

There are no comments yet

Leave a comment

Subscribe via email and know it all first!