BrickPulse

Make your call. Score against the rest of us.

Will the Eiffel Tower retire by Q4? Will the median sealed Falcon clear $1,200? Will the new flagship hit a top-1000 rank in its first month? Cast your vote. Watch the consensus shift. Build a track record nobody can fake.

No money on the line. Just bragging rights and a shared scoreboard. Free tier views every question; Collector votes; Reseller sees the track-record-weighted aggregate the long-time veterans live by.

Public demo market — no signup needed to look. Sign up to predict.

app.brickpicker.com/predictions/market/7
BrickPulse demo market — multi-series consensus chart showing how community predictions shifted over 60 days

Why we built it

A forum thread is not a forecast.

Most LEGO "predictions" live in 80-comment forum threads, vague tweets, and YouTube hot takes. None of them resolve. None of them score. Nobody's tracking who's been right and who's been wrong for years. The signal gets lost in the noise.

BrickPulse fixes the structure. Every question has a deadline, a resolution rule, and a verifiable outcome. Every vote is logged. Every user has a public track record. The community consensus is no longer a vibe — it's a number, weighted by who's actually been right, with a resolution date attached.

That structure is what makes it fun. You stop arguing about whether the modular is retiring; you place your call, everyone places theirs, and we settle up against the actual outcome.

What's in BrickPulse

Six pieces — structure, vote, score, alert, discuss

Every part of the system is designed so the consensus is something you can actually use — not something you have to second-guess every time.

Real questions, real deadlines

Every question has a clear thesis, a clear deadline, and a clear resolution rule. "Will set 75192 be marked retired by Dec 31?" Yes/no, dated, resolvable. Not vague forum thread predictions.

  • Yes/no or multi-choice with a deadline
  • Resolution rule stated up front
  • Locked once resolved — no retroactive editing
  • Tied to a specific set, theme, or market signal
Prediction market detail page with multi-series timeline chart and predict panel

Vote. Watch the consensus shift.

Every vote shows the running consensus — the percentage on each side, the trend line over time, and how the consensus has shifted as new market data drops. The track-record-weighted view is what veterans actually use: people with a strong scoring history count more than someone who joined yesterday.

  • Live consensus % updated as votes come in
  • Trend chart showing how consensus shifted
  • Track-record-weighted aggregate
  • Disagreement signal — when smart users split

The data is right next to the vote

Every prediction question links to the relevant set's market data — current price, history, retirement signals, sold-comp depth, part-out floor. You're not voting in a vacuum. The data is right there if you want to do your homework.

  • Embedded set detail snapshot
  • Active retirement signals at vote time
  • Recent eBay sold-comp depth and pricing
  • BrickLink part-out value as a floor anchor

Build a track record nobody can fake

Every user accumulates a public track record — questions answered, accuracy rate, calibration curve (do your 80%-confident calls actually hit 80% of the time?). The leaderboard is who's actually been right, not who posts the loudest. Quietly out-call the loud ones for years.

  • Per-user accuracy on resolved questions
  • Calibration curve (confidence vs. outcome)
  • Public profile + leaderboard
  • Theme-specific track record

Pinged when something opens or resolves

When a new prediction question opens on a set you own or watch, you find out. Same for resolution: when a question you voted on closes, you see how it scored — and how the consensus performed against the actual outcome. Nothing to remember.

  • Alerts when a question opens on a watched set
  • Alerts when one you voted on resolves
  • Weekly digest of upcoming resolutions
  • Resolution outcomes vs. consensus, scored

The arguments under each question

Every question carries a discussion thread. The vote is the summary; the thread is the homework. Leak signals, retailer-side gossip, theme-cycle pattern matching — the long-form arguments live there.

  • Thread anchored to the BrickPicker forum
  • Long-form analysis from veteran community
  • Linked source citations
  • Search across resolved questions for past patterns

Real questions

Four prediction-question patterns

Each is structured with a date, a resolution rule, and a market data anchor. None are vibes. Every one resolves automatically when the rule fires.

Retirement

