Bag Crowdfunding Benchmarks: Average Goal, Backers and Timeline

Creators want one number. They want to be told that bag campaigns raise a certain amount, attract a certain number of backers and take a certain time to fund, and then they want to plan against those figures. The honest answer is that the useful benchmark is a band, and the useful band is one computed from campaigns that resemble yours. This article gives the eight benchmarks our team uses in planning conversations, states the basis for each, and is explicit about which ones are drawn from publicly observable campaign data, which are drawn from production arithmetic, and which are observation from the programmes we have supported. It is written to be used alongside the crowdfunding bag guide rather than instead of it, and it assumes you will replace several of these ranges with your own comparables once you have found them.

What a benchmark is for and what it cannot do

A benchmark does three useful things. It tells you whether your plan is unusual, which is worth knowing because unusual plans need unusual justification. It tells you which inputs are worth arguing about, because the inputs with wide bands are the ones where your own situation matters more than any average. And it gives you a defensible answer when someone asks why the goal is set where it is, which happens more often than creators expect, including in the comments.

What it cannot do is forecast your outcome. The distributions behind crowdfunding figures are wide and skewed, and two campaigns in the same category with similar pages can differ by an order of magnitude because one creator arrived with an audience and the other did not. Treating a benchmark as a forecast is the single most common misuse we see, and it produces the specific failure where a creator sets a goal at the category average, funds at a fraction of it, and discovers the production minimum was computed for the larger number.

The third caution is about mixing sources. A funding rate from a platform-wide report, a backer count from a category survey and a unit cost from one quotation do not form a coherent plan, because each was measured on a different population at a different time. Our programme coordinator keeps benchmarks in a single sheet with a basis column next to every figure, and asks creators to do the same, because the basis column is what stops a range from hardening into a fact.

Benchmark one: funding goal size

For carry campaigns, publicly observable data suggests goals typically sit in a band from the low tens of thousands to the low hundreds of thousands of currency units, with first-time creators clustering in the lower part and established brands in the upper part. That band is wide and it is not the number we would plan against. The number we would plan against is the production floor, computed from your own quotation: minimum run times landed unit cost, plus sampling and tooling amortised across the run, plus packaging, plus platform and payment fees of roughly a tenth of the raise, plus contingency.

The reason the floor matters more than the average is that it is the smallest goal at which the campaign can actually deliver. A 500 pcs per style and per colourway minimum at a landed unit cost that includes fabric, hardware, labour, decoration, packaging and freight sets a hard lower bound, and every goal below that bound is a campaign that will fund and then be unable to make the product. In our observation, the goals that look surprisingly similar across bag campaigns are similar because their floors are similar, not because their creators read the same statistics.

There is a second structural point about goal size that is easy to miss. Because the minimum is per style and per colourway, the floor scales with the number of variants. A campaign offering two colourways has roughly twice the floor of a campaign offering one, and a campaign offering a system of five components has roughly five times the floor of a single bag. Goal size and variant count are the same decision, and treating them as separate decisions is how a plan acquires a gap that only appears after funding.

Benchmark two: backer count

Publicly observable campaign data suggests funded design campaigns typically collect pledges in the hundreds to low thousands, with a median well below the mean because a small number of very large campaigns pull the average upward. In our observation across carry projects, planning against a median in the several hundred range and then stress-testing up to a few thousand is more robust than planning against a mean, because the mean describes an outcome most campaigns did not achieve.

The required backer count is derived rather than benchmarked, and the derivation is where most plans are actually set. Required backers equals goal divided by average pledge, adjusted for the share of pledges that come from tiers below the hero tier. Because both inputs are ranges, the output is a range too, and the useful exercise is to compute it at the pessimistic and optimistic ends. A plan that only works at the optimistic end of both inputs is not a plan, it is a hope with a spreadsheet.

There is also a floor on backer count imposed by production, and it works in the opposite direction from the one creators expect. Fewer backers at a higher pledge is usually better for a physical reward, because it means fewer units to make, fewer units to ship and a simpler kitting operation, while the margin per unit is higher. Our campaign bag specialist would rather support a campaign with 400 backers at a strong price than one with 1,200 backers at a thin one, because the failure modes at scale are operational and unforgiving.

Benchmark three: average pledge

