Crowdfunding on Your Website: Does a Pledge Depend on the Whole Campaign Succeeding?

Before commissioning a crowdfunding website, decide whether each contribution stands alone or depends on a shared funding target. That choice changes what supporters are agreeing to, how the campaign ends and which totals staff can safely use. A progress bar and a payment button do not define the funding contract.

This guide concerns the campaign decision, not permission to collect money, charitable status, tax treatment or investment regulation. Those questions need appropriate review for the actual organisation and markets. Do not describe a creative-project pledge as a tax-deductible donation or a guaranteed purchase without a separate basis.

Decide whether the project is conditional

Imagine a small publisher considering a new illustrated book. It cannot sensibly produce the proposed edition unless enough people commit. An ordinary pre-order can describe when one buyer pays for a forthcoming item. A conditional campaign adds a different question: may the project proceed only if the combined commitments satisfy a campaign-wide rule?

Write that rule before designing the screen. Specify the target, currency, deadline and the contributions eligible to count. Decide whether the deadline is evaluated in a named time zone and who has authority to launch the campaign. A supporter should be able to understand the condition before committing, not discover it in a staff-only report.

Kickstarter provides one documented example. Its all-or-nothing explanation distinguishes backing a creative process from making a guaranteed store purchase. It also states that the funding goal and deadline are locked once a campaign launches. These are Kickstarter-specific rules, not automatic properties of a custom website.

Do not let the displayed total become the whole decision

For a custom brief, distinguish commitments accepted by the campaign from payments actually collected and funds available to the organisation. Choose labels that describe the evidence. A pledged total is not itself a bank balance, a production instruction or proof that a reward has been delivered.

Ask what the counter includes. Does a revised commitment replace its earlier amount? How are withdrawn or unresolved records shown? If a payment outcome is unknown, staff need a visible reconciliation task rather than a reassuring total assembled from whichever record arrived first.

These are proposed requirements to settle with the implementer and payment specialist. The cited Kickstarter passage establishes the conditional model and locked campaign terms; it does not certify a custom collection process or a method for reconciling failed payments.

Define the end of the campaign as an explicit decision

Specify the permitted outcomes at the deadline. What happens when the target is reached, missed or cannot yet be evaluated because records remain unresolved? Name the evidence used for that decision and the person responsible for an exception. Reaching the goal early should not silently replace the agreed deadline or trigger production unless that is genuinely the approved model.

Keep evaluation, collection and reward fulfilment visible as separate steps. The public page should explain the campaign outcome without claiming that every charge has settled or every promised item is ready. Where collection is conditional, have the chosen provider demonstrate a supported mechanism; do not assume an ordinary card hold can remain valid throughout an arbitrary campaign.

Also decide how late requests are handled. A new campaign or extended offer must not quietly rewrite the terms under which existing supporters committed. If the first release does not support late pledges, make that limitation clear rather than letting a still-working button create ambiguous records.

Make changes understandable to existing supporters

Treat the target and deadline as published terms, not casual editable page content. For a model that locks them, restrict the administrative controls accordingly. For any different model, obtain the necessary business and legal review and define how existing commitments are affected before allowing changes.

Keep a traceable campaign version and a supporter-facing account of material changes. A corrected image is not the same event as changing what the project promises to produce. Decide who can communicate an update and how staff identify the supporters to whom it applies. Do not promise that a platform notice alone resolves every obligation.

Accept the campaign with boundary cases

Using non-sensitive test records, demonstrate a campaign below target at close, exactly at target, above target and still open after reaching the target early. Include a revised commitment, an unresolved payment result and two concurrent closing attempts. Check the public explanation, campaign decision and downstream work rather than only the animation of the counter.

Bring the funding condition, supporter promise and payment-provider constraints to your website or app project discussion. Put the end-of-campaign outcomes into your acceptance criteria. The useful deliverable is a clear collective commitment with an accountable closing process, not a fundraising dashboard that makes money or delivery look more certain than it is.