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 Much Does it Cost to Build an Online Marketplace?

  • 69064 views
  • 11 min
  • Jan 08, 2020
Sviatoslav A.

Sviatoslav A.

Copywriter

Vlad V.

Vlad V.

Chief Executive Officer

Share

The sharing economy has been growing rapidly, leading many people to consider starting their own online marketplace. Web-based marketplaces can help people share goods, services, accommodations, and relevant information.

If you want to develop your own online website marketplace, you first need to know roughly how much it will cost.

Cost to develop a marketplace depends on the option you choose. There are essentially two options for developing such a project. You can develop on a platform, such as Sharetribe (built with the Ruby on Rails framework) that offers certain ready features. Using Sharetribe or a similar platform is the fastest and cheapest way to develop such a website.

The second option is to build a marketplace from scratch. Although this option demands more time and money, a bespoke marketplace can be customized to meet your specific needs better than a platform such as Sharetribe.

We can help you decide which option is right for you during the requirements elicitation stage.

Examples of web marketplaces - eBay, Etsy, Airbnb, Couchsurfing

From the technical point of view, creating such a project is easy for us for a few reasons:

  • We have experience building marketplaces
  • We have our own libraries
  • We use Sharetribe, which is a great open source solution that speeds up marketplace development

We’re going to provide you with two estimates: the cost of building a web marketplace from scratch and the cost of building it using Sharetribe.

Technology Stack for Building a Website Marketplace

The technology stack we use to create a marketplace website varies depending on a marketplace’s specifications. But we typically use the technologies listed below:

  • Sharetribe
  • HAML
  • Sass
  • CoffeeScript
  • Ruby
  • Ruby on Rails
  • RSpec
  • Capybara
  • PostgreSQL

Keep in mind that we listed only core frameworks and preprocessors, and the stack usually includes more technologies. The technology stack may also change should we consider other frontend frameworks.

Technology stack for marketplace development

How We Estimate a Marketplace Project

According to Agile principles, we estimate development tasks in story points rather than in hours (you can read more about reasons to estimate with story points). But for the purposes of this article we’ll provide you with a story points estimation converted into an hourly rate estimation.

Implementing a marketplace, regardless of whether the marketplace is based on Sharetribe or made from scratch, is similar to implementing any other web application. Here’s the work we’ll do, in a general sense:

  • User Interface and User Experience design (the look & feel and behavior of the marketplace)
  • Responsive HTML and CSS (so your marketplace works great on any device)
  • Front-end programming (user interactions in the browser)
  • Back-end programming (server-side business logic)
  • Automation tests to remove bugs
  • Acceptance tests (manual testing)

After the initial launch of a marketplace we collect feedback from users, and after that we’ll need to develop your marketplace further. In the next section, we’ll provide you with our estimates for marketplace development, both made with Sharetribe and built from scratch.

How Much Does It Cost to Build a Marketplace Website

Building a marketplace Minimum Viable Product (MVP) with common features is a practical first step, as you’ll be able to launch your marketplace as soon as possible. The faster your product is released, the faster we can figure out what to improve.

In the article you’ll find a detailed explanation, expressed in user stories, of the functionality that will be included in the application. We’ll also provide an estimate in story points for each feature.

According to our estimation, a marketplace MVP requires 87 Story Points. 87 Story Points translate to around 750 hours of development time if the application is built on Sharetribe, and around 1050 hours if we develop your project without Sharetribe.

We analyzed data provided by Clutch.co to show an average hourly rate for web development teams in several countries. Here’s what the hourly rates looks like:

Average development hourly rates in various countries
[Based on data from Clutch.co]

Now take a look at the table below to see the approximate cost of web marketplace development:

Web Marketplace MVP Approximate Cost Sharetribe-based (1 story point ~ 8-9 hours) Built from Scratch (1 story point ~ 12 hours)
Ukraine ($31.5/hour) $23,294 $32,886
Europe ($60/hour) $44,370 $62,640
USA ($100/hour) $73,950 $104,400

Keep in mind that we can provide a more precise estimate for your marketplace only after the requirements elicitation stage.

What Features Do We Estimate for a Marketplace MVP?

Your marketplace project (even if it’s built on Sharetribe) will require:

  • User Experience & User Interface design. Our designers describe UX scenarios, choose a color scheme, create a style guide, and design a logo.

Estimate: 4 story points (34 hours).

  • Database, web application design and deployment scripts. Our web developers configure backend and frontend tools, design a database, and write scripts for deployment.

Estimate: 3 story points (25.5 hours).

Once we complete the first two steps listed above, we can then implement the actual functionality. Each feature in your project will be associated with a specific type of user:

  • Site visitor
  • Authorized user (a visitor who’s logged in)
  • Customer (an authorized user who buys an item)
  • Publisher (an authorized user who sells something, i.e. a seller)

When developing functionality, we'll create wireframes similar to the ones shown below.

An online marketplace wireframe

In the next section we’ll describe user-related features that we implement when building a marketplace MVP.

Authorization and Security

In order to fully use a web marketplace, a user must sign up and provide personal details such as their name, gender, birth date, email, language, and phone number. We implement all necessary features for creating user accounts and saving user data securely.

How much does it cost to build an online marketplace?

Managing account data is also important. Authorized users should be able to easily change notification and privacy settings, e.g. opt not to share their activity on Facebook.

We also need to let users sign up via their preferred social network, as this offers a simple way of registering on a new website.

Therefore, site visitors will be able to:

  • Sign up using an email and password or via a social network such as Facebook, Twitter, or Google+
  • Sign in to the marketplace with an email and a password or via a social network
  • Reset their passwords

