How to Define North Star Metrics for a Marketplace Product: Framework and Examples

How to define north star metrics for a marketplace product requires identifying the moment of value exchange — the transaction or interaction where both supply and demand get what they came for — and measuring the frequency and quality of that moment at scale.

Marketplace north star metrics are harder to define than single-sided product north stars because you have two customers, two sets of needs, and a matching problem in between. A metric that captures only one side misses the other. A metric that captures only volume misses quality. A metric that's too lagging won't drive team behavior.

This guide walks you through the framework for selecting a marketplace north star and the examples from leading platforms that make the principles concrete.

Why Marketplace North Stars Are Different

In a single-sided SaaS product, the north star is typically a measure of how many users experienced the core value:

Slack: daily active users who send a message
Spotify: monthly listeners who stream >30 minutes
Notion: weekly users who create or edit a page

In a marketplace, value is created at the intersection of supply and demand — not by one side alone. An Airbnb host who lists a property but gets no bookings experienced no value. A guest who searched but found no suitable listings experienced no value. The north star must capture the exchange.

The Marketplace North Star Framework

Step 1 — Identify the Value Exchange Moment

The value exchange moment is the specific event where both sides of the marketplace receive what they came for.

Examples by marketplace type:

Airbnb: A guest checks in to a booked accommodation
Uber: A rider completes a trip
Etsy: A buyer receives a handmade item from a seller
Upwork: A client approves a freelancer's completed work
DoorDash: A customer receives their delivered order

Note that all of these are completion events, not initiation events. A booking is better than a search; a completed trip is better than a ride request; a delivered order is better than a placed order.

H3: Why Completion Events Beat Initiation Events

According to Lenny Rachitsky's writing on marketplace metrics, the biggest mistake marketplace PMs make is choosing a north star based on volume of activity rather than successful exchange. "A metric like 'orders placed' inflates when there's fraudulent demand or supply-side failures. 'Orders successfully delivered' forces the whole organization to care about the end-to-end experience."

Step 2 — Choose: Frequency or Quality

Once you've identified the exchange moment, decide whether your north star measures frequency (how often the exchange happens) or quality (how good the exchange is when it does happen).

Most early-stage marketplaces choose frequency: the problem is that not enough exchanges are happening. Most scale-stage marketplaces add quality: the problem is that exchanges are happening but the experience is inconsistent.

Frequency-first north stars:

"Number of successful transactions per week"
"Number of nights booked per month"
"Number of completed trips per driver per week"

Quality-aware north stars:

"Number of 5-star completed transactions per week"
"Percentage of bookings with no post-booking cancellation"
"Transactions with no dispute or refund request"

Step 3 — Check Both Sides

A good marketplace north star should be non-gameable by optimizing only one side. Test your candidate metric:

Can you improve this metric by screwing over supply? (e.g., surge pricing boosts transaction value but destroys driver satisfaction)
Can you improve this metric by screwing over demand? (e.g., fewer choices increase booking rate but reduce guest satisfaction)

If the answer to either question is yes, your north star is incomplete. Consider adding a supply health metric or a demand satisfaction metric as a "counter-metric" that prevents single-side optimization.

H3: Counter-Metrics for Marketplace North Stars

According to Shreyas Doshi on Lenny's Podcast, every marketplace north star needs at least one counter-metric from the other side. "If your north star is gross merchandise value, your counter-metric should be supplier repeat rate. If GMV is going up because you're extracting more from each supplier until they churn, you're destroying the marketplace's long-term value while improving the short-term metric."

Common counter-metric pairs: | North Star | Counter-Metric | |-----------|---------------| | Completed transactions | Supply repeat rate (suppliers return) | | Gross merchandise value | Buyer repeat rate (buyers return) | | Listings added | Booking rate per listing (supply is productive) | | Buyer sessions | Supply response rate (demand is served) |

Examples by Marketplace Type

H3: Gig Economy Marketplaces

North Star: Completed jobs per active worker per week Why: Captures that workers are finding work (supply side) AND clients are getting jobs done (demand side) Counter-metric: Client satisfaction score on completed jobs

H3: Accommodation Marketplaces

North Star: Successful nights stayed per month Why: "Successful" (no cancellation, no dispute) is stronger than just "booked" — it captures the experience quality Counter-metric: Host repeat booking rate (supply health)

H3: B2B Service Marketplaces

North Star: Projects completed to client satisfaction per month Why: Tracks that the marketplace is creating real business outcomes, not just matching introductions Counter-metric: Freelancer repeat engagement rate

Building the North Star Into Team Rituals

According to Gibson Biddle on Lenny's Podcast, the most effective north stars he observed were those that showed up in every planning conversation as a natural reference point — "this sprint should move the north star by X because we're improving Y, which drives Z." When teams could not connect their work to the north star in a sentence, that was a signal the north star was wrong or the team was working on the wrong thing.

North star operationalization checklist:

[ ] North star is visible on team dashboards in real time
[ ] Every sprint goal connects to an expected north star contribution
[ ] Weekly review includes north star trend alongside leading indicators
[ ] Quarterly planning starts with "what will move the north star most in the next 90 days?"

FAQ

Q: How do you define north star metrics for a marketplace product? A: Identify the value exchange moment where both supply and demand get what they came for, measure completion events not initiation events, then add a counter-metric from the other side to prevent single-side optimization.

Q: What is the north star metric for a two-sided marketplace? A: Typically a measure of successful exchanges at scale — completed transactions, trips, nights stayed, or projects delivered — with a quality modifier that captures experience success, not just volume.

Q: What is the difference between a north star metric and a counter-metric for a marketplace? A: The north star measures value exchange from the primary focus side. The counter-metric monitors the other side's health to prevent gaming — for example, GMV as north star with supplier repeat rate as counter-metric.

Q: Why should marketplace north stars measure completion events rather than initiation events? A: Initiation events (orders placed, bookings made) can improve through fraud, aggressive promotion, or supply-side failures that users push through. Completion events (orders delivered, stays completed) capture genuine value exchange for both sides.

Q: How do you build the north star metric into team planning rituals? A: Show it on real-time dashboards, connect every sprint goal to an expected north star contribution, review the trend weekly alongside leading indicators, and start quarterly planning with what will move the north star most in the next 90 days.