WPIntell

Commercial thesis review

Generic thesis backlog

Ambiguous market labels that are not yet specific enough to promote as commercial plugin opportunities.

262generic reports
262in this filter
4AI critique ready
4need product research
2evidence watchlist
16generic category risk
0kept generic
240directory/tag noise
8research lanes
5research families
1-20visible range

Review Rule

structured API

Rows stay out of promoted opportunity families until they show a specific buyer, painful paid workflow, clear wedge, revenue logic, competitor gap, and source evidence. Evidence-watchlist, generic-category, and directory-noise rows should not spend AI budget or appear as build recommendations until source evidence narrows them into a real paid workflow.

Research Lanes

8 lane(s)
Generic or noisy label · 240 Checkout, payment, or order workflow signals · 6 Mixed commercial signals · 5 Visual, builder, layout, or update-safety signals · 5 Unclassified generic label · 3 Automation, integration, or data handoff signals · 1 Content, media, or publishing workflow signals · 1 Developer, database, or technical operations signals · 1

Research Families

5 family hint(s)
checkout and revenue assurance · 6 agency visual QA and update safety · 5 automation and reporting layer · 1 developer change safety and site customization · 1 media publishing and video operations · 1

Family Research Briefs

4 shown

Research family, not promoted

checkout and revenue assurance

6 rows

Likely buyer/workflow: store owners and WooCommerce agencies · protecting checkout revenue and order operations

Review first with: WooCommerce store owners · secondary: WooCommerce agencies, store owners

267 complaint(s), 260 high-severity signal(s), 86 weak-competitor signal(s), 1096 analyzed conversation(s)

Next research question: Validate whether store owners and WooCommerce agencies already pay for protecting checkout revenue and order operations, starting with missing outside proof: SEO demand, SERP competitors, Adjacent substitutes.

Needs product research · 2 Generic category risk · 4

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes

  • Bot · Generic category risk · 78.0 commercial
  • Surecart · Generic category risk · 66.0 commercial
  • Custom Order Number · Needs product research · 62.0 commercial

Guardrail: This is a non-promotional research family. Do not promote it until a row proves buyer, painful workflow, paid proof, competitor gap, wedge, revenue logic, and source evidence.

Research family, not promoted

agency visual QA and update safety

5 rows

Likely buyer/workflow: site builders and agencies · preventing client-site regressions before updates or edits go live

Review first with: agencies maintaining client page-builder sites · secondary: site builders, client-site operators

167 complaint(s), 37 high-severity signal(s), 10 weak-competitor signal(s), 540 analyzed conversation(s)

Next research question: Validate whether site builders and agencies already pay for preventing client-site regressions before updates or edits go live, starting with missing outside proof: SEO demand, SERP competitors, Adjacent substitutes.

Needs product research · 2 Evidence watchlist · 1 Generic category risk · 2

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes

  • Estimated Time · Evidence watchlist · 67.0 commercial
  • Blog Grid · Needs product research · 64.0 commercial
  • Tree View · Needs product research · 58.0 commercial

Guardrail: This is a non-promotional research family. Do not promote it until a row proves buyer, painful workflow, paid proof, competitor gap, wedge, revenue logic, and source evidence.

Research family, not promoted

media publishing and video operations

1 row

Likely buyer/workflow: publishers, creators, agencies, and media-heavy site owners · keeping media embeds, galleries, watermarks, and video experiences reliable

Review first with: publishers · secondary: creators, agencies

21 complaint(s), 12 high-severity signal(s), 5 weak-competitor signal(s), 104 analyzed conversation(s)

Next research question: Validate whether publishers, creators, agencies, and media-heavy site owners already pay for keeping media embeds, galleries, watermarks, and video experiences reliable, starting with missing outside proof: SEO demand, SERP competitors, Adjacent substitutes.

Generic category risk · 1

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes

  • Gemini · Generic category risk · 64.0 commercial

Guardrail: This is a non-promotional research family. Do not promote it until a row proves buyer, painful workflow, paid proof, competitor gap, wedge, revenue logic, and source evidence.

Research family, not promoted

automation and reporting layer

1 row

