Considering a Kickstarter or Gamefound board game? This step-by-step checklist helps you assess the real cost, delivery risk, evidence behind the design, and reliability of the campaign before you commit. Use the scoring template to compare several projects, then revisit your assessment as updates change the information.
Overview
Crowdfunded board games can offer unusual themes, ambitious components, and direct access to projects that may not reach traditional retail. They also ask backers to accept more uncertainty than they would when buying a game already on a store shelf. A campaign page is a sales presentation, not a guarantee of a finished product, fixed delivery date, or final shipping cost.
The useful question is not simply “Does this game look good?” It is “Does the likely value justify the money, wait, and risk for me?” That answer depends on your budget, tolerance for delays, interest in the finished game, and confidence in the publisher’s plan.
Before backing, separate three decisions:
- Design decision: Does the game appear suited to your group, preferred complexity, player count, and available time?
- Project decision: Has the creator shown enough evidence that the game can be manufactured and delivered?
- Financial decision: Is the total landed cost acceptable if shipping, taxes, add-ons, and a pledge-manager charge change the initial estimate?
A promising prototype can still be a poor backing choice if you will not have the right group, lack storage space, or cannot comfortably absorb a delay. For practical planning, compare the campaign with a retail purchase, a later edition, or another game already available. Our player-count and playtime guide can help test whether the proposed game fits your actual table.
How to estimate
Use a repeatable process rather than making a decision from the trailer, artwork, or stretch-goal list alone.
1. Record the offer
Write down the campaign name, creator, platform, campaign end date, estimated delivery window, pledge level, included content, and stated shipping regions. Save the campaign page or note the date of your assessment. Campaign pages can change during or after funding, so a dated record makes later comparison more useful.
2. Calculate the landed cost
Use this formula:
Total estimated cost = pledge + estimated shipping + estimated taxes or import charges + likely add-ons + optional storage or accessory costs.
If a figure is unknown, do not treat it as zero. Mark it as “unconfirmed” and create a low, likely, and high scenario. For example, a pledge may look affordable until shipping, an expansion, sleeves, or a later pledge-manager fee is included. If the high scenario would strain your budget, wait for clarification or choose a lower pledge.
3. Check the design evidence
Look for a playable prototype, rules or rulebook excerpts, recorded playthroughs, reports from varied playtesters, and explanations of changes made during development. Evidence is stronger when it shows the game in use rather than only finished-looking renders. A polished prototype does not eliminate risk, but it gives you more to evaluate than a concept and component list.
4. Examine production and fulfillment
Identify what the creator says about manufacturing, quality control, freight, fulfillment partners, and regional delivery. You do not need a manufacturing degree to ask whether the plan is specific. Watch for a clear distinction between development, production, freight, and delivery; these are separate stages and can be affected by different problems.
5. Review the communication record
Read updates and comments for clarity, not just optimism. Does the creator answer difficult questions directly? Are changes to components, contents, shipping, or timing explained? A campaign with a modest presentation but consistent, candid updates may deserve more confidence than one with elaborate marketing and little practical detail.
6. Score the project and set a limit
Score each category from 0 to 5, then write one sentence explaining the score. The number is a decision aid, not a prediction. Set a personal rule before backing, such as requiring a confirmed budget, acceptable group fit, and no unresolved red flag in shipping or fulfillment.
Inputs and assumptions
Use the following comparison template for every Kickstarter or Gamefound board game you are considering:
| Category | Questions to answer | Score (0–5) |
|---|---|---|
| Publisher track record | Has the creator delivered comparable projects? Are previous projects resolved, with support still available? | |
| Design evidence | Can you inspect rules, a prototype, playtest feedback, and meaningful changes? | |
| Production plan | Are components, quantities, manufacturing stages, and quality expectations described clearly? | |
| Cost confidence | Are pledge contents, shipping assumptions, taxes, add-ons, and currency clearly stated? | |
| Fulfillment timeline | Does the schedule allow for production, freight, customs, and regional delivery rather than promising only one broad date? | |
| Pledge-manager plan | Is it clear when it opens, what can be changed, how late pledges work, and whether additional charges may apply? | |
| Community signal | Do updates and responses show useful communication, realistic expectations, and documented problem-solving? | |
| Personal fit | Will your group play it at the stated player count, length, complexity, and theme? |
Add the scores for a maximum of 40 points, but read the notes beside the numbers. A high total should not override a serious unresolved issue. Treat missing information differently from negative information: missing shipping detail is not proof of failure, but it is a reason to reserve money for uncertainty and ask a specific question.
Red flags include a history of unresolved projects, unexplained changes to the pledge, unusually vague delivery language, pressure to upgrade for fear of missing out, claims that rely on renders without playable evidence, and comments being answered with general assurances rather than details. None of these alone proves that a project will fail. Together, they justify waiting, reducing your pledge, or passing.
Also consider practical ownership. Large campaigns may require substantial shelf space, sorting, and setup time. If you expect a large component count, review our board game storage guide and insert guide before adding deluxe content.
Worked examples
Example A: Strong design, incomplete cost. Campaign A has a playable prototype, clear rules, and a creator with relevant delivered projects. It scores well for design and track record. However, international shipping is described only as an estimate, and taxes are not discussed. Record a strong project score but mark the landed cost as unresolved. The sensible action is to ask for a regional shipping range and budget above the visible pledge rather than assuming the lowest possible total.
Example B: Attractive contents, weak evidence. Campaign B includes many stretch goals and detailed miniatures, but the rules are unfinished, playtesting is lightly documented, and the delivery schedule is compressed. The content may look valuable, yet the evidence behind the core game is limited. Score the design, timeline, and production categories conservatively. If the game would not interest you without the stretch goals, that is an additional warning that the decision is being driven by extras rather than the base product.
Example C: Reliable creator, poor personal fit. Campaign C comes from a publisher whose prior projects were delivered and whose updates are detailed. The total project score may be high, but the game requires a regular group for a long campaign and your table usually plays short cooperative games. Score personal fit low. Backing a credible project is still not the same as buying a game you will use. Compare it with our solo game guide if your likely play pattern has changed.
For a side-by-side review, place each campaign in a spreadsheet with columns for total cost, cost confidence, expected delivery window, score in each category, unresolved questions, and final decision. Add a follow-up column for what actually happened. This turns a one-time purchase into a useful personal record for future crowdfunded board games.
When to recalculate
Re-score a campaign whenever a meaningful input changes, not only when the funding deadline approaches. Recalculate after a new shipping estimate, revised pledge contents, component change, stretch-goal announcement, updated rulebook, manufacturing image, pledge-manager notice, or delivery update. Also revisit the decision if your budget, location, group, or storage situation changes.
Platform features, payment arrangements, regional availability, and pledge-manager terms can change. Check the current campaign and platform information rather than relying on an older guide or a previous campaign’s process. Similarly, do not carry one publisher’s delivery history across every project without checking whether the new game has different size, production complexity, or fulfillment regions.
When the game arrives, compare the outcome with your original notes: final cost, delivery timing, component quality, rulebook condition, and how often it reaches the table. Update your scores and identify which assumptions were accurate. Over time, this gives you a more reliable personal benchmark than generic confidence ratings.
The final rule is simple: back because the base game fits your group and budget, not because the campaign creates urgency. If key costs remain unknown, the evidence is thin, or the project would be painful to lose, waiting is a valid decision. Use this checklist again when the information improves, and keep your backing choices aligned with the games you will actually play.