Average pledge for carry campaigns, in our observation of public campaign data, typically sits in a band from around the price of a mid-range retail bag upward, with the upper end reached by campaigns selling bundles, systems or premium materials. The figure is unusually sensitive to tier design, which makes it one of the few benchmarks a creator can genuinely move rather than merely observe. Adding a bundle tier or raising the hero tier price by a modest amount shifts the required backer count materially.

The tier mix matters as much as the average. Public campaign data suggests a large share of pledges in most campaigns concentrate in one or two tiers, so the hero tier price effectively sets the average pledge, and the tiers below and above it are there to capture the edges. Pricing the hero tier is therefore the highest-leverage pricing decision in the campaign, and it should be made against the landed unit cost plus a deliberate margin rather than against what comparable campaigns charged.

Shipping treatment is the most common distortion in this benchmark. Campaigns that bundle shipping into the reward price report a higher average pledge and a lower net receipt, while campaigns that charge shipping separately report a lower pledge and a cleaner margin. Comparing an average pledge across the two without adjusting is meaningless. The pricing mechanics are set out in Kickstarter Reward Pricing: What Backers Pay for Bags, and the tier mechanics in Kickstarter Reward Tiers for Bags: Structure That Converts.

Benchmark four: funding speed

Pledges are not distributed evenly across a campaign. Publicly observable funding curves typically show a strong opening 24 to 48 hours, a long flatter middle, and a pronounced rise in the final 24 to 48 hours, with the two ends together accounting for a large minority of total pledges and sometimes more. In our observation this shape is stable enough to plan around, and it has two direct operational consequences.

The shape also has a diagnostic use once a campaign is live. Comparing your own progress curve against the typical shape at the same point in the run tells you whether a slow middle is normal or whether the opening underperformed, and those two situations call for different responses. A normal slow middle needs a reason to commit; an opening that missed needs traffic, and treating the second as though it were the first is how a campaign spends its final week on updates that cannot reach anyone new.

The first consequence is that the pre-launch list is the highest-return marketing asset a creator can build, because the opening wave is almost entirely drawn from people who already knew the campaign was coming. A campaign that funds a meaningful share of its goal in the first day has a different middle period from one that does not, because early momentum affects platform discovery and press interest. That is why pre-launch list building is treated as a production-phase activity rather than a marketing-phase one.

The second consequence is that the middle period is the dangerous one, and it should be planned as a period of activity rather than a period of waiting. Campaigns that go quiet in the middle rarely recover in the final surge alone, because the final surge draws partly on people who have been watching and need a reason to commit. Updates, a new colourway unlock, a press mention or a comparison piece are all standard ways to give them one, and all of them are easier to arrange before launch than during it.

Benchmark five: campaign length

Publicly reported patterns suggest 30-day campaigns show higher funding rates than 45 to 60 day campaigns, with the caveat that longer campaigns sometimes accumulate more in absolute terms simply because they have more days of exposure. The mechanism usually proposed is urgency, and while we would not claim to have isolated it, the pattern is consistent enough that 30 days is a sensible default for a first campaign.

For a physical reward there is a second argument for the shorter window, and it is the one that usually decides it. A 30-day campaign plus a pledge manager period of roughly two to four weeks plus a 6 to 10 working day sampling cycle plus a 35 to 50 day bulk window plus ocean freight of several weeks is already a delivery promise measured in months. Adding thirty days of campaign to that pushes delivery into a different season, and in the worst case across the lunar new year stoppage, which typically halts production for one to three weeks with reduced capacity either side.

The timing of the funding event itself is worth noting too. Because a large minority of pledges arrive in the final 48 hours, the date a campaign funds is close to the date it ends, which means the pledge manager period rather than the campaign end is the effective start of the production clock. Our sourcing partner plans sampling and slot reservation against the pledge manager close rather than the campaign close, because that is when the colourway split is finally known.

Benchmark six: page conversion

Conversion from campaign page view to pledge is the benchmark with the widest band and the most misuse. Publicly reported figures for crowdfunding generally put page conversion in the low single digits as a percentage of visitors, with wide variation by traffic source, price point and category. A warm email list converts far above that, cold advertising converts below it, and platform discovery sits somewhere in between. A single figure applied to all traffic produces traffic plans that are wrong by multiples.

The useful way to use this benchmark is to build the traffic plan by source rather than in aggregate. Estimate the list size and a warm conversion rate, estimate the advertising spend and a cold cost per pledge, and treat platform discovery as an uncertain bonus in the first campaign rather than a planned input. In our observation, creators who plan discovery as a bonus rather than a channel are the ones least likely to be surprised in the middle period.