Will set 10307 (Eiffel Tower) be marked retired on LEGO.com on or before December 31? Resolves YES if the LEGO.com page shows "Retiring Soon" or returns 404/redirect by the resolution date.

Retirement questions are the bread and butter — the EOL window is what the asset class trades on.

Price target

Will the median sealed eBay sold price for set 75192 close above $1,200 in the rolling 30-day window ending Dec 31? Resolves against the BrickPicker price guide snapshot.

Price-target questions resolve against our published guide — no ‘which listing do we count?’ arguments.

Demand spike

Will set 21034 (London Skyline) hit a Best-Seller Rank below 1,000 on Amazon in any 7-day window between now and Q4? Resolves YES on first qualifying day.

Demand questions catch the early signal — rank moves before the price does.

Theme call

Will the Modular Buildings theme aggregate appreciation curve outperform Star Wars UCS over the next 12 months? Resolves against BrickPicker theme analytics with the methodology disclosed in the question body.

Theme calls force the long-term thesis: which sub-asset class actually compounds.

How tiers split

Free views. Collector votes. Reseller weighs.

The consensus number on the screen is the same for everyone — what changes is who can vote and who sees the track-record-weighted version that's actually predictive.

Free

$0

Forever free

View questions + consensus

Browse all open and resolved prediction questions. See the running consensus, the discussion thread, and the resolution outcome. Get a feel for how the community calls the market before you decide to vote.

Start free
Most popular

Collector

$9.99

/month

Vote + track record

Vote on questions, build your own public track record, see your calibration curve, get alerts on watchlist-set questions. Right-sized for serious collectors who want to play, not just watch.

Compare plans

Reseller

$39.99

/month

Weighted aggregate + analytics

Track-record-weighted consensus (the version that's actually predictive), per-theme leaderboards, full export of resolved questions for backtesting, and the early-question feed for sets that just landed.

Compare plans

FAQ

Real questions about how this works

Anything else? [email protected]

Why crowd-source predictions instead of using a model?
We do both. Our retirement signal feed runs algorithms on LEGO catalog flags, retailer disappearance patterns, and availability scoring — that's what surfaces in the retirement watchlist. BrickPulse is the complementary layer: the community vote drawn from veterans who follow this market all day. The two signals together are stronger than either alone.
How do questions resolve?
Every question has its resolution rule stated up front: a specific data source, a specific date, and a specific threshold. We don't editorialize after the fact. If the rule fires, it resolves YES. If the deadline passes without firing, it resolves NO. Disputed edge cases get adjudicated transparently with the source data attached.
What's the difference between BrickPulse and the retirement watchlist?
The retirement watchlist is our internal algorithm + LEGO/Brickset signals. BrickPulse is the community vote. They cover overlapping but different question sets: the watchlist is "is this set retiring soon based on the data?" — BrickPulse is also "will this set retire BY THIS DATE?", "will the price hit $X?", "will demand spike?" The vote also captures qualitative signals — leaks, retailer gossip, design-cycle pattern matching — that an algorithm can't see.
Can I propose a question?
Yes — Collector and Reseller tiers can submit questions for moderation. We screen for: (1) a clear thesis, (2) a verifiable resolution rule, (3) a real deadline, (4) something the community can actually weigh in on. We don't run "will LEGO acquire Marvel?" — we do run "will set 76309 hit a sub-1000 BSR by Q4?" because that has a data source and a date.
What does the weighted consensus actually weight?
Each user's vote weight is a function of resolved-question accuracy, calibration (do your 80%-confidence calls hit 80% of the time?), and volume. New users start at unit weight; track records compound over time. Theme-specific track records weight more on theme-specific questions. The full methodology is documented in the app.
Is this gambling?
No. There's no money on the line, no payout, no escrow. BrickPulse is forecasting, not betting. The output is a community-aggregated probability that informs your own buying or holding decisions — and a leaderboard that says who's actually been right.

Stop guessing. Vote.

Free views every open question and the running consensus. Collector unlocks the vote and the public track record. Reseller adds the track-record-weighted aggregate the long-time veterans live by.

No money on the line — BrickPulse is forecasting, not betting.