Likely buyer/workflow: agencies, operators, and marketing teams · protecting analytics tracking, client reporting, and automation handoffs

Review first with: agencies accountable for client reporting · secondary: marketing operators, analytics teams

267 complaint(s), 42 high-severity signal(s), 51 weak-competitor signal(s), 651 analyzed conversation(s)

Next research question: Validate whether agencies, operators, and marketing teams already pay for protecting analytics tracking, client reporting, and automation handoffs, starting with missing outside proof: SEO demand, SERP competitors, Adjacent substitutes.

Generic category risk · 1

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes

  • Geo · Generic category risk · 54.0 commercial

Guardrail: This is a non-promotional research family. Do not promote it until a row proves buyer, painful workflow, paid proof, competitor gap, wedge, revenue logic, and source evidence.

Needs product research

Blog Grid

64.0 commercial · priority 1

Blog Grid has meaningful score signals but no specific buyer workflow or paid wedge yet.

Next action: Use product research or a capped AI critique to decide whether this is a real commercial workflow before promoting it.

Research lane: Visual, builder, layout, or update-safety signals · medium confidence

Research family hint: agency visual QA and update safety · site builders and agencies

Review first with: agencies maintaining client page-builder sites · secondary: site builders, client-site operators

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Missing specific buyer.
  • Missing paid adjacent proof.
python -m app.collect ai-refinement --market-key 'blog grid' --limit 1 --dry-run
Evidence brief

Research lane: Visual, builder, layout, or update-safety signals · medium confidence

  • Matched builder in saved report, paid-signal, or evidence text.

Lane question: Check whether the evidence is really about visual QA, layout regressions, editor handoff, or client-safe updates.

Research family hint: agency visual QA and update safety · preventing client-site regressions before updates or edits go live

Candidate buyer segment: agencies maintaining client page-builder sites

Closest non-promotional family for the Visual, builder, layout, or update-safety signals lane based on builder.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 4 complaint(s), 5 high-severity signal(s), 3 weak-competitor signal(s), 74 analyzed conversation(s)

Paid signals: 0 paid-signal plugin(s); no paid terms yet

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Blog Grid describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Needs product research

Custom Order Number

62.0 commercial · priority 1

Custom Order Number has meaningful score signals but no specific buyer workflow or paid wedge yet.

Next action: Use product research or a capped AI critique to decide whether this is a real commercial workflow before promoting it.

Research lane: Checkout, payment, or order workflow signals · medium confidence

Research family hint: checkout and revenue assurance · store owners and WooCommerce agencies

Review first with: WooCommerce store owners · secondary: WooCommerce agencies, store owners

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Missing specific buyer.
python -m app.collect ai-refinement --market-key 'custom order number' --limit 1 --dry-run
Evidence brief

Research lane: Checkout, payment, or order workflow signals · medium confidence

  • Matched order, woocommerce in saved report, paid-signal, or evidence text.

Lane question: Check whether the source evidence is really about protecting revenue, payment completion, fulfillment, or order operations.

Research family hint: checkout and revenue assurance · protecting checkout revenue and order operations

Candidate buyer segment: WooCommerce store owners

Closest non-promotional family for the Checkout, payment, or order workflow signals lane based on order, woocommerce.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 4 complaint(s), 11 high-severity signal(s), 0 weak-competitor signal(s), 61 analyzed conversation(s)

Paid signals: 3 paid-signal plugin(s); terms: order

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Custom Order Number describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Needs product research

Tree View

58.0 commercial · priority 1

Tree View has meaningful score signals but no specific buyer workflow or paid wedge yet.

Next action: Use product research or a capped AI critique to decide whether this is a real commercial workflow before promoting it.

Research lane: Visual, builder, layout, or update-safety signals · medium confidence

Research family hint: agency visual QA and update safety · site builders and agencies

Review first with: agencies maintaining client page-builder sites · secondary: site builders, client-site operators

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Missing specific buyer.
  • Missing paid adjacent proof.
python -m app.collect ai-refinement --market-key 'tree view' --limit 1 --dry-run
Evidence brief

Research lane: Visual, builder, layout, or update-safety signals · medium confidence

  • Matched page, menu in saved report, paid-signal, or evidence text.

