How to Explain What Fan Contributions Will Be Used For

Explain fan contributions by naming the project, listing the main costs, stating the total goal, and describing what will happen when it is funded. Make clear that amounts are estimates when necessary and disclose how any surplus will be used. Fans should understand the purpose before they pay.

This page covers the transparency piece specifically: what to say about where contributions go and how specific to get. For the full process—from setup and the ask through follow-through—start with the pillar guide on funding your next creative project with fan support.

What is Project Support, and why does that change the wording?

Project Support lets fans send cash toward a creator-defined goal, with progress displayed on a funding bar on the creator’s FanBell page (how it works, verified August 2026).

Project Support is not a store: fans are not buying a product that ships to them, and there is no built-in tiered “give $50, get a sticker” reward system (how it works, verified August 2026). Your copy should therefore explain what the goal funds without implying that every contributor is purchasing a product, reward, or delivery.

These are the core mechanics to reflect in your wording:

How specific should the cost breakdown be?

Specific wording helps fans understand both the intended outcome and why you selected the goal amount. Compare:

• Vague: “Help me level up my content!”
• Specific: “This goal covers a new microphone ($180), acoustic panels for cleaner audio ($120), and editing software for the next six months ($100)—$400 total.”

The dollar amounts above are illustrative examples, not FanBell requirements or prescribed prices.

The specific version lets a fan picture the intended outcome and see how the total was calculated. You do not need to publish a full accounting ledger; a short, honest list of the main estimated costs is usually enough.

A simple format works for most projects:

If the project has one major cost, such as a piece of equipment, venue deposit, or production run, one line is enough. Do not invent extra line items merely to make a simple goal look more detailed.

How do you keep the scope honest and narrow?

State only what the goal is genuinely intended to fund, and keep that scope consistent after contributions begin.

• Do not add unrelated costs later. If the goal is for a microphone, do not quietly start counting rent or unrelated general expenses toward the same breakdown. Create a separate goal for a different purpose.
• Do not promise a date you cannot confidently meet. Project Support has no campaign deadline or all-or-nothing mechanic (how it works, verified August 2026). State what you plan to do once funded, but use an estimate rather than a guaranteed date if the timeline is uncertain.
• Label estimates clearly. Write “estimated at $300” or “roughly $300” if the final price may vary.
• Explain plan changes. If the project costs less than expected or shifts to a different item, tell supporters. See keeping supporters updated on a creator project for practical wording.

A narrow scope also makes follow-through easier: you can show what happened against the same clear plan fans saw before contributing.

How do you write the “where it goes” section?

Most fan pages benefit from a short section that can be understood in a few seconds. Use this structure:

1. Name the goal. “Raising for a new ring light setup.”
2. Break down the estimated cost. “An estimated $150 for the light, $90 for stands and diffusion, and $20 for cables—$260 total.”
3. State what changes when funded. “This setup will improve the lighting on future videos, not just one upload.”
4. Address possible surplus. “If the final cost is lower or contributions exceed $260, the remainder will go toward replacement bulbs and lighting accessories.”

The $150, $90, $20, and $260 figures are illustrative wording examples, not platform-set amounts or requirements.

For guidance on where this section belongs and how to write the surrounding title, suggested amounts, and call to action, see what to put on a project support page.

Frequently asked questions

Do I need to show exact receipts for every dollar?

No. For clear fan-facing copy, a short and honest breakdown of the principal costs is generally more useful than a public ledger. After funding, you can close the loop with a brief “here’s what I bought” update; see keeping supporters updated on a creator project.

What if I do not know the exact cost yet?

Use your best estimate and label it clearly: “Roughly $300 for gear; the final cost may vary slightly.” An explicit estimate tells fans what you currently expect without presenting an uncertain figure as guaranteed.

What if contributions exceed the listed breakdown?

Explain how the surplus will support the same project. For example, if an illustrative $400 goal receives $460, you could write: “The additional $60 will go toward a spare cable and backup battery for this setup.” Name the actual use instead of leaving supporters to guess.

Do I need to update fans once the goal is reached?

A follow-up update is the clearest way to show that you used contributions as described and to explain any changes. A short note stating what you bought, what it cost, and how it is being used is enough.

Ready to set up a transparent goal? Create your free FanBell link and add a Project Support goal with a clear breakdown of what it funds—a FanBell funding bar shows that goal filling in real time, and you keep all but 12% of what fans contribute (pricing, verified August 2026).