Three hypotheses. Their evidence. Their weak points.

1. WooCommerce pickup workflow configuration and maintenance

Potential buyer: merchants offering local pickup, and agencies maintaining their stores.

Problem: pickup needs a distinct order state and dependable customer notifications. Failures in bulk actions or notification rules can create manual store work.

Observed evidence

• WooCommerce feature request asks for a pickup-ready state and customer email.
• Merchant support report describes pickup selection and bulk-status problems. The thread is marked resolved and is historical; it does not establish an unresolved current gap.
• Notification customization request asks for payment-method-specific email behavior. This is a separate historical support thread.

Possible offer

A configuration and regression-check service for pickup status, email rules and bulk actions, with integration into existing plugins. This is a hypothesis, not a demonstrated unmet product category.

Competition and counterevidence

Advanced Local Pickup already serves this workflow. Existing plugins, agency work and future core improvements may satisfy the need. A request for a core feature can indicate a preference for a free solution.

Evaluation

Evidence supports a workflow problem across several reports; confidence in a new profitable service is low. Support-ticket count is not buyer count. Cost, recurrence and current resolution status need interviews. No trend score is assigned from this small, unevenly dated sample.

Next validation

Ask five pickup merchants to demonstrate their current workflow. Measure manual touches and support incidents, then offer a paid configuration pilot only where a current problem is confirmed. An interview is not a sale.

2. Accessibility regression checks for WooCommerce storefronts

Potential buyer: agencies maintaining stores with grouped products and customized templates.

Problem: an input can display a product-specific label while presenting a generic accessible name to assistive technology.

Observed evidence

A WooCommerce issue reports that quantity fields in grouped products share a generic accessible name. It contains reproduction steps, but is one issue in one repository; it does not establish broad agency demand.

Possible offer

Repeatable checks for cart and product-page interactions before and after theme or plugin updates, with reproducible findings and remediation verification.

Competition and counterevidence

Core fixes, existing accessibility scanners and agencies' own test suites can remove the need. Automated scanning alone cannot establish full accessibility. This note makes no compliance claim.

Evaluation

Confidence in a recurring technical risk is moderate; confidence in a distinct paying market is low. There is no evidence here for budgets, repeat incidents or customer acquisition cost. Publication criteria are not met.

Next validation

Interview five agencies about regressions they have actually encountered. Test whether they would pay for reproducible storefront checks rather than another general scan. Track a paid pilot and repeat use separately.

3. Small rooftop-garden irrigation planning

Potential buyer: gardeners and property managers with small rooftop or container gardens.

Problem: water supply, timer compatibility and installation constraints make small irrigation setups difficult to choose.

Observed evidence

• A rooftop plumbing question describes installation choices.
• A garden timer question asks about a particular power and timing setup.

Both belong to the Stack Exchange network and count as one source group, not two independent platforms. These questions are historical and cannot establish growing demand.

Possible offer

A small-site planning service that turns stated constraints into an installation checklist and compatibility questions for a qualified installer. A hardware recommendation requires a separate site-specific review.

Competition and counterevidence

Retail kits, installers and free forum advice may already solve the problem. The need may be seasonal or one-off, making a subscription inappropriate.

Evaluation

Low confidence in a viable paid niche. There are too few independent observations and no measured willingness to pay. No market-size, safety or growth claim is made.

Next validation

Ask gardeners and installers about recent failed setups and the cost of rework. Test a one-time planning offer only after confirming a current problem; do not infer subscription demand.