Conversion also has a price sensitivity worth benchmarking against your own page rather than against the category. A reward priced well above the band backers expect for the product type will convert worse at identical traffic, and the only way to find the ceiling is to test it before launch with a landing page or a waitlist. The product validation work is where that test belongs, and it is cheaper than discovering the ceiling during the campaign.

Benchmark seven: stretch goals

Stretch goals produce a second pledge wave in many campaigns, and in our observation the size of that wave varies far more than creators expect, from negligible to substantial. The variable that seems to matter is whether the stretch goal adds something backers want or merely adds something the creator wants to make. Colourway unlocks and add-on components consistently outperform feature additions, and feature additions carry a production cost that colourway unlocks largely do not.

The sequencing of the unlocks matters as much as their content. Stretch goals set close together produce a continuous reason to return, while a single distant goal produces a long period with nothing to report, and publicly observable funding curves suggest the middle period is where campaigns either hold attention or lose it. Our programme coordinator suggests spacing unlocks so that one is plausible every week to ten days, which also gives the update schedule something factual to report rather than only encouragement.

The production reason is concrete. A colourway unlock changes thread, ink or fabric colour, which does not create a new minimum for embroidery or print, though it does for patches. A feature addition changes the specification, which can require another sampling round of 6 to 10 working days or 12 to 15 working days for a complex build, and that happens after the campaign when the calendar is tightest. Our production team recommends stretch goals that can be delivered without touching the approved specification.

There is a second-order effect on the order itself. A stretch goal that unlocks a fourth colourway on a campaign that sold 1,600 units across three colours does not add 400 units, it redistributes them, and the result can be four colourways of 400 that each fall below the 500 pcs per style and per colourway minimum. Unlocks should be modelled against the minimum before they are published, which is the same arithmetic described in Custom Bags With Mixed Colours.

Benchmark eight: delivery windows

Delivery is the benchmark where we can be precise, because it is governed by commitments rather than by distributions. Sampling runs 6 to 10 working days, extended to 12 to 15 working days for complex builds. Bulk production runs 35 to 50 days. Inspection is held to AQL 2.5 to ISO 2859-1. Terms are FOB Xiamen with T/T 30/70, which means the freight legs and customs clearance sit after the factory gate and belong to the creator's logistics plan rather than to the production window.

The failures in this benchmark are almost always calendar failures rather than production failures. A campaign that promises delivery in a stated month and then discovers that bulk would fall across the lunar new year stoppage has not been let down by the workshop, it has been let down by a plan drawn forwards from launch rather than backwards from delivery. Publicly reported fulfilment data suggests a substantial share of physical campaigns deliver later than promised, and in our observation the cause is usually the missing backwards calendar rather than slow production.

There is also a benchmark for how late is survivable, and it is a communication benchmark rather than a logistics one. In our observation, backers tolerate a slip of a few weeks when the campaign has been updating on a schedule, and they do not tolerate a slip of the same size announced after a silence. The delivery window and the update schedule should therefore be planned together, and the regional timing behaviour is set out in Bag Crowdfunding Fulfilment Data: On-Time Rates by Region.

Building your own benchmark set

The best benchmark set is the one you build from comparables, and it takes an afternoon. Find five to ten campaigns in the same sub-category, at a similar price point, launched in the last two years, and record for each: goal, final raise, backer count, average pledge computed as raise divided by backers, campaign length, number of tiers, number of colourways, and the delivery month promised versus the month delivered. Those eight columns give you a band that is specific to your product rather than to a category.

Then replace the category figures in your plan with your comparables, keeping the production commitments as they are, because those do not change. Compute your floor, compute your required backer count at the pessimistic and optimistic ends of your own pledge band, and check whether the pessimistic case still clears the minimum in every colourway you intend to offer. If it does not, reduce the colourways or raise the price before launch rather than hoping for the optimistic case.

Finally, keep the set live. A benchmark collected before launch is a planning input, and the same set updated during the campaign is a diagnostic. If your funding curve is tracking below your comparables at the same point, that is information, and the response is a mid-campaign change rather than a hope. The platform comparison is available in Kickstarter vs Indiegogo: Bag Campaign Data Compared and the cross-platform view in Multi-Platform Bag Campaign Conversion Benchmarks.

Frequently Asked Questions

People Also Ask