How to Write a Funding Goal Description That Converts

A funding goal description is more likely to be read in full and acted on when it opens with one specific sentence naming the project and why it is needed now, states exactly what the money buys, carries a clear ask plus a photo or short video, and stays short enough to finish in one pass. That four-part pattern — specific headline, concrete ask, image, short body — comes from published crowdfunding-platform guidance and web-reading research, not from FanBell conversion data, which FanBell does not publish.

FanBell is free to start with no monthly fee and applies a 12% platform fee only when a fan pays (pricing).

A weak funding goal description rarely fails because fans don't want to help. It fails because fans can't tell, in the time they're willing to spend reading, what they'd be helping with. If a goal has already gone quiet, rewriting the description is usually the first move — see how to restart a stalled funding goal for the rest of that playbook. Jakob Nielsen of the Nielsen Norman Group found that users have time to read at most 28% of the words on an average web page during a visit, and that 20% is more realistic (Nielsen Norman Group, "How Little Do Users Read?"). Nielsen Norman Group's analysis of more than 205,000 web pages and over 2 billion recorded dwell times found that the average page visit lasts a little less than a minute and that users often leave a web page within 10 to 20 seconds.

What makes a funding goal headline work?

A funding goal headline works when it names one specific project — "New studio mic so livestream audio stops cutting out" — instead of a general appeal like "help me create." FanBell's Project Support card renders that title directly above the progress bar, so the title alone must convey the project (how it works).

"Help me keep making content" names a category, not a project, and gives a fan nothing concrete to picture. "New studio mic so livestream audio stops cutting out" names one thing, one reason, and one outcome. A headline that specific also sets up the rest of the page: every paragraph below can expand on that single claim instead of introducing a second and third goal that dilute the first. Nielsen Norman Group's F-shaped-reading write-up instructs writers to "start headings and subheadings with the words carrying most information: if users see only the first 2 words, they should still get the gist". A companion Nielsen Norman Group study tested how accurately users understood links and headings from only their first 11 characters, because users typically scan a list rather than read it. A funding goal headline that opens with "Help me" spends its first two scanned words on nothing.

Keep the headline to the project itself. Save the dollar total, the timeline, and the platform-fee math for the goal-setting step covered in how to set a realistic creator funding goal — a headline's job is to be understood in one pass, not to carry every number.

How much detail belongs in the opening line?

The opening line of a funding goal description should state what is needed and why now, in one sentence a fan could repeat back accurately. The opening line sits directly under the headline and does the actual persuading; the paragraphs beneath the opening line support that single claim rather than replacing it or introducing a competing one.

An exact dollar figure is optional in that opening sentence, because the FanBell Project Support card already displays the goal amount, the amount raised, and the percentage complete on the progress bar above the description (FanBell Project Support card layout). What the opening line has to supply is a scale a fan can picture and a reason the ask is happening now — the exact total is already on screen. That "why now" is a writing choice rather than a platform constraint, since a funding goal carries no deadline of its own on FanBell.

"I've wanted to do this for a while" explains motivation but not urgency. "My current mic died mid-stream last week, and the replacement costs about what three months of tips would cover" ties the ask to a real event and a rough scale, without the itemized math — itemized math belongs in the fund breakdown, not in the hook.

If a funding page needs to account for exactly what each dollar funds — parts, taxes, contingency, what happens with a surplus — write that separately. How to explain what fan contributions will be used for covers that breakdown; keep the opening sentence focused on the "what" and the "why now."

What is the ideal length for a funding description?

There is no single ideal length, but two published numbers bracket the range. GoFundMe tells fundraisers to write no fewer than 400 words, while FanBell's Project Support goal editor caps the "Project story" field at 800 characters — roughly 120 to 140 words. A FanBell funding description therefore targets 100 to 140 words.

GoFundMe's fundraising-mistakes guide tells fundraisers to write no fewer than 400 words and warns against burying the lead under preamble before the real story starts (GoFundMe: 11 Mistakes to Avoid for Fundraising Success). That 400-word figure is written for medical, memorial, and emergency donation stories, where a reader who has never met the fundraiser needs the full circumstances before deciding. A FanBell Project Support goal is a different job: the reader is usually an existing fan who already knows the creator, and the product enforces a shorter field — the "Project story" textarea in the FanBell goal editor (Dashboard → Support goals → New support goal) stops accepting input at 800 characters, so a 400-word story cannot be saved on a FanBell goal even if a creator wanted one (FanBell Project Support goal editor).

