The numbers from Amplitude Analytics in 2025 were a gut punch: 42% of mobile product teams got hit with unexpected budget cuts of 15% or more in a single quarter. This is the new reality for mobile PM leadership in an economic crisis, and it forces a brutal question, how do you guide your team and product through this kind of financial storm without sinking?
Key Takeaways
- Shift your focus from new user acquisition to initiatives with a clear, measurable ROI, especially retention and conversion.
- Build a flexible resource model so you can shift engineering and marketing money fast based on what the real-time data is telling you.
- Keep your team’s morale and output high by being brutally honest in your communication and finding ways to invest in their skills.
- Validate every big product change with A/B tests and deep analytics. In this environment, you can’t afford to be wrong.
The Stark Reality: 42% of Mobile Teams Faced Significant Budget Cuts
The late 2025 Amplitude Analytics report confirmed what many of us were feeling: nearly half of mobile product teams saw their budgets slashed without warning. And a 15% cut isn’t just tightening your belt. It’s a direct hit to your roadmap, your hiring, and the features you have in flight. For any mobile PM, this kind of number means your priorities just got rewritten for you, forcing a brutal focus on what can deliver immediate, provable value. I’ve lived this, at a previous company, a sudden drop in ad revenue made us kill a big new social feature mid-development and throw all those engineers at our onboarding flow because the data showed us exactly where users were dropping off. Fixing that leak was a much surer path to recovering revenue than launching a speculative new feature, and making those kinds of fast, data-driven pivots is what separates the leaders who survive from those who don’t.
User Acquisition Costs Soared by 30% in Q4 2025
As if budget cuts weren’t enough, Branch Metrics reported that the average Cost Per Install (CPI) jumped by 30% in Q4 2025, throwing a wrench in old-school growth playbooks. When it costs that much more to get a new user, you have no choice but to turn your attention inward to the users you already have. Your focus has to shift to keeping them engaged and getting them to convert, which means prioritizing features that actually improve loyalty. It’s simple math: if a new user costs $5 to acquire through ads, but a feature that keeps an existing user happy costs $0.50 in developer time, the decision is made for you. This redefines growth as something sustainable and profitable, not just a bigger number on a vanity dashboard. PMs need to live in their analytics platforms, hunting for the exact points of friction in the user journey and shipping fixes, often unglamorous but powerful improvements to core features or personalization, that solve those specific problems.
Churn Rates Increased by an Average of 5% Across Subscription Apps
Then Mixpanel’s early 2026 study showed subscription app churn had ticked up by an average of 5% over the last year. A 5% jump might not sound like much, but it’s a disaster in the making. For a service with 100,000 subscribers, that’s an extra 5,000 people walking out the door every single month. That number should force every mobile PM to obsess over their retention strategies, because you have to build a product that’s impossible to leave. This means digging into user behavior to find out *why* they’re leaving. Is your value prop unclear? Is your onboarding a mess? Is a competitor simply doing it better? You have to start shipping features that get people using the app actively, like better recommendations or clearer benefits. That could mean small, detailed work like tweaking notification copy or adding a new content tier that makes long-term users feel valued. In my experience, PMs consistently undervalue the impact of making small, steady improvements to existing features, especially when you’re also listening to user feedback, as a way to stop the bleeding.
Engineering Productivity Declined by 10-15% in Teams Experiencing Layoffs
The human cost of these cuts shows up in the data. A GitLab report analyzing dev teams found that those hit by significant layoffs in 2025 saw engineering productivity, measured by things like how often they could ship and how long it took, drop by 10-15%. That’s a huge, often invisible, tax on your roadmap. As a mobile PM, you have to be the one to face this reality, which means better team management and adjusting your own expectations. You are not going to get the same results from a smaller, demoralized team, and pretending otherwise is just cruel. You have to lead with empathy, be painfully clear about the new, smaller set of priorities, and fiercely protect your team’s well-being. This is where you earn your salary by cutting scope, pushing back on deadlines, and even fighting for a pause on new work so the team can stabilize. If you ignore the productivity drop, you’ll just burn out the people you have left and watch your best talent walk out the door. You have to talk about the stress, celebrate every small win, and make sure your team knows they’re valued when everything else is uncertain.
The Conventional Wisdom is Wrong: Don’t Just “Build Faster”
In every downturn, you hear the same tired advice from pundits for product teams to just “build faster” or “do more with less.” This is terrible advice that leads to bad products. The GitLab data on productivity drops after layoffs proves you can’t just demand more from a smaller team. The real answer is to start building smarter. Building smarter is about ruthless prioritization, which is mostly about saying “no” to things, even good ideas, that aren’t the absolute most important thing you could be working on right now. It means you don’t commit a whole team to a big new feature until you’ve validated the core assumptions with a rigorous A/B testing framework against actual user behavior. Instead of trying to ship five new things, you ship one, you test it, you iterate on it based on the data, and only then do you move on. It feels slower, but it prevents wasting months of engineering time. Building smarter also means paying down technical debt, which sounds crazy when budgets are tight, but cleaning up the codebase now makes every future feature faster to build. The PM who gets this, who prioritizes real impact over just being busy, is the one who will get their team through the storm, while the one who just cracks the whip will fail. When every dollar and engineering hour is under a microscope, a mobile PM’s job changes. You become a financial strategist and a frontline leader for your team. The way you adapt, prioritize, and protect your people is what will make or break the product and the business.
How should I change my prioritization during a downturn?
Your roadmap needs to be laser-focused on things that directly affect retention, conversion, and ARPU. Every feature you prioritize must have a clear, measurable return on investment (ROI) that you can defend, pushing any long-term, speculative bets to the back burner until the situation improves.
How do I keep my team from quitting after layoffs?
Be radically transparent. Tell them what’s going on with the business and why the strategy is changing. Give them clear goals they can actually hit, celebrate every win no matter how small, and find cheap or free ways to help them learn new skills so they don’t feel like they’re stagnating.
What do I do when user acquisition costs are too high?
You stop pouring money into a leaky bucket. Your product strategy has to pivot away from top-of-funnel growth and concentrate entirely on getting more value from your existing user base through better retention, deeper engagement, and smarter monetization.
Why is data so important during a crisis?
In a crisis, data is your only defense. You need to be using your analytics to find specific user pain points and justify every decision you make about where to spend money or engineering time. It’s how you de-risk your roadmap and prove that your team’s work is actually delivering results.
Should we stop innovating during a recession?
No, but your innovation needs to be smarter and more focused. Forget about big, risky moonshots. Concentrate on small, incremental improvements that solve a proven user problem or make your core product better. Small, validated wins can have a huge impact without betting the farm.