Authorized users will be able to:

  • Update their personal details
  • Manage their account data and listings
  • Hide their private data from other users

Estimate: 8 story points.

User Profiles

Since the main goal is to help users buy and sell goods, seller information should be clearly presented to buyers and easily managed by publishers. We must let publishers change settings for their public information.

Site visitors will be able to:

  • See detailed information about customers and publishers

Customers and publishers will be able to:

  • Manage their public data (e.g. personal descriptions or work emails)

Estimate: 5 story points (42.5 hours).

Functionality to Let Users Become Publishers

We’ll add an option for users to become publishers so they can sell and share their items. Publishers will have access to the most functionality on your online marketplace, meaning they will be able to indicate the minimal or fixed price for their item, for example.

  • Authorized users will be able to become publishers

Estimate: 4 story points (34 hours).

Managing Listings

Products or services on a web marketplace are called listings. Sellers need to publish and manage items they sell, which is another chunk of functionality we need to implement.

Site visitors will be able to:

  • Filter listings added by publishers
  • Search for a listing
  • View detailed information about a listing

Publishers will be able to:

  • Add new listings
  • View their listings
  • Manage their listings (i.e. remove, revise, or end early a listing)
  • Publish or unpublish a listing

Estimate: 19 story points (161.5 hours).

Booking Process

We need to add booking functionality to ensure users can reserve goods or services. Publishers will also need to collect delivery information so they can ship items.

Customers will be able to:

  • Book a listing and add booking details (date, time, etc.)
  • Add shipment details
  • Communicate with publishers during the booking process
  • Send requests to publishers related to a booked listing
  • Accept a new publisher’s offer for a booked listing
  • Decline a new publisher’s offer for a booked listing

Publishers will be able to:

  • Accept booking requests
  • Submit new offers for their booked listing to customers
  • Decline customers’ booking requests

Estimate: 8 story points (68 hours).

Payment

Your online marketplace requires advanced payment functionality. But should you let users pay with credit cards or PayPal? Or with some other payment system? Or even with cash? A marketplace MVP must provide at least one payment method, but may include multiple.

Payment functionality for marketplace

We usually create a special tab for payment information and let customers manage their payment data in this tab.

Therefore, customers will be able to:

  • View their payment details (e.g. transaction history)
  • Manage payment methods (add, remove, and update payment methods)

Estimate: 5 story points (42.5 hours).

Payout

Your marketplace must let publishers retrieve their money from the system, and this functionality also demands additional code.

Publishers will be able to:

  • View payout details
  • Manage payout methods (add, remove, and change any relevant payout details at any time)

Estimates: 5 story points (42.5 hours).

Bookings

If a customer wants to purchase a desired item, they need to know when the item will arrive. Sellers need to know for how long their item was rented, for example. We’ll let buyers and sellers access all booked listings to view each listing details.

Therefore, customers will be able to:

  • View their booked listings
  • View detailed information about each booking

Publishers will be able to:

  • View an index of their listings that have been booked by customers
  • View detailed information about each booking

Estimate: 5 story points (42.5 hours).

Reviews & Ratings

To build trust between customers and sellers, we must implement functionality for ratings and reviews.

Therefore, marketplace users will be able to:

  • See a listing’s reviews

Customers will be able to:

  • Write reviews and rate listings
  • Update reviews and ratings

Publishers will be able to:

  • Send requests for reviews to customers
  • Accept reviews from customers
  • Decline reviews from customers
  • View customers reviews

Estimate: 8 story points (68 hours).

Notifications

Notifications are a great way to help users stay informed when, for example, a seller ships a product or when the product arrives.

Notification settings

Authorized users will be able to:

  • Change notification settings
  • View notifications based on their notification settings

Estimate: 3 story points (25.5 hours).

Browsing Сontent

Adding complex functionality to your marketplace is pointless if users can’t find what they’re looking for. We work to make navigation smooth across all parts of your product.

Authorized users and site visitors will be able to:

  • See the main page of the website and its content with a brief description of the website’s purpose and services
  • Perform a quick search from the main page of the website
  • Visit standard pages (Contact Us, About Us, Terms of Use, etc.)

Estimate: 10 story points (85 hours).

Marketplace Website Development Cost

Here is a summary table with all features your marketplace project will have.

Features Amount of Story Points Time Cost
User Experience & User Interface 4 Story Points 34 hours $1,071

Database

Web Application Design

Deployment Scripts

3 Story Points 25.5 hours $803
Authorization and Security 8 Story Points 68 hours $2,142
User Profiles 5 Story Points 42.5 hours $1,339
Functionality for Publishers 4 Story Points 34 hours $1,071
Managing Listings 19 Story Points 161.5 hours $5,087
Booking Process 8 Story Points 68 hours $2,142
Payments 5 Story Points 42.5 hours $1,339
Payout 5 story points 42.5 hours $1,339
Bookings 5 story points 42.5 hours $1,339
Reviews & Ratings 8 Story Points 68 hours $2,142
Notifications 3 Story Points 25.5 hours $803
Browsing Сontent 10 Story Points 85 hours $2,677

Developing an MVP from scratch for such project will cost you around 30-35 percent more time and money than if you opt to build with Sharetribe.

CONTENTS

Authors:

Sviatoslav A.

Sviatoslav A.

Copywriter

Vlad V.

Vlad V.

Chief Executive Officer

Rate this article!

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

Share article with

Comments (0)

There are no comments yet

Leave a comment

Subscribe via email and know it all first!