Insights

How to plan the go-to-market for a bank’s mobile app re-launch

Techtone Group · Aug 3, 2026 · Last reviewed Oct 14, 2026

Start about 20 weeks before the launch date, and no later than 14 weeks. A good plan works in four phases: customer insight and concept, a detailed strategy and tactical plan, sunsetting the old app and preparing branches and the contact center, then go-live. The goal is not downloads but customer lifetime value.

Why the plan matters more than the app

Banks spend years building a new app and weeks planning its launch. The result is familiar: downloads spike, active use falls back, the old app lingers, and branch staff tell customers to wait. A launch plan exists to prevent that. Its goal is to maximize customer lifetime value, which rests on two measures:

• Adoption: customers move to the new app faster than they would on their own.
• Stickiness: they use it often and use several services in it, ahead of the main competitors.

The timing: 20 weeks, 14 at the latest

The optimal start is about 20 weeks before the planned launch date. A project can still start 14 weeks out, but every week lost comes out of training, communication and legacy migration, which are the parts customers notice.

Phase 1: insight and concept (20 to 16 weeks before launch)

• Collect and analyze the existing product and marketing material, plans and budgets.
• Analyze the current customer base and define or refine personas, for existing and new customers.
• Map the customer journeys the app has to serve, including the moments where customers drop out.
• Review national and international launch practice and agree what applies.
• Agree a high-level, comprehensive go-to-market concept.

Phase 2: strategy and tactical plan (15 to 11 weeks)

• Turn the concept into a detailed go-to-market strategy.
• Build the tactical plan for every stakeholder, including detailed briefs for marketing and the product team.
• Consolidate all launch activities into one task list and roadmap.
• Write the public FAQ and the plan for customer education and troubleshooting.

Phase 3: legacy, branches and contact center (10 to 7 weeks)

• Set the sunset strategy for the old apps and the messages that move customers across.
• Design an incentive program for the branch network and the contact center.
• Prepare the internal communication plan, the training plan and the training material.

This phase is the one most often cut, and the one that decides adoption. Customers ask branch staff and call center agents first; if the front line is not trained and rewarded for the switch, the old app survives.

Phase 4: go-live and the first months

Launch is a start, not a finish. Track adoption and stickiness weekly against the targets set in phase 1, watch the support topics, and adjust communication and incentives while the window is still open. Decide in advance when the old app stops working, and keep to the date.

Who should own the plan

A launch touches product, marketing, IT, operations, the branch network, the contact center and compliance, and each of them owns part of the result. The plan works best with one accountable owner on the business side, a weekly cross-functional rhythm, and targets for adoption and stickiness agreed before the first campaign is briefed. Without that, every function delivers its own part on time and the launch still misses its numbers.

The measures that tell you it is working

• Migration rate: the share of active users of the old app who have logged in to the new one, week by week.
• Activation depth: the number of services each customer uses in the new app, such as payments, cards, savings and messages.
• Frequency: monthly logins per active customer, compared with the old app and with the main competitors.
• Support load: contact center and branch queries about the app, by topic, which show where the journey breaks.
• Store rating and reviews: an early warning that moves faster than surveys.

Four mistakes we see most often

• Planning the launch after the build. By then the date is fixed and the time for training and communication is gone.
• Running the old and new apps side by side without an end date. Customers stay where they are, and the bank pays for two apps.
• Measuring downloads. Downloads say nothing about adoption or value; active use and depth do.
• Leaving the front line out. Branch and contact center staff who were not trained or rewarded will not move customers across.

What a disciplined plan returns

Across more than 25 app launches over the past 10 years in more than 10 countries, Techtone has seen a well-planned, disciplined go-to-market return three to five times its cost on average projects, with average client savings of EUR 250,000 to 450,000. The numbers depend on the bank, but the pattern holds: the plan pays for itself through faster migration and fewer support costs.

Related service: Go-to-Market Strategy