Why users bail before they ever hit 'contact support'?
For every customer who complains, 25 others just uninstall. I walk through products so you can see where they're bleeding users - and highlight fixes before you burn another dollar on ads.
About me: Hey, welcome! If we haven’t met before, here’s a few words about me.
I’m Daria Littlefield, CEO & Founder of Silicon Valley Support. For the past decade, I was Head of Customer Care for a $400M ARR portfolio spanning 35+ dating and social apps.
I’ve partnered with founders to use support as a signal channel - iterating on products to nail product-market fit and build apps that actually stick.
When I’m not doing that → I’m probably on a plane to a new country, diving in Bali, riding my motorbike or geeking out over artisanal mezcal. I’m working on my Spanish, devouring books, learning to code, playing drums or having philosophical debates with my husband, William Littlefield.
Like you, I use dozens of apps daily. Some get installed for short-term needs and quickly deleted. Others stick around, building habits and serving long-term goals.
There’re also different apps in different continents and countries, and because I’m moving around so much I have to use so many - just to get things done: order food, get a taxi, get mobile data, meet new people, book experiences.
Over time, I’ve maxed out my iPhone storage with screenshots: broken flows, clever UI decisions, genius onboarding moments, catastrophic churn points. My Notes app is bursting with observations about what makes products stick and what dooms them to deletion.
In the past year at Silicon Valley Support I’ve spent hundred hours testing dozens consumer apps and SaaS platforms of my clients who build for US, European and Southeast Asian markets: going through customer journey and giving feedback on what to improve before public launch. Silicon Valley Support was built with intention to deliver support function as a product-growth driver.
By doing it long enough here’s what I couldn’t ignore:
For every 2 customers who reach support and describe their problem, you’ve already lost 200 who hit the same friction point and churned silently.
Even more striking:
I’ve sat through countless calls with founders saying:
“We don’t really know why people aren’t sticking”
“We drove thousands in traffic, but only 20% complete registration and 5% stay active”
“Support tickets are just deletion requests with no explanation - should we do more customer research?”
Here’s the brutal truth: If something feels off, looks uncool, or seems too expensive, users won’t write to support about it. They’ll just leave. You’ll never hear why. Unless they’re already daily active users and something breaks, they’re gone without a trace - and your marketing budget is pouring into a leaking bucket.
The solution? Put on your customer’s shoes and walk their journey. But to extract real insights, you need pattern recognition - you need to know what good and bad looks like across hundreds of products.
More often than not, even the best engineers need a fresh perspective from someone who’s been exposed to thousands of products to really see what they’re missing. When you’re deep in the build, you lose the beginner’s eye. You know how it’s supposed to work, so you can’t see where it actually breaks.
You don’t have time for that. But I do, and I’m already doing it.
In every ‘Do Not Churn’ issue, I’ll break down real product walkthroughs, dissect what’s working (and what’s bleeding users), and give you specific tactics you can steal.
Consider this your churn prevention playbook, delivered straight to your inbox.
Sounds good?
