The archive · Business Models · Product decision · 2017
Demand Rush lets customers pledge monthly fees for side projects before they are built
Customers post software problems with a monthly fee attached; developers build and own the product with paying users lined up — 1100 HN points on launch day.
Demand Rush
What it had to solve
Side projects usually start with a builder guessing what people want, then hoping customers appear after launch. Demand Rush's 2017 launch tried a two-sided alternative: anyone with a problem posts it and states what they would pay per month, and developers browse the list and decide what is worth building.
How it works
In June 2017, a builder posting as 'hackerews' launched Demand Rush with a simple inversion of the usual side-project formula. Instead of developers dreaming up products and hoping customers showed up, would-be customers posted the software problems they wanted solved and attached the monthly fee they would pay, while developers browsed the list and decided what was worth building.
Listings on the site read like 'gamified savings app' or 'onsite community chat', each carrying pledges such as $5 a month from one user. A developer could take a problem, build the product, keep full ownership and charge a monthly subscription, with the pledgers already lined up as its first customers — one commenter captured it as a way to find projects that already have people willing to pay for them.
The thread scored 1,100 points and 451 comments within a day. Supporters called it 'a democratized efficient tender process driven by the market' and said it pre-validated the market before code exists; skeptics pointed at pledges that topped out around $500 a month and asked how vague requests with tiny budgets could cover real software. The founder confirmed commenters' summaries and took suggestions on curation and 'already solved' flags, but the discussion stayed on the model itself.
What made the idea stand was structural: it moved the risk of guessing demand from the builder to the market, and it let a developer keep the upside of ownership. When one commenter asked whether builders owned their work 'in an open source way', the answer came back: 'No. You own it in a business way.' The economics of the pledges were never settled in the thread, but the format had shown a cleaner demand signal than any idea list.
Why it lands
- Reversing the pitch lets demand speak with money: a stated monthly fee from real would-be users is stronger evidence than votes or comments that a project is worth building.
- Builders keep ownership of what they make and charge for access, so the platform points toward a SaaS opportunity rather than a freelance job at a fixed price.
- Publishing real listings with real prices made the model concrete enough to argue about, which is why 451 commenters engaged with the mechanics instead of the marketing.
- Asking customers to describe problems rather than ideas forced demand-side language — outcomes people will pay for — onto the supply side of the market.
What it did
The Show HN drew 1,100 points and 451 comments on 14 June 2017. Supporters called it 'a democratized efficient tender process driven by the market' and read it as pre-validating demand before code exists; skeptics noted pledges that topped out around $500 a month and asked whether such budgets could ever cover real software. The debate stayed on the model's mechanics rather than its marketing.
What you can take
Let demand name itself before you build: a monthly price volunteered by real would-be customers is sharper market feedback than any idea list — provided the pledges are big enough to pay for the work.
Since then
The record that survives is the discussion itself: when the material was captured, the archive's crawler could no longer reach demandrush.com and kept the Hacker News thread as the fallback, so no later outcome for the company is documented here. What the thread preserves is the mechanism it aired — collecting monthly payment commitments before building — and the sharp debate about whether pledged amounts could ever match the cost of real software.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe the brief you are staring at, and see who has been given the same problem.
Free account · 3 free questions · no card