Indiegogo vs Kickstarter: What Backers Expect When the Bag Ships

What Backers on Each Platform Think They Bought

A backer's expectation is set by the promise they believe was made to them, and the two platforms frame that promise differently. A Kickstarter backer experiences a campaign as a product launch that happens to be funded in advance: the page is polished, the reward tiers read like a store, and the funding model means the campaign either reaches its goal or nothing happens. That framing produces a backer who expects the item to arrive as advertised, close to the stated date, with no further decisions required.

An Indiegogo backer experiences a campaign as an early-access purchase with a longer relationship attached. The platform's flexible funding option, its continued sales through the post-campaign store, and its stronger association with hardware and technology projects all mean the backer has implicitly accepted more uncertainty about the product itself. That acceptance is real and it is valuable, but it attaches to the product, not to the process. Being late, vague or uncommunicative is not covered by it.

This is the practical reason the difference matters for a bag campaign: the tolerance for product iteration is different, and the tolerance for process failure is not. An Indiegogo audience will accept that the strap hardware changed between the prototype and the production unit if you told them. Neither audience will accept a six-week silence. The operational implication is that your communication plan has to be built to the stricter standard of the two, whichever platform you are on.

There is a second-order effect worth naming, because it affects the production order rather than the messages. A backer who expects a retail-grade experience will inspect the delivered item against the page closely and will comment publicly on any discrepancy. That makes the golden sample and the pre-shipment inspection the two documents that protect the campaign's reputation, and it is why our Custom Bags for Indiegogo & Multi-Platform Crowdfunding planning starts with the specification rather than with the page.

How the Funding Model Sets the Expectation Baseline

Kickstarter is all-or-nothing, and that single mechanic shapes everything downstream. A campaign that funds has, by definition, reached the volume the creator asked for, so the backer reasonably assumes the production run is viable and will happen. The psychological contract is: the money exists, the product exists, therefore the date is real. A campaign that misses and relaunches carries none of that baggage, which is one reason relaunching is often wiser than scrambling.

Indiegogo offers both fixed and flexible funding, and the flexible route creates a subtly different contract. A backer on a flexibly funded campaign knows the campaign could close below its goal and still proceed, so they are more alive to the possibility that the run will be smaller than planned, that a colourway might not be made, or that the schedule depends on a second wave of sales. That awareness makes them more receptive to honest messages about volume and less shocked by a change.

• All-or-nothing sets a binary expectation. Funded means it will be made, and the date is understood as a commitment.
• Flexible funding sets a conditional expectation. Backers expect progress updates tied to volume, not just to dates.
• Both models set a communication expectation. The funding model does not reduce the duty to report; it changes what is reported.
• Volume news is news. On a flexible campaign, passing the 500 pcs per colourway floor is itself worth an update.
• Neither model permits silence. An unanswered comment thread becomes the campaign's public record either way.

The fourth item is the one most creators miss, and it is a genuinely useful piece of communication. Telling backers that the order has cleared its minimum, that fabric is booked, or that the run has moved from sampling into bulk gives them a concrete milestone to hold on to, and it costs nothing but attention. On a flexibly funded campaign those milestones carry more weight than dates, because they are the evidence that the campaign is real.

The production side of the funding model is more mechanical and just as important. An all-or-nothing campaign that funds has a known volume on the day it closes, so the order can be placed against locked numbers. A flexibly funded campaign may close below goal and continue selling, which means the volume at close is not the final volume, and the 35 to 50 day production window has to be scheduled against a number that is still moving. Decide in advance whether you place the order at close, at a fixed later date, or in two waves.

Delivery Date Expectations and How Precise They Are

Kickstarter backers read the delivery date on the campaign page as a promise with a month's resolution, and they hold it. Indiegogo backers read it as an estimate with a wider band, and they hold the updates more tightly than the date. That difference is small and it is frequently over-interpreted by creators who use it to justify a loose date. The correct reading is that the tolerance band is a few weeks wider on one platform, not that dates are optional on either.