Lane question: Check whether the evidence is really about visual QA, layout regressions, editor handoff, or client-safe updates.

Research family hint: agency visual QA and update safety · preventing client-site regressions before updates or edits go live

Candidate buyer segment: agencies maintaining client page-builder sites

Closest non-promotional family for the Visual, builder, layout, or update-safety signals lane based on page, menu.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 57 complaint(s), 7 high-severity signal(s), 2 weak-competitor signal(s), 122 analyzed conversation(s)

Paid signals: 1 paid-signal plugin(s); terms: order

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Tree View describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Needs product research

Frequently Bought Together

54.0 commercial · priority 1

Frequently Bought Together has meaningful score signals but no specific buyer workflow or paid wedge yet.

Next action: Use product research or a capped AI critique to decide whether this is a real commercial workflow before promoting it.

Research lane: Checkout, payment, or order workflow signals · high confidence

Research family hint: checkout and revenue assurance · store owners and WooCommerce agencies

Review first with: WooCommerce store owners · secondary: WooCommerce agencies, store owners

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Missing specific buyer.
  • Missing clear revenue logic.
python -m app.collect ai-refinement --market-key 'frequently bought together' --limit 1 --dry-run
Evidence brief

Research lane: Checkout, payment, or order workflow signals · high confidence

  • Matched checkout, order, woocommerce in saved report, paid-signal, or evidence text.

Lane question: Check whether the source evidence is really about protecting revenue, payment completion, fulfillment, or order operations.

Research family hint: checkout and revenue assurance · protecting checkout revenue and order operations

Candidate buyer segment: WooCommerce store owners

Closest non-promotional family for the Checkout, payment, or order workflow signals lane based on checkout, order, woocommerce.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 58 complaint(s), 31 high-severity signal(s), 2 weak-competitor signal(s), 153 analyzed conversation(s)

Paid signals: 6 paid-signal plugin(s); terms: order, checkout, conversion, pro

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Frequently Bought Together describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Evidence watchlist

Estimated Time

67.0 commercial · priority 2

Estimated Time has raw score signals, but the commercial-quality gate still treats it as weak evidence rather than a research-ready workflow.

Next action: Inspect source evidence or gather outside proof before spending AI critique on this label.

Research lane: Visual, builder, layout, or update-safety signals · medium confidence

Research family hint: agency visual QA and update safety · site builders and agencies

Review first with: agencies maintaining client page-builder sites · secondary: site builders, client-site operators

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Missing specific buyer.
  • Missing paid adjacent proof.
Evidence brief

Research lane: Visual, builder, layout, or update-safety signals · medium confidence

  • Matched block in saved report, paid-signal, or evidence text.

Lane question: Check whether the evidence is really about visual QA, layout regressions, editor handoff, or client-safe updates.

Research family hint: agency visual QA and update safety · preventing client-site regressions before updates or edits go live

Candidate buyer segment: agencies maintaining client page-builder sites

Closest non-promotional family for the Visual, builder, layout, or update-safety signals lane based on block.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 24 complaint(s), 2 high-severity signal(s), 1 weak-competitor signal(s), 51 analyzed conversation(s)

Paid signals: 0 paid-signal plugin(s); no paid terms yet

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Estimated Time describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Evidence watchlist

Space Saver

64.0 commercial · priority 2

Space Saver has raw score signals, but the commercial-quality gate still treats it as weak evidence rather than a research-ready workflow.

Next action: Inspect source evidence or gather outside proof before spending AI critique on this label.

Research lane: Unclassified generic label · low confidence

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Missing specific buyer.
  • Missing paid adjacent proof.
Evidence brief

Research lane: Unclassified generic label · low confidence

  • No repeated paid-workflow lane terms were visible in the saved report signals.

Lane question: Does Space Saver hide a specific paid workflow in the source evidence, or should it remain generic?

Promotion guardrail: Keep this row below promoted opportunities until a specific workflow and paid proof are visible.

Evidence: 2 complaint(s), 4 high-severity signal(s), 1 weak-competitor signal(s), 63 analyzed conversation(s)

Paid signals: 0 paid-signal plugin(s); no paid terms yet

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Space Saver describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Bot

