SignalForge — Real Run: "independent coffee shops"

Command:

python main.py --cli --niche "independent coffee shops"

Output (verbatim, from the bundled sample dataset):

SignalForge - analyzing niche: 'independent coffee shops'
============================================================
Signals scanned:            20
Flagged as problem signals: 8
Problem clusters found:     2

#1  [75.5/100]  milk, menu, improvise, milk delivery, delayed improvise
     6 signals - avg sentiment -0.30 - 3 distinct source(s)
     e.g. "Milk delivery got delayed again this week, had to improvise the whole menu."

#2  [21.7/100]  pos, apps, receipts pos, spent, sunday
     2 signals - avg sentiment +0.10 - 1 distinct source(s)
     e.g. "I swear I have four different apps open just to run this shop - POS, online orders, loyalty, and my spreadsheet. It's exhausting."

============================================================
BLUEPRINT for top-ranked cluster: milk, menu, improvise, milk delivery, delayed improvise

Problem statement:
  People connected to "independent coffee shops" keep describing friction around: milk, menu, improvise, milk delivery. It reads as consistently negative in tone (average sentiment -0.30 on a -1 to +1 scale) across 6 separate signals.

Persona:
  Someone active in "independent coffee shops" who has recently expressed this kind of frustration in public - on 3 distinct sources in this scan.

Solution concept:
  Based on the language used, a narrowly-scoped tool or service that addresses this specific friction point directly.

MVP scope:
  - A single, obvious fix for the 'milk' friction point - resist adding more.
  - A way to import the data this workflow already produces, instead of asking for new manual entry.
  - One clear before/after metric a user can see within their first week of use.

Business model:
  If this pattern holds across a larger sample, price it against the cost of the friction itself (time lost, money wasted, or deals lost) rather than against generic 'software' pricing - anchor the price to what the pain is already costing.

Go-to-market:
  This pain surfaced on: cafe owners forum (sample), r/KitchenConfidential (sample), r/smallbusiness (sample). Start distribution there rather than on a generic channel - that's where this exact audience already gathers and already uses this language.

Competitive snapshot:
  This tool doesn't do live competitor discovery. Before building, manually search for existing tools using the terms "milk, menu, improvise, milk delivery" plus your niche name, and note specifically why they fall short for this audience.

Tech feasibility:
  Not automatically assessed - this pipeline only scores how strong and consistent the complaint is, not how hard it is to solve. Treat a high opportunity score as 'worth investigating,' not 'easy to build.'

Validation plan:
  Before building anything: find 8-10 people who sound like the signals below, ask them one question - "walk me through the last time this happened" - and see if their unprompted answer matches this cluster's keywords. If it doesn't, the cluster is too broad or mislabeled.

Risk / feasibility: High signal. This is showing up often and strongly - validate fast.

Also verified against freelance graphic designers, solo personal trainers, and indie mobile game developers from the bundled sample set — each produces distinct, coherent clusters, not the same output reworded.