About SaaS Fieldwork
I started SaaS Fieldwork with a simple observation: builders spend months creating solutions for problems that don't really exist, while professionals suffer daily with workflows held together by spreadsheets and duct tape.
There's a disconnect. And it's costing everyone.
What We Do
Every week, I conduct fieldwork in professional communities—specialized subreddits, industry forums, niche Slack groups. I'm looking for one thing: real problems that real professionals complain about repeatedly.
Not theoretical pain points. Not market sizing exercises. Actual people describing actual friction in their daily work.
I analyze these problems through two lenses:
First, understanding (Thursday's free Problem Deep Dive): Who feels this pain? Why does it exist? What bandaid solutions are people using?
Second, opportunity (Tuesday's paid Builder Brief): What would a solution look like? Who's already trying? What's the path to building something better?
Why This Matters
The failure rate for new SaaS products is brutal. Most die not because they're poorly built, but because they solve the wrong problem—or no problem at all.
Meanwhile, millions of professionals wrestle with broken workflows every single day, assuming "that's just how it is."
SaaS Fieldwork bridges this gap. Real problems, properly researched, ready for builders who want to create something people actually need.
Who This Is For
Builders ready to start their next project
Founders who want evidence before they code
Investors scouting for overlooked spaces
About Me
I'm Chris, a product manager who got tired of watching talented builders waste months on problems nobody has. I started doing this research for myself and realized others needed it too.
Questions? Ideas? Industries you want me to explore? Reply to any email—I read everything.
Ready to find your next opportunity?
