Relationship Manager

I think about growth in two separate streams: deepening existing relationships and adding new ones, and I spend more time on the first because it's cheaper and more reliable than acquisition. For existing clients I run a wallet share review every quarter, looking at what products and services a client uses with us against what I know about their broader financial position, and I flag the gaps as conversation starters rather than sales pitches. If a business client is running payroll and trade finance through a competitor, that's a specific, needs-based reason to have a conversation, not a generic upsell. For new business, referrals from existing clients and from internal partners like the mortgage or wealth teams convert far better than cold outreach, so I make a point of asking every satisfied client whether they know someone in a similar situation, and I make sure I'm useful to internal partners so the referrals flow both ways. I track my pipeline the same way a salesperson would, with a realistic probability and expected close date on each opportunity, because a portfolio that grows on hope rather than tracked pipeline stalls the moment I get busy with servicing existing accounts.

The first meeting is where I do the least talking and the most listening, because most relationship managers make the mistake of pitching before they've actually understood the client's situation. I go in with a structured set of questions about the client's business or personal finances, their current banking relationships, and what's actually keeping them up at night financially, and I let the conversation go where it needs to go rather than running through a script. I follow up within 48 hours with something specific, not a generic thank you, usually a short note that reflects back what I heard and one relevant idea or piece of information tied to what they told me, which shows I was actually listening rather than just taking notes. I'm also upfront early about what I can and can't do: overpromising on pricing or turnaround time in the first meeting to win the relationship creates a problem I have to manage for years afterward. By the third meeting I want the client to have seen me solve or progress at least one small thing for them, even something minor like getting an account query resolved quickly, because a demonstrated action builds more trust than any amount of relationship-building conversation.

I don't see those as opposed most of the time, because a client who gets the right product stays longer and refers more business than one who gets oversold something that doesn't fit, so good advice is usually good for the numbers too. Where it does get harder is when I have a target that's easiest to hit by pushing a product that's marginal for a specific client, and in those situations I default to what I'd recommend if I had no target at all, then find a different client or a different product where the fit and the target actually line up. I'm also honest with my manager about it rather than quietly missing target: if I think a target for a specific product is structurally mismatched with my client base, I'd rather raise that directly than either force bad fits or just underperform silently. There have been specific cases where I turned down a chance to sell a product that would have counted toward my number because the client's cash flow couldn't support it, and I've never regretted one of those decisions, because the client relationship and my own credibility with that client outlasted any single quarter's numbers.

My CRM is the backbone of how I run my day, not a system I update after the fact. I log every meaningful client interaction with a next step and a date, because a book of 90 to 120 relationships is too many to track from memory, and the moment I rely on memory is the moment something important slips. I use the CRM's segmentation to tier clients by value and by relationship risk, not just by revenue, because a smaller client with strong growth potential deserves more proactive attention than a larger, stable client who barely needs me. I set up alerts for events that should trigger a call: a large deposit or withdrawal, a change in a business client's filing status, a covenant test approaching, or a product anniversary that's a natural point to review pricing. I also pull data outside the CRM when I need it, like public filings for a business client or market data for a rate conversation, because relying only on what's already in the system means I'm always one step behind on anything the client hasn't told me directly. The goal is that nothing important about a client relationship lives only in my head.

A long-standing business client applied for an increase to their credit facility to fund a warehouse expansion, and after I submitted it, credit came back with a decline based on the debt service coverage ratio falling below policy once the new facility was factored in. I didn't want to just relay the decision by email, so I called the client and asked to meet in person within a few days. I walked through the actual numbers that drove the decision rather than giving a vague 'the bank said no', because a client who understands the specific reasoning can work with me on a path forward, while a client who just hears 'declined' feels like the decision was arbitrary. I came prepared with two alternatives: a smaller facility sized to what the current cash flow could support, and a structure with a shorter amortisation the client could revisit for the full amount in two quarters once a large contract they had pending came through. The client was frustrated but stayed with the bank, took the smaller facility, and came back for the full expansion financing eight months later once the contract had closed and the numbers supported it. The relationship survived because I brought a path forward, not just the bad news.