78.0 commercial · priority 3

Bot is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Checkout, payment, or order workflow signals · medium confidence

Research family hint: checkout and revenue assurance · store owners and WooCommerce agencies

Review first with: WooCommerce store owners · secondary: WooCommerce agencies, store owners

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Bot is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Checkout, payment, or order workflow signals · medium confidence

  • Matched checkout, order in saved report, paid-signal, or evidence text.

Lane question: Check whether the source evidence is really about protecting revenue, payment completion, fulfillment, or order operations.

Research family hint: checkout and revenue assurance · protecting checkout revenue and order operations

Candidate buyer segment: WooCommerce store owners

Closest non-promotional family for the Checkout, payment, or order workflow signals lane based on checkout, order.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 116 complaint(s), 163 high-severity signal(s), 62 weak-competitor signal(s), 517 analyzed conversation(s)

Paid signals: 22 paid-signal plugin(s); terms: analytics, lead, order, integration

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Bot describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Aeo

66.0 commercial · priority 3

Aeo is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Mixed commercial signals · medium confidence

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Aeo is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Mixed commercial signals · medium confidence

  • Signals are split across Analytics, reporting, or attribution signals, Automation, integration, or data handoff signals, Lead capture or conversion workflow signals.

Lane question: Inspect source evidence before choosing one buyer workflow; broad paid terms may come from unrelated plugins.

Promotion guardrail: Treat this as a research triage lane, not a promoted opportunity family.

Evidence: 16 complaint(s), 10 high-severity signal(s), 2 weak-competitor signal(s), 119 analyzed conversation(s)

Paid signals: 4 paid-signal plugin(s); terms: analytics, lead, integration

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Aeo describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Surecart

66.0 commercial · priority 3

Surecart is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Checkout, payment, or order workflow signals · high confidence

Research family hint: checkout and revenue assurance · store owners and WooCommerce agencies

Review first with: WooCommerce store owners · secondary: WooCommerce agencies, store owners

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Surecart is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Checkout, payment, or order workflow signals · high confidence

  • Matched checkout, order, payment, shipping in saved report, paid-signal, or evidence text.

Lane question: Check whether the source evidence is really about protecting revenue, payment completion, fulfillment, or order operations.

Research family hint: checkout and revenue assurance · protecting checkout revenue and order operations

Candidate buyer segment: WooCommerce store owners

Closest non-promotional family for the Checkout, payment, or order workflow signals lane based on checkout, order, payment, shipping.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 2 complaint(s), 1 high-severity signal(s), 0 weak-competitor signal(s), 51 analyzed conversation(s)

Paid signals: 6 paid-signal plugin(s); terms: automation, order, email marketing, checkout

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Surecart describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Pdfjs

66.0 commercial · priority 3

Pdfjs is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Unclassified generic label · low confidence

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Pdfjs is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Unclassified generic label · low confidence

  • No repeated paid-workflow lane terms were visible in the saved report signals.

Lane question: Does Pdfjs hide a specific paid workflow in the source evidence, or should it remain generic?

Promotion guardrail: Keep this row below promoted opportunities until a specific workflow and paid proof are visible.

Evidence: 24 complaint(s), 9 high-severity signal(s), 2 weak-competitor signal(s), 75 analyzed conversation(s)

Paid signals: 0 paid-signal plugin(s); no paid terms yet

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Pdfjs describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Gemini

64.0 commercial · priority 3

Gemini is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Content, media, or publishing workflow signals · medium confidence

Research family hint: media publishing and video operations · publishers, creators, agencies, and media-heavy site owners

Review first with: publishers · secondary: creators, agencies

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Gemini is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Content, media, or publishing workflow signals · medium confidence

  • Matched content, image in saved report, paid-signal, or evidence text.

Lane question: Check whether the evidence points to publishing throughput, media delivery, branded content, or asset operations.

Research family hint: media publishing and video operations · keeping media embeds, galleries, watermarks, and video experiences reliable

Candidate buyer segment: publishers

Closest non-promotional family for the Content, media, or publishing workflow signals lane based on content, image.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 21 complaint(s), 12 high-severity signal(s), 5 weak-competitor signal(s), 104 analyzed conversation(s)