Concise writing is measurably easier to use, not just faster to skim: Nielsen Norman Group measured 124% higher usability for a website rewritten to be concise, scannable, and objective at the same time (Nielsen Norman Group, "Concise, SCANNABLE, and Objective: How to Write for the Web"). The FanBell-specific recommendation: write 100 to 140 words in the "Project story" field — one headline, one opening sentence carrying the ask, then two to four short paragraphs — and put the itemized cost list in the separate "How funds will be used (optional)" field rather than spending story characters on it (FanBell Project Support goal editor).

How do you write the actual ask?

The ask is the one sentence telling a fan what to do, and it names a specific request instead of a vague invitation. "Any support helps" asks for nothing in particular, while "chipping in toward the new mic gets me back on stream with clean audio" asks for one concrete thing tied to the headline.

"A successful fundraiser starts with honest, often courageous storytelling—and compelling stories turn passive visitors into active donors and sharers." — GoFundMe, "How to Write a Fundraiser Story that Inspires Donations"

GoFundMe states on its own About page that $40 billion has been raised through GoFundMe technology since 2010, from more than 190 million people worldwide, and the storytelling guide from the same company opens by telling fundraisers that compelling stories are what turn passive visitors into donors. GoFundMe's guidance is written for donation campaigns rather than creator projects, so read it as a transferable principle: a fan who understands exactly what a contribution buys has more to act on than a fan asked to support something described in general terms. On a FanBell Project Support page, the ask can point at the progress bar itself, because that bar shows the amount raised against the goal — "help close the last $80" is more concrete than "help me reach my goal" (FanBell Project Support card layout). For a larger goal, naming a specific next chunk instead of the full total often reads as more concrete still — see how to split a funding goal into milestones.

Does a photo or video change how the page reads?

Yes — a photo or short video makes an ask feel like it comes from a specific person about a specific project instead of reading as generic copy. Kickstarter's own creator-tips post reports that projects with videos succeed at a much higher rate than those without, 50% versus 30% (Kickstarter, "How To Make an Awesome Video").

GoFundMe's fundraising-mistakes guide states that fundraisers featuring at least five photos raise significantly more than those having only one (GoFundMe: 11 Mistakes to Avoid for Fundraising Success), and GoFundMe's own photo lesson puts a number on the same research in its page summary: fundraisers with five or more photos collect twice as many donations (GoFundMe: Enhance Your Fundraiser With Photos). Both the Kickstarter and GoFundMe figures come from rewards and donation platforms rather than from FanBell, so treat those figures as directional evidence for a creator funding page, not as a measured FanBell result.

Two placement recommendations below are FanBell's editorial reading of Nielsen Norman Group scanning findings rather than measured platform data. First, an image belongs near the top, close to the headline and opening line, rather than below paragraphs a fan may never scroll to. Nielsen Norman Group's scrolling research measured that users spend about 57% of their page-viewing time above the fold and 74% of it within the first two screenfuls (Nielsen Norman Group, "Scrolling and Attention"), so an image set below several paragraphs is competing for the remaining quarter of a visitor's attention. Second, production value is not the job the image is doing: a phone photo of the broken gear, a screenshot of the project in progress, or a 20-second selfie clip all make the headline's claim visible rather than merely stated. On FanBell the placement decision is already made by the layout — the Project Support card renders the cover image above the goal title — and the field itself is labelled "Cover image (optional)" in the goal editor, so a goal can be published without one (FanBell Project Support goal editor).

What order should the page follow?

A funding goal page reads best in the order a fan actually scans: headline first, then the specific ask, then a photo or short video, then the supporting story, then a close that repeats the ask. Persuasive elements belong at the top of that sequence, because a visitor decides whether to stay within the first seconds of the visit.

Nielsen Norman Group's foundational web-reading study found that 79% of test users always scanned any new page they came across and only 16% read word-by-word. A funding description written in scanning order survives scanning; a funding description that saves its point for paragraph four does not.

"It's clear from the chart that the first 10 seconds of the page visit are critical for users' decision to stay or leave." — Jakob Nielsen, Nielsen Norman Group, "How Long Do Users Stay on Web Pages?"

The five-row table above describes the order a creator writes in, not the order the product renders. On FanBell the cover image position is fixed by the layout rather than chosen: the Project Support card renders the cover image above the goal title, and the story text sits below the progress bar (FanBell Project Support card layout).

Putting an itemized cost breakdown first pushes the actual hook further down the page, working against how briefly most visitors read before deciding. Save cost detail for the section right after the ask — see how to explain what fan contributions will be used for for how to write that breakdown.

What does a rewritten funding goal description look like?

A rewritten funding goal description replaces a category with a project, a mood with an event, and an invitation with a request. The before/after below shows one equipment goal written twice: first as a vague 38-word appeal, then at about 120 words with a headline, an opening line, a short story, and a specific close.

