Skip to content
App Graveyard
Plot #0008
FailedWebMarketplaceComposite example · Metrics illustrative

SkillSwap

A skill-barter marketplace that ran into the double-coincidence problem immediately

Autopsy summary

SkillSwap was built for Web in Marketplace. It died primarily from bad business model, but the useful signal is the lesson: Ignoring a 2,000-year-old economic lesson. Money was invented precisely because barter (trading skills/goods directly) is insanely inefficient. A skill marketplace recreates the barter problem. The Twitter validation ('200 likes!') measured concept appeal, not actual willingness to use. People love the idea of trading skills. Almost nobody will actually schedule time to teach a stranger guitar in exchange for a stranger teaching them Python.

Cause of death

Bad Business Model

The matching problem was brutal. For a swap to happen, you need two people in the same area (or both willing to do video calls) where person A wants what person B offers AND person B wants what person A offers. That's a combinatorial nightmare at small scale. With 95 listings, the probability of a perfect match was near zero. Most people offered 'web development' or 'design' and wanted 'music' or 'language' lessons — the supply was tech-heavy and the demand was arts-heavy, with almost no overlap. Of 95 listings, I was only able to suggest credible matches for about 12 pairs, and of those 12, only 6 actually followed through. The rest ghosted after matching. The fundamental issue is that skill swaps require simultaneous double coincidence of wants — the same problem that made barter economies fail and led to the invention of money.
Useful signal

What worked

Signup was easy and people liked the concept. The Indie Hackers post drove 150 signups in a day. The skill listing flow was fast — name your skill, describe your experience level, say what you want to learn, done. People browsed and seemed interested. A few users told me it was 'such a cool idea' and they'd 'definitely use it once there are more people.'
Takeaway

What to avoid

Ignoring a 2,000-year-old economic lesson. Money was invented precisely because barter (trading skills/goods directly) is insanely inefficient. A skill marketplace recreates the barter problem. The Twitter validation ('200 likes!') measured concept appeal, not actual willingness to use. People love the idea of trading skills. Almost nobody will actually schedule time to teach a stranger guitar in exchange for a stranger teaching them Python.
Editorial read
3/10Revival potentialSolo Builder
Time spent6 weeks
Revenue$0 (planned to take a transaction fee eventually, never reached transaction volume)
Users~340 signups, 95 created a skill listing, 6 completed a swap
Money spent$250 (domain, Supabase, a few promoted tweets)
Traffic~5,000 unique visitors, mostly from Indie Hackers and a few tweets
Launched2024-10
Shut down2025-02
Built with
LovableSupabaseVercel
Composite launch case studyCurated by App Graveyard editors
Failed becauseBad Business Model
Key lesson

Ignoring a 2,000-year-old economic lesson. Money was invented precisely because barter (trading skills/goods directly) is insanely inefficient. A skill marketplace recreates the barter problem. The Twitter validation ('200 likes!') measured concept appeal, not actual willingness to use. People love the idea of trading skills. Almost nobody will actually schedule time to teach a stranger guitar in exchange for a stranger teaching them Python.

Worth rebuilding?
3/10

Timeline

Launch2024-10
Current statusFailed
Shutdown or pause2025-02
Narrative

The story

The useful part is not that it failed. It is where the founder saw signal, where the bet broke, and what a second builder should avoid.

Context

What was built

SkillSwap was a web marketplace where people listed skills they could teach and skills they wanted to learn. The matching worked like a dating app — if person A offers 'web development' and wants 'guitar lessons,' and person B offers 'guitar' and wants 'coding,' the platform would suggest a swap. Users could browse listings, message each other, and schedule video calls through the platform. I built it with Lovable in about 3 weeks for the first version, then spent another 3 weeks on messaging, matching, and profiles.

Thesis

Why they built it

I wanted to learn Spanish but couldn't afford a tutor. I'm a web developer and figured someone learning to code would happily trade — I teach them React, they teach me Spanish. I posted about the idea on Twitter and got 200+ likes, so I assumed there was demand. The 'sharing economy for skills' felt like a concept that should exist.

Signal

What worked

Signup was easy and people liked the concept. The Indie Hackers post drove 150 signups in a day. The skill listing flow was fast — name your skill, describe your experience level, say what you want to learn, done. People browsed and seemed interested. A few users told me it was 'such a cool idea' and they'd 'definitely use it once there are more people.'

Breakage

What failed

The matching problem was brutal. For a swap to happen, you need two people in the same area (or both willing to do video calls) where person A wants what person B offers AND person B wants what person A offers. That's a combinatorial nightmare at small scale. With 95 listings, the probability of a perfect match was near zero. Most people offered 'web development' or 'design' and wanted 'music' or 'language' lessons — the supply was tech-heavy and the demand was arts-heavy, with almost no overlap. Of 95 listings, I was only able to suggest credible matches for about 12 pairs, and of those 12, only 6 actually followed through. The rest ghosted after matching. The fundamental issue is that skill swaps require simultaneous double coincidence of wants — the same problem that made barter economies fail and led to the invention of money.

