PAIN TRIGGERS
Killing plants by guessing incorrect sunlight levels in rooms.
Vague directional labels fail to account for real-world obstructions and variations.
SaaS· plant loversPain 7.00/10WTP 6.0/10Market 7.0/10Validation 8.0Confidence 75%May 11, 2026
SunForge: Precise Per-Window Sunlight Mapping for Homes
Generic directional labels ('north facing') fail to account for real obstructions like trees, neighboring buildings, and window specifics, leading to repeated plant deaths and poor home optimizations for plants, desks, sleep, and heat.
analyticsarhomeownersmobile-appplant-loversproductivityreal-estatesaas
1
STAGE 01 · PROBLEM
Is the problem real?
CANONICAL PROBLEM
Users cannot accurately determine real sunlight exposure per room/window due to obstructions like trees and buildings, making 'north facing' labels useless.
FREQUENCY
Multiple repeated complaints in the post and comments.
INTENSITY
Users explicitly describe existing tools as bloated/overkill and mention workaround behavior.
EVIDENCE
I built an app that maps sunlight room by room in any home using your phone's GPS and compass, Solis: Home Sun Tracker
SideProject14
I built an app that maps sunlight room by room in any home using your phone's GPS and compass, Solis: Home Sun Tracker
SideProject14
i've killed so many because i just guessed whether a spot got 'enough light.'
commentwait, 6.56% conversion in the first 2 days is actually really solid. most apps don't see numbers like that until much later, if at all. the use case that jumps out for me is plants. i've killed so many because i just guessed whether a spot got 'enough light.' is that a common use case you're hearing, or are people more into it for things like home buying or furniture placement?
2
STAGE 02 · CUSTOMER
Who feels this pain?
TARGET USERS
plant loversIndoor Plant Owners And Homeowners
Homeowners with indoor plants, home offices, or property decisions who must match specific light needs to rooms but can't reliably predict exposure.
Context
Map exact daily/seasonal sunlight hours for each room to support plants, optimize home setups (desk, furniture, sleep), and evaluate properties.
Guessing sunlight adequacy based on rough direction or observation.
Current Workarounds
Guessing based on rough compass direction like 'north facing'
Observing over multiple days and still killing plants
Using generic online charts that ignore trees and buildings
3
STAGE 03 · MARKET
Where's the gap?
EXISTING SOLUTION GAPS
Generic 'north facing' or compass directions ignore site-specific obstructions and window details.
Manual guessing of light levels leads to repeated plant death and suboptimal home setups.
OPPORTUNITY & VALUE
Why Now
Multiple users report killing multiple plants due to inaccurate light assessment; strong emphasis on obstructions making standard labels useless.
Value Proposition
Hyper-local, obstruction-aware analysis via phone camera instead of generic direction or manual guesswork; focused on consumer home use rather than professional solar design.
Product Direction
Mobile app that lets users point their phone camera at windows/rooms to generate accurate daily and seasonal sunlight hour maps using AR, AI obstruction detection, and location data.
4
STAGE 04 · BUSINESS
How does it make money?
MONETIZATION
$4.99/moUnlimited rooms and scans
Model
SaaS subscription
WILLINGNESS TO PAY
Users repeatedly report killing multiple plants and express strong frustration with guessing; they already invest time and money replacing plants and would pay a low monthly fee for prevention and better home decisions.
5
STAGE 05 · EXECUTION
How do you ship it?
MVP PLAN
“Know exactly how many sunlight hours each room gets — stop killing plants today.”
Mobile app that lets users point their phone camera at windows/rooms to generate accurate daily and seasonal sunlight hour maps using AR, AI obstruction detection, and location data.
Core Features
Camera-based window scan with AR overlay for sunlight hours
Daily and seasonal exposure report per room
Basic plant compatibility suggestions
Weekly Roadmap
1
W1-W2
Core camera scan and basic sunlight calculation engine working.
- •Build camera capture with location services
- •Implement simple sun position API integration
- •Store room scans with basic report generation
2
W3-W4
AR overlay and obstruction hints complete for single room.
- •Add ARKit/ARCore sun path visualization
- •Basic tree/building obstruction estimator
- •Generate daily hour charts
3
W5
Plant suggestions and internal testing done.
- •Add simple plant light requirement database
- •Polish UI reports and export
- •Test with 10 beta users from Reddit
4
W6
Subscription billing live and first public users.
- •Integrate Stripe for subscriptions
- •Prepare launch post with demo video
- •Track initial signups and retention
Launch Strategy
Launch in r/houseplants, r/IndoorGarden, r/homes, and real estate Facebook groups with before/after plant survival stories.
RISKS & ASSUMPTIONS
Top Risks
Scanning accuracy and user error
Phone camera AR and AI obstruction detection may not be precise enough on first try, leading to distrust if results mismatch reality.
Data model for seasonal prediction
Building accurate year-round forecasts requires good location + 3D modeling of nearby objects which is complex for MVP.
Limited repeat usage
Users may scan once after moving or setting up plants and churn, reducing subscription revenue.
Competition from free tools
Free sun path calculators exist, users may not see enough value in paid room-level precision.
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 8/10 against 3 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", "ar", "homeowners", 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 "SunForge: Precise Per-Window Sunlight Mapping for Homes" 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.