Paid signals: 14 paid-signal plugin(s); terms: automation, pro, lead, client

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Gemini describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Experiments

60.0 commercial · priority 3

Experiments is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Mixed commercial signals · medium confidence

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Experiments is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Mixed commercial signals · medium confidence

  • Signals are split across Analytics, reporting, or attribution signals, Automation, integration, or data handoff signals, Checkout, payment, or order workflow signals.

Lane question: Inspect source evidence before choosing one buyer workflow; broad paid terms may come from unrelated plugins.

Promotion guardrail: Treat this as a research triage lane, not a promoted opportunity family.

Evidence: 5 complaint(s), 2 high-severity signal(s), 4 weak-competitor signal(s), 25 analyzed conversation(s)

Paid signals: 3 paid-signal plugin(s); terms: analytics, automation

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Experiments describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Abilities

60.0 commercial · priority 3

Abilities is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Mixed commercial signals · medium confidence

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Abilities is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Mixed commercial signals · medium confidence

  • Signals are split across Automation, integration, or data handoff signals, Checkout, payment, or order workflow signals, Performance, hosting, or reliability signals.

Lane question: Inspect source evidence before choosing one buyer workflow; broad paid terms may come from unrelated plugins.

Promotion guardrail: Treat this as a research triage lane, not a promoted opportunity family.

Evidence: 2 complaint(s), 1 high-severity signal(s), 0 weak-competitor signal(s), 21 analyzed conversation(s)

Paid signals: 4 paid-signal plugin(s); terms: automation, client

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Abilities describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Manifest

60.0 commercial · priority 3

Manifest is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Unclassified generic label · low confidence

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Manifest is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Unclassified generic label · low confidence

  • No repeated paid-workflow lane terms were visible in the saved report signals.

Lane question: Does Manifest hide a specific paid workflow in the source evidence, or should it remain generic?

Promotion guardrail: Keep this row below promoted opportunities until a specific workflow and paid proof are visible.

Evidence: 16 complaint(s), 6 high-severity signal(s), 2 weak-competitor signal(s), 87 analyzed conversation(s)

Paid signals: 0 paid-signal plugin(s); no paid terms yet

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Manifest describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Publishing

54.0 commercial · priority 3

Publishing is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Mixed commercial signals · medium confidence

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Publishing is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Mixed commercial signals · medium confidence

  • Signals are split across Automation, integration, or data handoff signals, Content, media, or publishing workflow signals, Developer, database, or technical operations signals.

Lane question: Inspect source evidence before choosing one buyer workflow; broad paid terms may come from unrelated plugins.

Promotion guardrail: Treat this as a research triage lane, not a promoted opportunity family.

Evidence: 152 complaint(s), 36 high-severity signal(s), 34 weak-competitor signal(s), 419 analyzed conversation(s)

Paid signals: 39 paid-signal plugin(s); terms: automation, integration, analytics, lead

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Publishing describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Ux

54.0 commercial · priority 3

Ux is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Checkout, payment, or order workflow signals · high confidence

Research family hint: checkout and revenue assurance · store owners and WooCommerce agencies

Review first with: WooCommerce store owners · secondary: WooCommerce agencies, store owners

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Ux is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Checkout, payment, or order workflow signals · high confidence

  • Matched checkout, order, woocommerce in saved report, paid-signal, or evidence text.

Lane question: Check whether the source evidence is really about protecting revenue, payment completion, fulfillment, or order operations.

Research family hint: checkout and revenue assurance · protecting checkout revenue and order operations

Candidate buyer segment: WooCommerce store owners

Closest non-promotional family for the Checkout, payment, or order workflow signals lane based on checkout, order, woocommerce.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 81 complaint(s), 19 high-severity signal(s), 20 weak-competitor signal(s), 273 analyzed conversation(s)

Paid signals: 8 paid-signal plugin(s); terms: analytics, conversion, checkout, lead

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Ux describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Geo

54.0 commercial · priority 3

Geo is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Automation, integration, or data handoff signals · medium confidence

Research family hint: automation and reporting layer · agencies, operators, and marketing teams