Before — vague, 38 words:

Help me keep making content

Hey everyone! I've wanted to upgrade my setup for a while and it would mean a lot if you could help out. Any support helps and I really appreciate you all. Thanks for being here.

After — specific, about 120 words:

New studio mic so livestream audio stops cutting out

My mic died mid-stream last Thursday, and the replacement costs about what three months of tips would cover.

I've streamed on the same secondhand mic for two years. It started dropping out mid-sentence in July, and the last two streams had stretches where nobody could hear the answer to a question. Recording a phone backup has kept episodes usable, but a phone backup isn't a fix.

This goal covers a replacement condenser mic and a shock mount. The itemized list is in the funds-use section under the bar.

Chipping in toward the new mic gets me back on stream with clean audio — helping close the last $80 finishes it.

The rewritten version above runs 677 characters and 119 words, which fits inside the 800-character limit on the "Project story" field in the FanBell Project Support goal editor (FanBell Project Support goal editor). The vague 38-word version and the specific 119-word version would both save; only one of them tells a fan what the money buys.

Fill-in template:

[Specific thing] so [specific problem stops]

[What broke or what starts] happened [when], and it costs about [a scale a fan can picture].

[Two to four sentences: what the situation has been, what a regular viewer may already have noticed, what you tried first.]

[What the money buys, in one sentence, pointing at the funds-use field for the itemized version.]

[Specific ask tied to the progress bar: "help close the last $X."]

What mistakes make a funding description harder to act on?

Four mistakes recur in weak funding descriptions: a vague ask naming no specific project or outcome, a story that buries the ask under preamble, no photo or video at all, and one goal mixing several unrelated projects. FanBell publishes no frequency ranking for those four mistakes, so treat the list as unordered rather than measured.

GoFundMe's fundraising-mistakes guide names burying the lead explicitly, telling fundraisers to open by explaining the specific event that led them to take action instead of starting with background detail (GoFundMe: 11 Mistakes to Avoid for Fundraising Success). A vague ask fails for a related reason: "help support my art" reads as a category, and a category gives a fan nothing to picture or repeat.

Fixing any of those four mistakes is usually a rewrite of the description rather than a change to the goal amount.

On FanBell, a fan can read the description, see the live progress bar, and contribute directly on the creator's page: FanBell's own how-it-works FAQ states that fans check out as a guest and pay by card through Stripe, with no FanBell account to create and no app to install. For the full five-step setup — defining the project, sizing the goal, and publishing the page — see how to fund your next creative project with fan support. And once the bar reaches 100%, the description's job isn't quite done — see what to do after you hit your funding goal for how to close it out with fans.

Frequently asked questions

Four questions come up most often about FanBell funding goal descriptions: how long the description should be, whether the dollar breakdown belongs in it, whether a photo or video is required, and what FanBell charges to run a goal. Each answer below cites either FanBell's own documentation or a named crowdfunding or usability source.

How long should a funding goal description actually be?

On FanBell, 100 to 140 words, because the "Project story" field in the Project Support goal editor accepts 800 characters (FanBell Project Support goal editor). GoFundMe's guidance recommends no fewer than 400 words for a donation story (GoFundMe: 11 Mistakes to Avoid for Fundraising Success), but that target is written for readers who don't know the fundraiser. The structural rule matters more than either number: the headline and opening sentence should carry the full pitch alone, since Nielsen Norman Group found users read about 20% of the words on an average page during a visit.

Should the description include the exact dollar breakdown?

Not in the headline or opening line. Put the itemized breakdown in the "How funds will be used (optional)" field of the FanBell Project Support goal editor, after the ask has already been made (FanBell Project Support goal editor). How to explain what fan contributions will be used for covers how to write that breakdown so it reads as transparent rather than as a spreadsheet.

Does the description need a photo or video to work?

No. The cover image field is labelled "Cover image (optional)" in FanBell's Project Support goal editor, so a goal publishes without one (FanBell Project Support goal editor). Adding one is still worth it: Kickstarter reports that projects with videos succeed at 50% versus 30% for those without. A phone photo or a short unscripted clip is enough.

What does FanBell charge to run a funding goal?

FanBell is free to start with no monthly fee and applies a 12% platform fee only when a fan pays. There's no follower minimum, and payouts run to a connected Stripe Express account on Stripe's payout schedule. Card-processing costs are separate from that platform fee: Stripe's published pricing lists 2.9% + $0.30 per successful domestic card charge in the US. Stripe's payouts documentation states that after a first successful live payment, "Stripe typically schedules your initial payout to complete within 7–14 days" (Stripe, "Receive payouts").

Create your free FanBell page and rewrite the pitch before you rewrite the price.