WPIntell

Commercial thesis review

Generic thesis backlog

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

262generic reports
6in this filter
4AI critique ready
4need product research
2evidence watchlist
16generic category risk
0kept generic
240directory/tag noise
8research lanes
5research families
1-6visible 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

Selected Family Brief

1 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.

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

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?

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

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

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

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?

Review Queue Navigation

6 shown