Get paid to work your backlog.
Your community backs the issues they need with a few dollars each. You fix them on your terms, in your own editor, with your own tools. When the fix merges, the pool pays you. No bots in your repo, no invoices, no PR spam, ever.
One issue, end to end
Little by little, it ships.
Small backings pool until an issue is worth your time. You fix it the way you always do; the only new part is the payout at the end. Scroll to follow one issue from funded to paid.
See what's funded.
As community members back a public issue in your repo, CleverCrow keeps a single comment in sync with the funding pool. The money waits on your fix; backers stay withdrawable until it ships.
Fix it your way.
Your editor, your tools, your branch. There's no workflow to adopt and nothing to configure; CleverCrow never touches your repo while you work.
Open the PR that closes it.
Say Fixes #19 in the pull request and CleverCrow
links it to the pool. CI runs as normal; nothing about your
review process changes.
Everyone sees it coming.
The issue's live comment and its public backing page track the PR, so the people who funded the fix watch it land in the open. No invoices, no chasing.
Merge, and get paid.
You merge, the pool settles: CleverCrow takes a flat 10%, and the rest is paid to you. Every settled issue shows the receipt, line by line.
Pebble queue is eventually consistent; crow is immediately thirsty
Funded · yours to fixsyrinxian/pitcher · issue #19
For backers
Fund the fix, not a fork.
That bug in your dependency that's blocked you for six months? Paying a stranger prices it in the hundreds and stalls waiting for one to bite. Here you back the issue with a few dollars, and the maintainer who knows the codebase drives the fix home and gets paid for it.
Back the issues you depend on.
Put a few dollars behind any open issue you depend on. Backings pool with other backers' on the issue and wait; your money stays withdrawable until the fix ships. You're paying the maintainer who knows the codebase, not a stranger's weekend.
Your money pays the maintainer, not a markup.
When the fix merges, the pool pays the maintainer, minus a flat 10%, and the receipt shows every line. If nothing merges, your money returns to your wallet.
Recruit the maintainer.
Repo not on CleverCrow yet? Back the issue anyway and the dashboard writes the invite for you to post on the thread. A backer with money already on the line is the credible version of "you should try this", and a funded pool waiting is the strongest onboarding pitch a maintainer can get.
For maintainers
How you get paid.
No invoices, no chasing. The pool settles the moment you merge, and the receipt shows every line.
Your fix, your terms.
There's no workflow to adopt and no tooling to install. Fix the issue the way you always do, and merge a pull request that closes it; the pool settles the moment the merge lands.
One flat fee, published.
CleverCrow's only fee is 10% of the pool at settlement. No subscription, no listing fee; Stripe's payout costs pass through at cost on the monthly payout. Every settled issue gets a line-item receipt: pool, fee, payout.
Stripe payouts, monthly.
Connect a payout account once; Stripe handles the identity checks. Settled pools accrue to your balance and pay out monthly, with a $10 minimum that rolls forward. Stripe's payout costs ($2.25 plus 0.25%, plus 0.25% outside the US) come out of each monthly payout at cost. Available today for maintainers in the US, UK, EEA, Canada, and Switzerland.
Your backers show up on the repo.
A live comment on each backed issue shows visitors the pool and what the fix pays you. Merged PRs credit the backers who funded them, and a README badge counts the issues your community has shipped. The receipt is the marketing, on your repo, working for your next issue.
Fair question
Why not just pin a sponsor button?
You should, and keep it. Sponsorships fund a person; CleverCrow funds outcomes. Three honest reasons maintainers run both.
Every dollar names the fix it wants.
A sponsorship is a tip jar; generous, and disconnected from the backlog. Here each backing lands on a specific issue, so the money tells you exactly which fixes your community values, in dollars, before you spend an hour on them.
Only you can collect.
Public money on an issue usually summons a swarm of drive-by pull requests racing for the prize. CleverCrow pays the maintainer, and no one else, so there is no prize to race for and no spam incentive; just your backlog, priced by the people who depend on it.
Everything settles with a receipt.
When you merge, the pool settles in one pass: a flat 10% fee, the rest to you, itemized on a public receipt on the issue. Backers see what their money did, which is exactly what makes them back the next issue.
Aesop · The Crow and the Pitcher
Little by little does the trick.
One funded issue at a time, the work gets done. Your community funds it. You fix it, you ship it, and the pool pays you.