Most "opportunity" write-ups skip straight to a verdict. This one walks through an actual candidate from Idea Miner's own board end to end, unedited, including the parts that don't make for a clean pitch.
The candidate: clients on outsourcing platforms repeatedly hire freelancers to turn a Figma design or spec document into a live, pixel-perfect WordPress or WooCommerce site. This is a real, published demand feature, not a hypothetical -- in the most recent month tracked, it recorded 6 real mentions and $777.31 in aggregate posted budget across the underlying tasks (budget figures posted with the job, not confirmed final payment), backed by individually verifiable tasks ranging from a $30 five-page business site to a $750 WooCommerce build with a Figma handoff.
The opportunity score is 45 out of 100 -- decent, not a headline number, and this piece isn't going to round it up. Two independent evidence searches were run against this candidate: one against GitHub for existing open-source tools, one against general web search results for competing commercial products. Neither search surfaced a direct competitor automating "design file to WordPress theme" conversion. What both searches found instead was generic WordPress-development content and forum discussion, nothing that does the actual automation. That result means these two searches didn't find a competitor -- not that one doesn't exist anywhere; the distinction matters and this piece isn't going to blur it.
The system flagged two risks on this candidate, and both are reproduced here rather than summarized away. The first is technical, severity 52 out of 100: arbitrary input designs create arbitrary edge cases in responsive behavior, plugin conflicts, and long-term maintainability, and without a hard scope boundary a "standardized product" quietly turns into a bespoke project every time. The second is demand durability, severity 43 out of 100: the underlying sample is thin, with limited outsourcing mentions and social discussion at the time of the scoring pass, zero measurable trend momentum, and zero user votes on the platform. Real interest, not yet a proven, repeatable pipeline.
If this were worth building, the shape of a sane first version follows directly from those two risks rather than ignoring them. Risk one argues against a general-purpose "upload any Figma file, get a WordPress theme" tool -- the scope explosion isn't justified at this demand level. The narrower move is a semi-automated tool scoped to the single most common spec shape actually seen in the real tasks: a five-page-or-fewer business site, optionally with basic WooCommerce checkout, generating a starter theme and responsive header/footer/landing templates from a Figma file's frame structure and design tokens, leaving pixel-perfect polish and plugin integration as a deliberate manual step rather than trying to automate the exact part that risk one warns about. Risk two argues for validating against the same channel the demand data came from -- bidding on real live listings with the narrower, faster offering, and setting an actual stop condition (roughly a month) tied to whether mention volume for this pattern grows, rather than assuming it will.
None of this is a recommendation to build it. A score of 45 and a thin sample aren't a "go" signal, and this piece isn't going to dress them up as one. What it demonstrates is the judgment process itself: a real recurring paid signal, two independently checked search results reported with their actual scope and limits, both risks stated in full rather than summarized into something more flattering, and a validation plan that costs almost nothing because it reuses the same channel the underlying demand came from.