Skip to main content

The partnership manager - A new key role in every bank and Fintech


Thanks to Open Banking, embedded banking and banks positioning their apps as super-apps, the financial sector becomes more and more an ecosystem of parties collaborating together to execute upon a customer’s journey and needs.

As a result, more and more banks and Fintechs sign partnerships with other financial players and players from other industries, in order to deliver value-added services wherever, whenever and however the customer desires.

Some examples:

  • Banks (like KBC or Belfius in Belgium) offering third party services in their banking app, like buying mobility services (train, bus, metro, shared bikes, shared cars, parking…​), buying cinema and amusement parc tickets, consulting social vouchers (like Monizze), recharging pre-paid phone cards…​

  • Banks and insurers offering financial products via third parties in context of a specific user product journey. E.g. offering mortgages and home insurances in a real estate search engine (e.g. in Belgium Belfius in ImmoVlan and KeyTrade in Immoweb), offering consumer credits and car insurances via car dealers (e.g. Alpha Credit for Renault, Nissan or Toyota), travel insurances on websites of hotel booking platforms or airline companies…​

  • Banks partnering with Bigtech to offer financial products, like Amazon partnering with Bank of America for Amazon Lending, the Apple credit card issued by Goldman Sachs or Google partnering with Citigroup and Stanford Federal Credit Union.

  • Banks partnering with Fintechs to offer specific value-added services, e.g. Billshark with Radius Bank for renegotiating bills, Minna Technologies with Swedbank, Spare Bank or ING for subscription management, Bank of America with Zelle for peer-to-peer payments, Barclays with Flux for digital receipts…​

While banks were traditionally very hesitant and skeptical towards these kind of partnerships (out of fear for reputation risk), this starts to become more and more common in recent years.
Multiple reasons can be identified for this trend:

  • A high number of Fintechs or other tech firms have gained a reputation of being credible and secure

  • The increased digitalization makes the creation of those partnerships easier, more profitable and more desired

  • Customers expect more and more that financial services are part of their overall customer journey and not a separate process, which puts the main customer journey temporary on hold.

  • The increased competition meaning that Time to Market has become critical. As such a partnership can considerably reduce the Time to Market and allow to stay ahead of competition.

  • The scarcity in IT resources (or more general resources allowing to setup digital processes), forcing banks to be extremely picky to which projects they allocate their precious resources. However via partnerships, it becomes possible to increase this capacity and deliver more (digital) innovation in parallel.