Review first with: agencies accountable for client reporting · secondary: marketing operators, analytics teams

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Geo is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Automation, integration, or data handoff signals · medium confidence

  • Matched automation, integration in saved report, paid-signal, or evidence text.

Lane question: Check whether the evidence is about paid operational handoffs that fail between WordPress and another system.

Research family hint: automation and reporting layer · protecting analytics tracking, client reporting, and automation handoffs

Candidate buyer segment: agencies accountable for client reporting

Closest non-promotional family for the Automation, integration, or data handoff signals lane based on automation, integration.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 267 complaint(s), 42 high-severity signal(s), 51 weak-competitor signal(s), 651 analyzed conversation(s)

Paid signals: 9 paid-signal plugin(s); terms: analytics, automation, premium, integration

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Geo describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Anthropic

54.0 commercial · priority 3

Anthropic is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Mixed commercial signals · medium confidence

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Anthropic is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Mixed commercial signals · medium confidence

  • Signals are split across Automation, integration, or data handoff signals, Booking, event, membership, or learning workflow signals, Content, media, or publishing workflow signals.

Lane question: Inspect source evidence before choosing one buyer workflow; broad paid terms may come from unrelated plugins.

Promotion guardrail: Treat this as a research triage lane, not a promoted opportunity family.

Evidence: 11 complaint(s), 1 high-severity signal(s), 2 weak-competitor signal(s), 27 analyzed conversation(s)

Paid signals: 4 paid-signal plugin(s); terms: client, subscription, premium, automation

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Anthropic describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Payfast

54.0 commercial · priority 3

Payfast is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Checkout, payment, or order workflow signals · high confidence

Research family hint: checkout and revenue assurance · store owners and WooCommerce agencies

Review first with: WooCommerce store owners · secondary: WooCommerce agencies, store owners

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Payfast is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Checkout, payment, or order workflow signals · high confidence

  • Matched order, payment, woocommerce in saved report, paid-signal, or evidence text.

Lane question: Check whether the source evidence is really about protecting revenue, payment completion, fulfillment, or order operations.

Research family hint: checkout and revenue assurance · protecting checkout revenue and order operations

Candidate buyer segment: WooCommerce store owners

Closest non-promotional family for the Checkout, payment, or order workflow signals lane based on order, payment, woocommerce.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 6 complaint(s), 35 high-severity signal(s), 2 weak-competitor signal(s), 41 analyzed conversation(s)

Paid signals: 3 paid-signal plugin(s); terms: payment, integration, subscription

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Payfast describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Generic category risk

Reactions

54.0 commercial · priority 3

Reactions is still a broad market label, not a specific buyer workflow.

Next action: Do not spend AI critique or promote this label as-is; combine it with source evidence or map it to a specific paid workflow first.

Research lane: Developer, database, or technical operations signals · high confidence

Research family hint: developer change safety and site customization · developers, agencies, and technical site owners

Review first with: developers · secondary: agencies, technical site owners

Why blocked:

  • External proof gate is not strong enough for promotion.
  • Reactions is still a generic category, not a specific paid workflow.
  • Missing specific buyer.
Evidence brief

Research lane: Developer, database, or technical operations signals · high confidence

  • Matched log, debug, php, error in saved report, paid-signal, or evidence text.

Lane question: Check whether the evidence points to paid developer operations, diagnostics, migration, or change-safety workflows.

Research family hint: developer change safety and site customization · shipping custom code and site changes without breaking production

Candidate buyer segment: developers

Closest non-promotional family for the Developer, database, or technical operations signals lane based on log, debug, php, error.

Promotion guardrail: This is only a research lane. Do not promote it until source snippets and outside proof confirm buyer, painful workflow, competitor gap, wedge, and revenue logic.

Evidence: 91 complaint(s), 25 high-severity signal(s), 12 weak-competitor signal(s), 304 analyzed conversation(s)

Paid signals: 1 paid-signal plugin(s); terms: premium

Missing outside proof: SEO demand, SERP competitors, Adjacent substitutes, PublicWWW adoption

Research question: Does Reactions describe a repeatable paid buyer workflow, or is it only a noisy WordPress tag?

Review Queue Navigation

20 shown