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.

The Chicken and Egg Problem of Peer-to-Peer Marketplaces: Who to Attract First?

  • 24263 views
  • 7 min
  • Jan 02, 2018
Irina M.

Irina M.

Copywriter

Dmitriy G.

Dmitriy G.

Head of BA Office

Share

Every peer-to-peer marketplace struggles with user acquisition. What makes it even worse is the chicken and egg problem: should you attract buyers or sellers first? The issue is that a marketplace needs to have both customers and providers of goods or services, but one won’t come without the other. So how can you find a way out of this vicious cycle?

Supply and Demand Problem of Marketplaces

In this article, we'll consider several options for launching a marketplace: getting sellers first, getting buyers first, attracting both sides simultaneously, or acting as a producer yourself.

Getting sellers first

Getting sellers in your marketplace first seems like the safest choice. You can advertise your marketplace to sellers by promising a future influx of customers once a base of sellers is established. It's not necessary to pay sellers from the start before they get actual orders, but it can be helpful if you have the resources on hand – this might increase your chances of getting your critical first sellers.

Getting sellers first is convenient because if customers are introduced to a marketplace and it’s completely lacking products and services, they'll leave. Unlike customers, who want goods and services immediately, sellers can wait and won’t lose anything in case of a temporary lull.

Still, how do you get sellers to enter a market that has no consumers? Let’s review the most effective strategies.

Strategy #1:

Provide an economic incentive. This is quite risky, but if you’re confident that there’s a substantial untapped market and you can attract customers once you have the service providers – and if you have the financial resources – then this is the way to go.

For example, when Uber first launched it sought out drivers and promised them a fixed minimum wage even if they didn’t transport any passengers. Drivers could sign up and still work their usual jobs while waiting for the service to pick up and receiving their small, but still valuable, paycheck. This strategy worked out for Uber, as it’s now one of the largest global transportation companies.

Strategy #2:

Intrinsic value strategy. One way that you can establish a functional marketplace is to find a product that doesn’t need both customers and producers in order to offer value. In other words, figure out a certain value that your product can offer to one of the players in the marketplace independently, regardless of whether the other side is involved.

Take the booking service OpenTable, for instance. They started gathering a database by allowing restaurants and cafes to register with the service, which at first looked like a simple search platform for local eateries. Once there were enough registered businesses, OpenTable started to attract customers by letting them search for places to eat as well as book tables in advance online.

Getting buyers first

Depending on what type of marketplace you’re building, sometimes it makes more sense to build a user base and then move on to finding suppliers.

Let’s look at two sure ways you can get buyers first and consider in which cases you should start with building your client base.

Strategy #1:

We’ve already discussed how the intrinsic value strategy can help you get sellers to your marketplace first, but this strategy actually works both ways, and can be just as effective at attracting customers first. Take the Facebook Marketplace, for example, which is used by both merchants as well as customers.

The idea behind the Facebook Marketplace is that sellers can list their products, which are either filtered by fixed categories such as cars, clothes, and furniture or presented as separate lists advertised by Facebook itself on an official page – for example, used toys for Christmas presents. Buyers, on the other hand, can wait for an item they want or post a request on the Facebook Marketplace Community page to give sellers an idea of what’s in demand.

Strategy #2:

Incentivize potential customers. Similarly to providing an economic incentive to your service providers, you can offer users some money for signing up early. Obviously, this doesn’t mean that you should just give away cash for people’s emails. For instance, you can offer a discount on the first order or offer $15 off the first purchase of $30 or more and get the ball rolling with orders (surely, if the rest of your marketing strategy works well).

For example, when the design marketplace Creative Market launched, they offered $5 for every new user. They reported that this promotion guaranteed enough signups from the start and that they weren’t concerned with offering money since most people would spend more than $5 later on. This strategy paid off.

Creative Market Offering

Attracting both sides simultaneously

The holy grail when launching a marketplace is having both sellers and buyers signing up with your service at the same time. Nothing seems more perfect than having suppliers ready to serve and customers waiting to place orders. Seems too good to be true? It’s not if you have the right concept and have a detailed plan of action.

Let’s look at two approaches that can help you attract producers and customers simultaneously.

Strategy #1:

Prompting sellers to bring in buyers and vice versa. In this scenario, you have one of the sides doing the work of establishing the customer or supplier base for you. You can achieve this by developing a marketplace that absolutely needs both sides to work, in which case nobody can do anything without their counterpart. This approach is most effective in the following cases:

  1. When suppliers already have clients that they can bring along to the marketplace.
  2. When clients have producers that will follow them wherever they go.
  3. When you have points of influence that will make either buyers or sellers actively involve one another in the marketplace.

Strategy #2:

Targeting buyers and sellers from the same community. When customers and suppliers have the same interests and provide similar goods and services, then they can take turns playing the roles of buyer and seller in the marketplace.

Let’s take a look at Etsy, an ecommerce marketplace for vintage and handmade products. Etsy’s target audience is people interested in handmade crafts: they craft unique products themselves and enjoy purchasing handmade things as well.

Thus, it makes sense to support fellow artisans by buying their goods and offering your own. This is exactly the idea of being participants in the same community. Buyers and sellers can take turns playing both roles and as a result keep your marketplace alive.

Acting as a producer

Lastly, you can act as a seller yourself when first launching a marketplace. Or better yet, you can launch a marketplace with the sole agenda of selling your own products or services and then attract similar producers if your launch is successful. In this latter scenario, you have a certain number of customers, which will encourage service providers to join.

For example, eBay’s founder Pierre Omidyar launched eBay with the intention of auctioning items he no longer needed. His stuff sold with such great success that other people wanted to put their items up for sale as well, and the rest is history.

Another example is the luxury ecommerce marketplace AHAlife, which was started by Shauna Mei, whose father would bring her items from places he travelled and tell stories about them. Mei appreciated that each item had a backstory and wanted to share these unique items with the rest of the world on her website. The idea to present each product with information about how it was created and a biography of the designer attracted many creators, and now AHAlife features a broad community of designers that offer their one-of-a-kind items.

AHAlife Information

As you can see, the decision of how to launch and start seeding your marketplace should be based on multiple factors, but especially on the type of marketplace you’re building. Carefully consider what kinds of goods or services your marketplace will provide. Once you have that figured out, we can help you realize your vision and bring your marketplace to life.

CONTENTS

Authors:

Irina M.

Irina M.

Copywriter

Dmitriy G.

Dmitriy G.

Head of BA Office

Rate this article!

Nay
So-so
Not bad
Good
Wow
4 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!