BricksDeal
Independent LEGO price tracker for the Dutch market.
Hey IH,
I'm Frank, the solo maker behind BricksDeal: an independent LEGO price tracker for the Dutch market.
I built it because buying LEGO sets in the Netherlands is oddly hard to judge. The same set can move across dozens of retailers, crossed-out prices often exaggerate the real price drop, and there was no simple CamelCamelCamel-style reference for LEGO buyers here.
BricksDeal compares live prices across 72 Dutch retailers, shows RRP, price history, all-time lows, stock signals, and lets people set free price alerts.
The stack is deliberately boring: Laravel, SQLite, Python scrapers, Cloudflare/R2 for images, and a pipeline that turns messy retailer data into public set pages, deal pages, and buying guides.
The hard part has not been the UI. It has been product matching, retailer-specific data quality, price history, and deciding what actually helps a buyer answer one question:
“Is this LEGO set genuinely worth buying right now?”
I’m treating it as both a consumer product and a long-running indie engineering project. Current focus: better alert flows, stronger SEO pages, cleaner retailer coverage, and making the price history more useful before users click out to a retailer.
Would love feedback from anyone building comparison/search/affiliate products: early on, what would you treat as the strongest signal — outbound clicks, repeat visits, saved alerts, or successful price-drop emails?
1 Comment
I'd be careful with one thing.
The interesting question may not be which signal is strongest.
It may be which decision each signal is encouraging you to make.
Those can look similar early on while pushing the product in very different directions.