Kickstarter Bag Project Updates: Communication That Builds Trust

The campaign closing is not the end of the selling, it is the start of the part where you have no new product to show and a fixed group of people watching. Most creators handle this badly by going quiet while they work, which is understandable and wrong. Backers do not experience quiet as work in progress, they experience it as risk. This article gives you a calendar that keeps you visible without inventing news.

Why silence after funding is the biggest risk

During the campaign you had something to say every day because something was happening every day. After the campaign closes, the next genuinely new thing may be three weeks away, and the temptation is to wait for it. That gap is where trust erodes. A backer who has given you 129 dollars and hears nothing for a month will not assume you are busy, they will assume the project has stalled, and a small number of them will say so publicly, which then sets the tone for everyone else reading.

The asymmetry is worth understanding. A short update that says nothing has changed costs you thirty minutes and buys another month of goodwill. A month of silence costs you the same month of goodwill and buys nothing. Over a production cycle that runs 35 to 50 days in bulk plus sampling at 6 to 10 working days plus freight and fulfilment, you are looking at three to five months of post-funding contact, and the cumulative effect of regular short updates over that period is the difference between a backer base that recommends your next campaign and one that warns people off it.

• Silence is interpreted as risk, not as progress, by almost every backer.
• One public complaint sets the tone for everyone reading the comments afterwards.
• Short updates compound: five two-paragraph updates beat one long explanation after a crisis.
• Your next campaign is being decided now, by the people watching how you handle this one.

There is also a practical benefit that creators underestimate. A backer base that hears from you regularly is far more forgiving when something goes wrong, and something will go wrong. Campaigns that communicated monthly through production and then hit a three week delay tend to absorb it with a shrug. Campaigns that went quiet and then announced the same delay tend to get refund requests. The delay is identical; the reaction is entirely a function of what happened before it.

The post-funding update calendar

Write this calendar before the campaign closes, with dates attached to each entry rather than vague intentions. The dates will move, and that is fine, but a calendar with dates gives you a commitment you can feel, and it lets you see a gap coming before it arrives. The structure below assumes a typical bag campaign: close, survey, sampling, bulk, inspection, freight, fulfilment. Adjust the intervals to your actual schedule and then hold to them.

Note the two places where cadence increases: the survey period, which needs three contacts inside three weeks, and the despatch period, which needs fortnightly contact because that is when backers are most anxious and most likely to compare notes with each other. Everywhere else, monthly is right. Monthly is frequent enough to feel present and infrequent enough that you will actually keep it up, and a cadence you abandon is worse than a cadence you never promised.

Update one: the close and the backer survey

The first update goes out within 48 hours of the campaign closing and it has three jobs: state the result, state what happens next with a date, and ask for one action. The one action is the survey. Do not bury the survey link at the bottom of a long celebratory post, because the response rate of that first contact is the highest you will ever get and you should spend it on the thing you actually need.

Keep the survey to four questions: colourway, any variant choice such as size or strap option, shipping address confirmation, and anything regulated or safety related. Every additional question costs you response rate, and a response rate below 85 per cent creates a production planning problem, because you cannot allocate colourways you do not know about. State a deadline, state what happens to non-responders, and state the default you will apply, which is usually the primary colourway.

• State the total and the backer count in the first line, because that is what people came to read.
• Give one date for the next update rather than a range of intentions.
• Put the survey link in the first three lines, then repeat it at the end.
• State the default rule for non-responders so nobody is surprised by what they receive.
• Say what is locked and what is not, so late requests for a new colourway have an answer already written.

The what is locked line deserves a sentence of its own, because it is the one that saves you the most correspondence later. Colourways are locked once the survey closes, and each one is a separate commitment at 500 pcs per style and per colourway, so a late request to switch is not a small favour. Saying that plainly in the first update, with the reason, is far better than refusing the same request individually forty times over the following month.

Updates during sampling

The sampling stage is the easiest update to write and the most valuable, because it is the moment the product becomes real and you have photographs to prove it. Sampling runs 6 to 10 working days for a standard style and 12 to 15 working days for complex constructions, and the update should say which band you are in and when the sample is expected. Then, when it arrives, post photographs from the same angles you used on the campaign page, so backers can compare directly.

The valuable part of this update is not the photographs, it is the changes. If the sample revealed that a pocket needed to move 2 cm or a strap needed a different webbing, say so and say why. Backers interpret a disclosed change as competence, and they interpret a silent change as concealment if they later find out. Our programme coordinator keeps a change log through this stage for exactly this reason, and the update is essentially that log written in plain language with photographs.