Read that table as a chain and the slack becomes visible. The only genuinely controllable slack is in the pledge data lock and in material booking, and both are decisions made in the first fortnight after the campaign closes. Everything else is a physical process with a duration that does not respond to urgency. A campaign that promises a date without having walked this chain has not made a promise, it has made a guess with a month attached.

The practical recommendation is the same for both platforms and it is worth stating plainly: publish the month you get from this table, add two weeks, and then outperform it. A campaign that promises October and delivers in late September generates goodwill that no marketing spend can buy. A campaign that promises September and delivers in mid-October generates comments, refund requests and a permanent mark on its public record, and the difference between the two was one line on a spreadsheet.

Update Cadence and the Silence Threshold

Silence is the most damaging thing a campaign can do and it is entirely within the creator's control, which makes it the least excusable failure there is. The threshold is shorter than most creators assume: on a busy campaign, two weeks without an update is noticed, and four weeks is commented on. The good news is that the content bar is low. An update that says what happened, what is happening next and when the next update will come is sufficient, and it takes fifteen minutes to write.

1. Set a cadence before launch and state it on the page, so backers know the rhythm they are entitled to expect.
2. Keep the cadence during the quiet period, which is the long stretch between the deposit and the first production photos.
3. Photograph the production run. A photo of cut panels or a packed carton is worth more than three paragraphs of reassurance.
4. Report bad news within 48 hours of learning it, with a revised date and a cause, never with reassurance alone.
5. Close every update with the next date. Backers measure reliability by whether the promised update arrives.

The second item is where most campaigns fail, and the reason is structural rather than careless. Between placing the order and seeing the first production photos there is genuinely nothing happening from the creator's point of view, because the run is in progress and progress is invisible. That is exactly when the campaign goes quiet and exactly when backers start to worry. The fix is to schedule updates against the production milestones rather than against the news: material booked, cutting started, first units off the line, inspection booked, inspection passed, packed, shipped.

There is a specific practice worth adopting for bag campaigns because it costs almost nothing and it does more than any other single message: photograph the first unit off the bulk line next to the approved golden sample and post both. It demonstrates that the bulk run matches the sample, it demonstrates that production has actually started, and it pre-empts the single most common backer anxiety, which is that the thing they receive will not be the thing they saw.

Shipping Costs: Collected at Pledge or Collected Later

Shipping is where expectation gaps turn into money, and the two platforms differ in how shipping is typically handled at the point of pledge. Kickstarter's flow generally collects shipping as part of the pledge, so the backer has already paid for delivery and expects nothing further. Indiegogo campaigns more often collect shipping later, through a survey or at the point of dispatch, which means the backer has made a pledge that does not yet include delivery.

That structural difference produces a specific failure on each side. On the platform where shipping is collected up front, the failure is under-collection: the creator estimates the zones wrong, the freight bill is larger than the pot, and the margin is gone. On the platform where shipping is collected later, the failure is sticker shock: the backer pledged 60 and is now asked for 25 more, and a proportion of them refuse, abandon the survey or request a refund.

• Model the zones from real data, not from assumptions. Use your existing audience geography or a comparable campaign's backer map.
• Collect shipping at pledge wherever the flow allows. A paid-for delivery is a settled expectation; a later invoice is a renegotiation.
• If you must collect later, say so loudly on the page, with a stated range per region, before anyone pledges.
• Build a buffer of 10 to 15 per cent into the shipping line to absorb rate rises between launch and dispatch.
• Never announce dispatch before tracking exists. That is the fastest route from a delay to a dispute.

The second and third items are the operational ones, and they connect to the production plan through the packing specification. Shipping cost is a function of packed dimensions and weight, and a bag that ships flat-packed costs materially less per unit than the same bag shipped stuffed and boxed. Deciding the packing format during sampling rather than during packing is therefore a freight decision as well as a presentation decision, and the custom bag packaging options each carry a different volumetric profile.

There is one more expectation worth stating because it is universal and it catches creators out: free shipping means free to the backer, not free. Both audiences understand that the cost is inside the price, and both will object if free shipping is announced and then a handling fee appears. If the campaign offers free delivery, the freight, duty and last-mile cost have to be inside the tier price from the start, which is the arithmetic the backer shipping cost page sets out in full.

