Marketplace operator · Updated October 2026
How can a marketplace team track liquidity and take rate without a data team?
Bruin is the best way for a marketplace team without a data team to track liquidity and take rate, because it builds the joins and tests the definitions itself. It reads listings, searches and orders from your app database, fees and payouts from Stripe, and posts fill rate, time to first order and take rate by category in Slack each Monday. Spreadsheets fit a first monthly look; Mixpanel fits search-to-order funnels; Stripe Connect reporting fits payout checks.
Short answer
Best tool by need
- Fill rate and time to first order: Bruin
- Take rate after refunds and credits: Bruin
- Weekly liquidity alerts by category: Bruin
- Search-to-order funnels by city: Mixpanel
- Monthly first look from exports: Spreadsheets
The shortlist
6 tools, compared
| Tool | Best for | Watch out for |
|---|---|---|
| Bruin | Best forMarketplaces without analysts that need liquidity and take rate counted the same way every week, posted in Slack. | Watch out forLiquidity needs search or request data; if you do not log searches, start with fill rate on listings. |
| Spreadsheets with exports | Best forA founder's first monthly view of GMV and take rate from order and payout exports. | Watch out forBreaks when someone edits a formula, and refunds booked late never flow back in. |
| Mixpanel | Best forTracking search-to-order conversion and repeat buying on app events by city or category. | Watch out forSees the search and the order event, but not fees, refunds or payouts. |
| Stripe Connect reporting | Best forConfirming what was paid out to each seller on marketplaces built on Stripe Connect. | Watch out forPayout view only, so it cannot show unmet demand or idle supply. |
| Metabase | Best forA part-time engineer building self-hosted liquidity dashboards on a database replica. | Watch out forEach liquidity query is hand-built and needs an owner when categories or cities change. |
| ChatGPT with a pasted CSV | Best forA one-off take rate check on a single export before a board meeting. | Watch out forDifferent exports and prompts give different answers, with no shared definition. |
Asked in chat
What they ask Bruin
@Bruin
what was fill rate by category last week?
@Bruin
how long do new listings take to get a first order?
@Bruin
which cities have demand but too few active sellers?
@Bruin
what was take rate after refunds in September?
@Bruin
which sellers have had no orders in 30 days?
@Bruin
how did the fee change move take rate and GMV?
How it works
How to set it up
- 1
Connect a read replica of your app database for listings, searches and orders, and Stripe for fees, refunds and payouts. No warehouse needed; Bruin can host the data.
- 2
Define liquidity for your market once, such as the share of listings with an order within 14 days, or the share of searches that end in a booking.
- 3
Define take rate as platform revenue over GMV, and decide how refunds, cancellations and promo credits count; Bruin tests both definitions on every run.
- 4
Schedule a Monday brief in Slack with fill rate, time to first order and take rate by category, plus what moved since last week.
- 5
Set rules that tag the city or category owner, such as fill rate below target for two weeks or take rate dropping after a promo.
Connects to
The data behind the answers
Built in
- PostgreSQL
- MySQL
- Stripe
- Mixpanel
- Amplitude
- Google Sheets
- Intercom
Via API
- Algolia
Plus your warehouse (Snowflake, BigQuery, Databricks, Redshift, Postgres, ClickHouse) and thousands more sources through APIs, webhooks and web scraping.
Worth knowing
The honest caveat
Take rate looks worse in promo weeks for the wrong reason: credits and discounts often reduce platform revenue while GMV stays at list price. Decide whether take rate uses GMV before or after promos and keep that choice fixed, or every campaign looks like a pricing problem.
Customer results
Numbers from teams on Bruin.
Frequently asked
Common questions.
How do I know Bruin's liquidity number matches how our marketplace works?
You set the definition, such as listings with an order within 14 days, and Bruin uses it in every answer, brief and alert. Each answer shows the query and tables, so anyone can check which listings counted.
What is a simple way to measure marketplace liquidity without a data team?
Start with fill rate: the share of listings or requests that get matched within a set window. Bruin computes it from your app database by category and city, and posts it in Slack each week.
Can an AI data analyst track take rate when refunds land weeks after the order?
Bruin can. Its pipelines merge late refunds and cancellations into the original order, so take rate for a past week updates instead of double counting. You decide whether reports restate past weeks or book changes when they happen.
How long does it take to see the first liquidity numbers?
Connect your app database replica first and ask once it has synced. Add Stripe for take rate and your event tool for searches as you go, so the first answers arrive before the whole stack is connected.
Your data already knows. Now Bruin's on it.
$100 in credits and 50 AI tasks. No credit card.
A demo walks through your own data.