Imagining the Challenge of Product Deprecation After Acquisition
Picture this: your newly expanded fintech company just acquired a competitor specializing in small business lending. Both teams brought their own loan origination platforms, customer portals, and underwriting algorithms to the table. Now, you’re tasked with deciding which products stay, which merge, and which get phased out—without disrupting cash flow or customer trust.
This scenario is common in fintech M&A, especially with lenders serving small businesses of 11-50 employees, where agility and clear communication are crucial. We spoke with Priya Desai, a product strategist who has guided several post-acquisition consolidations in business lending fintech. Priya shares practical tactics creative directors can adopt to smooth product deprecation after acquisition.
What’s the first step creative directors should take when approaching product deprecation post-M&A?
Priya: Imagine the product landscape as overlapping circles from both companies. The first move is a thorough product audit focused on customer impact and tech overlap. This means mapping which features serve the same need, which customer segments rely on them, and how they differ technically.
For instance, when one company’s loan origination system had a 25% faster approval time but lacked the other’s customer communication suite, the combined team could identify a priority on building a hybrid solution rather than simply shutting one down.
Digging into usage metrics matters here. A 2023 Deloitte report highlighted that 62% of fintech product deprecation failures stem from ignoring actual user behavior in strategic decisions. Mid-level creative directors should dive into analytics platforms and customer journey maps to understand what truly drives retention and growth.
How do you align deprecation strategies with both companies’ cultures and customer expectations?
Priya: Culture often shapes product design and customer messaging, which can complicate consolidation. Picture two teams - one highly data-driven with a “test and iterate” mindset, the other more relationship-focused with manual underwriting nuances.
To align these, creative directors should foster joint workshops early on, bringing product, UX, and customer success teams together. This helps harmonize the voice and tone across platforms and sets a common baseline for how the deprecation will be communicated.
A fintech lender I worked with used Zigpoll to gather real-time feedback from small business borrowers during a soft sunset phase of their legacy product. The direct voice of the customer helped ease cultural tensions by validating that certain legacy features still mattered, guiding a more empathetic transition.
What are the practical communication tactics for users during product phaseout?
Priya: Imagine telling a customer that their trusted loan portal will retire in six months. Abrupt or unclear messaging risks attrition.
I recommend a multi-channel, phased approach:
- Advance notice via email and in-app messages at least 90 days out.
- Dedicated microsite or FAQ section explaining why the product is deprecated, alternative solutions, and support resources.
- Interactive feedback tools like Zigpoll or Hotjar to collect concerns and questions.
- Regular updates and reminders as retirement dates approach.
- Personalized outreach from account managers for SMEs in the 11-50 employee range who may have more complex needs.
One client’s approach went from a 2% churn rate during deprecation communication to 11% by layering in personalized webinars and direct outreach, showing that investment in communication pays off.
How do tech stack considerations shape product deprecation decisions and timelines?
Priya: Tech debt is the elephant in post-acquisition rooms. From a creative direction perspective, understanding infrastructure constraints is key to realistic timelines.
If legacy product A relies on monolithic architecture and product B is microservices-based, migrating users or integrating features can take quarters, not weeks. Creative teams need to coordinate closely with engineering leads to map dependencies and define milestones.
A fintech company I advised initially underestimated the effort moving loan dashboard features from the acquired platform to their main stack, pushing product sunset by six months. This delay highlighted the need to embed engineering reviews in early strategy phases.
Are there specific metrics creative directors should track during deprecation to ensure success?
Priya: Yes, beyond standard KPIs, I focus on these:
| Metric | Why It Matters | Typical Target Range (SMBs) |
|---|---|---|
| User engagement on legacy platform | Signals readiness to migrate or need for support | Decline to below 20% monthly active users |
| Support ticket volume | Measures confusion or friction | Spike early, then should normalize |
| Conversion rates on new product | Confirms adoption and satisfaction | Aim for >15% improvement post-migration |
| NPS (Net Promoter Score) | Tracks sentiment through transition | Maintain or improve baseline of 35+ |
Tools like Amplitude for engagement and Zigpoll for sentiment work well in tandem. A 2024 Forrester study found that fintech companies monitoring behavior and feedback simultaneously reduced churn by 7% during product sunsetting.
How do you balance speed vs. thoroughness in deprecation post-acquisition?
Priya: This is tricky. Speed is critical to capture acquisition synergies and reduce duplicated costs, but rushing without thorough user and tech analysis can backfire.
For small business lending, where borrowers rely heavily on trusted systems, a phased approach works best—slow enough to catch issues, fast enough to consolidate costs within a fiscal year.
One team I collaborated with initially planned a rapid 3-month sunset but extended it to 9 months after discovering critical manual underwriting features in legacy software. The later timeline reduced churn by helping customers adapt gradually.
What limitations should creative directors keep in mind when applying these strategies?
Priya: Not every scenario fits these tactics. For example:
- If the acquired product supports a niche business type or region, retiring it prematurely can alienate those segments.
- Regulatory constraints in lending (e.g., fair lending laws) might require maintaining certain features or data access.
- Cultural resistance within teams can stall communication plans.
These factors highlight why ongoing stakeholder engagement—from compliance to frontline sales—should be core to deprecation planning.
Final advice for mid-level creative directors tasked with product deprecation post-M&A?
Priya: Always center the small business borrower’s experience while balancing internal realities. Start with data-driven audits, align cross-functional teams culturally, and communicate transparently with customers using multiple channels.
Remember, product deprecation isn’t just turning something off—it’s about thoughtfully guiding customers through change with empathy and clarity. For mid-level creative directors, being the bridge between tech, culture, and customer needs will make the difference.
Before you finalize plans, run quick pulse surveys using tools like Zigpoll or Typeform to test messaging and uncover hidden concerns. These insights often reveal nuances that dashboards alone miss.
Lastly, don’t underestimate the power of storytelling in your messaging. Small business owners aren’t just numbers; they’re navigating their own growth journeys. Frame deprecation as part of that journey, not as an obstacle.
This practical lens on post-acquisition product deprecation will serve you well — your borrowers and internal teams will thank you for it.