Refund, Cancellation and Chargeback Behaviour

Refund behaviour is a lagging indicator of expectation failure, and by the time it appears the damage is already done, but the pattern is worth understanding because it changes what you should do in week one of a delay. Backers generally do not ask for refunds because a campaign is late. They ask because a campaign is late and silent, or because a campaign is late and the explanation changed twice. The trigger is loss of confidence, not the calendar.

The practical consequence is that refund requests are preventable, and the prevention is the communication described above. A campaign that announces a delay with a cause, a new date and a named milestone will typically lose a small single-digit percentage of backers. A campaign that goes quiet for six weeks and then announces a delay will lose considerably more, and the second group includes the backers who leave public comments, which is the more expensive loss.

The second pattern is about what happens at delivery rather than before it. A backer who receives a bag with a visible defect does not usually want a refund; they want a replacement, and they want it quickly. That is the reason to hold a unit buffer on every run. Ordering two to five per cent above the pledge count costs a small amount and converts a replacement request from a four-week problem into a two-day one, and it is the difference between a resolved ticket and a public complaint.

Chargebacks are the last and most expensive category, and they are almost always a payment-mechanics problem rather than a product problem. They arise when a pledge was taken a long time before delivery and the backer no longer recognises the transaction, which is why a reminder update shortly before the payment is captured, and a clear descriptor on the statement, are worth the effort. On long campaigns this is not a marginal concern.

The Quality Threshold Each Audience Tolerates

The quality threshold differs between the two audiences in a specific and useful way. A Kickstarter audience, framed as buying a finished product, judges the delivered item against retail: they compare it to a bag they could have bought in a shop, and visible defects are read as a failure of the promise. An Indiegogo audience, framed as backing an early build, is more prepared to accept that a first production run has rough edges, provided the function is right and the issues are acknowledged.

The fourth row is the interesting one, and it is the only place where the two audiences genuinely diverge. A disclosed specification change is acceptable to an early-access audience and much less acceptable to a retail-framed one. That gives an Indiegogo campaign a genuine option that a Kickstarter campaign does not have: if a component is unavailable or a construction proves unreliable, the change can be communicated and absorbed. It does not remove the obligation to get it right, but it changes the cost of a late correction.

Note what is not on that table: any defect class where the tolerance is high. There isn't one. The difference between the audiences is a matter of degree on two rows, and everything else is judged to the same standard. That is why the inspection discipline does not vary by platform: AQL 2.5 to ISO 2859-1 against a retained golden sample and a written tolerance list, on every order, regardless of where the campaign ran.

There is a final point about quality that belongs to fulfilment rather than to production, and it is the one that generates the most comments: consistency across the shipment. Backers talk to each other. A run where 3 per cent of units have a visible fault generates a thread in which the fault looks ubiquitous, and the campaign's reputation is set by the thread rather than by the percentage. Holding the defect rate down is a reputation decision, not just a cost decision.

Communication Channels and Where Complaints Appear

Complaints appear in predictable places, and knowing where they appear is half of managing them. Campaign comments are public and permanent, and they are read by potential late backers as well as by existing ones. Direct messages and platform messages are private and voluminous. Email goes to the support inbox. Social posts reach an audience that has not backed. Each needs a different response time, and the public one needs the fastest, because a comment left unanswered for a week becomes the top of the thread.

1. Public comments: acknowledge within 24 hours, even if only to say a full answer is coming.
2. Private messages: answer within two business days with a specific, non-templated reply.
3. Support inbox: set an auto-reply stating the response window, and keep it.
4. Social posts: redirect to a channel you control, politely and publicly.
5. Repeated questions: promote the answer into an update rather than answering it forty times.

The fifth item is the efficiency trick that makes the whole thing manageable, and it is worth building into the campaign plan at launch. Every backer question that gets asked more than five times should become a line in the next update, an FAQ entry on the page, or both. A campaign that does this from the start will find that its message volume falls rather than rises, because the questions are being answered before they are asked. A campaign that answers each one individually will drown in week three.

