oss-sponsors-fundraising

Start by making the project findable and payable: add .github/FUNDING.yml, fill package-manifest funding metadata, and put a funding link within two clicks of every surface users touch. Then build a short tier ladder with company-priced placement tiers, since individual sponsorship alone typically stays under $1,000/month.

Price company tiers against the audience a placement reaches, such as monthly README or docs views, not against generosity. Published tier prices cannot be edited on GitHub Sponsors, only retired and replaced, so design the ladder for two years out and keep it to three to five tiers.

Yes, but invoiced sponsorships through GitHub carry a $5,000 minimum per invoice, so smaller corporate asks must route through a fiscal host that can issue invoices. You also need a legal entity or contractor arrangement, the payer's tax form, and bank details before outreach.

Stress-test every reward at ten times your current sponsor count. Near-zero rewards like README placement, badges, and thank-you posts scale safely, while monthly calls, priority support, and bespoke work become a second job and belong in a separately priced retainer, not a tier.

A grant fits projects with a research, infrastructure, or security angle and is a fixed-term contract with eligibility gates and reporting duties, not a larger sponsor. Check licence, payee, geography, and maturity gates first; programs like NLnet pay individuals directly while CZI EOSS funds organizations only.

Early access to releases is among the best-converting rewards but also the most expensive to keep delivering. Gate convenience only, never the core library, security fixes, or documentation, and publish a fixed release threshold you will honor rather than moving it later.