PAIN TRIGGERS
Builders look for problems to fit an already chosen solution rather than identifying the problem first.
Asking technical communities for feedback on non-technical consumer domains like divination is ineffective.
SaaS· side project creatorsPain 6.00/10WTP 5.0/10Market 4.0/10Validation 6.0Confidence 85%Aug 30, 2026
DivinationFeedback: Niche User Research & Churn Audit for Esoteric Apps
Developers build and iterate on divination apps without valid domain feedback, relying on programmer forums rather than target users, which leads to unresolved user annoyances and high subscription churn.
analyticsmarket-researchmobile-appproduct-managementsaassolo-founders
1
STAGE 01 · PROBLEM
Is the problem real?
CANONICAL PROBLEM
Developers build divination apps without first validating target user preferences, and ask programmers instead of domain users for advice.
FREQUENCY
Limited repetition signal.
INTENSITY
Users explicitly describe existing tools as bloated/overkill and mention workaround behavior.
EVIDENCE
What makes you stop using a divination app?
SideProject7
Why would you ask a bunch of programmers and not divination people
commentWhy would you ask a bunch of programmers and not divination people
2
STAGE 02 · CUSTOMER
Who feels this pain?
TARGET USERS
side project creatorsIndie App Creators
Solo developers and small teams building consumer wellness and esoteric apps who lack direct access to domain-specific user feedback.
Context
Identify user pain points, subscription cancellation reasons, and frustrations with existing divination, tarot, astrology, and horoscope apps.
Polling general developer subreddits to gather feedback for specialized consumer niche applications.
Current Workarounds
polling general technical subreddits for non-technical consumer app feedback
guessing user preferences without validating subscription cancellation reasons
3
STAGE 03 · MARKET
Where's the gap?
EXISTING SOLUTION GAPS
Existing divination apps have unresolved user annoyances that lead to app deletion or subscription cancellation.
Developer-focused communities lack domain-specific feedback for niche consumer apps like divination.
OPPORTUNITY & VALUE
Why Now
Builders acknowledge the flaw in asking technical communities for non-technical consumer insights, highlighting a gap in domain-specific feedback.
Value Proposition
Purpose-built specifically for the esoteric and divination app market rather than generic developer feedback tools
Product Direction
A niche user research platform and feedback aggregation service that connects esoteric app developers directly with active tarot, astrology, and horoscope users to identify cancellation reasons and usability friction points.
4
STAGE 04 · BUSINESS
How does it make money?
MONETIZATION
$49/moUp to 3 active research projects
Model
SaaS subscription
WILLINGNESS TO PAY
Developers waste hundreds of hours building apps that get deleted; $49/mo is a minor fraction of potential lost subscription revenue and wasted dev time.
5
STAGE 05 · EXECUTION
How do you ship it?
MVP PLAN
“Uncover why divination app users churn in 6 weeks.”
A niche user research platform and feedback aggregation service that connects esoteric app developers directly with active tarot, astrology, and horoscope users to identify cancellation reasons and usability friction points.
Core Features
Targeted panel matching for tarot and astrology app users
Automated exit-survey and churn-reason analysis templates
Weekly Roadmap
1
W1-W2
Core survey builder and niche respondent recruitment flow created.
- •Build churn-reason and feature-preference survey templates
- •Set up landing page to capture interested indie developers
- •Recruit initial beta panel of esoteric app users
2
W3-W4
Feedback dashboard and matching pipeline functional.
- •Build developer dashboard for viewing aggregated feedback
- •Implement automated matching between makers and niche users
- •Add export functionality for research insights
3
W5
Billing integration and private beta testing with 5 developers.
- •Integrate Stripe subscription billing
- •Onboard 5 indie divination app creators for private beta
- •Refine survey templates based on beta feedback
4
W6
Public launch and first customer acquisition.
- •Launch on IndieHackers and maker communities
- •Publish case study from a beta creator
- •Monitor user conversion and retention metrics
Launch Strategy
Reach indie makers directly on communities like IndieHackers, X, and targeted maker Discords where developers build side projects.
RISKS & ASSUMPTIONS
Top Risks
Sourcing niche divination users
Recruiting a reliable, engaged panel of tarot and astrology users for developer feedback is challenging.
Hobbyist budget constraints
Side project creators often have zero software budget and prefer free, informal community advice.
Low initial signal volume
Early-stage app creators may not generate enough traffic or churn data to make the insights actionable.
6
STAGE 06 · DECISION
Should you build it?
NEED A CLEARER CALL?
Run an Investment Memo to get a structured Go / No-Go verdict, competitor landscape, unit economics, and a 90-day validation roadmap for this opportunity.
Generate an investment memoWhat this score means
This idea scores in the upper-middle range of opportunities surfaced by MonetScope, with a validation sub-score of 6/10 against 2 independently sourced evidence signals. A "promising" rating usually indicates a real pain has been detected and discussed in the open, but the pipeline did not find enough signal to flag it as urgent or high-frequency. These opportunities can still produce excellent businesses — they often correspond to "boring" problems that established players have ignored — but the founder should expect a longer customer-development cycle to confirm willingness to pay.
Why this matters for SaaS founders
It sits at the intersection of "analytics", "market-research", "mobile-app", which makes it relevant to a specific subset of founders rather than a generic horizontal opportunity. SaaS opportunities at this stage tend to win on the strength of their initial wedge — a single workflow that the target user runs every week, where the existing solution is either spreadsheets, a clunky incumbent feature, or a manual process they hate. The build cost is moderate; the distribution cost is everything. The MonetScope pipeline surfaces this category alongside other saas signals, which is why it appears here rather than in a generic "trending ideas" feed.
Scores are derived from real forum discussions across Reddit, Hacker News and X, weighted by evidence volume and signal quality. How scoring works
Frequently asked questions
Is "DivinationFeedback: Niche User Research & Churn Audit for Esoteric Apps" a real validated startup idea or just an AI-generated suggestion?
MonetScope does not generate ideas from a language model's imagination. Every opportunity on this site is anchored to specific source posts and comments from real public discussions — typically on Reddit, Hacker News, or X — where actual users describe the pain in their own words. The AI's role is structuring, scoring, and grouping those signals into a navigable opportunity, not inventing the problem.
How recent is the underlying data for analytics?
MonetScope's spider pipeline runs continuously and surfaces opportunities as new evidence accumulates. The "Updated" date in the header reflects the most recent re-scoring of this specific opportunity. Most saas opportunities visible in the public catalog draw from discussions in the last 30-60 days; older signals are de-prioritized because user pain shifts faster than most founders assume.
What's the difference between "overall score" and "validation score"?
Overall score is a composite across six dimensions — pain, urgency, willingness to pay, market size, defensibility, and execution ease — designed to give a single number for triage. Validation score is narrower: it asks "how cleanly does the same signal repeat across independent sources?" An opportunity can score high on overall but lower on validation when one or two large discussions dominate the evidence; conversely, validation can be high on a smaller-overall idea where the signal is consistent but the addressable market is modest.