There is a staffing implication that creators consistently underestimate, and it has a number attached. A campaign with 1,000 backers will generate somewhere in the region of 300 to 600 inbound messages across its life, concentrated in three waves: at launch, at the first delay and around dispatch. Budgeting four to eight hours a week for the quiet periods and considerably more during the waves is realistic, and it should be assigned to a named person rather than absorbed informally.

Indiegogo InDemand and the Long Tail Expectation

The post-campaign store changes the shape of fulfilment in a way that has no Kickstarter equivalent, and it is the single biggest operational difference between the two platforms. An Indiegogo campaign can keep selling after it closes, which means the production plan does not end at close, and a creator who placed one order against the closing number will find themselves running a second production run weeks later, at a worse unit price and with a disrupted schedule.

The fix is to plan the second slot in advance. Reserve a production window for a re-order before the first one starts, tell backers what the reorder cadence is, and batch the long-tail orders rather than chasing each one. Batching matters because the 500 pcs per style and per colourway minimum applies to the reorder as well, and a steady trickle of individual sales will never clear it. A monthly or quarterly batch that clears the minimum is the workable pattern.

The second consequence is inventory. A campaign that continues selling needs a unit buffer held back for late orders, replacements and the reorder gap, and that buffer has to be decided at the packing stage rather than discovered later. Holding 3 to 5 per cent of the run in reserve is normal for a campaign with a long tail, and it is the cheapest insurance available against both replacement requests and a stalled reorder.

The third consequence is the expectation itself. A backer who orders from the post-campaign store expects a much shorter delivery window than a campaign backer, because the product demonstrably exists. That expectation is reasonable and it should be met: quote a dispatch window from stock, not from a production run, and hold the reserve that makes it true. If the store sells from a batch that has not been made yet, say so explicitly on the store page.

Translating Expectations Into a Production Plan

Every expectation described above has a counterpart in the production plan, and translating them is the actual work. A precise delivery month requires a locked specification and a booked material slot. A photograph of the first bulk unit requires the inspection schedule to be agreed in advance. A replacement-ready campaign requires a unit buffer. A store that ships from stock requires a reserve. None of these are expensive and all of them are decided before the deposit, not after.

The sequencing that satisfies both audiences looks like this. Lock the specification and approve a golden sample before launch, using the 6 to 10 working day sampling window, or 12 to 15 working days for a complex construction. Collect shipping at pledge wherever the flow allows. Lock the pledge data and place the order with a 30 per cent deposit. Run bulk for 35 to 50 days with material booked in advance. Inspect to AQL 2.5 to ISO 2859-1. Ship FOB Xiamen into your chosen lane. Pay the 70 per cent balance before shipment. Announce dispatch only when tracking exists.

Two decisions inside that sequence do most of the work of managing expectations, and both are cheap. The first is booking materials before the campaign closes, which removes the largest source of schedule variance and makes the published month defensible. The second is holding the unit buffer, which converts the two most common complaints, a defective unit and a late order, from problems into transactions. Campaigns that do both are the ones whose comment sections stay calm.

The crowdfunding rewards fulfilment pillar covers the downstream shipping mechanics in full, and the bag campaign fulfilment promise page covers how to write the promise in the first place. Read them together with this comparison, because the promise on the page and the plan behind it have to be the same document.

A Comparison Table and Pre-Launch Checklist

Reading the last row as the summary is the right instinct. The differences between the two audiences are real and they are worth designing for, but they are differences of degree on most dimensions and they disappear entirely on the one that actually decides a campaign's reputation. Communicate early, report milestones, publish a date derived from the schedule rather than from hope, and hold the buffer and the golden sample that let you respond when something goes wrong.

The pre-launch checklist that follows from all of this is short. Have a physical sample and a golden sample. Have a unit price quoted against that sample, not estimated. Have the delivery month derived from the 35 to 50 day window plus inspection plus freight. Have shipping modelled by zone and collected the way the page says it will be. Have a named person owning updates. Have the buffer and the reorder slot decided. Seven items, and each one prevents a specific and predictable failure.

Frequently Asked Questions

People Also Ask