During a routine annual review with a mid-sized manufacturing client, the finance director mentioned in passing that they were struggling with the administrative burden of paying international suppliers across four currencies through their existing process. I'd gone in to review their existing facility, not to sell anything, but the comment was a specific, needs-based signal, so I asked a few more questions about their volume and pain points rather than letting it pass. I brought in a colleague from our trade and treasury team for a follow-up call within the week, and together we proposed a multi-currency payments setup that cut their processing time and reduced FX costs on a meaningful share of their annual international spend. The client hadn't asked for this and hadn't compared it to competitors, because they didn't know it was something we offered well. The relationship value roughly doubled once that product was added, and just as importantly, the finance director now proactively mentions operational friction points to me because that conversation showed I'm listening for problems, not just selling products. The lesson I took was that the best referral opportunities come from listening during unrelated conversations, not from asking directly what else a client needs.

A private banking client moved a significant share of their assets to a competitor after what I later learned was a slow response on a time-sensitive request during a period when I was covering an unusually large book due to a colleague's leave. I found out only when the client called to formally notify me, which was itself a signal that I'd lost visibility on the relationship before that call. I didn't get defensive on the call. I asked directly what had gone wrong, took detailed notes, and didn't try to talk them out of the decision in the moment, because a client who's already decided doesn't want to be argued with, they want to be heard. I followed up two weeks later, once the immediate frustration had settled, with a specific accounting of what I'd have done differently and asked whether there was room to rebuild trust with a portion of the relationship rather than trying to win everything back at once. The client kept a smaller share of assets with us and increased it modestly over the following year. What changed in my own process was that I now flag any client whose response time expectations I can't reliably meet during coverage gaps, and I loop in a colleague proactively rather than letting service quality silently slip.

I start from the client's actual objective, not the product I might sell them, because the same surface request, like 'I need more working capital', can point to completely different real problems depending on the underlying financials. For a business client I look at trailing cash flow, not just the P&L, since a profitable business can still be cash constrained by receivables timing or inventory buildup, and I check leverage and existing debt service against the new request to see whether adding a facility actually solves the problem or just delays it. I also look at concentration risk in their customer or supplier base, because a working capital gap driven by one slow-paying customer needs a different solution than a structural gap from the business model itself. For a private client the equivalent is understanding liquidity needs, time horizon, and existing exposure across accounts they may hold elsewhere, which I ask about directly rather than assuming everything relevant sits with us. I involve credit or the relevant product specialist early rather than late if the request has any complexity, because bringing in expertise after I've already set expectations with the client is how relationship managers end up promising things the bank can't actually deliver.

I maintain KYC as a standing requirement for the life of the relationship, not a one-time form completed at account opening. At onboarding I verify identity and beneficial ownership for any entity client, understand the source of funds and, for larger relationships, source of wealth, and document the expected account activity so that future transactions can be assessed against a real baseline rather than a guess. I flag anything that doesn't fit a clean profile, like a business structure with layers that don't have an obvious commercial rationale, or wealth that doesn't match the client's stated occupation or business history, and I escalate rather than explain it away, even when the client is otherwise a good prospect and I'd rather not slow the relationship down. I keep the file current between formal reviews, not just at the scheduled refresh date, so if a client's business changes materially, a new ownership structure, a new jurisdiction, a significant change in transaction patterns, I update the record rather than waiting. I also make sure I understand, not just follow, why a specific control exists, because a relationship manager who understands the purpose behind a KYC requirement catches things a checklist alone would miss.

I segment the book by a combination of current value, growth potential, and risk, not just by current revenue, because a client who's small today but growing fast deserves more proactive time than their current numbers alone would suggest. I set a minimum contact cadence by tier, monthly touchpoints for the top segment, quarterly for the middle, and an efficient annual review plus responsive service for the base of the book, so that servicing the smaller relationships doesn't quietly consume all the time meant for growing the larger and higher-potential ones. Within any given week I protect blocks of time for the top-tier relationships and proactive outreach before I fill the calendar with reactive requests, because reactive work will always expand to fill the time available if I let it. I also delegate what doesn't need my specific judgement, routine service requests go to my assistant or the service team, so I'm not the bottleneck for things that don't actually require a relationship manager's decision. When I'm stretched, I'm transparent with lower-tier clients about response times rather than letting service quality silently slip and finding out about the problem when they leave.