Narrow ICP or workflow — Narrow NightOwl Notes from general note-taking to a single ICP: solo indie hackers who journal build logs.
Evidence — for
23 of the last 5 paying users specifically mentioned using it to log daily build progress, unprompted.
https://example.com/evidence/support-thread-1Two customer calls this week said they'd pay more for a public build-log template.
https://example.com/evidence/interview-notes
Evidence — against
1Exit survey shows 4 churned users wanted general-purpose notes, not a build-log-specific tool.
https://example.com/evidence/churn-survey
Mixed / unclear signal
1A support thread requests both broader and narrower templates in the same conversation — mixed signal.
https://example.com/evidence/support-thread-2
Confidence — High
- Both sides are represented: 2 supporting and 1 opposing item(s).
- 4 evidence item(s) were reviewed, giving more than a single data point.
- Live usage or revenue data is present, grounding this in real traction rather than intent alone.
Unknowns
- 1 item(s) were marked mixed or unclear and were not counted for either side.
- This brief only reflects what you entered — Soloop does not fetch, crawl, or independently verify the linked pages.
7-day test
For 7 days, route new signups or outreach through X / Twitter into the single ICP or workflow you're testing, and measure conversion only within that segment.
Continue / watch / stop thresholds
6+ distinct users take the test action within 7 days (~15% of your 42 current users). Continue as planned.
Between 2 and 5 users take the test action. Extend the test one more week before deciding.
Fewer than 2 user(s) take the test action, or you see explicit negative signal (churn, refund request, or direct "not for me" feedback). Stop or pivot rather than keep building.