Crowdfunding

Crowdfunding Rewards and Stretch Goals That Don't Wreck Your Timeline

Every reward tier and stretch goal is a promise you're obligated to keep, often at a scale fulfillment nightmares are made of. Here's how to design rewards backers want and you can actually deliver — and where extra canon quietly becomes extra work you didn't budget for.

CanonBoard EditorialJuly 11, 20269 min read

Rewards and stretch goals are the most exciting part of building a campaign and the most dangerous. They're where you get to imagine delighting your backers, and where a few generous-sounding ideas can quietly commit you to a year of unbudgeted work at a scale you won't see until it's too late to change. This is the reward-design chapter of the crowdfunding for fiction pillar, and it exists because reward decisions made in the optimism of pre-launch are the ones people most regret in fulfillment.

The core reframe is simple: a reward is not a marketing feature, it's a contract. Every tier you list and every stretch goal you announce is a promise you're now legally and reputationally obligated to keep, multiplied by however many people choose it. Enthusiasm designs rewards as if the campaign will do fine; survival designs them as if the campaign will do great — because the great outcome is the one that has to still be deliverable.

The multiply test: design for success, not for average

The mistake that hurts most isn't offering a bad reward; it's offering a good reward without imagining it at scale. A personalized short story sounds like a wonderful $75 tier until four hundred people select it and you've sold yourself a year of writing you'll never be paid for again. A signed-and-sketched edition is charming until the sketching alone is six weeks between you and shipping. None of these look dangerous at ten backers — they look dangerous at the number you're actually hoping for.

So run every tier through one unforgiving test before it goes on the page: multiply it by the backer count of a campaign that does really well, and ask whether you'd still offer it at that volume. If the answer is no — if the reward is only survivable when the campaign underperforms — it isn't a reward, it's a liability priced as a perk, and it will come due exactly when you're busiest. Design for the success case, every time.

Separate what scales from what you make by hand

Sort every reward idea into two piles. The first is things that cost roughly the same effort per backer regardless of volume: digital editions, a print run, bundles, add-on books. These can carry the bulk of your backers safely, because a thousand of them is barely more work than a hundred. The second pile is things that cost your personal time per backer: custom writing, personalized art, naming a character after someone, a one-on-one anything. These are precious and dangerous, and they must be capped.

The winning structure uses scalable rewards for volume and reserves a small number of hand-made, high-touch rewards as genuinely limited tiers — capped at a quantity you could deliver on your worst week, not your best. This gives backers the special options they love without betting your delivery timeline on how many of them want one. The pricing side of this — making sure even the scalable tiers actually cover their cost once fees and shipping are counted — is covered in how to crowdfund a novel and Kickstarter for writers.

Beware the stretch goal that adds canon

Stretch goals come in two kinds, and the difference decides whether they help or hurt. Quality stretch goals improve the thing you're already making — nicer materials, a hardcover upgrade, professional narration — and they mostly add cost, which the extra funding covers. Scope stretch goals add new work: a bonus novella, an extra character, three more chapters, a side story set in your world. These feel like the generous ones, and they're the ones that wreck timelines.

The trap is that a scope stretch goal isn't just more pages; it's more canon. A bonus story set in your world has to agree with the main work in every detail — the same characters behaving consistently, the same rules holding, the same timeline intact — which means it carries all the continuity obligations of the core project, added late and under the same deadline. This is precisely where a single, checkable source of truth for the world earns its place: a story bible for IP is what lets you fold new material in without it quietly contradicting what backers already paid for.

If you offer scope stretch goals at all, plan them as fully as the main project before you announce them — know the story, know how it fits the canon, know what it costs and how long it takes. An unplanned stretch goal announced in the heat of a surging campaign is a promise made by your optimism that your future self has to keep under pressure. The full picture of keeping those promises without breaking the world is in delivering a crowdfunded project.

Frequently asked questions

Are stretch goals a good idea for a fiction campaign?
They can be, but they're the single most common way a funded campaign becomes an unfulfillable one, so treat them with suspicion. The safest stretch goals improve the thing you're already making — better paper, a nicer cover, a higher production value — because they add cost, not scope. The dangerous ones add new work: bonus stories, extra characters, additional chapters. Those expand the project you have to finish and the canon you have to keep consistent, often right when you're most stretched. If you offer scope-based stretch goals at all, plan them as fully as the main project before you announce them.
How do I design rewards I won't regret at scale?
Run every tier through one test: multiply it by the number of backers you'd have if the campaign does really well, and ask whether you'd still offer it. Rewards that cost roughly the same effort per backer at any volume — digital editions, print copies, bundles — are safe to offer broadly. Rewards that cost your personal time per backer — custom writing, personalized art, naming characters after people — are only safe when capped at a small, genuinely limited quantity. Design for the success case, because success is the scenario that has to remain deliverable.
Stop discovering continuity breaks in the table read.

CanonBoard scans your whole world and tells you where it disagrees with itself.

Start free
Share