One more thing this update should do is answer the question backers are forming but not yet asking: is the bag in the video the bag I am getting. Answer it explicitly, in one sentence, with the sample in shot. Saying this is the production sample, photographed this week, in the colourway you selected costs fifteen words and removes a doubt that would otherwise sit in the comments for two months. Our crowdfunding bag sampling page explains what happens at each sample stage if you want more detail to draw on.

Updates during bulk production

Bulk is the long quiet stretch, running 35 to 50 days, and it is where discipline matters most because there is genuinely less to report. The mistake is to wait for a milestone. The right approach is to report on the stage you are in, even mid-stage: cutting, printing or embroidery, assembly, trimming, finishing, packing. Each of those is a legitimate update topic with a photograph, and a backer who has seen fabric being cut is more confident than one who has only been told production has started.

Every bulk update should reconfirm the delivery estimate, even when it has not changed. This sounds repetitive and it is the single most useful line in the update, because a date restated monthly is a date people believe, and a date that is only mentioned when it changes becomes a date people watch nervously. Put it in the same place in every update, ideally as a standing line near the top: current delivery estimate, unchanged, as of this date.

• Report the stage, not just the milestone: cutting, assembly, trimming, finishing, packing.
• Include one photograph of the actual production floor, however ordinary it looks.
• Reconfirm the delivery estimate every time, in the same position, with the as-of date.
• Answer the top comment question in the update body, by name, so readers see questions get answered.
• Flag anything uncertain early, even before you know the outcome, rather than waiting for certainty.

That last point is the one creators resist, and it is the one that protects them. If a fabric lot is two days late and might matter, say so in the monthly update as a watching this note rather than waiting until you know whether it affects the date. Early uncertainty communicated is read as transparency. Late certainty communicated is read as an excuse, even when the news is good, because the backer now knows you were sitting on information.

Inspection and shipment updates

The inspection update is short and specific, and it should name the standard. Inspection at AQL 2.5 to ISO 2859-1 means a defined sample size and a defined acceptable defect count, and telling backers the result tells them the product was actually checked rather than assumed. If it passed first time, say so. If it failed and was reworked, say that too, with what was reworked and what the re-inspection found. A failed inspection honestly reported is a credibility gain, not a loss.

The shipment update sets expectations for the next waiting period, which is often the longest felt wait of the whole project. State what has left, by what method, with what estimated transit time, and then state what backers should expect next: customs clearance, arrival at the fulfilment partner, sorting, despatch. Naming the remaining steps matters because a backer who knows there are three stages left is more patient than one who thinks the parcel is simply late. Repeat the delivery estimate and say whether it is still on track.

Freight is also the stage where the delivery estimate is most likely to move, because transit times are the least controllable part of the chain. If it moves, this is the moment to say so, not after arrival. A shipment update that says goods departed on the 14th, transit is running 5 days longer than planned, our revised estimate is now the third week of June is doing exactly the right thing: it gives a fact, a cause and a new date in one sentence, and it gives backers two weeks to adjust rather than two days.

Fulfilment updates: the despatch sequence

Despatch is the highest-anxiety stage and needs the highest cadence, fortnightly at minimum. The content is operational and specific: how many parcels have left, which zones, what order, and what a backer in each zone should expect. Backers compare notes with each other constantly at this stage, and an update that explains the despatch order stops the most common complaint, which is not that a parcel is late but that someone else in a different country got theirs first.

1. Publish the despatch order before it starts: by tier, then by zone, then by pledge date within zone.
2. Post a fortnightly count: how many despatched this week, how many remain, which zone is in progress.
3. Explain zone differences once, clearly, and link back to it rather than re-explaining in every update.
4. Set a query window: tell backers not to raise a missing parcel query until a stated number of days after despatch.
5. Close with the next update date, so the rhythm is visible and nobody has to ask.

The query window is worth emphasising because it protects your support capacity at the moment it is most stretched. Carrier tracking is frequently silent for several days after a label is created, and a backer seeing that will contact you. Telling everyone in advance that tracking can take up to seven days to show movement, and asking them not to query before day fourteen after despatch, removes most of that load. The rewards and fulfilment page covers the operational side of this in more detail.

The delay update: structure and wording

Every production project eventually hits a delay, and the delay update is the single most important message you will write. It has four parts in a fixed order: what happened, what the new date is, what you are doing about it, and what backers should do if they are affected. Write them in that order and resist the urge to open with context or apology, because the first two questions in every reader's mind are what went wrong and when do I get it.

Part one

What happened, stated factually

Part two

The new date, stated as a month or a date

Part three

What you are doing about it

Part four

What backers should do, including the refund route

Length

200 to 350 words

Timing

Within 48 hours of knowing