Failure analysis

Primary failure reason

Bad Business Model

Contributing factors
No Distribution

Failure chain

  • The idea generated social approval because trading skills feels fair and optimistic.
  • Listings quickly became imbalanced: many users offered tech skills and wanted language or music lessons.
  • Every successful swap required two people to want exactly what the other person offered.
  • Even credible matches often died in messaging because there were no stakes or payment.
  • The marketplace recreated barter's double-coincidence problem without enough liquidity to overcome it.

What the signals looked like

Signup was easy and people liked the concept. The Indie Hackers post drove 150 signups in a day. The skill listing flow was fast — name your skill, describe your experience level, say what you want to learn, done. People browsed and seemed interested. A few users told me it was 'such a cool idea' and they'd 'definitely use it once there are more people.'

Where it actually broke

The matching problem was brutal. For a swap to happen, you need two people in the same area (or both willing to do video calls) where person A wants what person B offers AND person B wants what person A offers. That's a combinatorial nightmare at small scale. With 95 listings, the probability of a perfect match was near zero. Most people offered 'web development' or 'design' and wanted 'music' or 'language' lessons — the supply was tech-heavy and the demand was arts-heavy, with almost no overlap. Of 95 listings, I was only able to suggest credible matches for about 12 pairs, and of those 12, only 6 actually followed through. The rest ghosted after matching. The fundamental issue is that skill swaps require simultaneous double coincidence of wants — the same problem that made barter economies fail and led to the invention of money.

Builder takeaway

Lessons

What the founder learned

Social media engagement (likes, retweets, 'great idea!' comments) is the worst form of validation. It measures 'this sounds nice' not 'I would use this.' Actual validation is people paying money or repeatedly using the product. Also, two-sided marketplaces need critical mass on both sides simultaneously, and skill-exchange marketplaces have it worse because both sides must want what the other offers. At small scale, the match rate is nearly zero. The only way this works is with a huge user base (thousands in one city) or by introducing credits as intermediate currency (teach anything, earn credits, spend credits to learn anything). But credits turn it into a payment system, which defeats the 'no money' premise.

What they’d do differently

I'd abandon the barter model entirely. Instead, I'd build a marketplace where people teach skills for money, but at affordable rates — think '$15/hour peer tutoring' instead of '$80/hour professional tutoring.' The money removes the matching problem. Or I'd build it as a community tool for a specific group (a university, a coworking space, a church) where people already know each other and are more likely to follow through on swaps.

Editorial scorecard

Revival Potential3/10

How viable is rebuilding this today?

Demand Signal3/10

Did real users or customers want this?

Execution Quality4/10

How well was it built and shipped?

Distribution3/10

Did they have a path to reach users?

Monetization1/10

Was the business model viable?

Lesson Value9/10

How useful is this postmortem for other builders?

Scores are assigned by App Graveyard editors after review. They are directional, not scientific.

Rebuild opportunity

3/10

Rebuild thesis

The barter premise should be retired. The salvageable idea is affordable peer tutoring where money or credits make matching one-sided instead of requiring two perfect wants at once.

Best operator fit

A marketplace operator with community-building experience who can start in one dense niche, such as junior developers teaching practical tools.

What to avoid repeating

I'd abandon the barter model entirely. Instead, I'd build a marketplace where people teach skills for money, but at affordable rates — think '$15/hour peer tutoring' instead of '$80/hour professional tutoring.' The money removes the matching problem. Or I'd build it as a community tool for a specific group (a university, a coworking space, a church) where people already know each other and are more likely to follow through on swaps.

First 30-day revive plan

Pick one skill niche, recruit 20 credible helpers, sell five paid sessions manually, and track whether learners book a second session.

Major risks

Quality control is hard, low-price tutoring can attract unreliable supply, and marketplaces need trust and liquidity before software helps.

Founder opt-in

Revive this app

The founder is open to revival interest. App Graveyard has not verified ownership, asset claims, pricing, or availability yet. This is an interest signal, not a transaction.

Submit private interest
Open to
Sell domainAllow rebuildOpen to offers
Available assets
DomainUsers or waitlistBrand assets
Asking priceFixed price: $750
Contact preferenceApp Graveyard relay
Contact through App GraveyardYour message is reviewed by App Graveyard first. Founder emails are never shown publicly.Open form
Avoid this failure pattern

Turn this postmortem into a pre-flight check.

Monetization Mismatch

The product creates interest or usage, but the pricing model does not match the value or behavior.

Study the pattern ->

Related postmortems

Built something that didn't work out?

Every failed app has a lesson. Submit yours and help the next builder avoid your mistake. Anonymous submissions welcome.