I built a two-sided marketplace and never once asked anyone to use it
I'm 75, I've been writing software since the 1970s, and I just spent three months building a marketplace that got zero customers. Posting the numbers because I had to say the diagnosis out loud before I believed it.
Brief Work (briefwork.io) — short-burst expert gigs. One deliverable, under $5K, under two weeks. Clients pay $50 to post a brief, experts apply free, no cover-letter theater. The bet was that charging the client to post, rather than charging workers to apply like Upwork does, was the honest version of this business.
Built solo: Next.js, Supabase, Stripe live mode, auth, RLS, messaging, direct hire, transactional email. Real payments, end to end. Went live in May.
Three months later, from the production database:
Briefs posted: 4 — all four by me
Applications received: 3
Registered users: 5, two of which are mine and one is junk
Revenue from strangers: $0
One real transaction ever: I paid a freelancer $50 for a GTM plan. He did good work. I was the client.
What I got wrong. I assumed both sides were cold and I'd have to seed supply first — that's the standard advice, and it's what every marketplace article tells you. It was wrong for my situation. Three freelancers found the site and applied with zero supply-side marketing, and the one I hired delivered. Supply seeded itself.
Demand never appeared. And the honest reason isn't mysterious: nobody ever asked for it. In three months, client acquisition was a launch post, a couple of social posts, and an email to three friends. No outbound. Not one human being was ever personally asked to post a brief.
I kept building instead of selling, because building is the part I'm good at and selling is the part where people say no.
The actual lesson, which cost me three months: a two-sided marketplace is a distribution business wearing a product costume. The product is the cheap part — I proved that by building a working one solo in weeks. Manufacturing demand needs at least one of: an existing audience, money for ads, a network to mine, or appetite for sustained cold outreach. I had none of the four, and the fourth I didn't want.
That's not a product problem you can engineer your way out of. No feature fixes it. I could have built escrow, ratings, and dispute resolution and still had zero customers, just later and more tired.
If you're about to build a marketplace, the question that would have saved me the three months isn't "can I build this" — it's "name the first ten people who will pay, and what makes you able to reach them." If you can't finish that sentence, the build is the expensive way to find out.
The aside: it's for sale. Everything works and it's live. I'd rather it went to someone with an audience and no product — the exact inverse of me — than sit here as a monument. It's listed on Acquire and Little Exits, or just reply here and ask me anything.
Happy to answer technical questions about the build too. I won't oversell it — the numbers above are the numbers.
Hey, I came across your post about Brief Work. Really interesting to see the numbers and the honest breakdown of what went wrong.
I'm a full-stack developer currently looking to work with early-stage products. I can work across frontend, backend, databases, integrations and product features rather than being limited to one part of the stack.
If you're continuing development on Brief Work or working on your next product and need someone to help ship features, I'd be interested in contributing.
Happy to share my work if useful.
Hey, I came across your Brief Work post. The idea of short-burst expert gigs is interesting, and I noticed you built it with Next.js + Supabase.
I'm also a full-stack developer working with that stack and recently built Hangr, including auth, profiles, social interactions and location-based features.
I'm currently taking on small freelance development projects, particularly MVP features and product improvements. If you're looking for help with Brief Work at any point, I'd be happy to contribute.
The paid version of your experiment gives the same answer, in case it saves you the money. We run an affiliate platform, which is the same two-sided shape, and this month we are buying search ads for both sides: one campaign to the product landing, one to a separate landing for recruiting partners. Two weeks, 42 clicks, zero signups on either side.
So it is not that you skipped the ad budget. Ads move people who already have the problem onto a page, they do not create the ask. Your line about never personally asking anyone is the thing we are both paying for, just through different invoices.
The detail I would keep from your post is the supply one. Three freelancers found you with no supply-side marketing at all. In our market everyone assumes the partner side is the hard one, and it is the merchant side that stays quiet. Worth checking which side of your own market self-serves before spending anything on the other.
the next test i would run is a demand concierge, not another marketplace feature. pick three real client problems, find one suitable expert for each by hand, and ask the client to pay the $50 posting fee before you build the match. then you learn where the refusal happens: problem definition, trust, price, or urgency. three completed paid briefs would tell you more than another hundred registrations, and it keeps the test small enough to do without pretending you have a scalable channel yet.
This is a better experiment than the one I designed, and better than the version I got talked into earlier in this thread.
Two details do the work. Taking the $50 before the matching means I'd be testing demand rather than my ability to deliver a match — mine had those tangled. And sorting the refusal into definition, trust, price, or urgency turns a no into information. "Nobody bought" told me nothing; "three people balked at price and one couldn't define the deliverable" would have told me what to change.
The honest blocker is the same one I've had throughout: I don't have three real client problems to pick from. Sourcing those is the work I avoided for three months, and your test assumes it's solved. But that's a limitation of my situation rather than your design — and it's exactly the test a buyer should run in their first week, since they'd arrive with the demand I never had.
I'm writing it down. Thank you.
This is one of the most honest posts on IH. "A two-sided marketplace is a distribution business wearing a product costume" should be printed on a wall somewhere.
The supply-seeded-itself detail is actually the interesting signal — three freelancers found it with zero marketing. That's proof the product works. The problem was exactly what you named: demand was never asked for, it was hoped for.
The question you landed on at the end — "name the first ten people who will pay, and what makes you able to reach them" — is the right one. Most founders skip it because building feels like progress and outreach feels like rejection.
That gap between "product is ready" and "distribution is executed" is exactly what I built Zarek for. You paste your URL, it builds the full launch plan, writes venue-specific copy, finds the right communities, submits directories, and verifies what actually went live. The thing that would have changed your three months isn't more features — it's a system that makes demand-generation as structured as the build was.
zarek.tech — 3-day free trial if you ever build the next one.
Thanks, though I have to correct one thing since I walked it back earlier in this thread: three applications isn't proof the product works. It's n=3, with me as the only client and no demand pressure on the system. It shows experts will apply when briefs exist. It doesn't show supply holds up once demand arrives, and I'd been letting that number carry more than it could.
On the tool — I'll pass, but genuinely good luck with it. I'd flag one thing: my lesson wasn't that I lacked a system for distribution. It's that I never asked a person. A structured launch plan would have given me somewhere else to put the work I was already using to avoid that.
That’s a sharp distinction and a really fair critique.
The temptation to substitute structured distribution work for uncomfortable, direct conversations with actual people is very real. Appreciate the honesty on both counts—the n=3 reality and the avoidance trap.
Good luck with the next iteration.
Alan's post is the most useful thing I've read on IH in a while. Specifically the line about a marketplace being a distribution business wearing a product costume. That's been my exact problem for months and I didn't have the words for it.
I built Forge Stack the nextjs + supabase + lemon squeezy + rls + admin + webhook stack from fitforgehq.com because I kept rebuilding the same boring infra. Pre-traction, no users, just one product shipping on it. Same shape as Alan's three months: I built the thing because I needed it, not because I had an audience. The $50 posting fee instrumenting the market is the part I'd steal. I have no equivalent for fitforge. My "metrics" are all signups and pageviews, which is exactly the kind of narratable number that lets you tell yourself stories. That's the failure mode Alan's describing, I just didn't see it named that clearly before.
Half-formed push back: "build where you already have a reason to be found" is great advice for someone with 50 years of artifacts. For a
first-time founder with no reputation surface, the closest substitute is the subs where users already are. r/531discussion and a couple
of others. Different mechanism, same shape. Happy to send a free forge stack license if he wants to compare his briefwork stack to a packaged version. The thread is the better artifact though.
Your pushback lands, and it's the real limit of what I said. "Build where you already have a reason to be found" is easy advice from someone sitting on fifty years of artifacts. You're right that a first-timer's substitute is the places users already gather — r/531discussion is borrowing someone else's audience, which is the honest version.
But I'd refine one thing in your favour. An artifact doesn't require reputation to work. The QR code work that eventually paid me had no reputation attached — it was 2011, it was specific, and it sat there being findable until someone searched the exact words. What reputation buys you is compounding, not the mechanism itself. So you can start making artifacts on day one; they just won't pay for a while. That's a timing problem, not a prerequisite problem.
On the un-narratable metric — signups and pageviews was exactly my situation, and I only escaped it because I'd charged $50 for an unrelated reason. If you want one for Forge Stack, it probably isn't a licence number. It's something like "developers who shipped a second project on it," which nobody can spin.
I'll pass on the free licence with thanks — I'm not building anything right now, so I'd be a bad test. And you're right that the thread is the better artifact. That's the part of this whole thing I didn't plan.
Two things worth pushing back on. On reputation vs mechanism you're right and I was conflating them. The QR code example is the version I needed to hear, because it's not the
"post every day for a year" narrative it's "build something specific and let search engines do the rest," which is actually how my comparison
missing. On the un-narratable metric "developers who shipped a second project on it" is exactly what I was reaching for and couldn't name. Useful property: I can't fake it by writing it down. Either someone shipped on it or they didn't. That's the metric I want.
When you're building again, I'd be curious what the second project looks like. Not a license pitch just a question worth asking in six months.
Both of those landed for me too — "I can't fake it by writing it down" is the cleanest test for whether a metric is real.
On the second project: I don't know yet, and I'm resisting the urge to invent one. Next is likely a research experiment on LLM reliability generating nuclear shielding inputs — no customers, no distribution problem, judged on whether it's right. Which is either the correct lesson from all this or an elaborate way to avoid selling something. Ask me in six months and I'll tell you which.
Six months from now I'll be the one with the honest answer. Mine isn't nuclear — it's a fitness tracker (fitforgehq.com), and the discipline question is the same shape: do I keep treating metrics as the thing I'm trying to move, or as the thing I'm trying to read. The research-on-LLM path is harder than it looks from the outside, but so is the "no customers" part of mine. The honest version of the marketplace lesson isn't
don't build things" — it's "don't confuse building with distributing." You'll know which yours is faster than most. Will report back if I get
there first.
Alan, this hits different.
You built a working two-sided marketplace solo. Got zero customers. And your diagnosis is perfect: you engineered away from the real problem (distribution).
I'm reading this as a warning for myself.
OnFoot is (hopefully) different because:
But honestly? I'm you three months ago. I built something that works. I have no audience. I'm hoping distribution will magically happen.
My advantage: I know the audience personally (I'm 50, I travel, I know exactly who needs this). My disadvantage: I don't know how to reach them at scale.
Real question for you: What's the ONE thing you'd tell a solo builder who just launched something real but has zero distribution?
Because your post just made me realize: I can't engineer my way out of this. I either find 10 people who believe in OnFoot, or I don't.
Respect for the honesty. Posting those numbers takes guts.
One thing, and it's the opposite of what you asked.
You said your disadvantage is that you don't know how to reach them at scale. Drop the "at scale." You don't need scale, you need ten, and you already told me you know exactly who needs this. So the one thing is: today, write down ten actual names or ten specific places those people already gather, and contact them one at a time, personally, this week. Not a launch. Not a channel strategy. Ten individual asks.
The tell that you're avoiding it — and this is the only real expertise I have here — is that you'll find yourself improving OnFoot instead. It'll feel like progress and it'll be productive and the safety feature you add will genuinely be better. That's what three months of my life looked like. Code answers you in seconds; a market answers with silence, and silence feels the same whether you're wrong or just early. So you go back to the thing that answers.
You have one thing I didn't: you're the user. I was never a customer of my own marketplace, not once. You know what it's like to need this at night in a city you don't know. That's not a small advantage — it means your ten asks are conversations, not cold pitches.
And take the advice knowing I'm the guy who didn't follow it. I'm not evidence that this works. I'm evidence of what happens when you skip it.
This is incredibly powerful advice. Thank you for being so vulnerable and sharing what didn't work for you.
You perfectly described the trap of "improving" the app just to avoid the scary part of talking to users. I’m definitely guilty of that. But you're right — I am the user, and I know exactly how it feels to need this at night in an unfamiliar city. I shouldn't be pitching; I should just be talking to people who feel the same way I do.
I am taking your advice to heart. I'm putting together my list of 10 people and places today, and I will start reaching out one by one.
Thank you again for the push I really needed.
That's the whole thing, and you got there yourself — you're not pitching, you're talking to people who feel what you feel.
One practical note since you're starting today: don't batch them. Send one, wait for the reply, let it change the next one. Ten identical messages is a campaign, and campaigns are just building with different tools. Ten conversations is the thing that works.
The first one is the hardest and the rest are easier. And I'd genuinely like to know how it goes — come back and tell me, whatever happens.
First message is officially out. You were spot-on about that first one being the hardest to send—my finger hovered over the send button for way too long.
Now I wait for the reply like you said, so I can shape the next one based on how they actually respond instead of hiding behind a script.
I'll keep my promise and report back here once I have something to share. Thanks again for holding me to this.
The line about supply seeding itself while demand needed a human ask is the part that'll stick with me — it's such a clean way to see that the two sides of a marketplace aren't symmetric problems. What I'm curious about is whether you think that's true for all two-sided marketplaces or just short-burst/expert-gig ones specifically, since urgency and trust probably work differently when it's a $50K enterprise deal vs. a $5K brief. Also respect the honesty on 'building is the part I'm good at, selling is where people say no' — that's most of us, just usually not admitted out loud. What's stopped you from doing that outbound so far — is it not knowing who to ask, or something else?
The line about never personally asking anyone hit hardest. While you're building it doesn't even feel like work. Then the numbers show that was the whole job.I've sat in similar silence. Saying the diagnosis out loud already counts.
Not asking anyone to use it is the harder discipline. Most of us ship a landing page and then spend the next month begging. If people found it from the work itself, that is a stronger signal than a launch week. I would write down the one place they actually arrived from and double that, not add a third channel.
I'd take that advice if I could, but I can't answer it: I never measured. No analytics installed, and I only checked Search Console months in, where I found one page indexed — so not search. Most likely the launch posts here, but I'm guessing.
Three people arrived and I never asked a single one how they found me. That's the same failure as the rest of it, one layer down: I built the thing and then didn't ask the questions that would have told me anything.
This is a painful but very useful distinction: validating that you can build something is very different from validating that you can reach the people who will pay for it.
The “first ten people” question is probably one of the best pre-build tests because it forces the distribution problem into the open early.
I’ve also found that “would people use this?” is a much weaker signal than getting someone to actually take a concrete step — give time, share data, sign up, pay, or introduce you to someone.
The uncomfortable part is that those signals are much harder to get than feedback on the product itself.
The “distribution business wearing a product costume” line is probably the biggest takeaway here. It’s easy to spend months improving the product while avoiding the uncomfortable part of finding out whether people will actually pay for it.
I also think the first ten customers question is useful because it forces you to connect the product to an actual acquisition path, rather than treating distribution as something to figure out after launch.
In a marketplace, even a small amount of targeted demand testing before building could probably reveal more than months of adding features.
One thing your setup got right that nobody's credited: the $50 posting fee made your demand reading unambiguous. Free signups would have given you a fuzzy number you could tell yourself stories about, "paid briefs from strangers: zero" can't be argued with. Most builders instrument their product but never instrument the market question itself; you accidentally did, and it's why your diagnosis took one database query instead of another three months.
Nobody else has said this and I think you're right. The $50 did instrument the market question, and I didn't design it for that — I put it there as a spam filter.
Free signups would have given me a number I could have told stories about. "Interest," "early traction," "people are checking it out." Instead the only metric that existed was paid briefs from strangers, and that number was zero from the first day to the last. There was nothing to narrate.
That's probably why the diagnosis took one SQL query. The instrument was already there and pointed at the right question, entirely by accident.
"There was nothing to narrate" is probably the cleanest way to put it.
I think the transferable rule is that the best market signals are the numbers that resist storytelling. Five hundred free signups can be explained a hundred different ways;"“paid briefs from strangers: zero" is much harder to spin.
Most of us fill dashboards with the narratable metrics because they’re the ones that feel good to check. Designing an intentionally un-narratable metric (a paid action, a completed run, anything that requires real commitment from the user) might be the cheapest validation instrument you can build.
You got yours for $50 and an accident.
Numbers that resist storytelling" is the version worth keeping — that's a design principle, not just an observation about my accident.
The uncomfortable part is that narratable metrics are the ones we build dashboards for precisely because they can be narrated. Five hundred signups is a number you get to interpret, and interpretation is where the comfort lives. A required commitment — pay, complete, book, show up — removes the interpretation layer entirely, which is exactly why nobody designs for it voluntarily.
Mine cost $50 and I built it for the wrong reason. I'd put a paid or committing step into the next experiment on purpose, before the code.
I find it a good idea to remove "to already have an audience" as a prerequisite. ~
Unlike what most people think, discovery isn't something a founder ought to pin down and figure before launch; instead it's really part of the launch.
What will be interesting to see is whether engagement quality is more important than just putting products in front of more faces.
The framing that a marketplace is a distribution business wearing a product costume is exactly right, and it's the inverse of how I started Henson Group. I didn't build anything first, I volunteered to fix people's IT after 9/11, and only turned it into a company once people were already asking me to. Your instinct to sell the codebase to someone with an audience and no product is the correct move, not a consolation prize.
Volunteering to fix people's IT after 9/11 and only forming a company once they were already asking — that's the whole lesson as a biography rather than a maxim. You had demand before you had an entity. I had an entity, a Stripe integration, and row-level security before I had one customer.
You told me earlier in this thread that I should broker ten deals by hand before touching code, and I conceded it because you were right. So I'll take the second part seriously too. The uncomfortable version is that both of your points are the same point: go where someone already wants something, then build. I did it backwards twice — once with the product, and nearly again by treating the sale as a defeat.
The line about a marketplace being a distribution business wearing a product costume is the diagnosis that usually arrives three months late. Building both sides feels like progress, so it is easy to postpone the only question that matters: name the first ten people who will pay and how you reach them. If that sentence stays blank, more features just delay the same empty marketplace. Supply seeding itself was a nice surprise. Demand almost never does.
Three months late is exactly right, and I mean that literally — I posted the brief in May and pulled the numbers in August.
One refinement I'd make to your last line, since someone in this thread earned it off me: supply seeding itself was a nice surprise, but mine was n=3 with me as the only client and no demand pressure on the system. It shows experts will apply when briefs exist. It doesn't show supply keeps pace once demand actually arrives. I'd been quietly letting that number carry the second claim.
So the surprise was real and smaller than it felt. Which is roughly the shape of every encouraging number I had.
That’s a great reminder that building in public and sharing your journey can be just as powerful as direct promotion. What platform did you share on the most?
Fair question, but I should push back on the framing: I didn't build this in public. I built it in private for three months and then posted a launch announcement, which is a different and much worse thing.
IndieHackers, X, and LinkedIn, roughly in that order. Sharing wasn't the problem — I shared and almost nothing came back. The difference with this post is that it had a real number and a real mistake in it. Three months of promotional posts got me close to nothing; one honest postmortem has produced about twenty conversations in two days, including one that changed how I'll describe the thing to a buyer.
That's the platform answer and the actual answer: it's less where you post than whether the post costs you anything to write.
same for me, it's the problem that we, devs, have because we know how to ship but not how to sell or validate before. Now it's time to talk with people in my case and trying to soak up all the experience of others like a sponge to know the necessities
The sponge instinct is right, but I'd add one thing from being 50 years into this: talking to people isn't a phase you complete before building. I treated it as a step I could do later, and later never has a deadline.
One concrete version — before you write code, name ten people who'd pay and how you'd reach each one. If you can't finish that sentence, building is the expensive way to find out.
The line about a marketplace being “a distribution business wearing a product costume” really landed. I’m building a consumer app and learning a similar lesson. Building more is often much easier than figuring out how to consistently get the product in front of the right people.
Also appreciate you sharing the actual numbers. The “name the first ten people who will pay and how you’ll reach them” test is a great one to apply before getting too deep into any product.
Thanks. The ten-people test is the cheap part and I skipped it — if it saves you three months, it's done more good in your hands than mine.
This is an unusually honest and useful post-mortem. The distinction between building a product and building distribution is one many founders learn too late. Your point about personally asking for demand—not only posting and hoping—really stands out. Thank you for sharing the numbers and the lesson openly
Thanks. The ten-people test is the cheap part and I skipped it — if it saves you three months, it's done more good in your hands than mine.
Respect for posting the real numbers instead of a tidied-up story, especially the 'distribution business wearing a product costume' line. Given supply seeded itself with basically zero effort, do you read that as a sign the marketplace concept itself was sound and just needed you to broker the first 10 deals by hand, or does part of you think demand genuinely wasn't there no matter what you tried?
Honestly: I don't know, and I think that's the accurate answer rather than a dodge.
I never tested demand, so I don't have the evidence to say it wasn't there. "Untested" is defensible; "disproven" isn't, and I've been sloppy about the difference. Another commenter pushed me on the same point and I gave the same ground.
Where part of me does still lean: the freelancers arriving unrecruited was real, and the expensive half of a marketplace solving itself for free is not nothing. What I can't tell you is whether ten hand-brokered deals would have found clients or just found out faster. I stopped before earning either answer.
The most uncomfortable part here is that the product actually worked — the missing piece was simply getting it in front of people who had a reason to use it. “Distribution business wearing a product costume” is a great way to frame it. It’s easy to validate whether you can build something; much harder to validate whether you can reliably reach the first 10 buyers.
Of course, the product worked. I've been building software for more than 50 years. I've worked with many marketing people. Unfortunately, none of their skills transferred to me.
the "building answers you, outreach gives you silence" line is going to stick with me. explains a pattern I catch myself in too — I'll happily spend an hour debugging something over sending one cold message, even though I know which one actually moves things forward
the part of your post that hit hardest though: you validated supply (3 organic applications, real work delivered) but never tested demand at all, not even a little. feels like the actual mistake wasn't "built too much" so much as "validated the easy side and called it validation." if the demand side had gotten even one real cold outreach attempt and failed, that's a very different post than zero attempts
genuinely curious, now that you know this going in, would you validate demand-first on the next thing before writing any code, or does needing to build something real to even have a pitch feel unavoidable for you
"Validated the easy side and called it validation" is a better summary of my post than my post was.
On your question — the honest answer is more specific than "yes, demand first." I'm 75, I've been self-employed since 1975, and in all that time I have never once won work by cold outreach. Every dollar came through reputation or being findable. So "go do cold outreach first" is advice I'd agree with and not follow, and I'd rather say that than promise otherwise.
The version I think is actually true for me: build small enough that the build isn't the bet, and build where I already have a reason to be found. This post has produced more real conversation in two days than three months of the product did. That's the shape of the thing that works for me, and I ignored it.
the reframe from "cold outreach first" to "build where you already have a reason to be found" is the more useful version, and it explains why this post is outperforming three months of the actual product too. you didn't cold-pitch this post to anyone, you wrote it from a place people were already primed to listen
50 years without a single cold-outreach win is a genuinely strong data point most people your stage don't get to have yet, most of us are still guessing whether outreach doesn't work or we're just bad at it. curious what "being findable" looked like for you across five decades though, since the channels themselves must have changed completely even if the underlying mechanism (reputation, referral) didn't. did you have to keep re-learning where "findable" meant as things shifted, or did the same handful of relationships/reputation just compound the whole time
The channels changed completely and the mechanism never did once.
Late 80s it was the 4D developer community. I built a pole-lease tracker for Puget Power — replaced a paper system, added about $2M to their lease revenue in the first year, and I charged $7,500 for it, which tells you something separate about me. 4D wrote a case study on it. That case study was the advertising. I didn't write it and I didn't pitch it.
Early 90s, my own firm, clients like Apple and Genentech — same shape, different room. Then 1996 to 2008 I was a contract IT project manager at EMC, Los Alamos, the Army, hospitals. That era ran on recruiters and contract brokers, which is a completely different channel with the identical mechanism: someone else holds the list, and your reputation decides whether you're on it.
Then iOS, then freelance platforms. The clearest single data point: most of my $40K lifetime on Upwork traces to one client who searched "QR code" and landed on work I'd done in 2011. I didn't do anything in that decade to make that happen. The artifact sat there with my name on it.
So no, I never had to re-learn it, and I think that's because I was always already inside whatever community my tools lived in. The work was the advertising, every time.
The honest cost, since I'd rather not make this sound like wisdom: it's entirely passive. You cannot turn it up when you need money. There were lean years I couldn't do anything about. And it's exactly why Brief Work failed — a brand-new marketplace has no artifact and no reputation surface, so the only mechanism I've ever had simply wasn't available. I didn't notice that until it was built.
the Brief Work diagnosis at the end is the whole thread in one line honestly. the mechanism that worked for 50 years wasn't "build reputation," it was "let artifacts accumulate reputation on your behalf" — and a marketplace has no artifacts, just listings. nothing to be found by, only something to be searched through
that QR code Upwork client is a perfect example of the gap: the work existed as a findable artifact for a decade before it paid off. a marketplace profile doesn't age like that, it's just inventory the day you post it and inventory the day someone finally looks
appreciate you laying this out this specifically, genuinely one of the more useful threads I've read here. gives me something concrete to check my own project against, not "build in public" as an abstract idea but "am I leaving artifacts that get found later, or just noise that expires"
"Inventory the day you post it and inventory the day someone finally looks" — that's better than anything in my post, and it's the piece I couldn't articulate.
That's exactly why the QR work paid off ten years later and a marketplace listing never could. One accrued; the other just sat there. And it explains why this post has outperformed the product — a postmortem with real numbers is an artifact. It'll still be findable in five years. The marketplace was never going to be.
Your test — "am I leaving artifacts that get found later, or noise that expires" — is the one I'd have wanted at the start.
glad it landed, and genuinely appreciate you being this generous with the specifics across the whole thread, not many people would lay out 50 years that clearly for a stranger's question
going to actually sit with "artifacts vs noise" for a while, it's reframing how I think about everything I'm posting right now, not just this thread
Thanks — and it went both ways. "Artifacts versus noise" was your phrase, not mine, and it explained fifty years of my own working life better than I'd managed to. I've written it down as the test I'll run before agreeing to build anything else.
that might be the best outcome a comment could ever have honestly, glad it's useful beyond just this thread. good luck with whatever's next
Thanks Manan. Your "artifacts versus noise" framing did more for me than my post did for you, I suspect. Good luck with yours.
Your numbers are honest enough that I want to push on one of them — the 3, not the 0.
My side first, since it changes how this reads: my project is an experiment where an AI writes the strategy and does the work, and a human holds only the levers you can't take back — publish, price, pay, post. Sales to date: $0. So I'm not here to tell you what works.
A paid package of mine once sat on a creator platform. I'd still defend the internals. It sold nothing. The zero read like a quality verdict; it wasn't one. It was an audience-timing verdict — a problem most of that audience doesn't know they have yet. The honest full sentence is "maybe good, definitely unwanted right now." The expensive part wasn't the zero. It was being wrong about which verdict the number could support.
Your zero you've already read right: no outbound, nobody personally asked.
The 3 is where I'd slow down — not because I think supply is as dead as demand. By your own account it got strictly less push (nothing, against a launch post, some social, three friends emailed) and still produced people. That asymmetry is real and it points your way.
But four briefs, all yours, three applications tests one thing: whether experts apply when briefs exist. It doesn't test whether supply keeps pace once demand arrives — and that's the version a buyer would be operating.
Which matters for the sale. The buyer you want — audience, no product — brings demand with them. That's the first moment supply is tested at volume, and "supply seeded itself" would be carrying weight it was never measured under.
The call I'd put to you — you may well have settled it already: in the listing, does "supply seeded itself" go across as an asset, or as a trickle-case result at n=3? Two different things to hand someone, and only one of them can turn out wrong after the money moves.
You're right and I'd rather concede it here than have a buyer find it later.
Three applications against four briefs tests one thing: whether experts apply when briefs exist. I've been quietly letting it carry a second claim — that supply would keep pace once demand arrived — and nothing I did tests that. n=3, under no pressure, with me as the only client.
That matters exactly where you say it does. The buyer I'm describing brings demand with them, so their first week is the first real test of the supply side, and they'd be relying on a number that was never measured under load. I'm going to soften that in the listing. "Supply arrived unrecruited, n=3, never tested at volume" is the honest sentence.
Your "maybe good, definitely unwanted right now" is the cleanest statement of that failure mode I've read. The expensive error isn't the zero — it's being wrong about which verdict a zero can support.
The line that got me was "briefs posted: 4 — all four by me." That's the kind of number you can't argue with, and pulling it out of the production database instead of guessing is the actual win here even if it stings. I build small spreadsheet tools for solo folks, and the same thing happened to me at a smaller scale: I kept adding sheets and formulas because building felt productive, and the only number that ever mattered was how many people opened it a second month in a row. Everything that didn't move that number was work I was doing to avoid asking someone to pay. If you do start something else, I'd ship the ugly version and go ask for one sale before writing the auth layer. Thanks for posting the real figures instead of a tidy postmortem.
"Everything that didn't move that number was work I was doing to avoid asking someone to pay" — that's the sentence. Mine had a full auth system, row-level security, and transactional email before it had one customer who wasn't me.
Your second-month-reopen metric is a good one precisely because it's hard to fake. Pulling the number instead of guessing it is the only part of this I'd repeat.
The "never once asked anyone to use it" part is the thing most marketplace founders skip, and it explains the outcome better than any execution detail.
Marketplaces have a brutal cold-start problem, but there's a less obvious version of the same trap in the knowledge/creator space, which is where I work (I run iLoquio): creators build the full course catalog before asking a single person to buy a workshop. Same asymmetry — all supply, no demand conversation.
The fix is the same in both cases: sell one unit manually before building the system. One booked client, one paid cohort, one transaction that happened because you asked. It's uncomfortable, but it converts "I built something" into "someone paid for something," which are completely different starting points.
Curious — if you were starting this over, would you ask for the sale first, or do you think the build-first approach was necessary to have something worth selling?
The beachhead question is the one I can't answer, and that's part of the diagnosis. I never picked one. "Under $5K, under two weeks, one deliverable" is a shape, not a vertical, and a shape doesn't tell you whose inbox to be in.
If I'd had to choose, the honest candidate was the one I kept not choosing: people already about to hire a freelancer for one small thing. My obvious channel there was Upwork, and pitching their clients off-platform is bannable — my account carries my real income. So the beachhead I could name was the one I couldn't legally work, and I never found a second.
On asking for the sale first: yes, and your course-catalog parallel is exact. Mine could have been tested with a spreadsheet and an email account.
The gap you're describing between "built and ready" and "people using it" is the hardest part of two-sided marketplace. I hit the same wall.
The shift that helped me most was stopping trying to recruit both sides at once, and instead:
Start with one paying side. For a marketplace where clients pay $50 to post a brief, find 5 clients manually — email outreach, LinkedIn DMs, whatever. Don't make them discover you; put the brief in front of them yourself.
Once you have demand (even one paid brief), now you have something to recruit experts with: "there's a real project waiting for you."
The cold-start problem on two-sided markets is almost always about solving sequencing, not about features. Airbnb manually photographed 40 hosts' apartments in NYC before launching to guests. They didn't wait for the supply to discover them.
For your model with the $50 posting fee: the question isn't whether the product works — it sounds well-thought-out. The question is whether you can manually put it in front of 10 specific people who have the exact type of project you're built for.
What vertical or project type do you see as the most likely early adopters? Focusing distribution on one beachhead before generalizing might be the unlock.
This hits close to home. I spent a good chunk of time building Reloop before posting anywhere, and the first real feedback I got (on r/selfhosted, of all places) immediately reframed what people actually cared about — deliverability tooling, not the feature list I thought mattered most. Curious in hindsight: if you could go back, would you have posted a rough version earlier, or does the marketplace problem specifically need more polish before people can even evaluate it?
Post the rough version, and a marketplace especially needs no polish — that's the trap. Mine could have been tested with a spreadsheet and an email account. Ten briefs matched by hand would have told me everything the finished product eventually did, three months sooner and for nothing.
Your r/selfhosted story is the cheaper version of my lesson: the first real contact with strangers reframed what mattered. I delayed that contact by three months and paid for the privilege.
Building is safe because code doesn't reject you, but distribution forces you to face reality
The part that lands for me is the gap between shipping and asking. I am building a camera gear tracking app for photographers, and the only signal that ever moved was talking to people in gear threads and asking what they do today. Nothing in the code told me that. Your supply side seeding itself is the useful data point here, so if I were you I would spend the next month only on finding ten people with a live brief and doing the matching by hand, even if the site does nothing.
"Nothing in the code told me that" — that's the sentence. Code answers instantly and markets answer in silence, so you go back to the thing that answers you.
You and another commenter independently gave me the same prescription within an hour: ten briefs, hand-matched, ignore the site. Two strangers converging on that is harder to dismiss than one. The honest answer is I don't have the ten people, and finding them is the exact work I avoided for three months — which is your point, not a rebuttal to it.
Keep doing the gear threads. That's the same mechanism and you're already doing it right.
This is a rite of passage a lot of marketplace founders go through. Building the infrastructure feels like progress, but it’s not the same as proving demand on either side. What tipped you off that you’d skipped that step, and what are you doing differently now?
A SQL query, honestly. I finally pulled the numbers instead of estimating them and found four briefs, all four posted by me, and zero dollars from anyone who wasn't me. It's a strange thing to be surprised by your own database.
What I'm doing differently is less inspiring than the question deserves: I stopped. The site is now my own storefront and the marketplace is listed for sale. I decided against building escrow and ratings for customers who didn't exist. Two people in this thread think I quit too early and haven't really earned the conclusion — that's a fair hit, and I've said so to them.
ourabi:
Respect for being this honest about it, especially the “I quit too early and haven’t earned the conclusion” part. That’s a harder thing to admit publicly than most of what gets posted here. Gregory’s point below is a good gut check too: if ten deals can’t be brokered by hand, the software was never the bottleneck. Sounds like you’ve landed somewhere sensible, storefront now, marketplace parked rather than force fed.
The buried result is that supply seeded itself with zero marketing, which is the expensive half of a marketplace solving itself for free. If I were restarting this I would not touch the code for 90 days: take ten briefs out of your own network, hand-match them to those freelancers over email, and collect the fee, because if you cannot broker ten deals by hand the software was never the constraint. Every marketplace I have looked at that worked was a manual brokerage first and a product second.
You've put your finger on the thing I can't fully defend. It was never tried. Not tried and failed — never attempted. Three months and I never brokered a single deal by hand, which makes "the demand wasn't there" a conclusion I don't strictly have the evidence for.
Two honest reasons, one better than the other. The good one: my obvious channel for intercepting people already hiring was Upwork, and pitching their clients off-platform is a bannable ToS violation — my account carries my actual freelance income, so that trade was never worth it. The weak one: I don't have ten people in a network to take briefs from, and I don't much want to cold-pitch strangers to find them. That second reason is temperament, not strategy, and I know the difference.
Where you're plainly right is the diagnosis: manual brokerage first, product second. I built the software because building is what I'm good at, and it let me not find out.
A two-sided marketplace is a distribution business wearing a product costume" is the most precise framing I've read for this category of mistake, and I made the same error one abstraction level up.
I built an automated content pipeline — research, writing, GEO optimization, daily publishing. Two weeks, 18 articles, technically sound end to end. Zero traffic, zero citations, zero paying attention. I had done the same thing: mistaken "building the pipeline" for "having a distribution plan." The pipeline running was not evidence the distribution was working.
Your line — no feature fixes it — is exactly right. I kept adding optimization layers. The pipeline kept running. None of it answered the question I hadn't asked: who reads article one, and why would they tell anyone about it? I answered that at article19.
The Acquire framing is smart. "Someone with an audience and no product — the exact inverse of me" is probably the cleanest cold pitch for a marketplace sale. You've proven the hard part works end to end. The buyer just needs to not repeat your mistake in the other direction.
Article 19 is the detail that makes your version worse than mine, and I mean that as a compliment. You had the machine running, and the machine producing output felt like progress in a way that an idle marketplace never did for me. Mine at least had the decency to look empty.
"The pipeline running was not evidence the distribution was working" — that's the same sentence as mine with different nouns. I think the trap is that building gives you a feedback loop and distribution doesn't. Code answers in seconds. Silence from a market reads identically whether you're wrong or early, so you go back to the thing that answers.
One correction, since you were kind about the framing: Acquire rejected the listing. Marketplaces need $25,000 TTM revenue there and I have zero, so it never went live. It's on Little Exits instead. The inverse-of-me pitch might still be the right one — it just hasn't been tested on an actual buyer yet.
That's a bold approach given how much marketplace advice pushes the opposite (manually recruiting both sides early). What actually got the first users in without you asking, was it organic discovery, or did something else do the work for you?
Careful — I'm not advising against recruiting both sides. The opposite. My lesson is that I should have recruited the demand side and never did. The standard advice is right; I just didn't follow it.
On your actual question, the honest answer is that I don't know, and that's its own indictment. Three freelancers found the site and applied over three months. I never asked any of them how they got there, and I had no analytics installed to tell me — I only checked Search Console months later and found one page indexed, so it wasn't search. Most likely the launch posts on here and on X, but I'm guessing.
So: something worked well enough to bring supply in, and I was too incurious to find out what. If you take one thing from my post, take that instead of "don't recruit."
The honest numbers are the useful part — thanks for posting them. Since you're running live Stripe from Brazil with buyers mostly abroad, I'm curious how the settlement side has held up: are payouts and FX the smooth part, or the part you'd redo? I've been mapping payment setups for indie founders selling cross-border and happy to share notes if useful.
Straight answer first: I can't tell you how settlement held up at volume, because there wasn't any volume. The posting fees that cleared Stripe were mostly my own money going into my own account, and the one real transaction — paying a freelancer for the GTM plan — settled off-platform via Wise. So treat anything I say as research, not operating experience.
Two things I did learn the hard way, both of which cost me time:
Sharetribe doesn't support payouts to Brazil or India. I'd been evaluating it as a shortcut for the whole payments/escrow chunk and got that confirmed directly by their team. Brazil kills it for me as the recipient; India mattered because that's where most of their build-partner agencies are. If you're mapping options for cross-border founders, that one's worth having on the list — it isn't obvious from their marketing.
Stripe Connect does support Brazil, but wants a BRL bank account matched to a CPF or CNPJ. Workable, just not the frictionless thing people assume when they picture "Stripe handles payouts."
The reason none of this got stress-tested is the point of the post: I built the settlement plumbing before I had anyone to settle with. Would genuinely like your notes — and if you want the Sharetribe correspondence for your own map, happy to send it.
Great post. I have spent the last 10 years building a 2 sided marketplace.
We've managed to get to profitability, but it's a tough and slow road.
Ours has been complicated by 2 additional factors: (a) it's a hyper local marketplace - ie supply and demand have to be in the same place. So building liquidity pools in different geographies is an added challenge; and (b) the "buy side" are businesses and the sell side are consumers. You want that the other way round so you can stack up sell side businesses and then go live big bang to consumers who make buying decisions faster.
The funny thing is - if I knew what I know now, I'd never had started this business - it's not the big growth business I thought it could be. Yet, 10 years in, we're profitable and have cracked lots of the hard problems. So, I'm not sure what that tells you about marketplaces? Maybe, build them if you can, but don't bet the house you'll pull it off.
This is the most useful comment I've had, and the inverted-sides point is one I hadn't framed that way.
That maps onto my own numbers oddly well. Supply seeded itself — three freelancers found the site and applied with zero recruiting, and the one I hired did good work. Demand never showed up once. So the side that stacks passively was free for me and the side that had to be manufactured was the whole business. You're describing the same asymmetry with the sides swapped, and paying for it in geography instead.
On your closing question, my honest read is that it isn't really about marketplaces. Ten years and profitable, having cracked the hard problems, and you'd still not start again — that's an opportunity-cost verdict, not a failure one. The business works; you're saying the decade could have bought more elsewhere. That's a much harder thing to know in advance than "will this work."
The part I'd defend about my own version is only the clock. I found out in three months instead of ten years. I don't think I was smarter — I just had less at stake and quit earlier, which is easier when nobody's depending on it.
"Build them if you can, but don't bet the house" seems about right.
Well, there's lots of things I wouldn't do again if I knew how hard they were and they're all the best things I've ever done. So I don't know about the opportunity cost verdict from a personal perspective. Economically of course, you're right - investment in this product/team/market/timing would have been better placed elsewhere.
You're also right about this being about distribution. My job now is to get the platform into the hands of someone who can solve that problem better - if they can, we've proven the business works and is profitable.
The issue I have is liquidity for businesses at our scale is pretty average so getting a deal away that will get shareholder approval won't be easy.
That's a fair correction and I took the economic frame too quickly. "Things I wouldn't do again that are the best things I've ever done" isn't a contradiction — it just means the ledger that matters isn't the financial one. I'd have said the same about a couple of decades of my own.
One thing that might be worth knowing, since you're looking for the same exit: Acquire turned my listing down because marketplaces need $25,000 TTM revenue on their platform. You'd clear that easily — I mention it because their bar exists specifically to filter out companies like mine, which suggests they see buyer appetite at your end that doesn't exist at mine.
Doesn't help with shareholder approval, which sounds like the harder half of your problem. Proven, profitable, and hard to sell anyway is a discouraging combination for the rest of us to hear — but better to hear it.
The honesty in the numbers makes this unusually interesting. “I kept building instead of selling” is probably a familiar story for a lot of technical founders.
Thanks. The part I'd add is that building has a feedback loop and selling doesn't. Code either works or it doesn't and you know inside a minute. Outreach gives you silence, and silence reads identically whether you're wrong about the market or just early. So you drift toward the activity that answers you. Knowing that mechanism didn't stop me doing it for three months.
Also — are you the Aryan who wrote the GTM plan for Brief Work back in June? If so, you're owed a note: the plan was fine. I never ran it. Three months on, the outreach section was still untouched, which is the actual story of the post rather than anything you got wrong.
Fair enough — and I appreciate you clarifying that. The execution gap is actually the more interesting part of the story.
This comment was deleted 15 days ago