Case file — 8C39CE53
The idea
“VinylExport — Freemium web tool for Discogs users to export their vinyl collection and sales history to spreadsheets. Free tier covers basic collection export (artists, labels, formats, conditions).”
The panel
The competitive landscape is almost entirely free, open-source tools. GitHub already has Python scripts (victorloux/discogs-get-collection, 13 stars) and a Google Sheets tracker (t8ortot/sheets-discogs-tracker) that do basic collection export via the Discogs API. These aren't funded startups—they're hobby projects—but they solve the free-tier problem for any moderately technical user, which describes much of the Discogs power-user base. Red flag you're ignoring: Discogs itself offers CSV export, and their API is public. Your free tier competes with zero-cost open-source scripts, making conversion to Pro extremely difficult. The addressable paying audience—sellers needing tax-ready fee breakdowns—is narrow and seasonal. Genuine strength: No one has packaged the sales history with fee breakdowns for tax reporting into a polished, non-technical tool. That's a real pain point for high-volume Discogs sellers around tax season and could justify a small subscription if marketed tightly to that niche.
The core technical challenge you're underestimating is Discogs API rate limiting — they cap at 60 requests per minute for authenticated users, and large collections (10k+ records) with marketplace price lookups will hit walls fast, requiring queue management, caching layers, and graceful degradation that adds real backend complexity. Build vs. buy: you'll be tempted to build your own background job processing and caching infrastructure, but you should use Redis + Bull/Sidekiq from day one — rolling your own will waste months. There is zero technical moat here. The Discogs API is public, the export logic is trivial, and any developer could replicate this in a weekend. Someone already has CSV export tools. What's genuinely well-chosen: OAuth via Discogs is dead simple, the data model is clean, and an MVP for the free tier is honestly a two-week solo build. The problem is this is a feature, not a product — and Discogs could ship it themselves tomorrow.
The addressable market is tiny—Discogs has ~10M registered users, but active sellers needing tax export are probably sub-500K globally, and willingness to pay for a spreadsheet tool is low. Your CAC problem is acute: you're targeting a niche inside a niche, so paid acquisition channels won't work economically—you're entirely dependent on organic discovery through Discogs forums and Reddit, which is slow and unpredictable. Your $5-10/month Pro pricing assumption is likely too high; this feels like a $2-3/month or $15/year utility, maybe a one-time $10 purchase. With no traction and assuming $15-20K in development costs, you need ~1,000 paying users just to break even annually at realistic pricing—that's 12-18 months minimum. What works: near-zero marginal cost per user, Discogs OAuth removes onboarding friction, and tax season creates a natural recurring urgency trigger. But this is a feature, not a company—Discogs could ship this themselves tomorrow.
This is reasonably well-timed but faces a narrow ceiling. The vinyl resale market has matured significantly—Discogs crossed 15 million users and secondary vinyl sales keep growing, meaning more sellers face tax reporting friction, especially after the US 1099-K threshold dropped to $600. That's your strongest timing factor: tax compliance pain is real and recent. However, the window is already partially occupied—several Discogs export tools and Chrome extensions exist (Discogs CSV export is native, tools like DiscogsOGraph and various GitHub projects serve power users). You're late to basic export, but the tax/fee breakdown angle still has a gap. The macro trend that matters most: tightening tax reporting requirements for gig/resale income across the US and EU. Window is open but narrow—Discogs itself could add these features anytime, and your dependency on their API and OAuth means they control your oxygen supply. Move fast or don't bother.
Cause of death
Your free tier is competing with free things that already exist — including Discogs itself
Discogs has native CSV export. GitHub has open-source scripts that do exactly what your free tier does. Your target audience — Discogs power users — skews heavily toward people who are comfortable running a Python script or using a Google Sheets integration. You're wrapping a public API in a slightly nicer UI and calling it a product. The free tier won't generate the flywheel you need because the people who'd use it already have a solution that costs them nothing and requires no OAuth trust handoff to a stranger's web app.
This is a feature living in existential terror of its platform
Both your tech and finance panels said the same thing independently, which should alarm you: Discogs could ship this themselves tomorrow. You're building on their API, authenticating through their OAuth, serving their users, and solving a problem they are best positioned to solve. You have zero technical moat — the export logic is trivial, the API is public, and your entire value proposition depends on Discogs not caring enough to add a "Download Sales Report" button. That's not a business strategy; that's a prayer. And when Discogs inevitably improves their seller tools (they're actively developing), you don't pivot — you evaporate.
The paying audience is a sliver of a sliver, and they only need you once a year
Active Discogs sellers who need tax-ready fee breakdowns are maybe 500K globally, and that's generous. Of those, the ones who can't figure out a spreadsheet themselves, who will trust a third-party app with their Discogs credentials, and who will pay for the privilege? You're looking at a few thousand people, max. Worse, the need is seasonal — tax time. You're not building a daily-use tool; you're building something people remember exists in March, use once, and cancel. At realistic pricing ($15/year or a one-time $10), you need ~1,000 paying users just to break even on modest development costs. That's 12-18 months of grinding organic discovery in Discogs forums for a lifestyle micro-business at best.
⚠ Blind spot
You're thinking about this as a data export problem. It's not. The actual pain for high-volume Discogs sellers isn't getting data out of Discogs — it's getting it into their accounting workflow. The seller who needs tax-ready fee breakdowns doesn't want a spreadsheet. They want a QuickBooks integration, a Schedule C pre-fill, a direct feed to their tax preparer's portal. A CSV is the starting point of their pain, not the end of it. You're solving the easy half of the problem and stopping right where the willingness to pay actually begins.
Recommended intervention
Kill the freemium model entirely. Kill the "collection export" tier — it's a commodity. Instead, build a seasonal tax tool specifically for US Discogs sellers affected by the $600 1099-K threshold. One-time annual purchase, $19-29, available January through April. It pulls their complete sales history, calculates net proceeds after Discogs fees and shipping, categorizes by tax lot, and generates a report formatted for Schedule C or direct import into TurboTax/H&R Block. Market it as "TurboTax for your Discogs side hustle." You're no longer competing with free CSV exporters — you're competing with the $200/hour accountant who doesn't understand what a Discogs fee credit is. That's a fight you can win. The 1099-K threshold change is your one genuine timing advantage — use it before Discogs or a tax software company notices the gap.
Intervention unlocking
5seconds
No account needed. One email, no follow-ups.
Want your idea examined? Free triage or full panel →