Three wording rules make the difference. Use a date, not a season: mid-summer is interpreted differently by every reader and creates a second round of questions. Do not over-explain the cause: two sentences of factual cause is enough, and a long explanation reads as defensiveness. Name the remedy: if you are air-freighting part of the run, or splitting despatch, or upgrading a component at your cost, say so, because a remedy is what converts an apology into an action.

And one thing to avoid entirely: do not frame the delay as good news. Updates that open with exciting news before revealing a three week slip are widely disliked and are quoted in comments as evidence of spin. State the delay in the first line. If there is genuinely good news alongside it, put it in the second half, after the new date has been given and the remedy described. The ordering does more work than the wording.

Handling individual complaints in public

Individual complaints arrive in the comments, and how you answer them is read by every future visitor to the page. The rules are simple and worth writing down before you need them. Acknowledge within 48 hours, move the specifics to private message as soon as you have acknowledged, and never argue the facts in public. A comment thread where the creator argues with a backer is worse for the campaign than the original complaint, regardless of who is right.

The public reply should do three things: acknowledge the specific issue without admitting or denying fault, state the process you will follow, and give a timeframe. Something like: thanks for flagging this, I have messaged you directly, we will replace or refund once you send a photograph, and we will close this out within five working days. That reply is read by hundreds of people and it tells all of them that complaints are handled, which is the actual outcome you want.

There is a category of commenter who will not be satisfied by any process, and the discipline there is to stay procedural rather than emotional. Answer once, publicly, with the process. Answer again in private. Then stop. Other backers can see the difference between a creator who is being reasonable and a commenter who is not, and the audience generally sides with the reasonable party if you give them the evidence of it. Our longer piece on campaign risks and how to communicate them covers the same ground from the risk side.

Four update types that damage trust

The vague progress update: things are moving along well, we are on track. This is worse than no update, because it tells the reader there is nothing to report while implying there is. Every update needs at least one fact a reader did not have. The upsell update: using a project update to sell a different product or to drive traffic elsewhere. Backers read this as exploitation of a captive audience, and they are right to.

The blame update: attributing a delay entirely to a partner, a supplier or a carrier. Even when accurate, it reads as an attempt to avoid responsibility, and the backer's contract is with you, not with your production partner. State the cause factually without attribution. The apology-without-information update: a long apology with no new date, no cause and no remedy. Apology without information is a request for patience that offers nothing in exchange, and it usually generates more complaints than it settles.

There is a fifth pattern worth naming, which sits between the categories: the over-promising update written during a good week. It happens when sampling goes well or an inspection passes early, and the creator, feeling relieved, writes that everything is ahead of schedule and delivery may be earlier than promised. That is a promise you have now made publicly, and if the next stage slips by a week you have created a delay out of an improvement. Report progress factually and leave the delivery date where it is until it is actually confirmed.

The discipline that avoids all five is a simple test applied before you publish: does this update contain a fact the reader did not have, and does it leave them knowing more than they did? The vague progress update fails both. The upsell update fails the second. The blame update passes the first and fails the second, because the reader learns a cause but not a consequence. The apology without information fails both outright. If you cannot pass the test, wait a week and write it when you have something.

Three templates you can adapt

Templates are useful as structure, not as wording, and backers can tell the difference. Adapt these to your voice and put a real fact in every one. The first is the sampling update, the second is the delay update, and the third is the despatch update. Each is under 200 words, which is the right length for a project update: long enough to carry a fact and a date, short enough that people read to the end.

• Sampling update: the sample arrived on [date], here are three photographs, we changed [specific] because [reason], delivery estimate remains [month], next update [date].
• Delay update: [specific cause]. Revised delivery estimate is [month]. We are [remedy]. If this does not work for you, request a refund through [route] by [date].
• Despatch update: [number] parcels despatched this week to [zone]. Remaining [number]. Tracking can take up to [number] days to update. Next update [date].

What all three have in common is a fact, a date and a next step, and that trio is the whole method. If you cannot put a fact in an update, do not send one, and instead move the next date forward by a week. If you cannot give a date, say why and say when you will be able to, which is itself a date. An update that contains a fact, a date and a next step is one a backer can act on, and updates people can act on are the ones that build trust.

If you are planning a bag campaign now, build this calendar into the timeline before you launch, and make sure the dates in it are real. Bulk runs 35 to 50 days, sampling 6 to 10 working days for standard styles or 12 to 15 for complex ones, and inspection sits at AQL 2.5 to ISO 2859-1 on FOB Xiamen terms. The crowdfunding bag guide places all of it in one sequence so you can see where each update falls.

Frequently Asked Questions

People Also Ask