# Decision Memo: Exhibit-based learning games for small museums

Full report: https://ideanavigatorai.com/ideas/small-museum-learning-games/
Recorded: Not recorded

## Decision
- Team verdict: Park
- Validation verdict: Rethink (49/100)
- Confidence: 40%
- Recommendation: Keep this parked until the team has evidence for the next validation step: Build quests for three small museums at cost. Track school-group bookings, family dwell time and repeat visits over one term against the same term last year, and test whether two of the three would put a paid refresh into their next grant application.

## Team rationale
No team rationale recorded yet.

## Reviewers
- No named reviewers recorded.

## Source anchors
- Buyer: Director or sole educator at a small history, art or science museum (typically under $250,000 annual budget) that hosts school groups and families
- Market: Museum education
- Problem: Small museums run with a few staff and volunteers who each wear several hats, so school-group activities are printed worksheets reused for years and families wander through in 20 minutes. Off-the-shelf hunt apps need someone to write, test and update the content. Hiring a digital agency for a custom game costs more than the whole education budget, so visits stay passive and school bookings and repeat family visits fall off.
- Thesis: Exhibit-based learning games for small museums should be tested as a narrow first-win workflow for one buyer: Director or sole educator at a small history, art or science museum (typically under $250,000 annual budget) that hosts school groups and families.
- Source: https://www.imls.gov/news/imls-completes-grantmaking-cycle-major-investment-small-american-museums
- Source: https://aaslh.org/communities/smallmuseums/
- Source: https://www.aam-us.org/2026/04/06/aam-statement-on-the-presidents-fy27-budget-proposal/
- Source: https://en.actionbound.com/

## Validation rubric
Rubric version: INAV-VALIDATION-2026-06-04

### Demand signal - 4.4/10 (24% weight)
Demand looks weak because the report has 3 source-backed signal(s), an editorial confidence of 40/100, and a defined buyer in Museum education.

- AASLH's working definition says small museums typically run on under $250,000 a year with a small, multi-role staff and volunteers in key staff functions, so most have no in-house educator able to build digital content.
- Target buyer: Director or sole educator at a small history, art or science museum (typically under $250,000 annual budget) that hosts school groups and families

### Problem severity - 4.5/10 (22% weight)
Problem severity is weak when the buyer pain, customer value, and dream-outcome scores are combined.

- Small museums run with a few staff and volunteers who each wear several hats, so school-group activities are printed worksheets reused for years and families wander through in 20 minutes. Off-the-shelf hunt apps need someone to write, test and update the content. Hiring a digital agency for a custom game costs more than the whole education budget, so visits stay passive and school bookings and repeat family visits fall off.
- AASLH's working definition says small museums typically run on under $250,000 a year with a small, multi-role staff and volunteers in key staff functions, so most have no in-house educator able to build digital content.

### Willingness to pay - 5/10 (20% weight)
Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.

- Fixed-price build sized to fit a small grant line, plus a modest annual hosting and refresh fee; regional museum associations as group buyers.
- Build quests for three small museums at cost. Track school-group bookings, family dwell time and repeat visits over one term against the same term last year, and test whether two of the three would put a paid refresh into their next grant application.

### Competitive saturation - 4.8/10 (18% weight)
Competitive room is reduced by 2 recorded alternative(s); the wedge must stay narrow and differentiated.

- Recorded alternative: Actionbound
- Competitive score rewards a narrow wedge, not absence of research.

### Feasibility - 6.2/10 (16% weight)
Feasibility is thin for a moderate build if the MVP is limited to the first measurable workflow.

- Build quests for three small museums at cost. Track school-group bookings, family dwell time and repeat visits over one term against the same term last year, and test whether two of the three would put a paid refresh into their next grant application.
- The buyer's budget is thin and partly grant-dependent, and federal museum funding is under repeated budget pressure.

## Market gap
Underserved segments:
- Director or sole educator at a small history, art or science museum (typically under $250,000 annual budget) that hosts school groups and families who still run the workflow in spreadsheets, generic docs, email, or chat threads.
- Small teams in Museum education that feel the pain weekly but are too narrow for broad incumbents.
- New adopters who need guided proof before committing to a larger platform.

Feature gaps:
- A narrow workflow that reaches value without configuration-heavy onboarding.
- A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved.
- A handoff path from manual concierge service to repeatable software.

Differentiation levers:
- Use specificity as the wedge: one buyer, one workflow, one measurable result.
- Show proof earlier than broad competitors with before-and-after examples and small pilot data.
- Keep implementation lighter than incumbent suites or generic AI assistants.

## Roast and risks
Interesting hypothesis, but it needs sharper demand evidence before build time.

Blind spots:
- The buyer's budget is thin and partly grant-dependent, and federal museum funding is under repeated budget pressure.
- A broad AI assistant can flatten differentiation unless the wedge is painfully specific.
- The first release can become a generic dashboard if the job is not named tightly.

Hard questions:
- Who wakes up already trying to solve this?
- What do they stop paying for or stop doing when this works?
- What proof would make a skeptical buyer trust it in one screen?
- What is the smallest paid version of this idea?

## Kill criteria
- Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.
- No buyer can name a current cost in time, money, risk, or reputation.
- The first demo does not produce a clear next step, paid pilot, or specific objection.

## Offer ladder
- **Lead magnet (Free)**: Exhibit-based Learning Games For Small Museums checklist Goal: Capture qualified leads and learn the buyer's exact language. Value: Helps Director or sole educator at a small history, art or science museum (typically under $250,000 annual budget) that hosts school groups and families audit the painful workflow before buying software.
- **Frontend offer ($19-$99)**: Concierge review or paid template Goal: Validate urgency, workflow fit, and willingness to pay. Value: Delivers the first useful output manually before automation is trusted.
- **Core offer ($49-$499/month)**: Exhibit-based learning games for small museums focused SaaS Goal: Create the recurring revenue product after the narrow wedge survives tests. Value: Turns the recurring manual workflow into a repeatable product loop.
- **Continuity ($99-$1,000/year add-on)**: Monitoring, benchmarks, and monthly reporting Goal: Increase retention and make the product part of a routine. Value: Keeps the buyer engaged with ongoing proof, saved time, or reduced risk.
- **Backend offer (Custom)**: Done-with-you setup, agency, or team rollout Goal: Capture higher-value accounts once the productized wedge is proven. Value: Adds implementation help, integrations, and workflow migration.