Integrating the Wealthly Acquisition: 40% Engineer Attrition at Month Nine

Using Kotter as a diagnostic.

• Urgency: created in the deal narrative, not sustained - the bank's own staff never saw the platform as existential.
• Guiding coalition: missing. The integration is run by a GM without product authority and without the founders in the decision forum.
• Vision: "platform for affluent customers" is a strategy sentence, not an operating instruction for an engineer deciding what to ship next quarter.
• Communicate and empower: actively contradicted. The 30–45 day procurement cycle on ₹5 lakh is the clearest possible signal that the bank does not trust Wealthly to spend. Nothing demotivates a product team faster than losing a ₹3 lakh cloud decision to a committee.
• Short-term wins: none visible; the first visible events are roadmap slippage and attrition.
• Consolidate and anchor: impossible yet - the culture is being overwritten, not integrated.

Using the influence model (four levers).

• Understanding: partial. Engineers know the strategy but not their role or career path.
• Motivation: broken. ESOP-to-bonus conversion is a direct cut in expected value and in wealth-creation identity.
• Capability: intact but eroding through departures; bank managers cannot coach product.
• Reinforcement: negative. Grade caps, procurement delays and dual reporting actively reward leaving.

The diagnosis. This is not a culture clash; it is a decision-rights and reward-system failure dressed as one. Three of four influence levers are pulling in the wrong direction, which no amount of town halls will fix.

Test to confirm. Exit-interview coding should show "compensation and decision autonomy," not "bank culture," as the dominant reason - if it does, the remedy is structural, not cultural.

What you concede (and why).

1. Dual compensation track. A ring-fenced platform grade band for Wealthly engineers, benchmarked to product-market pay, reviewed annually, with a defined bridge into the bank's bands at two years. Refusing this guarantees continued attrition.
2. Retention pool and re-vesting. Replace unvested ESOP value with a cash-settled retention plan over 24–36 months, weighted to the engineers you cannot replace (platform, data, security). Not all 400.
3. Founders: re-contract, don't beg. Offer a defined 24-month role with named decision rights - product roadmap authority and a seat on the integration steering committee - plus an earn-out tied to platform revenue and release cadence. Accept that one may leave; plan for a successor CTO from inside Wealthly, not from the bank.
4. Delegated authority. Raise the procurement threshold for Wealthly to ₹50 lakh with post-facto audit for cloud and tooling; ring-fence an engineering budget under the CTO.

What you refuse.

• Do not promise permanent autonomy: the platform must eventually adopt the bank's security, audit and data-localisation standards. Say so now.
• Do not protect underperformers to keep headcount; a ring-fenced band with no performance bar corrodes the team you are trying to keep.
• Do not let the founders' exit become a hostage negotiation after month 12.

Governance. One accountable executive (platform CEO or business head) with P&L and decision rights; a monthly integration forum with founders, bank product and HR; a single reporting line for engineers; quarterly culture and attrition pulse with action items owned by the accountable executive.

The judgement. Retention is bought with decision rights and predictability, not just money - engineers leaving a bank-owned startup are usually leaving the approval queue.

The substance the CEO must land.

1. Name the asymmetry honestly. Some people are paid differently for a period because the external market prices their skills differently, and because the bank bought a capability it cannot build fast enough. Pretending otherwise destroys credibility.
2. Explain the trade. The acquisition is not a reward for Wealthly; it is a bet that the affluent-customer platform creates work for the branch network, relationship managers and operations teams. If the platform fails, the bank's cost-to-serve stays high and everyone loses.
3. Set a boundary in time. Dual tracks are for a defined period with a defined bridge. Bank staff can apply into platform roles through a transparent process - and some should, visibly, in the first year.
4. Show the internal wins. Publish the platform's revenue contribution and the number of bank customers onboarded; make the benefit visible in the units people care about.
5. Hold the line on performance. No group gets permanent protection from the bank's standards on security, conduct and delivery.

Risks and how to manage them.

• Two-tier resentment: mitigate with visible internal mobility and a published bridge mechanism, not with secrecy.
• The exception becomes precedent: consultants, risk and cyber teams will ask for platform bands. Define the eligibility test by market scarcity and revenue ownership, not by acquisition status.
• Signalling failure: announcing the package before the founders are re-contracted invites a second announcement and a second loss of credibility.
• Union and works-council reaction in the bank's traditional units; brief them before the town hall, not after.
• Over-promising the platform's contribution: publish what it can actually deliver in year one, or the same employees will discount the next strategy message.

The real test of leadership. Consistency between what the CEO says about the platform and what the procurement queue and grade structure actually allow; employees believe the queue, not the town hall.