Typically you can distinguish 2 types of partnerships:

  • Partners helping with customer acquisition: these can be pure marketing platforms (such as advertising, couponing, cashbacks…​), but also lead generators and even integrated sales channels.
    As customer acquisition is extremely expensive (estimated between 40 and 60% of the cost linked to a customer) such partnerships can be very valuable. Obviously incumbent banks, which already have a large customer base and good user engagement, are typically helping other parties with their customer acquisition, but there are many other parties that have an extensive customer base that can be leveraged for the customer acquisition strategy of a financial player, such as Telco players, Social Secretariats, digital marketplaces, social voucher issuers, eCommerce players (like PSPs or CMS platforms)…​
    In the above examples, ImmoVlan helps Belfius with customer acquisition for mortgages, while Belfius helps to bring customers to Jaimy, which is a digital marketplace for finding a handyman (or in both directions Belfius and Proximus will help each other in customer acquisition.

  • Partners helping with the execution (delivery) of a product or service. These are partners providing either specific technical components, full business outsourcing (e.g. taking care of your full customer support) or specific value-added satellite services.
    For example, ING partnering with Minna Technologies to offer subscription management service or the challenger bank N26 using Mambu as a banking-as-a-service platform.

With banks closing more and more partnerships, the role of a "Partnership Manager" (or Partner Account Manager) becomes more and more important. This person should guide a partnership from its conceptualization all the way to its operational management.

The first step in a partnership is obviously selecting the right partner. Even though partnerships can increase the capacity of a bank to deliver innovation, these partnerships will still absorb a lot of the scarce capacity to setup, implement and follow-up the partnership. This scarcity forces banks to be very selective in the parties they partner with.

A typical incumbent bank having thousands of customers and a strong customer engagement is a very desirable partner for many third-parties. This means a typical bank will get hundreds of proposals for partnerships a year. It is key therefore to find the right partner, i.e. a party that

  • can provide significant value to the customers (via an interesting product or service) and/or to the bank (e.g. access to new prospects)

  • can address all the constraints of the bank, like security, compliance, risk, audit, tight governance…​, but can also deal with the sometimes bureaucratic and political (decision-taking) processes.

  • shares the same values, i.e. ensure a cultural fit: even if 2 partners are perfectly complementary from a product/service point of view, a partnership is still managed by people and the partnership also needs to be convincing (feel authentic) to the end-customer. As such a cultural fit and fit in values is essential. A typical example of a misfit might be a financial services company partnering with a "Green" company, trying to boost its "Sustainability" reputation, while the financial services company takes very little effort to be sustainable itself.

  • has also sufficient gain of the partnership, i.e. the commercials should work in both directions (a Win-Win-Win situation, i.e. the bank, the partner and the customer). This is important for the long-term viability of the partnership, as a party which loses (or does not gain enough) from a partnership deal will not be very committed to the partnership in the long-term.

Once the right partner is found, the partnership can be negotiated and conceptualized. The key here is proper expectation management and a clear definition of roles and responsibilities, i.e.

  • What is the business strategy behind the partnership? In this track you define together, what are the objectives, success factors and risks (and associated mitigation actions) linked to the partnership. Important here is to have already a discussion about what will happen if the partnership fails (e.g. how can the partnership be stopped, what is the exit strategy for example with regards to data transfer, is there exclusivity…​), but also when it is very successful. A very successful partnership with a start-up can also be risky, as the dependency of the partner can become such a risk, you are forced to buy them at a very high valuation price.
    Additionally the monetization or commercial model of the partnership needs to be agreed. Does one party pay a commission to the other party and in which case? Is there a sharing of revenue? How are costs split (e.g. costs for marketing the partnership, IT investments…​)? Is a joint-venture setup? Will one party become a (minority) shareholder of the other company?

  • Agree on a high-level roadmap. A partnership should be gradually rolled-out and extended, so that decisions can be fine-tuned, but also that there are checkpoints allowing parties to step out of the deal, when assumptions are not achieved, thus limiting the investment cost for both parties. Furthermore such a roadmap gives a view to the future and defines the common journey on which both parties embark.

  • Marketing & communication: agree on a marketing and communication plan around the partnership. Important for the trust within the partnership, is that every party feels comfortable with each communication about the partnership that is sent out. Often start-ups have a more aggressive way of communicating, while large banks are very precise and more conservative in their communication. This difference can obviously lead to issues if not properly managed.

  • Fix the contractual and legal part, i.e. contractually agree on the roles & responsibilities of each party and the agreed commercial model (including potential price increases for the future due to e.g. indexation), but don’t forget to also contractually define all agreements to mitigate certain risks, like what happens in case bankruptcy or acquisition of one of the both parties (e.g. access to source code via Escrow service or possibility to acquire at pre-defined price), what happens in case of security or data breaches, confidentiality and non-disclosure agreements, GDPR data protection agreements (DPA agreements need to be signed, if there is personal data sharing between both parties), the payment conditions, the termination conditions, penalties in case of failures…​

  • Agree on the implementation (integration) of the partnership: which changes need to be made, what are the timelines, what are the integration points…​ Obviously during the implementation, deployment and roll-out phase a correct reporting and transparent communication between both parties should exist.

  • Agree on how the customer contact (typically via the Customer Support Desk) will occur, i.e. to which party will the end-customer call and how will this party involve the other party. Obviously for the end-customer the 2 parties should act as much as possible as 1 united party, but this is easier said than done.
    Ideally the customer should call to the party where the user journey is occurring (also providing a single support system), but often the support desk of this party will not be aware of the specifics of the partner’s functionality. At that moment it is important to avoid having to transfer too many calls to each other and avoid blaming the other party. This can best be solved by sharing good FAQs between the partners (so that each party can also reply standard questions about the other party), by assigning a unique owner to each request/call who does the end-to-end follow-up for the customer, by good SLA management on response times (to questions and incidents) and by sharing easy dashboards where the end-to-end status of any customer request can easily be tracked.

  • Finally agree also on how the partnership is followed-up and how it will evolve, i.e. define monitoring, reporting and SLA management, define which certifications should be maintained by each party, define how change management will work, define communication and escalation lines (like defining SPOCs)…​
    Again this comes down to defining clear roles and responsibilities of each party also after the go-live and to define a plan to keep the partnership alive, i.e. many partnerships start with a bang, i.e. with a big press release and marketing campaign, but after a few months there is nobody anymore looking after the partnership, resulting in a slow dead. To avoid this it is important to have a plan of repeating certain marketing campaigns, having quarterly partnership meetings to discuss results, potential improvements and next steps and putting the partnership objectives also in the KPIs of employees (at both sides), potentially even as part of their bonus plan.

Ultimate all these recommendations come down to Communication, Communication and Communication, in an open, transparent and respectful way, so that there is trust between both parties. Any issues need to be addressed as soon as possible in a constructive way, because once you start going legal, the partnership cannot be rescued anymore. It is the "Partnership Manager" to manage this communication and build out this trust. This should be done by both formal and informal communication channels, like formal communication plans, defining communication and escalation lines (like defining SPOCs), but also more informally by boosting personal connections between the people (at both sides) actively executing on the partnership (e.g. via joint team building events).

As such you will see more and more job offers in the financial sector for partnership managers and their importance within banking organizations will continue to grow in the coming years.

Comments

Popular posts from this blog

Transforming the insurance sector to an Open API Ecosystem

1. Introduction "Open" has recently become a new buzzword in the financial services industry, i.e.   open data, open APIs, Open Banking, Open Insurance …​, but what does this new buzzword really mean? "Open" refers to the capability of companies to expose their services to the outside world, so that   external partners or even competitors   can use these services to bring added value to their customers. This trend is made possible by the technological evolution of   open APIs (Application Programming Interfaces), which are the   digital ports making this communication possible. Together companies, interconnected through open APIs, form a true   API ecosystem , offering best-of-breed customer experience, by combining the digital services offered by multiple companies. In the   technology sector   this evolution has been ongoing for multiple years (think about the travelling sector, allowing you to book any hotel online). An excelle...

Are product silos in a bank inevitable?

Silo thinking   is often frowned upon in the industry. It is often a synonym for bureaucratic processes and politics and in almost every article describing the threats of new innovative Fintech players on the banking industry, the strong bank product silos are put forward as one of the main blockages why incumbent banks are not able to (quickly) react to the changing customer expectations. Customers want solutions to their problems   and do not want to be bothered about the internal organisation of their bank. Most banks are however organized by product domain (daily banking, investments and lending) and by customer segmentation (retail banking, private banking, SMEs and corporates). This division is reflected both at business and IT side and almost automatically leads to the creation of silos. It is however difficult to reorganize a bank without creating new silos or introducing other types of issues and inefficiencies. An organization is never ideal and needs to take a numbe...

RPA - The miracle solution for incumbent banks to bridge the automation gap with neo-banks?

Hypes and marketing buzz words are strongly present in the IT landscape. Often these are existing concepts, which have evolved technologically and are then renamed to a new term, as if it were a brand new technology or concept. If you want to understand and assess these new trends, it is important to   reduce the concepts to their essence and compare them with existing technologies , e.g. Integration (middleware) software   ensures that 2 separate applications or components can be integrated in an easy way. Of course, there is a huge evolution in the protocols, volumes of exchanged data, scalability, performance…​, but in essence the problem remains the same. Nonetheless, there have been multiple terms for integration software such as ETL, ESB, EAI, SOA, Service Mesh…​ Data storage software   ensures that data is stored in such a way that data is not lost and that there is some kind guaranteed consistency, maximum availability and scalability, easy retrieval...

IoT - Revolution or Evolution in the Financial Services Industry

1. The IoT hype We have all heard about the   "Internet of Things" (IoT)   as this revolutionary new technology, which will radically change our lives. But is it really such a revolution and will it really have an impact on the Financial Services Industry? To refresh our memory, the Internet of Things (IoT) refers to any   object , which is able to   collect data and communicate and share this information (like condition, geolocation…​)   over the internet . This communication will often occur between 2 objects (i.e. not involving any human), which is often referred to as Machine-to-Machine (M2M) communication. Well known examples are home thermostats, home security systems, fitness and health monitors, wearables…​ This all seems futuristic, but   smartphones, tablets and smartwatches   can also be considered as IoT devices. More importantly, beside these futuristic visions of IoT, the smartphone will most likely continue to be the cent...

PSD3: The Next Phase in Europe’s Payment Services Regulation

With the successful rollout of PSD2, the European Union (EU) continues to advance innovation in the payments domain through the anticipated introduction of the   Payment Services Directive 3 (PSD3) . On June 28, 2023, the European Commission published a draft proposal for PSD3 and the   Payment Services Regulation (PSR) . The finalized versions of this directive and associated regulation are expected to be available by late 2024, although some predictions suggest a more likely timeline of Q2 or Q3 2025. Given that member states are typically granted an 18-month transition period, PSD3 is expected to come into effect sometime in 2026. Notably, the Commission has introduced a regulation (PSR) alongside the PSD3 directive, ensuring more harmonization across member states as regulations are immediately effective and do not require national implementation, unlike directives. PSD3 shares the same objectives as PSD2, i.e.   increasing competition in the payments landscape and en...

Trade-offs Are Inevitable in Software Delivery - Remember the CAP Theorem

In the world of financial services, the integrity of data systems is fundamentally reliant on   non-functional requirements (NFRs)   such as reliability and security. Despite their importance, NFRs often receive secondary consideration during project scoping, typically being reduced to a generic checklist aimed more at compliance than at genuine functionality. Regrettably, these initial NFRs are seldom met after delivery, which does not usually prevent deployment to production due to the vague and unrealistic nature of the original specifications. This common scenario results in significant end-user frustration as the system does not perform as expected, often being less stable or slower than anticipated. This situation underscores the need for   better education on how to articulate and define NFRs , i.e. demanding only what is truly necessary and feasible within the given budget. Early and transparent discussions can lead to system architecture being tailored more close...

Low- and No-code platforms - Will IT developers soon be out of a job?

“ The future of coding is no coding at all ” - Chris Wanstrath (CEO at GitHub). Mid May I posted a blog on RPA (Robotic Process Automation -   https://bankloch.blogspot.com/2020/05/rpa-miracle-solution-for-incumbent.html ) on how this technology, promises the world to companies. A very similar story is found with low- and no-code platforms, which also promise that business people, with limited to no knowledge of IT, can create complex business applications. These   platforms originate , just as RPA tools,   from the growing demand for IT developments , while IT cannot keep up with the available capacity. As a result, an enormous gap between IT teams and business demands is created, which is often filled by shadow-IT departments, which extend the IT workforce and create business tools in Excel, Access, WordPress…​ Unfortunately these tools built in shadow-IT departments arrive very soon at their limits, as they don’t support the required non-functional requirements (like h...

An overview of 1-year blogging

Last week I published my   60th post   on my blog called   Bankloch   (a reference to "Banking" and my family name). The past year, I have published a blog on a weekly basis, providing my humble personal vision on the topics of Fintech, IT software delivery and mobility. This blogging has mainly been a   personal enrichment , as it forced me to dive deep into a number of different topics, not only in researching for content, but also in trying to identify trends, innovations and patterns into these topics. Furthermore it allowed me to have several very interesting conversations and discussions with passionate colleagues in the financial industry and to get more insights into the wonderful world of blogging and more general of digital marketing, exploring subjects and tools like: Search Engine Optimization (SEO) LinkedIn post optimization Google Search Console Google AdWorks Google Blogger Thinker360 Finextra …​ Clearly it is   not easy to get the necessary ...

The UPI Phenomenon: From Zero to 10 Billion

If there is one Indian innovation that has grabbed   global headlines , it is undoubtedly the instant payment system   UPI (Unified Payments Interface) . In August 2023, monthly UPI transactions exceeded an astounding 10 billion, marking a remarkable milestone for India’s payments ecosystem. No wonder that UPI has not only revolutionized transactions in India but has also gained international recognition for its remarkable growth. Launched in 2016 by the   National Payments Corporation of India (NPCI)   in collaboration with 21 member banks, UPI quickly became popular among consumers and businesses. In just a few years, it achieved   remarkable milestones : By August 2023, UPI recorded an unprecedented   10.58 billion transactions , with an impressive 50% year-on-year growth. This volume represented approximately   190 billion euros . In July 2023, the UPI network connected   473 different banks . UPI is projected to achieve a staggering   1 ...

AI in Financial Services - A buzzword that is here to stay!

In a few of my most recent blogs I tried to   demystify some of the buzzwords   (like blockchain, Low- and No-Code platforms, RPA…​), which are commonly used in the financial services industry. These buzzwords often entail interesting innovations, but contrary to their promise, they are not silver bullets solving any problem. Another such buzzword is   AI   (or also referred to as Machine Learning, Deep Learning, Enforced Learning…​ - the difference between those terms put aside). Again this term is also seriously hyped, creating unrealistic expectations, but contrary to many other buzzwords, this is something I truly believe will have a much larger impact on the financial services industry than many other buzzwords. This opinion is backed by a study of McKinsey and PWC indicating that 72% of company leaders consider that AI will be the most competitive advantage of the future and that this technology will be the most disruptive force in the decades to come. Deep Lea...