For product owners

Let your customers put money behind the features they ask for.

FeatureFuel is a free feature-request board for your product, with one thing no other board has: a request here can carry a pledge — money a customer commits to pay you if you build it. List your product, point your users at it, and find out what they'd actually pay for.

Add your product

Free, and about a minute. Already listed by one of your users? Find it in the directory and claim it.

A vote is an opinion. A pledge is a number.

Any feedback tool can tell you that forty people want dark mode. None of them can tell you what it's worth to those forty. Clicking an upvote costs nothing, so on a long enough list everything looks wanted and nothing is ranked.

A pledge costs something. When a customer puts $50 behind an integration, they've told you more in one click than a hundred upvotes could — and you're looking at a list sorted by what people will actually pay for, which is a much easier list to plan a quarter from.

Up and running in a minute.

Add your product with a name and a link, and it has a page. Share that link wherever you already talk to your customers — a changelog footer, a support reply, a Discord pin. They ask, vote, and pledge; you set status and answer, and everyone following gets told.

FeatureFuel is open by design, so a customer can add a product themselves and file the first request without waiting for anyone. If yours is already here that way, claiming it takes a click and it's yours to run from then on.

What you get

Every one of these is included, on the free plan, which is the only plan.

Pledges, not just upvotes

A customer can attach money to any request — a public promise, or a real card, verified up front and charged only if and when you implement it. You decide which of those your product accepts.

A ledger sorted by demand

Every request against your product, ranked by votes and by money pledged, with the discussion and the list of who's backing what.

Nothing for your customers to sign up for

No account, no password — an email address is enough to request, vote, comment or pledge. The friction that keeps people off most feedback boards isn't here.

A public roadmap you never write

Move a request through Requested, Planned, In progress, Implemented or Declined — on the request itself, or by dragging it across a board. Order the cards within a column the way you actually mean to do the work, and that becomes your public roadmap page: planned, in progress and implemented, in your order, kept current because arranging the board is the only step there is.

Two-way GitHub sync

Point a repo at your product and requests become issues, with the labels you choose; closing the issue resolves the request, and resolving the request closes the issue. Discussions sync too. Keep working where you already work.

Replies that carry weight

Comment as the verified owner. A "we're building this" from the actual team lands differently to the same thing in a status column.

Notifications, capped

People who follow a request get emailed when it moves — at most one digest per day, per person. Your update reaches the people who asked for it, without you running a mailing list.

Your product, presented as yours

Website, company, support contact, brand colour, donation link, and a verified badge on the page.

What it costs

Listing and running your product is free. The ledger, the board, GitHub sync, owner replies, status changes, notifications, branding — free, with no seat count, no tracked-user count, and no monthly minimum. There is no plan to upgrade to.

Trust pledges are free too. A trust pledge is a public promise, not a payment; no money moves, so we take nothing.

We charge 3.5% of a card-backed pledge, at the moment it's actually collected — which is after you've marked it Implemented. If it never gets there, nothing is charged, and we earn nothing. Minimum pledge is $5, so the flat card fee never eats an absurd share of a small one.

On a $100 pledge you collect

Pledged $100

Stripe (≈2.9% + $0.30) −$3.20

FeatureFuel (3.5%) −$3.50

You receive $93.30

About 93.3% passthrough. The charge lands directly on your own Stripe account under your own name — FeatureFuel never holds your money, and never has a balance to pay out to you. Stripe's own rate is theirs and varies by country and card.

How this differs

An honest read on the alternatives — including the ones worth keeping.

Hosted feedback boards

Canny, Nolt, UserVoice and the rest are good products, and they bill you monthly for a board that collects opinions. FeatureFuel is free and collects commitments: the same votes, plus the option for a customer to say what a feature is worth in money. What those tools have and we don't is a decade of enterprise workflow features — if you need those, they're worth the money.

GitHub issues

Excellent for tracking work, poor for measuring demand: "+1" comments don't rank, and most of your customers will never open an issue. This isn't a replacement — sync is two-way precisely so your engineers keep living in GitHub while the demand signal is gathered somewhere non-technical users will actually go.

A roadmap page you built yourself

It works, and then it's yours to maintain forever — auth, spam, email, moderation, and payments too if you ever want the money part. That's a side project competing with your actual product for attention. You get the roadmap page here either way: it's generated from the board you already use to triage, so it's current whenever the board is, and it sits on top of the votes and pledges that decided the order.

Requests scattered across email, chat and social

Right now a feature request turns up as a support ticket, a Discord message, a reply on social, a line in a sales call — and most of them are never written down anywhere. There's no list, so nobody can say how many people asked for the same thing, which request has been sitting there for a year, or what you told the last person who asked. FeatureFuel gives all of it one address: every ask lands in the same place, near-duplicates are caught as people type and merge into a single request with a single count, and you work the whole thing from one board — status, owner replies, and a public trail everyone who asked can follow instead of emailing you again to check.

A few things worth knowing up front

Card-backed pledges need your own Stripe account. Connecting one is a few minutes of Stripe's standard OAuth flow, and you choose whether cards are verified now and charged on ship, or charged up front. Until you connect, pledges on your product are trust pledges — a promise, not a charge — which still tells you plenty and costs nothing.
Claims are verified by a human. Every one of them, usually within a business day — claiming from an email address on the product's own domain is the quickest route through. It's a small deliberate speed bump, and it's there to make sure a product goes to the team that actually builds it.
We never hold your money. Pledges are charged directly to your own connected Stripe account, so you're the merchant of record and the money never sits in a FeatureFuel balance waiting to be paid out.

Give your customers somewhere to ask

A name, a link, about a minute — and a page you can send people to today. Free to list, free to run, and you only ever pay us out of money a customer actually paid you.

Add your product

More detail in the FAQ, or ask us directly on the support page.