Before You Build
Web AppShut Down

SellanApp

SellanApp was an Amsterdam app-crowdfunding marketplace that tried to connect idea owners, developers, designers, promoters, and small backers around mobile app projects. It raised early crowdfunding interest, but later filed for bankruptcy after the company lost focus, did not pivot fast enough, and could not raise enough money to keep the service running.

View original story

Product snapshot

What it was

SellanApp let people submit app ideas, seek crowdfunding, and connect with people who could help build or promote the resulting mobile app.

Who it was for

Non-technical people or small businesses with app ideasDevelopers and designers interested in app projectsSmall backers or crowdinvestors interested in app conceptsEarly app entrepreneurs looking for an alternative to agency development

Problem / value

It tried to turn app ideas into funded and developed mobile products without requiring the idea owner to hire an agency upfront.

Core workflow

Submit an app idea, attract support, raise money, find builders, and promote the app after development.

Core dependency

The model depended on enough credible ideas, funders, and builders joining the same projects.

Product form

Web platform for submitting and promoting app ideasCrowdfunding flow for app-development fundingMarketplace connecting idea owners, developers, designers, investors, and promotersRevenue-sharing model around future app exploitation

Pricing model

FinSMEs described revenue sharing between the idea owner, fund providers, and optionally developers. Public sources do not disclose SellanApp platform fees, take rate, average project budget, or successful app revenue.

Competitors or alternatives

The founder postmortem said app generators and other ways to get apps built emerged as the market changed.He named Assembly and Crew as alternative models.SellanApp sat between crowdfunding, app agencies, developer marketplaces, and DIY app-generation tools.

What happened

Summary

SellanApp filed for bankruptcy in 2014 after trying to scale a broad app-crowdfunding marketplace.

Outcome

Emerce reported that SellanApp filed for bankruptcy and closed the site.

Core risk

Many-sided marketplace launched before a focused transaction loop was proven.

Shutdown reason

Emerce reported a funding shortfall; the founder postmortem also points to lack of focus, weak pivoting, and market changes.

Demand signal

The public evidence does not show a simple lack of interest. SellanApp had crowdfunding backers and press coverage, but the founder postmortem says the model became too broad and attracted people without a strong product vision. That means early curiosity did not reliably become committed, high-quality projects.

Distribution issue

SellanApp needed several groups to show up at the same time: idea owners, funders, developers, designers, and promoters. Without a focused wedge, each side had weak reason to participate before the others were already active.

Timeline

  • January 2012: FinSMEs reported SellAnApp raised EUR 150,000 through Symbid.
  • April 2012: The Next Web reported SellanApp opened pre-registration for its private beta.
  • October 2014: Emerce reported SellanApp filed for bankruptcy and closed the site.
  • After bankruptcy: co-founder Milan van den Bovenkamp wrote that the company should have pivoted or sharpened focus after multiple seed investments.

Before you build

Why it matters

SellanApp had early financing and a clear promise, but the public record points to a model that needed too many participant groups to coordinate before one narrow transaction loop was proven.

Primary check

Before building a marketplace for ideas, builders, and backers, prove one narrow project type can move from committed buyer to completed delivery, with repeat participation and clear economics, before adding more participant groups.

Checklist

  • What is the first narrow segment with urgent pull?
  • Which side of the marketplace will you win first?
  • What proof would make you stop broadening the platform?
  • How many completed transactions must happen before automation is justified?
  • Can one project type be completed manually from buyer commitment to delivery?
  • Will credible builders join before there is already strong demand?
  • Will backers trust the quality of projects enough to fund them repeatedly?
  • What metric proves the marketplace works: completed projects, repeat projects, margin, or retention?

Relevant if

  • You are building a marketplace with more than two participant groups.
  • You are asking passive users to submit ideas and wait for other people to execute.
  • Your traction is mostly signups, submissions, backers, or press rather than completed transactions.

Less relevant if

  • You already run repeated completed transactions manually in one narrow segment.
  • Your product is a single-sided tool that does not depend on marketplace liquidity.

Pre-build tests

  • Run a concierge project with one app category before building marketplace software.
  • Ask idea owners for a paid commitment before recruiting builders.
  • Recruit builders for a real scoped project, not a hypothetical platform.
  • Track completed delivery, quality, support cost, and repeat intent.

Transferable lessons

  • Pick one narrow buyer or project category before serving everyone with an idea.
  • Measure completed projects and repeat participation, not just submissions or crowdfunding interest.
  • Validate that builders and backers trust the quality of projects before automating the platform.
  • Pivot or narrow quickly when market alternatives change the user behavior you depend on.

If you build this today

A tighter rebuild would start with one narrow app category and run projects manually until buyer commitment, builder availability, delivery quality, completion rate, and margin are proven. Only after repeated completed projects should the product expand into a broader marketplace.