<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[The Finserv Minute - Medium]]></title>
        <description><![CDATA[Providing opinions and commentary on relevant financial services topics to benefit industry players across the ecosystem. - Medium]]></description>
        <link>https://medium.com/the-finserv-minute?source=rss----92fb042c14f0---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The Finserv Minute - Medium</title>
            <link>https://medium.com/the-finserv-minute?source=rss----92fb042c14f0---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:28:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/the-finserv-minute" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Full Decks and Empty Promises — Part 2: How Not to Waste Millions on Consulting]]></title>
            <link>https://medium.com/the-finserv-minute/full-decks-and-empty-promises-part-2-how-not-to-waste-millions-on-consulting-eb327fa6977c?source=rss----92fb042c14f0---4</link>
            <guid isPermaLink="false">https://medium.com/p/eb327fa6977c</guid>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[financial-services]]></category>
            <dc:creator><![CDATA[Chris Rigoni]]></dc:creator>
            <pubDate>Thu, 02 Jul 2026 15:27:35 GMT</pubDate>
            <atom:updated>2026-07-02T15:27:37.050Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*wy3A7_kGgWLycbK4w2Mchg.png" /></figure><p>I’ve moved to Substack! Follow me there: <a href="http://thefinservminute.substack.com/">thefinservminute.substack.com</a></p><p><em>In part one, a $3 billion community bank spent $850,000 on consulting over six months and had nothing live when the new VP of Payments was hired. We covered why this keeps happening — misaligned incentives, expertise dependency, SOW signed by the wrong people, SMEs spread too thin. We covered pricing structures, blended rates, and scope language that should prompt you to ask questions.</em></p><p><em>Part two is the operational side. How to run the engagement once it starts. How to choose the right firm. How to know if the price is right. What to have sorted out before you make the first call. And the checklist to take into your next engagement.</em></p><h3>Tracking Progress and Reporting: Two Inputs, Not One</h3><p>Most banks have some version of a status report — a weekly update email and a monthly deck with red, amber, green (RAG) status on a tracker. Most banks treat the receipt of that report as governance. It isn’t.</p><p>A status report produced by the consultant is the consultant’s version of reality. It reflects what they want you to see, framed the way they want you to see it. That’s not dishonest — it’s just one-sided. Treating it as the authoritative view of engagement health is like asking someone to grade their own exam.</p><p>Real governance requires two inputs: what the consultant reports and what your internal team experiences. When those diverge — and they will — that gap is where the real information lives.</p><h3>What Good Reporting Requires</h3><p>Define this in the SOW before the engagement starts; do not leave it to informal convention. You want:</p><p><strong>Weekly written pulse updates.</strong> Not a deck. A brief summary: what was completed, what’s in progress, what’s blocked, and what’s needed from your team.</p><p><strong>Monthly formal milestone reviews</strong> tied directly to the SOW. Not a general project update — each deliverable has a status, a percent complete, a target date, and a RAG rating.</p><p><strong>Defined RAG criteria.</strong> Green means on track to meet the original timeline. Yellow means at risk. Red means off track and requires a remediation conversation. Define these upfront. Otherwise, green means whatever the consultant decides it means that week.</p><p><strong>Escalation triggers.</strong> What happens when something goes red? Who gets notified? What’s the response timeline? Build it before you need it.</p><h3>The Internal Mirror</h3><p>This is the piece most banks skip, and it’s arguably more important than anything the consultant produces.</p><p>You need someone internally who is independently tracking progress against the SOW on the same cadence as the consultant’s reporting. Their job isn’t to forward the consultant’s status update. It’s to answer a separate set of questions:</p><blockquote><em>· Do our SMEs feel like this engagement is delivering value?</em></blockquote><blockquote><em>· Are deliverables landing at the quality and specificity we expected?</em></blockquote><blockquote><em>· Does our team’s sense of progress match what the consultant is reporting?</em></blockquote><blockquote><em>· Are conversations happening informally that should be documented formally?</em></blockquote><p>That internal assessment gets compared against the consultant’s report every cycle. Alignment is good. Divergence is a conversation that needs to happen immediately — not at the end of the engagement when the budget is gone.</p><h3>The Conversation Nobody Has</h3><p>When internal perception and consultant reporting diverge, someone has to say something. That sounds obvious. It almost never happens.</p><p>Why? Because nobody wants to raise their hand and say “I don’t think this is working” when leadership approved the engagement, the consultant is reporting green, and everyone has organizational skin in it succeeding. That silence is incredibly common. It’s also incredibly costly.</p><p>Psychological safety around escalation isn’t just a culture requirement. In a consulting engagement, it’s a financial control. Make it explicitly clear to your internal team: surfacing problems early is expected and valued. The cost of silence is always higher than the cost of an uncomfortable conversation.</p><p>Build the escalation path into the SOW. Not an open-door policy — a formal mechanism. Defined meeting, defined format, defined timeline for resolution. Take it out of the realm of interpersonal discomfort and make it a process. That’s what removes the friction that keeps problems buried until it’s too late.</p><h3>Milestone Sign-Off Is Incentive</h3><p>Tying payment to formal acceptance of deliverables isn’t just a financial control. It’s a function that forces and tracks progress. When the bank must formally sign off before the next invoice clears, the consultant has an incentive to produce complete work, both sides stay calibrated on what done means, and problems surface at milestone boundaries — where they’re still recoverable.</p><p>Milestone sign-off requires a named internal approver with actual domain knowledge. Not just a budget approver. Someone who can honestly answer: is this what we asked for, and is it good enough to build on?</p><p><em>A status report from your consultant tells you what they want you to know. Your internal team’s gut tells you what’s actually happening. Governance means reconciling both. Every single week.</em></p><h3>The Consultant Type Matrix: Fit Over Brand</h3><p>Banks treat “consultant” as a single category. It isn’t. Hiring the wrong firm type for the job is one of the most expensive mistakes an FI can make — and it happens all the time because nobody thinks through the fit before they go to market.</p><p>The firm type should be driven by three things: where you are in the problem, what you need to produce, and what accountability looks like on the other side of the engagement. Get that right, and the selection becomes much clearer.</p><p><em>One reminder before we get into this: the RTP story can happen with any of these firm types. Firm type determines what you’re buying. Engagement structure determines whether you get it. Both matter equally.</em></p><h3>Big Four and Large Advisory Firms</h3><p>These are best for: regulatory remediation, consent order response, enterprise risk frameworks, anything where examiner credibility matters as much as the work product. When a regulator sees a Big Four signature on a risk framework, they read it differently. That brand has real currency, and that should be factored in.</p><p>But know what you’re getting. Don’t hire Big Four to build things. They’re built to assess, advise, and document. When you need something operational — a program built, a workflow designed for actual use — a large advisory firm will produce a beautifully formatted recommendation for someone else to execute. That’s not a knock. It’s just what they are. Use them accordingly.</p><p>You also need internal expertise to push back. The brand doesn’t protect you from substandard work product. Junior staff produces deliverables that partners briefly review before they go out. If nobody on your side has the domain expertise to evaluate what came back, you will accept work that isn’t good enough — not because you’re naive, but because you genuinely can’t tell the difference. Consider bringing in an independent practitioner specifically to review and pressure-test Big Four deliverables on specialized engagements.</p><p>Also, watch for the enterprise mismatch. Big Four frameworks are built to scale to $500 billion banks. When they deploy those same tools at a $3 billion community bank, they don’t scale them down; they deliver the enterprise version. The result is a risk framework with seventeen governance layers for an institution with forty people in its entire risk organization. Impressive on paper, but completely unworkable in practice. Before you sign, ask: can our current team actually operate this on day one without hiring three people or creating two new committees?</p><h3>Mid-Size Specialty Firms</h3><p>These are best for: implementation planning, technology selection, process design, operational buildouts in specific domains — payments, compliance, digital banking, BSA/AML. Enough depth to staff properly. Enough specialization to bring real expertise.</p><p>The quality can vary enormously here. A strong mid-size specialty firm with genuine payments depth is exceptional value. A mid-size firm that oversells specialization and staffs generalists is the worst of both worlds — boutique prices without senior attention and no Big Four brand credibility either. The staffing model conversation matters most with these firms. Ask specifically who is doing the work.</p><h3>Boutique Firms</h3><p>These are best for: highly specialized work that requires genuine domain expertise and direct access to senior management. A true boutique is three to ten senior practitioners who have actually done the thing you’re trying to do. Not studied it. Not advised on it from the outside. Done it. That experiential knowledge is hard to find. When you find it, it’s worth paying for.</p><p>The boutique’s biggest constraint is capacity. But there’s a model that solves it elegantly: a boutique principal with a trusted network of subcontractors. The experienced practitioner designs the work, sets the standards, makes the judgment calls, and runs the engagement day-to-day. Trusted subcontractors handle execution capacity. The bank gets senior judgment directing the work with a team that can actually absorb the load. That’s a fundamentally different model from that of a large firm, where the senior person is largely absent.</p><p>The critical word is trusted. This only works if the subcontractors are genuinely vetted — people whose work the boutique principal has seen and stands behind. Not just available. Not just affordable. Ask directly: who are your subcontractors, what’s your history with them, and how do you QC their work before it comes to us? A firm that can’t answer that clearly is not running a real delivery model.</p><h3>Independent Consultants and Fractional Operators</h3><p>The most underutilized category in banking. A former head of payments at a $5 billion bank who consults independently brings something no firm can replicate: they’ve sat in your chair, made your decisions, and lived with the consequences. That’s not advisory. That’s experiential knowledge. There’s a real difference.</p><p>Fractional operators are especially valuable in two specific scenarios. First: when you need senior expertise but can’t justify the full-time hire yet. Second: when you’re using Big Four for regulatory-facing work and need an independent practitioner to review and pressure-test their deliverables before you accept them.</p><p>Banks underutilize this category because a named firm on an invoice feels easier to defend internally. That institutional comfort is real. So is the cost of paying twice as much for half the relevant experience.</p><p><em>Consultant type isn’t a prestige decision. It’s a fit decision. The most expensive firm in the room is only the right answer if what you need is what they actually sell.</em></p><h3>How to Gauge Pricing: The Math Behind the Number</h3><p>Every procurement policy says get multiple bids. You should. But three bids only help you if you know how to evaluate what comes back. If all three proposals are structured differently — different scope assumptions, different staffing models, different deliverable definitions — you’re not comparing prices. You’re comparing apples to submarines. The cheapest number might be the worst value. The highest might be entirely justified. You can’t tell without a framework.</p><h3>Do the Math Yourself</h3><p>Take the total engagement cost. Divide by total hours. That’s your effective blended rate. Does it make sense given who they say is doing the work?</p><p>Then go one step further. Take the staffing model and run the weighted average yourself. Does it produce the blended rate they quoted? If it doesn’t, the staffing model and the pricing aren’t internally consistent. That’s a conversation worth having before you sign.</p><p>Then do one more. Take the total cost and divide by the number of months. That’s your monthly burn rate. What are you getting each month for that number? A defined deliverable? A milestone? Or just hours of activity? If you can’t answer that question, the engagement isn’t scoped tightly enough to price accurately.</p><h3>Market Rate Benchmarks</h3><p>These vary by geography, firm type, and specialty — but rough ranges give you a sanity check:</p><ul><li>Independent practitioner / fractional operator: $250–$500/hr</li><li>Boutique firm senior practitioner: $250–$450/hr</li><li>Mid-size specialty firm blended: $200–$350/hr</li><li>Big Four blended: $300–$600/hr depending on practice area</li></ul><p>These are baselines for general banking work. Not a cap on specialized expertise. The moment you move into highly specialized territory, these ranges become a floor.</p><p>A consultant who has launched a digital bank in Europe for a US institution has navigated PSD2, GDPR, local licensing requirements, local banking infrastructure — and done it from the American side of the table. That’s rare. Merchant services has its own world of complexity: interchange economics, acquirer relationships, ISO and PayFac structures, chargeback management. BaaS program management, real-time payments infrastructure, cannabis banking, crypto custody — each of these commands a premium from the small number of practitioners who have genuinely done the work.</p><p>You’re not paying for their time. You’re paying to skip the part where you learn by making expensive mistakes. That premium is almost always worth it when the expertise is real.</p><h3>Too Low Is a Red Flag Too</h3><p>An aggressive price that comes in well below market should prompt questions, not relief. Why might a firm underbid? They’re buying the relationship and plan to make margin on change orders once they’re embedded. They’ve under-scoped the work, and the change order conversation is coming, just later and from a position of your dependency. They’re staffing it with junior resources to protect margin. Or they need the work, and the financial pressure will show up in the quality of the engagement.</p><p>None of these automatically disqualify, but none of them are things you want to find out at month four.</p><h3>Cost Per Hour vs. Cost Per Outcome</h3><p>The math that actually matters isn’t cost per hour. It’s cost per outcome. A senior practitioner at $400/hr who has run twelve RTP implementations walks in on day one and starts producing. A junior analyst at $95/hr who is learning on your engagement produces slowly, requires oversight, and generates rework. Cheaper per hour is not cheaper. Know who is doing the work before you evaluate the cost.</p><p><em>Price is what you pay. Value is what you get. The only way to know if you’re getting value is to know exactly what you’re buying before you agree to what you’re paying.</em></p><h3>Before You Make the First Call</h3><p>Most banks think the risk in a consulting engagement begins when the SOW gets signed. It doesn’t. It begins the moment you pick up the phone without having done the internal work first.</p><p>If you don’t know what you need, what you have, and what you’re capable of, the consultant will define all those things for you. They’ll define them in a way that creates the greatest opportunity for engagement for their firm. That’s not cynical. It’s just what happens when one party comes to a conversation prepared and the other doesn’t.</p><p><strong>Define the Real Problem, Not the Presenting One</strong></p><p>Get leadership aligned on what you’re actually solving and why it matters now. There’s a difference between “we need to launch RTP” and the actual business problem underneath that statement. If you can’t write it in two sentences, you’re not ready to make the call.</p><p><strong>Know Where You Are on the Spectrum</strong></p><p>Problem identification, strategy and design, implementation planning, execution support, knowledge transfer. Be honest about where you actually are. Give yourself permission to start at strategy — or even problem identification. A $150,000 strategy engagement that correctly scopes an implementation saves you from an $850,000 implementation engagement that produces nothing.</p><p><strong>Name Your Internal Owner and Clear Their Calendar</strong></p><p>Not a coordinator. Not a liaison. Someone with authority, domain knowledge, and real bandwidth. If that person doesn’t exist yet, that’s the problem to solve first.</p><p><strong>Map Your SME Availability Honestly</strong></p><p>Name the specific people the consultant will need. Honestly assess their actual bandwidth. If they’re at capacity, either clear their plates or extend your timeline. Don’t sign an SOW built on availability you don’t have and make a formal organizational decision that this initiative is a priority — not just an addition to everyone’s existing workload.</p><p><strong>Define What Done Looks Like</strong></p><p>Document your success criteria before the first consultant conversation. What does the organization look like when this is complete? What can you do that you can’t do today? What problem no longer exists? This becomes your North Star for every SOW negotiation and every milestone review.</p><p><strong>Identify How You’ll Evaluate Deliverables</strong></p><p>If you don’t have internal domain expertise, figure out how you’ll get independent validation before you sign. A peer institution. A fractional practitioner. An independent reviewer. Have that answer ready.</p><p><strong>Plan for Knowledge Transfer from Day One</strong></p><p>Who owns the work product when the consultant leaves? Who maintains and builds on it? If the answer is nobody, that’s a scoping problem to solve now. A great framework that lives only in the consultant’s head is shelfware.</p><p><strong>Align Budget Authority — Not Just Approval.</strong></p><p>Approval means someone signed off on a number. Alignment means everyone controlling the budget understands what’s being bought, what success looks like, and what the organization is committing beyond the dollar amount — including their own people’s time.</p><p><strong>Talk to Peers Before You Talk to Consultants</strong></p><p>Other bank executives who have done similar work. Your correspondent banking relationships. Industry networks. What did it cost at a comparable institution? How long did it really take? What would they do differently? That market intelligence changes the dynamic of every conversation that follows.</p><p><strong>Involve Your Operational Team in SOW Review Before Signature</strong></p><p>The people who will live with the work product validate scope, deliverables, and timelines before anything gets signed. Three questions: Does this scope actually solve our problem? Are these deliverables ones we can use when the consultant leaves? Is this timeline realistic given our constraints? If the answer to any of those is no, the SOW needs to be adjusted.</p><h3>So What?</h3><p>None of this is complicated; most of it is just discipline. The banks that get consulting right aren’t smarter than the ones that don’t. They’re more deliberate about protecting their own interests before, during, and after the engagement.</p><h3>Before You Engage</h3><p>1. <strong>Define the real problem and get leadership aligned. </strong>Not the project description — the business case. Two sentences. If you can’t do it, you’re not ready.</p><p>2. <strong>Decide what kind of engagement you actually need. </strong>Problem identification, strategy, implementation planning, or execution. Give yourself permission to buy clarity before you buy execution.</p><p>3. <strong>Name your internal owner and clear their calendar. </strong>Authority, domain knowledge, real bandwidth. Not a liaison.</p><p>4. <strong>Map your SME availability honestly and make it a formal organizational priority. </strong>If they’re at capacity, clear their plates or extend your timeline. Don’t sign an SOW built on availability you don’t have.</p><p>5. <strong>Define success criteria in writing. </strong>What does done look like? What can you do that you can’t today? This is your North Star.</p><p>6. <strong>Identify how you’ll independently evaluate deliverables. </strong>Internal expert, peer institution, fractional reviewer. Have the answer before you sign.</p><p>7. <strong>Plan for knowledge transfer upfront. </strong>Who owns the work product when the consultant leaves? Solve this before the engagement starts.</p><p>8. <strong>Align budget authority, not just approval. </strong>Everyone who controls the budget must understand what’s being bought and what the organization is committing to beyond the dollar amount.</p><p>9. <strong>Talk to peers before you talk to consultants. </strong>Market intelligence makes you a dramatically more informed buyer.</p><p>10. <strong>Prepare your scope document before outreach. </strong>Don’t let the consultant define the problem for you.</p><p>11. <strong>Involve your operational team in SOW review. </strong>Scope, deliverables, timelines. Before signature. Not after.</p><h3>During the engagement</h3><p>12. <strong>Hold a structured kickoff. </strong>Scope, deliverables, milestones, reporting cadence, escalation process, change order requirements. Everyone in the room. Everything documented.</p><p>13. <strong>Require a milestone tracker tied to the SOW. </strong>Every deliverable: status, percent complete, target date, defined RAG. Not a general project update.</p><p>14. <strong>Require weekly written pulse updates. </strong>Completed, in progress, blocked, needed from your team. Brief. In writing. Every week.</p><p>15. <strong>Run your internal mirror independently. </strong>Your internal owner assesses progress separately. Compare to the consultant’s report. Divergence is an immediate conversation.</p><p>16. <strong>Create psychological safety to escalate. </strong>Surfacing problems early is expected and valued. Silence costs more than the conversation.</p><p>17. <strong>Hold formal monthly milestone reviews. </strong>Progress, deliverable quality, budget burn against milestones, open issues. Document outcomes.</p><p>18. <strong>Require formal deliverable acceptance before payment. </strong>Named internal approver with domain knowledge. Not just a budget approver.</p><p>19. <strong>Enforce change order discipline. </strong>Any scope change requires written documentation, revised estimates, and your written approval before work proceeds. No exceptions.</p><p>20. <strong>Monitor budget burn against milestone progress. </strong>60% of budget spent and 30% of milestones complete is a conversation that needs to happen now.</p><p>21. <strong>Conduct a formal mid-engagement health check. </strong>Is it delivering value? Is the consultant performing? Are we still solving the right problem? Adjust before it’s too late.</p><p>22. <strong>Plan the exit from day one. </strong>What gets handed off? To whom? What knowledge transfer sessions are required? Define it in the SOW and enforce it.</p><p>23. <strong>Do a formal post-engagement debrief. </strong>What worked? What didn’t? What would you do differently? Document it. The next engagement should be better than this one.</p><h3>The Right Consultant Changes Everything</h3><p>I want to be clear about something: none of this is an argument against using consultants. The right consultant, in the right engagement structure, for the right type of work, with the right internal support, genuinely accelerates what you’re trying to build. They bring expertise you can’t hire fast enough. Perspective you can’t develop internally. Execution capacity you don’t always have.</p><p>I’ve been on both sides of this. I’ve been the client who had to sort through what a consulting engagement actually produced, and I’ve been the practitioner brought in to build things correctly. The difference between a good engagement and a bad one almost never comes down to the consultant’s capability. It comes down to whether the bank did the work to structure it right.</p><p>The engagement that produces slide decks and empty promises isn’t inevitable. It’s a choice, usually made in a hurry, without enough scrutiny, by the wrong people in the room.</p><p><em>You now have the framework to make a different choice.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb327fa6977c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-finserv-minute/full-decks-and-empty-promises-part-2-how-not-to-waste-millions-on-consulting-eb327fa6977c">Full Decks and Empty Promises — Part 2: How Not to Waste Millions on Consulting</a> was originally published in <a href="https://medium.com/the-finserv-minute">The Finserv Minute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full Decks and Empty Promises — Part 1: How Banks Waste Millions on Consulting]]></title>
            <link>https://medium.com/the-finserv-minute/full-decks-and-empty-promises-part-1-how-banks-waste-millions-on-consulting-4190093777d1?source=rss----92fb042c14f0---4</link>
            <guid isPermaLink="false">https://medium.com/p/4190093777d1</guid>
            <category><![CDATA[baas]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[financial-services]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[banking]]></category>
            <dc:creator><![CDATA[Chris Rigoni]]></dc:creator>
            <pubDate>Thu, 18 Jun 2026 13:34:44 GMT</pubDate>
            <atom:updated>2026-06-18T13:34:46.046Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*wy3A7_kGgWLycbK4w2Mchg.png" /></figure><p>I’ve moved to Substack! Follow me there: <a href="http://thefinservminute.substack.com/">thefinservminute.substack.com</a></p><p><strong>$850,000. Six months. And not a single RTP payment live.</strong></p><p>That’s what a $3 billion community bank had to show for it when their new VP of Payments walked in the door.</p><p>She started on a Monday. By Wednesday, she knew something was wrong. By Friday, she knew exactly how wrong.</p><p>The bank knew they needed RTP. Commercial customers were asking for it. Competitors were moving. Leadership wanted to check the box. The problem was nobody inside the bank had ever done this before. They didn’t have the technical depth, the payments experience, or any real picture of what “launched” required from start to finish.</p><p>So, they hired a boutique payments consulting firm. The pitch was sharp. Experience launching RTP, a confident implementation plan, credible names in the room. The SOW landed at $850,000 over six months. Leadership signed it and felt good. The project was in motion. That feeling of motion is exactly where everything went wrong.</p><p>The engagement kicked off with energy. Lots of meetings, lots of slides, weekly calls, status reports that read green across the board every single month — the illusion of progress. But nobody internally actually owned the project. There was a liaison who forwarded updates and booked calls — but no one with the domain knowledge to look at a deliverable and say, “this isn’t right.” Leadership was involved but had no frame of reference for what “on track” even meant for an RTP implementation. They were evaluating progress they weren’t equipped to evaluate.</p><p>Then, scope drifted. The bank kept surfacing new questions — what does our core need to do? What’s the ops workflow when a payment hits? Each question became a new workstream. No formal change orders. The SOW quietly expanded while the timeline held still. Invoices cleared every month because there were no deliverable-tied milestones. Just hours running on autopilot.</p><p>The SMEs who needed to be in the room were already buried in three other projects. Nobody made this a formal priority. So, they gave it 20% of their time and the consultant billed for capacity that mostly sat idle. When the deliverables came back, nobody had the expertise to evaluate whether they were complete, accurate, or even usable.</p><p>Six months in, the new VP of Payments sat down with the project documentation and started asking the questions any competent operator asks when inheriting a project.</p><p>· Where’s the TCH certification status?</p><p>· What’s the core integration plan?</p><p>· Who owns the operational workflow when a payment hits?</p><p>· What does the testing plan look like?</p><p>The answers were either “the consultants are handling that” or silence.</p><p>She pulled the SOW. She pulled the invoices. She looked at what had been produced versus what had been paid. Then she walked into the executive’s office and closed the door.</p><p>The bank didn’t have RTP. What they had was documentation. A current state assessment. A gap analysis. A vendor evaluation. A proposed operating model.</p><p>Slide decks. A lot of slide decks.</p><p>The consultant needed another four to six months to finish the job.</p><p><em>Here’s the part I need you to hear: this isn’t a story about a bad consulting firm. The firm delivered exactly what the engagement was structured to produce. This is a story about a bad engagement — one the bank had just as much hand in creating as the consultant did.</em></p><p>That distinction is the whole point.</p><p>This happens with boutique firms. It happens with big four firms, mid-size specialists, and independent consultants. The firm type doesn’t determine the outcome. The engagement structure does. Get the structure wrong, and it doesn’t matter who you hired.</p><h3>Why This Keeps Happening</h3><p>Some version of the RTP story plays out at banks of every size, in every region, across every type of consulting engagement. The names change. The outcome doesn’t. Here’s why.</p><h4>Consultants Aren’t Incentivized to Wrap Up Clean</h4><p>Consulting firms are businesses. Their revenue model runs on billable hours and repeat engagements. A tightly scoped engagement that ends on time and on budget is a worse outcome for them than one that runs long. That’s not cynical — it’s just reality. The bank’s job is to understand that, going in, and to build an engagement structure that aligns incentives. Because left to their natural state, they don’t align.</p><h4>The Expertise Gap Makes You Dependent</h4><p>When you hire a consultant because you don’t have internal expertise, you’ve also lost your ability to evaluate their work. You can’t challenge a deliverable you don’t understand. You can’t push back on a timeline you have no frame of reference for. The consultant — intentionally or not — becomes the sole authority on whether the engagement is succeeding. That’s a dangerous position. And it requires deliberate countermeasures, or you’re flying blind.</p><h4>Activity Feels Like Progress Until It Doesn’t</h4><p>Sometimes banks hire consultants because leadership needs to feel like something is happening. The RFP process, the selection, the kickoff meeting — all of it feels like momentum. But activity isn’t progress. If nobody defines what progress looks like in measurable terms, you can run an engagement for six months on that feeling alone before reality shows up. By then you’ve spent the budget.</p><h4>Nobody Owns It Internally</h4><p>A consultant can only be as accountable as the client holds them. If the internal “owner” is really a liaison — someone who schedules calls and forwards status updates rather than challenges deliverables — the engagement runs on autopilot. The consultant fills the vacuum. Every green report goes up unfiltered. Every missed milestone goes unexplained. And when the engagement ends without the expected outcome, there’s no one internally who saw it coming because no one was actually watching.</p><h4>The SOW Gets Signed by the Wrong People</h4><p>Legal reviews it for liability. Finance reviews it for budget. But who reviews it for operational accuracy? Who asks whether the scope matches what the bank needs? Usually nobody with the domain expertise to know the difference.</p><p>And here’s the compounding failure: the people who will live with the work product — the payments team, the ops team, the technology team — find out what was promised after the ink is dry. They had no seat at the table when the scope was written. So, the consultant scopes to what leadership described, which is usually a high-level version of the problem. The operational team knows where the real gaps are. They know what “done” needs to look like to be usable. That knowledge never made it into the SOW.</p><p>Then the engagement kicks off, and the operational team gets handed accountability for something they had no hand in designing. Managing a consultant against deliverables they didn’t validate, on a timeline they didn’t set, against a scope they didn’t review. That’s a setup for failure regardless of how good the consultant is.</p><h4>SMEs Are Spread Too Thin</h4><p>Signing the SOW is the financial commitment. Clearing your SMEs’ calendars is the operational one. Most banks only make the first one.</p><p>The people the consultant needs — the core banking SME, the compliance officer, the IT architect, the payments ops lead — are already at capacity. They’re not being pulled off other projects. They’re just being added to this one. So, the consultant is ready to work, billing the clock, and waiting on your people to show up. When they do show up, they give it 20%. The consultant can only move as fast as your slowest internal dependency. Timelines stretch. Invoices don’t. And in the debrief, “awaiting client input” becomes the line that explains every missed milestone. It’s technically accurate. And it tells you nothing useful.</p><p><em>None of these failures happen in isolation. They compound. Together they create a system that produces bad outcomes almost by design — regardless of how good the firm you hired actually is.</em></p><h3>Fixed Price vs. T&amp;M vs. Hybrid: Know What You’re Actually Buying</h3><p>Before you decide how to structure the engagement, answer a more important question: what kind of engagement do you need?</p><p>This matters more than most banks realize. Consulting doesn’t mean code gets written or a payment goes live. Sometimes you need help thinking through the problem — or even identifying what the real problem is. That’s a legitimate engagement. It has real value. The disaster happens when you think you’re buying level four — execution — and the consultant scopes level two. Or when you pay implementation prices for strategy work without realizing it.</p><p>Consulting engagements exist on a spectrum: problem identification, strategy and design, implementation planning, execution support, knowledge transfer. Each requires a different structure, deliverables, and definition of done. Know where you are on that spectrum before you talk to anyone.</p><p><em>The pricing model isn’t a budget decision. It’s a risk decision. Who carries the risk of the unknown?</em></p><h4>Fixed Price</h4><p>Fixed price works when scope is genuinely knowable upfront. A gap analysis. A vendor selection. A policy framework. A current state assessment. Anything where you can describe what done looks like before the engagement starts and hold the consultant to it.</p><p>The upside is budget certainty. The downside is that consultants know the model too. Fixed price engagements get sandbagged on the estimate to protect margin — and then staffed with junior resources, while senior names show up just long enough to stay visible. Watch for that.</p><h4>Time and Materials</h4><p>T&amp;M makes sense when the work is genuinely exploratory. Standing up a new program. Working through regulatory remediation. Building something that requires real iterative discovery before you know what you’re building. The upside is flexibility. The downside is that without guardrails, T&amp;M is just an open credit card.</p><p><em>T&amp;M without a not-to-exceed cap is almost always a mistake.</em></p><h4>Hybrid</h4><p>Often, hybrid is the right answer. Fixed price on defined deliverables. T&amp;M with a hard cap on advisory and support hours. Budget certainty on the things you can scope. Controlled flexibility on the things you can’t.</p><p>The keyword is hard cap. Not a soft ceiling that turns into a change order conversation at month four. A contractual limit that requires mutual agreement and formal documentation to exceed. If they push back on a hard cap, that’s information.</p><h4>The Phased Approach: The answer to “subject to change based on findings”</h4><p>When you see “subject to change based on findings” in an SOW, that’s an admission that the work isn’t ready to be scoped yet. The wrong response is better contract language. The right response is a phased structure.</p><p>Phase one: strategy and discovery. Tightly scoped. Fixed price. Defined deliverables — current state assessment, gap analysis, recommendation on path forward. You know exactly what you’re buying and what done looks like. The consultant does the discovery work they need to do. The unknowns become knowns.</p><p>Phase two: implementation. Now you have the inputs to scope it accurately. Deliverables are specific. Timeline is grounded in reality, not padded with estimates for uncertainty. Pricing reflects actual complexity.</p><p>This structure gives the bank a natural decision point and off-ramp after phase one. It gives the consultant a fair basis for pricing against, and it surfaces whether the firm is actually good before you’ve committed to the big engagement. A consultant who resists a phased structure — who insists on scoping the whole thing upfront despite acknowledged unknowns — is telling you something.</p><h4>Blended Rate vs. Granular Staffing: The Math They Don’t Show You</h4><p>A blended rate sounds simple. One number. Easy to budget. Easy to compare across proposals. That’s exactly why firms love offering it. Because simple is doing a lot of work to obscure what’s going on underneath.</p><p>Here’s the math nobody walks you through. A firm quotes $225 blended. Sounds reasonable for a boutique payments shop. But look at what that rate might represent:</p><p>Partner: $450/hr — 20 hours total across six months</p><p>Manager: $275/hr — 80 hours</p><p>Senior Analyst: $175/hr — 300 hours</p><p>Analyst: $95/hr — 400 hours</p><p>Run that math. The weighted average lands near $225. But what you actually bought is 400 hours of analyst work. The partner who sold you the engagement shows up for the kickoff, the monthly executive touchpoint, and the final presentation. That’s it. The person with all the experience you thought you were paying for is almost entirely absent from the engagement itself.</p><p><em>A blended rate tells you what you’re spending. A staffing model tells you what you’re actually buying.</em></p><h4>What to Ask For Instead</h4><p>Get the staffing model in the SOW. Not a general team description, the actual model. Require named or role-defined resources, individual rates for each level, and estimated hours by role across the full engagement. A material change clause — if they swap a resource or redistribute hours down the org chart, that requires your written approval. Also, a right to billing details: monthly invoices should show hours by resource and by activity. Not “consulting services — 120 hours.”</p><h4>The Seniority Bait and Switch</h4><p>The partner who presents in the pitch meeting is not always the partner who runs the engagement. The senior manager who demos the methodology is not always writing the deliverables. You get sold on senior expertise. You get delivered junior execution.</p><p>This isn’t unique to consulting — it happens in law firms, accounting firms, and agencies, but it hurts especially in specialized domains like payments or BaaS where the value you’re paying for is specifically the senior practitioner’s judgment. Protect that in writing. Ask who, specifically, will run this engagement day-to-day. Get that person in the room before you sign. If the answer keeps changing or stays vague, you have your answer.</p><h4>The Boutique Nuance</h4><p>A true boutique — three to five senior practitioners — might legitimately offer a blended rate because their model is genuinely flat. Everyone billing is senior. The spread between their highest and lowest rate might be $50/hr, not $350. That’s a different situation than a mid-size firm using a blended rate to obscure a pyramid staffing model.</p><p>Knowing the difference means asking directly: walk me through who is actually doing the work day-to-day and what their individual rates are. A firm with nothing to hide answers that clearly.</p><h3>Scope Language Red Flags: The Contract Inside the Contract</h3><p>Most banks spend more time negotiating the rate than they spend reading the scope. That’s exactly backward.</p><p>A $50/hr rate concession means nothing if the scope language lets the consultant expand the engagement indefinitely. The price is what you pay. The scope is what you get. And vague scope language is how a well-intentioned engagement becomes the RTP story.</p><h4>Red Flag Phrases</h4><p><strong>“As needed”</strong></p><p>Probably the most dangerous phrase in any SOW. As needed by whom? Determined how? Capped where? Every single instance of this phrase needs to be replaced with a specific deliverable, a defined hour allotment, or both. There is no acceptable version of “as needed” that serves the bank’s interests.</p><p><strong>“Reasonable efforts”</strong></p><p>Sounds professional. Means nothing. Reasonable by whose standard? This phrase protects the consultant from accountability on timeline and quality without ever having to say so out loud.</p><p><strong>“General advisory support”</strong></p><p>What is this? A phone call? A full analysis? A working session? Unlimited email access? This language sounds like added value. It’s really just unstructured billing room. Define it — hours, format, turnaround expectations. Every time.</p><p><strong>“Deliverables to be refined during the engagement”</strong></p><p>Deliverables get defined before the engagement starts, not during it. This language means you’re signing a contract for something that hasn’t been fully specified yet. If the work genuinely isn’t ready to be scoped, the answer is a phase one discovery engagement — not vague language that leaves the bank holding the risk.</p><h4>The Change Order Problem</h4><p>Scope creep almost never happens dramatically. It happens in small increments. One additional workstream. One extra round of stakeholder interviews. One new deliverable leadership requested informally on a call. Each one feels reasonable in the moment. Collectively, they can double the scope of an engagement without a single formal change order being executed.</p><p>A well-structured SOW has a change order process with teeth: any scope change requires written documentation before work begins, new cost and timeline estimates must be provided, your written approval is required before the consultant proceeds, and change orders are addended to the original SOW — not handled via email where they disappear into someone’s inbox.</p><h4>The Deliverable Definition Test</h4><p>Every deliverable in the SOW should pass this test before you sign: can you describe specifically what it looks like when it’s complete, who reviews and approves it, and what criteria determine acceptance? If you can’t answer all three questions for every deliverable, the scope isn’t tight enough. Vague deliverables are how consultants produce something, anything, and call the milestone complete.</p><h4>The Revision Cycle Trap</h4><p>Cap revision cycles in the SOW. Two rounds is a reasonable standard. Define what constitutes a revision versus a new request. Tie final payment on each deliverable to formal written acceptance — not just delivery. The moment a deliverable lands in your inbox is not the moment it’s done.</p><p><em>The scope section of an SOW isn’t a standard template. It’s the contract inside the contract. Read every word like money depends on it. Because it does.</em></p><h3>The Setup Is the Strategy</h3><p>Everything in part one happens before a single deliverable is produced. The pricing structure. The staffing model. The scope language. These aren’t administrative details. They’re the foundation. Get them wrong, and it doesn’t matter how good the consultant is; the engagement is already structured to fail.</p><p>In part two, we’ll cover how to actually run the engagement once it starts. How to track progress and build real reporting governance. How to choose the right firm type for the right job. How to know if you’re paying the right price. What to have figured out internally before you ever make the first call. And a concrete step-by-step checklist you can use on your next engagement.</p><p>The goal is simple: make sure you never have to sit in that room, staring at a stack of slide decks, wondering what you actually paid for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4190093777d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-finserv-minute/full-decks-and-empty-promises-part-1-how-banks-waste-millions-on-consulting-4190093777d1">Full Decks and Empty Promises — Part 1: How Banks Waste Millions on Consulting</a> was originally published in <a href="https://medium.com/the-finserv-minute">The Finserv Minute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons in Partner Banking — Part 7: Wrap-Up]]></title>
            <link>https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-7-wrap-up-5c067142913d?source=rss----92fb042c14f0---4</link>
            <guid isPermaLink="false">https://medium.com/p/5c067142913d</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[baas]]></category>
            <category><![CDATA[banking-partner]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[financial-services]]></category>
            <dc:creator><![CDATA[Chris Rigoni]]></dc:creator>
            <pubDate>Thu, 11 Jun 2026 20:53:22 GMT</pubDate>
            <atom:updated>2026-06-11T20:53:23.403Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*5oNwKx8OqVIcHbvXwreOGQ.png" /></figure><p>Six installments in, and here we are. When I started this series, the goal was to give financial institutions a practical guide to building and running a partner banking program that actually holds up — under growth, under pressure, and under regulatory scrutiny. The FIs that are winning in partner banking are the ones that built it right. The ones that are struggling, or worse, are the ones that cut corners on the fundamentals. This final installment is a look back at the full picture: what every FI needs to have in place to make partner banking work.</p><p><strong>Strategy Is the Foundation</strong></p><p>Partner banking is not something you stumble into and figure out as you go. Every FI that has tried that approach has learned the hard way. The first lesson in this series was about strategy for a reason — everything else in partner banking flows from having a clear, well-documented plan before any partner is onboarded or any product is launched. That plan needs to span products, risk, compliance, infrastructure, and governance. It needs to include your regulators and be honest about what your FI actually knows how to do and what it does not.</p><p>One of the most common mistakes I have seen is FIs entering product categories or transaction types where they have no internal experience. You cannot manage risk you do not understand. If the expertise does not exist internally, you either build it before you launch or you do not launch that product. There is no third option. The North Star exercise matters here because defining what results would have the most impact on the FI forces honest conversations about where to play and where to stay out.</p><p><strong>Infrastructure Is Not Optional</strong></p><p>Infrastructure is where strategy becomes real. You can have a thoughtful plan, but if the systems underneath it cannot support the volume, the oversight requirements, or the complexity of a multi-partner program, the plan does not matter. Two areas deserve particular attention here: the bank-owned ledger and automation.</p><p>The sub-ledger challenge is at the heart of most BSA and reconciliation issues in partner banking. The FI needs a clear, point-in-time view of every end-user balance across all partners and the ability to reconcile down to the transaction level. A bank-owned sidecar ledger — one that the FI controls and that replicates partner sub-ledger activity — is the most reliable way to address this. It also enables real-time data distribution to downstream systems for BSA, accounting, and fraud. This is not aspirational infrastructure. It is table stakes.</p><p>On automation: the economics of partner banking only work at scale if the FI is not scaling headcount at the same rate it scales volume. The goal is to work on exceptions, not to find them. Whether that means automated alerts in transaction monitoring, system-generated reconciliation anomalies, or real-time partner dashboards, automation is what keeps the program manageable as it grows. Software, automation, and, in some cases, AI solutions for workflow management, risk and compliance, and reconciliation are not nice-to-haves — they are the program&#39;s architecture.</p><p><strong>Data Is the Product</strong></p><p>FIs are historically bad with data, and that is not an opinion — it is a pattern that plays out consistently in exams and operational failures. In partner banking, bad data management is not just an operational inconvenience. It is a compliance and safety-and-soundness issue. The FI depends on partner data for transaction monitoring, reconciliation, and BSA oversight. If that data is incomplete, inaccurate, or late, every downstream process is compromised.</p><p>The work starts with requirements — what does each team actually need, at what level of granularity, and at what frequency. From there, it is about verification: is the data the FI receives from partners complete, on time, and accurate? And it is about governance: do the policies, procedures, and controls around data management exist, and is there evidence they are being followed? Payments data is the most complex piece, particularly because the FI is receiving transaction data from multiple sources — the Fed, the networks, partners, and their vendors — that were never designed to connect to each other. Getting that normalized and reconciled is not easy, but it is required.</p><p><strong>Risk and Compliance Are Not Obstacles</strong></p><p>The framing matters. Partner banking does not have elevated risk. It has risks that are specific to the business — risks that can be understood, measured, and managed if the FI builds the right framework. The FIs that treat risk and compliance as obstacles to revenue tend to be the ones that end up with consent orders. The ones that bring risk and compliance into strategy and planning early, and treat them as partners in building the program, tend to be the ones that sustain it.</p><p>A risk framework for partner banking needs to be more granular than what most community banks are used to. The risk appetite needs to feed the risk assessments, which in turn feed the controls, which in turn feed the processes. There needs to be documented reasoning for what the FI considers material risk and what thresholds it has set. And there needs to be evidence — not just policy, but evidence — that the controls are being performed. This is where examiners look, and this is where FIs most commonly fall short.</p><p>Third-party risk management also takes on a different character in partner banking. Partners are not vendors, and the standard TPRM questionnaire was not designed with them in mind. The FI needs to assess partners across the full scope of the relationship — their disclosures, marketing, BSA program, vendor management, and financial health — and do so not just at onboarding but on an ongoing basis. Fourth-party risk is real too. If a partner’s core technology provider fails, the FI has exposure. That has to be anticipated and managed.</p><p><strong>Governance Makes It Scalable</strong></p><p>Governance is the operating system of a partner banking program. I have seen FIs with well-designed products and competent teams run into serious trouble because they had no formal governance structure — no documented approval process, no change management framework, no consistent reporting. Without governance, every exception becomes a judgment call. Every change becomes a risk. Every exam becomes a surprise.</p><p>Three things deserve the most attention. First, onboarding and offboarding structure: every partner should go through a consistent, documented approval process, and the process for ending a relationship should be as well-designed as the process for starting one. FIs consistently underinvest in offboarding, and that is where the risks of customer harm concentrate. Second, change management: partners change constantly, and without a formal process requiring advance notification of material changes, the FI is perpetually catching up to risks it did not anticipate. Third, reporting: the board and management committees cannot provide meaningful oversight if they are looking at dashboards full of data with no narrative and no context. Good governance reporting tells a story.</p><p><strong>Regulators Are Part of the Program</strong></p><p>The last installment of this series focused on regulators because, in my experience, the relationship with regulators is where many well-intentioned partner banking programs ultimately go wrong. Regulators are not adversaries. They have a job to do, and FIs that treat the regulatory relationship as something to manage around — minimizing disclosures, hoping issues do not surface — tend to be the ones that end up with consent orders. The FIs that build strong regulatory relationships are the ones that invest in them deliberately.</p><p>Bring your regulator into the story early. If you are building a partner banking program, tell your examiner what you are building, why, and how you are thinking about the risks. If you have an issue, surface it before the exam does. Regulators are far more forgiving of institutions that demonstrate self-awareness and proactive management than of those that appear to operate without visibility into their own programs. Come to every exam with a clear narrative about the program — its structure, its controls, its risks, its gaps, and what is being done about them. If you cannot tell that story clearly, the examiner will form their own version, and it may not be favorable.</p><p><strong>So What?</strong></p><p>If there is a single idea that runs through all six installments of this series, it is this: partner banking is not something you try. You either commit to building it right — with the investment, the people, the infrastructure, the framework, and the discipline it requires — or you do not do it at all. The market has been very clear about what happens when FIs try to find a shortcut.</p><p>The good news is that the FIs that build it right have a genuine competitive advantage. Partner banking, when done well, creates diversified revenue streams, deepens the FI’s capabilities, and builds institutional knowledge that is hard to replicate. The challenge is not the opportunity — it is the discipline required to pursue it responsibly.</p><p>Here is the summary of what that looks like in practice:</p><p><strong>Strategy first</strong>. Define your North Star, products, target market, and approach to risk and compliance before any partner is onboarded. Be honest about what your FI knows how to do and what it does not. Do not enter product categories or transaction types where you have no internal expertise.</p><p><strong>Invest in infrastructure</strong>. The bank-owned ledger is not optional. Automation is not optional. Software for workflow management, risk and compliance, and reconciliation is not optional. These are the systems that make oversight possible and economics viable at scale.</p><p><strong>Get serious about data</strong>. Know what data you need, verify what you receive, and govern how you manage it. Payments data normalization is one of the harder problems in partner banking. Solve it early.</p><p><strong>Build a real risk framework</strong>. Partner banking does not have elevated risk — it has specific risks that require specific controls. Document the framework with clear reasoning. Build it with evidence. Include risk and compliance in strategy conversations from day one.</p><p><strong>Treat governance as an asset</strong>. Structured onboarding and offboarding, formal change management, and clear reporting to the board and management committees are not bureaucratic overhead — they are what makes a program scalable and defensible.</p><p><strong>Partner with your regulator</strong>. Communicate early and proactively. Come to exams with a clear narrative. Disclose issues before examiners find them. The regulatory relationship reflects how well you are running the program, not a separate obligation to be managed around.</p><p>The FIs that succeed in partner banking over the long term are not the ones that got lucky. They are the ones who made deliberate decisions, invested in the right capabilities, and built programs that could withstand scrutiny — from their partners, their boards, and their regulators. That is the standard. It is achievable. And this series has been an attempt to show exactly what it takes to get there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c067142913d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-7-wrap-up-5c067142913d">Lessons in Partner Banking — Part 7: Wrap-Up</a> was originally published in <a href="https://medium.com/the-finserv-minute">The Finserv Minute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons in Partner Banking — Part 4: Risk and Compliance]]></title>
            <link>https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-4-risk-and-compliance-48da7d8e677b?source=rss----92fb042c14f0---4</link>
            <guid isPermaLink="false">https://medium.com/p/48da7d8e677b</guid>
            <category><![CDATA[partnerships]]></category>
            <category><![CDATA[baas]]></category>
            <category><![CDATA[financial-services]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Chris Rigoni]]></dc:creator>
            <pubDate>Sat, 06 Jun 2026 02:08:56 GMT</pubDate>
            <atom:updated>2026-06-06T02:08:57.947Z</atom:updated>
            <content:encoded><![CDATA[<h3>Lessons in Partner Banking — Part 4: Risk and Compliance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*5oNwKx8OqVIcHbvXwreOGQ.png" /></figure><p>Risk and compliance are perhaps the most critical portions of building a solid partner banking program. From building a solid risk framework to establishing an oversight process, each facet plays a role in ensuring the program stays compliant and appropriately mitigates the risk. It takes time and effort from the business and each stakeholder group to build the components needed for success.</p><p><em>Inclusive and Partnered</em></p><p>First, including risk and compliance, and even legal, in strategy and planning for building a partner banking program is imperative to accomplish a few goals:</p><ul><li>More complete understanding of partner banking structures, funds flows, and partner products</li><li>Ability to provide early feedback and direct improved oversight and risk framework</li><li>Assist in building requirements for data and processes</li></ul><p>While it is important for risk and compliance to be involved, it must be set up as a true partnership. Each stakeholder group must focus on how to work with the business to build a robust, scalable program rather than on eliminating risk. At times, it can be difficult to work toward a partnered solution, especially when building for a new segment with unknown risks; however, if the business and stakeholder groups can truly partner to assess and mitigate risk, the financial institution (FI) has a higher chance of success.</p><p><em>Hire, Hire, Hire</em></p><p>The experience in the FI will vary, but typically, in smaller institutions, the risk, compliance, and operations teams have many individuals who started out in the branch and worked their way up in the organization. While that is certainly admirable, it presents an issue when a partner banking strategy involves significantly higher volumes of customers and transactions, or transaction types that are not typical for the organization (e.g., international wire transfers, IATs, etc.). This is where the FI must do two things:</p><ol><li>Create an environment where employees are allowed to and encouraged to say “I don’t know” or “I don’t have experience” when certain questions arise. It is imperative that transparency be encouraged and even rewarded to ensure stakeholder groups don’t feel as if they need to just “figure it out” in order to keep their jobs or not be looked at negatively.</li><li>Hire to build competencies internally for volume and transaction types that align with the partner banking strategy. It is critical to have internal experience that understands the volume and transaction types, knows the questions to ask, controls to utilize, and how to build a risk framework for this new business segment. It is more important to hire individuals with experience in the details of payments, operations, and the risks associated with partner banking than to hire someone with specific partner banking experience.</li></ol><p>People are 95% of the strategy. The FI needs individuals who have seen the projected volumes from partner banking and the transaction types, who know the nuances that can arise and how to handle them, and who understand the questions to ask to dig into specifics and establish oversight and controls. This can be the difference between the success and failure of partner banking at the FI.</p><p><em>Risk Framework</em></p><p>First, I want to make something clear — partner banking does not have elevated risk and is not inherently higher risk. Just like many other segments, it has risks unique to the business, but that does not mean those risks are inherently higher. It is tempting to approach building a framework from a place of mitigating higher levels of risk, and including this approach in the risk appetite, assessments, and throughout the framework. If everything is high risk, then nothing is. There must be established risk levels that support a risk-based approach, both at the enterprise level and within each business segment.</p><p>For community banks that typically engage in partner banking, risk frameworks are based on lower transaction volumes, specific transaction types, and targeted business segments. While the focus makes sense, adding partner banking creates major gaps in the framework that need to be filled. In addition, the level of granularity in documentation and the framework is typically more relaxed than in a larger FI with higher volumes and more complex transaction and loan types.</p><p>At larger organizations, the risk framework is very detailed. The risk appetite feeds the risk assessments; the risk assessments feed the controls; the controls feed the processes; and evidence is clear and associated with each control. During exams, it is expected that each of these facets is well documented and that evidence is provided that the controls are adequately performed. While there is a similar expectation at smaller FIs, the level of detail and documentation required for these areas is risk-based. Given the smaller volumes of transactions, simpler transaction types and loan structures, and overall lower levels of risk at smaller FIs, these guidelines and requirements are not uniformly applied across all FIs in the US.</p><p>When partner banking is introduced and larger volumes of transactions, as well as more complex transaction and loan types, are part of the strategy, the detail of the risk framework and the level of granularity of the assessments must increase. The FI should also work to develop and document what is considered a material risk to the bank. This should include:</p><ul><li>Higher-level areas of material risk (financial, compliance, operational, etc.)</li><li>Metrics under each higher-level area that are used to quantify the materiality of the risk, such as red, amber, green (RAG) thresholds for applicable metrics</li><li>Controls to manage or mitigate each risk metric and compliance requirement</li><li>Reporting for each metric, including current status and trend analysis for management committees and the board</li><li>Evidence of each process of oversight and control to report during each audit and exam</li><li>Reasoning for each metric and threshold for material risk</li></ul><p>Developing a risk framework with documented reasoning for what the FI considers material risk, the thresholds at which material risk is realized, and the ability to demonstrate this framework (along with evidence that procedures have been completed) will position the FI for exams after the partner banking segment is launched. This instills confidence among the exam teams that the FI has thoroughly reviewed risk assessments and developed an approach to mitigating risk and overseeing the program. Examiners may disagree with the material risk components or the thresholds chosen, but the FI should be able to defend their reasoning and approach. In areas where audits or exams identify gaps in reasoning, or where the FI agrees with the outcomes, the approach can be adjusted.</p><p><em>Third-Party Risk Management</em></p><p>Partner banking can be complex when it comes to third-party risk management (TPRM). Partners are not really vendors, so typical TPRM questionnaires and reviews are not completely sufficient to manage them. Partners also have vendors, which, in some cases, present a 4th-party risk to the FI and require oversight from the partner and the FI.</p><p>TPRM needs to be involved in onboarding, ongoing due diligence, and offboarding processes. TPRM should be managing due diligence for all stakeholder groups, collecting documentation, documenting risk assessments, and managing oversight of the partners throughout each of these areas. While the FI is building partner banking, each stakeholder should review the vendor due diligence questionnaires and add specific areas that apply to the partner&#39;s product types and to situations that may be applicable to the partner or the relationship. Due to the unique nature of the agreements with the partner and the products the partner offers, there are going to be specific items that need oversight during due diligence, such as (but of course, not limited to):</p><ul><li>Disclosures/Terms and Conditions</li><li>Marketing materials</li><li>Website/Application</li><li>Policies and Procedures</li><li>Evidence of Procedure Completion</li><li>BSA and Transaction Monitoring Materials</li><li>Credit/Lending Materials, including model validation</li></ul><p>These areas and more are in addition to the typical due diligence of IT security, cybersecurity, financials, etc., which would be required. The holistic partner relationship should also be considered, including any open remediation issues the partner may have.</p><p>For 4th-party reviews, the partner’s due diligence program should be audited to validate its effectiveness and identify any gaps in the program. Once the partner’s vendor due diligence has been validated, the FI can rely on the completion reports, with the appropriate level of detail, to review and determine whether any follow-up questions or documentation are necessary. The partner should also be required to have at a minimum an annual audit of their vendor due diligence program. This approach prevents the FI from having to replicate the due diligence already performed by the partner, while also requiring the partner’s program to meet the FI&#39;s standards and policy.</p><p><em>So what?</em></p><p>Any FI planning on building a partner banking program should ensure they include risk, compliance, operations, and legal very early in the conversations. The FI should:</p><ul><li>Include stakeholder groups in strategic updates</li><li>Take feedback from each group at each stage of the planning process</li><li>Create feedback loops for questions and the ability to voice areas of gaps in experience to support the program</li><li>Work to build out process documentation with feedback from each stakeholder group to ensure proper controls at each step</li><li>Work with stakeholder groups to align onboarding due diligence with the strategy and risk tolerances of the FI</li><li>Involve each stakeholder group in creating requirements for offboarding, including situations where the partner may not be involved in offboarding the program</li></ul><p>As was mentioned previously, partner banking introduces unique risks to the FI; however, these risks do not have to be elevated if steps are taken to understand the experience needed to mitigate them. Building a partner banking program involves designing risk and compliance programs that are efficient and scalable.</p><p>Stay tuned for the next installment of Lessons in Partner Banking, where we dive into governance. More to come…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48da7d8e677b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-4-risk-and-compliance-48da7d8e677b">Lessons in Partner Banking — Part 4: Risk and Compliance</a> was originally published in <a href="https://medium.com/the-finserv-minute">The Finserv Minute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons in Partner Banking — Part 6: Regulators]]></title>
            <link>https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-6-regulators-f338a03cb665?source=rss----92fb042c14f0---4</link>
            <guid isPermaLink="false">https://medium.com/p/f338a03cb665</guid>
            <category><![CDATA[banking-partner]]></category>
            <category><![CDATA[embedded-finance]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[baas]]></category>
            <category><![CDATA[financial-services]]></category>
            <dc:creator><![CDATA[Chris Rigoni]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 15:33:12 GMT</pubDate>
            <atom:updated>2026-06-04T15:33:13.770Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*5oNwKx8OqVIcHbvXwreOGQ.png" /></figure><p>We’ve all seen the past 5 years in Partner Banking — formal agreements, consent orders, BSA issues, reconciliation issues — the list goes on. So any bank considering entering the space, or any bank already in it, needs a clear view of how it will partner with its regulators to support a successful program. Hoping they don’t find the issues is not a strategy. This should be a true partnership.</p><p><strong>Partnership</strong></p><p>I want to be clear about what I mean by &quot;partnership,” because this word gets thrown around loosely. Partnering with your regulator does not mean agreeing with everything they say or avoiding topics that might generate hard questions. It means treating the relationship with transparency, consistency, and intention — the same way a well-run FI treats its fintech partners.</p><p>Regulators are not adversaries. They have a job to do: make sure banks operate safely and soundly. When an FI launches a partner banking program and then tries to manage around its regulator — minimizing what gets shared, hoping findings don’t surface, or responding only when pushed — it creates exactly the dynamic that leads to consent orders. The FIs that end up in trouble are rarely the ones that had no issues. They are the ones who had issues that did not surface, be managed, or be communicated proactively.</p><p>The better approach is to bring your regulator into the story early. If you are building a partner banking program, tell your examiner what you are building, why, and how you are thinking about the risks. If you have an issue in the program, surface it, explain what happened, and come with a remediation plan. Regulators are far more forgiving of institutions that demonstrate self-awareness and proactive management than of those that appear to operate without visibility into their own programs.</p><p><strong>Come with a Plan</strong></p><p>The most common mistake I see FIs make in regulatory relationships is showing up to exams without a coherent story about their partner banking program. Examiners are not there to be educated from scratch. They have read the guidance, they know what a well-run program is supposed to look like, and they are there to assess how well yours measures up. If the FI does not walk in with a clear point of view on its own program — its structure, its risks, its controls, and its gaps — the examiner will form their own view, and it may not be favorable.</p><p>Coming with a plan means having the documentation, but it also means being able to narrate it. The FI should be able to walk examiners through how the program is structured, what due diligence was performed before onboarding each partner, how ongoing monitoring works, what the governance structure looks like, and what issues have been identified and how they are being addressed. If any of those answers require someone to dig through files or find the right person in the hallway, the program is not ready.</p><p>Before any exam, the FI should conduct an internal review that mirrors the exam itself. What would an examiner look for? Where are the documentation gaps? Are the controls documented and is there evidence they are being performed? Are the policies current? Are open findings from prior exams fully remediated, or are they still outstanding? This kind of self-assessment should not happen once a year — it should be part of the ongoing operating rhythm of the program. FIs that treat regulatory exams as external events to prepare for, rather than as a reflection of how they run the program every day, tend to be the ones that end up with findings they did not see coming.</p><p><strong>Explain It Well</strong></p><p>Having a plan is not enough if the FI cannot explain it clearly. I have sat in rooms where a bank had genuinely good controls and a thoughtfully designed program — and still walked away with more findings than expected because the staff presenting to examiners could not articulate what they were doing or why. The ability to explain the program clearly and in plain language to someone seeing it for the first time is a skill that FIs underestimate.</p><p>This starts with knowing your audience. Examiners are sophisticated, but they are not insiders. They are not going to immediately understand why the FI made a particular design choice, why a specific risk threshold was set where it was, or how a particular control works in practice. The FI has to tell that story. When an examiner asks why the bank uses a particular transaction monitoring rule, “because our vendor recommended it” is not a sufficient answer. “Because our risk assessment identified these specific transaction patterns as elevated risk for our partner portfolio, and this rule is calibrated to those patterns” is.</p><p>The same principle applies when issues arise. If an examiner finds something, the instinct for many FIs is to immediately begin minimizing — “it was a one-time issue,” “it has already been fixed,” “it was isolated to one partner.” In my experience, that approach often backfires. A better approach is to be direct: acknowledge the issue, explain what caused it, describe the corrective actions taken or underway, and identify the monitoring in place to ensure it does not recur. Examiners are looking for evidence that the FI understands its program and manages it responsibly. Transparency, even when the news is not great, builds more credibility than defensiveness.</p><p><strong>So What?</strong></p><p>Regulatory relationships in partner banking do not manage themselves. The FIs that build strong relationships with their regulators are the ones that invest in them deliberately — through communication, preparation, and transparency. Here is a practical guide for FIs looking to strengthen how they engage with regulators:</p><p><strong>Treat Your Regulator as a Stakeholder</strong>: Begin the relationship before the exam. If you are building a new partner banking program or making material changes to an existing one, proactively communicate this to your primary regulator. You do not need approval to share information, and regulators generally view early communication positively. Do not wait for an exam to be the first time your examiner hears about a major new initiative.</p><p><strong>Build Your Exam Narrative Before the Exam</strong>: Develop a clear, written description of your partner banking program that you could hand to an examiner and walk them through in an hour. It should cover the program’s structure and strategy; the partner onboarding and due diligence process; the ongoing monitoring and oversight framework; the governance and reporting structure; the key risk and compliance controls; and any open issues or remediation items currently in progress. If you cannot produce this document quickly, the program is not sufficiently documented.</p><p><strong>Run Internal Dry Runs</strong>: At least once a year, conduct an internal review that simulates the exam process. Assign someone — ideally someone who was not involved in building the program — to ask the questions an examiner would ask. Where does the documentation fall short? Where can staff not explain the rationale behind a design decision? Where are controls documented but not evidenced? Use the results of that review to close gaps before an examiner finds them.</p><p><strong>Disclose Issues Early</strong>: If the FI identifies a material issue in its partner banking program — a reconciliation error, a BSA/AML gap, a control failure — do not wait for an exam to surface it. Report it to your regulator proactively, with a clear explanation of what happened, what the FI has done to contain it, and what the remediation plan looks like. Early disclosure, paired with a credible remediation plan, consistently produces better outcomes than examiner discovery.</p><p><strong>Document Remediation Thoroughly</strong>: When the FI closes a regulatory finding, the evidence of that closure needs to be clear, complete, and retrievable. “We fixed it” is not a sufficient answer to a prior exam finding. The FI should be able to show what was found, what was changed, how the change was implemented, and what monitoring is in place to ensure it does not recur. Regulators follow up on prior findings in every subsequent exam, and weak remediation documentation creates the impression that the FI is not taking findings seriously.</p><p><strong>Invest in the Right People</strong>: The regulatory relationship is only as strong as the people managing it. The individuals who interact with examiners — both during exams and between them — need to understand the program deeply, communicate clearly, and know when to escalate. This is not a job for whoever is available. It requires preparation, subject-matter expertise, and the confidence to have direct conversations with regulators, including when the news is not good.</p><p>The FIs that succeed in partner banking over the long term are the ones that treat regulatory management as a core competency, not a periodic inconvenience. The exam is not the test — it is just the measure of how well you have been running the program all along.</p><p>Stay tuned for the <strong>last</strong> installment of Lessons in Partner Banking…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f338a03cb665" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-6-regulators-f338a03cb665">Lessons in Partner Banking — Part 6: Regulators</a> was originally published in <a href="https://medium.com/the-finserv-minute">The Finserv Minute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons in Partner Banking — Part 5: Governance]]></title>
            <link>https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-5-governance-fbdcd655f540?source=rss----92fb042c14f0---4</link>
            <guid isPermaLink="false">https://medium.com/p/fbdcd655f540</guid>
            <category><![CDATA[financial-services]]></category>
            <category><![CDATA[baas]]></category>
            <category><![CDATA[banking-partner]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[embedded-finance]]></category>
            <dc:creator><![CDATA[Chris Rigoni]]></dc:creator>
            <pubDate>Thu, 28 May 2026 14:35:56 GMT</pubDate>
            <atom:updated>2026-05-28T14:35:57.476Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*5oNwKx8OqVIcHbvXwreOGQ.png" /></figure><p>Governance is one of those topics that gets a lot of lip service in partner banking and not nearly enough action. I have seen FIs launch partner banking programs with virtually no formal governance structure in place — no documented approval process, no change management framework, no consistent reporting. The result is almost always the same: gaps that regulators find before the FI does. Getting governance right does not have to be complicated, but it does require intentional design from the start.</p><p><em>Onboarding/Offboarding Structure</em></p><p>How an FI structures the onboarding and offboarding process says a lot about how seriously it takes governance. A well-designed structure ensures that every prospective partner goes through a consistent set of reviews, that approvals are formally documented at each stage, and that there is a clear record of the decisions made — and the reasoning behind them. This matters not just for internal accountability, but for regulators, who will expect the FI to demonstrate that every partner in the program was vetted appropriately before going live.</p><p>The same discipline applies to offboarding. FIs often spend a great deal of time designing onboarding and very little time thinking about how a relationship ends — whether that is a voluntary exit, a compliance issue, or a partner going out of business. Offboarding should be as structured as onboarding, with defined triggers, escalation paths, and documented approvals. It should also include a plan for protecting customers throughout the process.</p><p><em>Change Management</em></p><p>This is the area where I see the most gaps. Partners change — their products evolve, their technology changes, their customer base shifts — and without a formal process for managing those changes, the FI can find itself exposed to risks it never signed up for. A change management framework requires partners to notify the FI of any material change in advance. Not after the fact. Before it goes live.</p><p>What counts as material? That needs to be defined and documented — but it typically includes new product features, fee structure changes, core technology migrations, new third-party vendors, or significant shifts in the partner’s customer base or business model. The management committee should be involved in reviewing and approving changes that cross the materiality threshold. Smaller changes can be handled operationally, but they still need to be documented and tracked.</p><p>One more thing worth requiring: a post-implementation review for significant changes. This is a simple ask — the partner confirms that the change went as expected and that no new risks or issues emerged. It creates an audit trail and reinforces that the FI is actively managing the relationship, not just passively watching it.</p><p><em>Board and Management Committee Reporting</em></p><p>Reporting is where governance becomes visible. If the board and management committees lack clear, consistent, and meaningful information about the partner banking program, they cannot provide effective oversight. And if they cannot provide meaningful oversight, that is a problem — both from a regulatory standpoint and from a risk management standpoint.</p><p>Tailor the reporting to the audience. Management committees need detail — partner-level metrics, compliance findings, open issues, pipeline, and any change management items under review. The board needs a high-level summary: where the program stands, what risks are elevated, what actions are being taken. A good rule of thumb is monthly reporting to management committees and quarterly reporting to the board, though the cadence should be adjusted based on the program&#39;s size and complexity.</p><p>The most common mistake I see is FIs that over-report without context — dashboards full of data with no narrative, no trend analysis, no clear indication of what requires attention. Good reporting tells a story. It should be obvious from a single read what is going well, what is not, and what decisions need to be made. If a board member has to dig to figure out what they are looking at, the reporting needs work.</p><p><em>So What?</em></p><p>Governance does not have to be a burden. When well designed, it actually makes the program easier to run. Here is a practical guide for FIs building or improving governance for partner banking:</p><p><strong>Document the Onboarding Structure: D</strong>efine the full approval workflow from initial prospect review through go-live. Identify which stakeholders must approve at each stage, what documentation is required, and how decisions will be recorded. Make sure the offboarding process gets the same level of detail, including triggers for suspension or termination and a plan for customer protection.</p><p><strong>Define What Constitutes a Material Change:</strong> Work with risk, compliance, and legal to create a documented definition of materiality for partner changes. This should include product changes, technology changes, vendor changes, and shifts in the partner’s business model or customer base. Having this defined upfront removes ambiguity when a change comes in and ensures the right level of review is<strong> a</strong>pplied consistently.</p><p><strong>Build the Change Management Process:</strong> Require partners to submit change notifications to the FI before implementing material changes. Define how those notifications will be reviewed, who is responsible for the review, and what the approval and sign-off process looks like. For significant changes, require a post-implementation review that confirms the change was performed as expected and that no new risks were introduced.</p><p><strong>Design the Reporting Framework: </strong>Determine what needs to be reported, to whom, and how often. Management committee reporting should be monthly and detailed. Board reporting should be quarterly and focused on material risks, trends, and items requiring board-level decisions. Build a reporting package that tells a story, not just presents data, and make sure it includes trend analysis and clear indicators of what requires attention.</p><p><strong>Document Everything: </strong>Governance only works if it creates a paper trail. Every approval, every change review, and every board report should be documented and stored so they can be retrieved during an audit or exam. If the FI cannot demonstrate that the governance process was followed, for regulatory purposes, it effectively was not. Documentation is the evidence that the program is being managed responsibly.</p><p><strong>Review and Iterate:</strong> Governance structures should not be set and forgotten. Schedule periodic reviews of the onboarding process, change management framework, and reporting package to ensure they remain aligned with the program&#39;s size and complexity. As the partner portfolio grows, what worked for two partners may not work for ten.</p><p>The FIs that treat governance as an asset rather than an obligation are the ones that build programs that last. Done right, governance is not what slows partner banking down — it is what makes it possible to scale with confidence.</p><p>Stay tuned for the next installment of Lessons in Partner Banking, where we dive into how to work with regulators…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbdcd655f540" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-5-governance-fbdcd655f540">Lessons in Partner Banking — Part 5: Governance</a> was originally published in <a href="https://medium.com/the-finserv-minute">The Finserv Minute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons in Partner Banking — Part 3: Data]]></title>
            <link>https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-3-data-6e3bab5586bc?source=rss----92fb042c14f0---4</link>
            <guid isPermaLink="false">https://medium.com/p/6e3bab5586bc</guid>
            <category><![CDATA[embedded-finance]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[baas]]></category>
            <category><![CDATA[banking-technology]]></category>
            <dc:creator><![CDATA[Chris Rigoni]]></dc:creator>
            <pubDate>Thu, 30 Oct 2025 13:54:08 GMT</pubDate>
            <atom:updated>2025-10-30T13:54:06.793Z</atom:updated>
            <content:encoded><![CDATA[<h3>Lessons in Partner Banking — Part 3: Data</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*5oNwKx8OqVIcHbvXwreOGQ.png" /></figure><p>In Partner Banking, it is fun to talk about APIs, modern cores, and innovative products, but beneath those topics lies an often-overlooked requirement — data. Financial Institutions (FIs) are historically bad with data. They often lack data strategies, infrastructure, governance, controls, and basic management. In fairness, FIs haven’t historically had to worry much about data because the focus was more on the results of operational processes than on the data itself. This changes with Partner Banking because the product management, risk and compliance, and operations rely solely on data. Any FI currently in Partner Banking or considering entering it should first take a hard look at how they manage data.</p><p><em>Do the work…</em></p><p>Before even approaching data infrastructure or management, an FI needs to understand the data requirements for each facet of the workflow. This includes operations, risk, BSA, compliance, business insights, and more. While some of the data fields needed will overlap across these groups, having a robust set of requirements to define the scope of data to be managed will inform decisions on infrastructure, security, and governance.</p><p>Unfortunately, asking each of these groups, “What are your data requirements?” is likely to elicit blank stares or “What data do you have?” It is likely better to start with specific use cases and work through specific data requirements for each. While it’s necessary to put in the work to gather as many requirements as possible, in practice, data needs can change. The important part, especially in Partner Banking, is to collect those changes within expected time frames so it isn’t cumbersome for your partners. For example, data changes and requests could be gathered throughout the quarter and presented to the partners for changes once each quarter.</p><p>The types of data and specific fields needed now can inform the security and data access requirements. The volume of data —both current and projected, based on growth — should also be considered to inform infrastructure decisions. It is also important to understand the results each group would like to see from the data. Feeding data into a transaction monitoring tool is vastly different from offering high-powered analytics to the business, and each has very different tools and options to satisfy them.</p><p>Don’t forget that, in addition to technically managing the data and providing it to the business and relevant systems, policies, procedures, data governance, data access controls, data integrity, and much more should be created, documented, and approved as appropriate. Digging into data integrity controls a little deeper, this is an incredibly important component for Partner Banking, specifically.</p><p>The FI needs to do two main things:</p><ol><li>Verify that the data is received from the partner or their vendor is accurate</li></ol><p>This can be done in multiple ways, but the main goal is to ensure there is some audit and attestation that the partner or their vendor is properly managing their own data, appropriately maintaining data integrity, and has processes that produce accurate data for transmission. If the FI&#39;s reconciliation, transaction monitoring, and other processes rely on partner data, as they do, then the FI should be confident that the data they receive is accurate.</p><p>2. Verify the data received is complete and on time</p><p>Whether the FI receives data via SFTP files, APIs, or another medium, there must be some verification on the front end that the data is complete.</p><p>It should check:</p><ul><li>All fields are present that are required/relevant</li><li>Fields are accurate (e.g., all 9s aren’t entered for an SSN)</li><li>The file/data is received in full and within the expected timeframe (e.g., each day, intraday, etc.).</li></ul><p>Doing the work on the front end to ensure data integrity will save so many problems down the road. If any of the components mentioned above produce an exception, there should be a process to alert the appropriate personnel at the FI and the partner to remediate the issue and handle it as an exception, ideally without stopping all data transmission. Data integrity will enable the processes and analytics that feed them to be as impactful as they need to be for operations, risk and compliance, and the business.</p><p><em>Connect the Dots on Payments</em></p><p>One of the most complex data needs for Partner Banking is payments. This includes any payment type. While ISO 20022 has helped standardize some payment processes, the 3rd and 4th-party relationships within Partner Banking create a level of complexity that is not easily overcome.</p><p>The FI is receiving payment data from many different sources, and those sources don’t always have an organic way to match those payments to the customer, entity, or channel used. So, the FI is forced to resort to aggregate reconciliation, separate data files for transaction monitoring, and complex account structures on legacy cores to supplement the disjointed data. There are modern providers in the market that offer sidecore capabilities that go a long way to solving this issue, but it still requires thought, planning, and detailed requirements to produce the ideal state for a Partner Banking FI.</p><p>The FI is receiving payment data from the Fed, The Clearing House, the networks, or their payments vendors while simultaneously receiving transaction data from the partners or their vendors. All this data must be normalized and distributed to become useful for transaction-level reconciliation, detailed transaction monitoring, and other reporting needs. Spending time getting this right is crucial to building a solid reconciliation practice and infrastructure to scale Partner Banking.</p><p><em>So What?</em></p><p>So what is an FI to do? Getting started may seem like a daunting task, and, to be honest, it is; however, the importance of data in Partner Banking warrants allocating resources and capital to this area to be successful. Below are a few ways to get started:</p><p>An FI with an existing Partner Banking business should:</p><ul><li>Begin the process of inventory for what data you are receiving today<br>o Gather requirements, or additional requirements from stakeholder teams (risk, compliance, BSA, operations, etc.)</li><li>Identify gaps in data requirements versus data received, and plan to present those changes as ideally one request with a timeline to the partners</li><li>Verify you have documented policies, processes, and evidence around data management and governance. Create any missing documentation and gain approvals as applicable</li><li>Evaluate your infrastructure for the types of data and volumes to determine if it is sufficient to handle the data needs for the next 3–5 years, and suggest applicable changes with estimated timelines, with a risk-based priority</li><li>Evaluate partner documentation for sales and onboarding to determine if any changes are needed to set appropriate data expectations with the partners and make any relevant changes, getting approvals where needed</li></ul><p>An FI without an existing Partner Banking business should:</p><ul><li>Gather requirements from applicable stakeholder teams (risk, compliance, BSA, operations, etc.)</li><li>Form plans around data security and infrastructure, and evaluate current infrastructure to determine what gaps, and additional resources may be needed</li><li>Form policies, procedures, and evidence process around data security, governance, and management, and gain necessary approvals as applicable</li><li>Set project milestones with appropriate timelines to prepare for supporting Partner Banking as you onboard new partners</li><li>Create partner documentation to set data expectations with partners as you have sales conversations and during onboarding</li></ul><p>As mentioned before, Partner Banking is not something you try. You either do it and invest appropriately, or it is best that you do not do it at all. As an added benefit, the data investments the FI makes to support Partner Banking can also benefit the general bank. The FI’s core businesses will see efficiencies and more insight from this effort. Now that we have a plan, let’s all get to work!</p><p>Stay tuned for the next installment of Lessons in Partner Banking, where we will cover everyone’s favorite topic — risk and compliance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e3bab5586bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-3-data-6e3bab5586bc">Lessons in Partner Banking — Part 3: Data</a> was originally published in <a href="https://medium.com/the-finserv-minute">The Finserv Minute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons in Partner Banking — Part 2: Infrastructure]]></title>
            <link>https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-2-infrastructure-ce8f3cd355cc?source=rss----92fb042c14f0---4</link>
            <guid isPermaLink="false">https://medium.com/p/ce8f3cd355cc</guid>
            <category><![CDATA[financial-services]]></category>
            <category><![CDATA[banking-as-a-service]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[payments-industry]]></category>
            <dc:creator><![CDATA[Chris Rigoni]]></dc:creator>
            <pubDate>Mon, 23 Jun 2025 23:25:52 GMT</pubDate>
            <atom:updated>2025-06-20T02:17:28.370Z</atom:updated>
            <content:encoded><![CDATA[<h3>Lessons in Partner Banking — Part 2: Infrastructure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*5oNwKx8OqVIcHbvXwreOGQ.png" /></figure><p>I have said it before, and I’ll say it again — partner banking is not something you <em>try</em>. It is either a strategic focus for the FI or not. If not, numerous problems can arise, including regulatory issues, a lack of sales, and persistent partner experience issues. Infrastructure is imperative to supporting a successful partner banking strategy, and it will require investment and a focus on efficiency.</p><p><em>Invest</em></p><p>First, leadership and the Board should not assume that entry into the partner banking segment will be cheap. The best use of capital is to have a well-thought-out strategy that includes target state requirements to drive investment phases and the implementation of infrastructure investment. This will help prevent investments that do not align with the strategic direction, minimize development rework, and coordinate with projected revenue to mitigate some of the capital required for investment.</p><p>One recommendation is that as investments are made and specific teams or infrastructure are dedicated to partner banking, the FI should keep track of these and establish ways to report on the time spent on shared resources working on partner banking activities, and even report down to the time spent on specific partnerships. While investments and profit and loss may not be measured this closely at early stages, it will be invaluable to measure once the business scales further.</p><p><em>Bank-Owned Ledger</em></p><p>One consistent challenge with partner banking is managing all the transaction activity in sub-ledgers and reconciliation activities. This also impacts BSA oversight for transaction monitoring and AML requirements. The overall consensus among regulators from multiple agencies and in various States is that the FI is expected to participate in partner banking form processes and receive data that validates the sub-ledger activity and maintains updated balances and outstanding activity. Most FIs have some form of sub-ledger activity; however, the level of detail in that sub-ledger as well as the accuracy of that information over time is the areas of focus to ensure the FI can fully understand how much each end-user of each fintech holds, even without access to the entity that may be managing that sub-ledger on behalf of the partner or from the partner itself.</p><p>One way to remedy this situation is to have a bank-owned ledger that operates as a “sidecar” or “shadow” core, replicating each partner&#39;s sub-ledger. This allows the FI to accomplish multiple goals:</p><ul><li>Point-in-time or near real-time ledger of all partner balances and activity</li><li>Flow of data distribution for ancillary systems used for BSA, accounting, fraud, and other activities</li><li>Audit capability for comparison to partner ledgers during ledger oversight</li><li>Potential “ledger-as-a-service” product for partners who are unable or unwilling to manage their sub-ledger</li><li>More integrated and consistent controls for transactions, data delivery, compliance, and other defined risk tolerances</li><li>More detailed view into transaction activity for reconciliation validation and research</li></ul><p>If the FI were to choose a more modern core solution for the “side core” solution, it would also allow for more efficient and modern approaches to integration, event triggers, real-time activity, and data distribution to internal systems. The requirements will vary by FI, the products offered within their partner banking solution, and the needs of their target market; however, time and effort must be invested in building a solid set of requirements before selecting a solution to address this need. The side core is essential if a partner chooses to manage their subledger. While established players in the market are well-vetted and seasoned in managing subledger activity, partners often seek more control over this operation and potentially realize cost savings by managing it internally. This presents challenges, as most partners lack experience in managing subledgers, and the FI will require detailed oversight for this activity. To be clear, the FI will need to have detailed oversight of subledgering, regardless of whether the partner chooses to self-manage or pass it off to a vetted third party. However, partners may underestimate the work and expense that self-managing may bring, especially when it comes to meeting the FI&#39;s oversight requirements.</p><p><em>Automate</em></p><p>Infrastructure, although it may seem like a straightforward necessity, has a significant impact on the economics and efficiency of the partner banking business. The key to creating efficiencies and keeping the economics in a competitive range is to automate as much of the process as possible. There are areas where this can make a significant reduction in staffing needs, and even allow for expanding the capabilities to the core bank for its operations.</p><p>Automation is aimed at a few different goals:</p><ol><li>Working on exceptions rather than looking for them</li><li>Removing menial tasks from staff</li><li>Improving oversight and management</li></ol><p>When automating processes to ensure teams are working on exceptions rather than looking for them, look for areas where there are clearly defined criteria and teams are manually searching for items that meet those criteria. For example, in processing wires, the travel rule may apply to specific use cases. The logic used to process those wires can look for those particular cases, the criteria required for travel rule compliance, and alert if there are anomalies in any wires for exception reviews. When building the logic for automation, always ensure that you clearly document the logic, fields used, and the foundational reasoning behind the automation so that it can be presented upon request. Especially in cases of compliance, regulators may want to see and understand how these cases are handled to have confidence in the FIs’ capabilities and logic.</p><p>Removing menial tasks is often what people like to call “low-hanging fruit.” This, especially in smaller FIs, usually involves digitizing the manual functions that staff perform daily or multiple times a day. An example of this is scanning documents for review by other teams. Another example could be the delivery method for receiving documentation from partners. If an FI does not have a straightforward way to transmit data or documentation between itself and its partners, this can result in manual tasks, such as downloading from a Google Drive, saving to an internal folder, and potentially sending it to multiple internal recipients.</p><p>Improving oversight and management is the ultimate goal of the infrastructure of partner banking, generally, but it is especially true in the context of automation. Automating partner dashboards to provide real-time views into partner health, including financials, invoice payments, specific risk metrics, and other key data points, can be beneficial not only for day-to-day operations but also for management and board reporting.</p><p>While the focus has been on automation, artificial intelligence (AI) is the talk of the town and could also play a role in creating efficiencies, as well as assisting with improving the economics. In areas where there are large amounts of data, some of which is unstructured, and reviews are labor-intensive, AI can help reduce the time and resources required to process each item. Some examples include complaints, BSA alerts, and fraud monitoring. With the growing popularity of AI in the market and among investors, there are numerous examples to research for each of these, as well as additional opportunities.</p><p><em>Software</em></p><p>The need for software can be categorized into three main areas: workflow management, risk and compliance, and reconciliation. Each of these areas has unique needs, and there are many software options in the market to solve for each; however, most of the options will need customization to fit the partner banking segment and even banking generally.</p><p>Workflow management involves not only tracking the process from beginning to end, but also documenting the process, identifying who participated, and providing evidence that the process was completed. For partner banking, this also includes many cases where the partner must be a key participant in the overall process. There are several solutions in the market that offer this capability, for example, Monday.com, ClickUp, and Themis. Monday.com and ClickUp (clickup.com) can be customized to fit any broad process and are not specific to financial services, but offer a wide range of applications. Themis (Themis.com) is one of the few solutions in the market that is not only designed specifically for financial services but also has capabilities and workflows tailored for partner banking.</p><p>Risk and compliance are areas where data, reporting, and evidence are imperative for a successful program. Software will be key to organizing each process, documenting the tasks of each process, storing evidence that each process was completed, and reporting all of these to audits, whether internal or external. Software can also help with automation, send notifications to partners, and provide partners with a medium to communicate and upload documentation. These capabilities are especially valuable for issue management. Software can consolidate all comments, responses, and documentation with partners into a single location for efficient management and reporting, especially during an audit.</p><p>Reconciliation, especially in partner banking, can become quite complex. Using software to analyze all applicable values and automatically identify anomalies can create efficient processes and provide documentation on specific issues and their resolutions. This is also an area where an FI will want to analyze all requirements and examine several market options to select the best fit.</p><p>In all these instances, software solutions will require a focus on data and data delivery. The foundation of these processes will be accurate data, delivered consistently, with a complete set of required fields from both internal sources and the partner.</p><p><em>Now what?</em></p><p>Infrastructure is built based on the strategic approach and detailed with requirements from each stakeholder group and the business. It cannot be overstated how important a thorough requirement gathering process is to the success of a partner banking program. To build or enhance infrastructure to support partner banking, the FI will need to include all applicable subject matter experts in a holistic requirements gathering exercise to accomplish the goals of maintaining a subledger, automating processes, and acquiring software solutions.</p><p>Requirements gathering is, in itself, something to be managed. The FI should have program management assistance to drive and document the requirements, facilitate any request for pricing (RFP) efforts, and report progress to executive leadership and the board of directors. This will ensure the requirements are adequately documented and that the process continues to progress.</p><p>Stay tuned for the next installment that covers data.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce8f3cd355cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-2-infrastructure-ce8f3cd355cc">Lessons in Partner Banking — Part 2: Infrastructure</a> was originally published in <a href="https://medium.com/the-finserv-minute">The Finserv Minute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons in Partner Banking — Part 1: Strategy]]></title>
            <link>https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-1-strategy-fd9dc3b65a69?source=rss----92fb042c14f0---4</link>
            <guid isPermaLink="false">https://medium.com/p/fd9dc3b65a69</guid>
            <category><![CDATA[baas]]></category>
            <category><![CDATA[banking-partner]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[embedded-finance]]></category>
            <category><![CDATA[financial-services]]></category>
            <dc:creator><![CDATA[Chris Rigoni]]></dc:creator>
            <pubDate>Mon, 19 May 2025 20:29:04 GMT</pubDate>
            <atom:updated>2025-05-09T20:20:56.846Z</atom:updated>
            <content:encoded><![CDATA[<h3>Lessons in Partner Banking — Part 1: Strategy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*hafZbYv9eptaqaeHl3Bjow.png" /></figure><p>I have been involved in partner banking since the early days and have worked at different institutions of different sizes with many different approaches. In that time, I can tell you that even the most well-executed programs had areas for improvement. There are many opportunities in partner banking, but also many pitfalls. The pitfalls and opportunities often start with how much effort is put into the strategy.</p><p><strong>Strategy</strong></p><p>For a financial institution thinking about entering partner banking, it is vital to form a strategy that is more than deposit gathering, lending, or the types of products that may be offered. The strategy should span products, marketing, risk and compliance, and internal governance. This plan should be well documented and include meetings with regulators to educate and present the plan of action.</p><p><em>Products</em></p><p>If an FI is putting together a strategy for partner banking, it should first determine what target market fits with the bank’s overall strategy and core competencies. This will determine what specific products will be needed and direct where additional staffing, automation, infrastructure changes, or other needs may be necessary. The strategy should encompass not only the overall approach for each product but also how that product will be implemented to create value and remain secure and compliant.</p><p>The product sets will also have to support an overall use case. For example, if a partner offers a DDA, that likely will need ACH to fund the account and potentially a debit card product to allow the customer an easy way to use funds within the account. Some use cases may have a new or novel approach, so there should be a strategy to evaluate those use cases within the overall partner banking strategy. Formulating a strategy does not mean there will not be variables that are not initially addressed, but it does mean that there will be clear direction and documentation on how those variables will be evaluated.</p><p>One major pitfall that has unfortunately resulted in regulatory action is that FIs should not enter into business segments or transaction types in which they have no experience. For example, if an FI does not have internal experience in each facet of credit cards, it would not be a good idea to offer credit cards as a product for partner banking. The experience needed to evaluate credit card products, monitor their use, provide oversight over compliance, and manage the product set as a whole is significant and should not be viewed as simply another banking product to be added to the suite. Another great example is international transactions. A smaller FI with no prior experience providing monitoring, reporting, and action for international transactions should not offer those in a partner banking relationship.</p><p>If an FI is to offer a segment, transaction type, or product in which there is no internal experience, it must first build the necessary expertise internally by either hiring experienced personnel at each level in the organization or significantly up-skilling the current personnel to take on this new venture. Even if up-skilling, at least hire leadership-level talent to be able to drive the overall needs of the product. In some cases, this means that internal personnel need to be reorganized to best meet the needs of the new product.</p><p>Each product being offered should be detailed as to who will own it and its development, whether dedicated support personnel are available in technology, risk, compliance, etc., and what reporting will be included for oversight (both internally and from the partner). Those building the product strategy should work with internal support groups to identify key areas that must be detailed and documented before launching with any prospective partner.</p><p>As a part of the strategy, how integrations will be handled must be determined. Especially in smaller FIs, this is typically file-based because it has less infrastructure and technology investment; however, offering APIs, even at the start, can be beneficial for the partners as well as the FI. I would recommend looking into building out an API infrastructure either with internal IT resources or by bringing in consulting help to offer expertise. This can even be done in a phased approach; however, the needs of risk, compliance, and general oversight should be considered as a priority, along with product effectiveness.</p><p><em>Investment</em></p><p>As a general point for partner banking, investment will be required. There will be opportunities to utilize existing infrastructure, staffing, and technology; however, I cannot emphasize enough the need to fully evaluate those situations to determine if they are the best solution for the partner and the FI. Many times, while these existing solutions may “work,” they present challenges or deficiencies for risk, compliance, oversight, or the partner. It will be much better to find a specific area where the FI has significant experience and expertise, invest in that area, and create valuable products with insights for partners that will add to the end-user offering rather than support it. A collaborative product that solves pain points, creates efficiencies, and offers innovative solutions will have the most impact. The FI is uniquely positioned to offer direct feedback on what it has seen across its customer base. In addition, some areas may be candidates for integrating partner solutions into the internal offerings of the FI.</p><p>Once an area of focus is found, scale will be incredibly important. Whether the FI is working with early-stage partners or established players, scale is going to be an expectation as well as an imperative for the survival of the partner and the revenue of the FI. While scale for the partner likely means growing acquisition, increasing volumes of transactions or services, and building additional products to cross-sell, for the FI, scale should be considered operational for each facet of the solutions. To power the partner’s scale, the FI must be able to support increases in the following examples (depending on the product type):</p><ul><li>Increased volume through infrastructure</li><li>Increased alerts through monitoring solutions</li><li>Increased credit risk</li><li>Increased issue management needs</li><li>Increased review of product/marketing changes</li><li>Increased complaint and dispute management</li></ul><p>While the above is not an exhaustive list, it gives an idea of the areas of focus for investment in either automation or staffing to ensure the FI is prepared for scale. In the case of early-stage partners, that scale could be phased, but the FI should have an articulated and documented plan to handle that scale.</p><p><em>Industry Groups</em></p><p>Receiving input from existing FIs on challenges and useful tools, approaches, and resources significantly improves a strategy. For an FI just starting out, knowing the best consulting groups that focus on partner banking, the most useful tooling for workflow management and issue management, and other bits of knowledge are invaluable. This creates an opportunity to learn from others’ mistakes and take advantage of the current tools in the industry.</p><p>One group I highly recommend is the <a href="https://www.fintechcouncil.org/">American Fintech Council (AFC)</a>. They are an amazing and collaborative group of FIs and partners at all stages, where new entrants are welcome. The participants in the AFC are very knowledgeable and understand the challenges. They also have a line of sight into the regulatory and political landscape to give a broader view of the overall partner banking environment.</p><p>I recommend contacting FIs that have been involved in partner banking since the early days to discuss their experience and insights. Many of these FIs are willing to meet with other FIs to discuss approaches, issues, risks, etc. The partner banking world is among the most collaborative I have seen amongst FIs and partners in the financial services industry.</p><p><em>People</em></p><p>While putting together a strategy is important, it cannot be overstated how important the people participating in the planning, execution, and operation of a partner banking business strategy are to the business&#39;s success. Having people in the right positions with experience in partner banking is imperative.</p><p>There must also be an expectation and a culture of collaboration between leadership, risk and compliance, and the business. A true partnership between the three will allow risk tolerances to be set appropriately to mitigate risk and support effective revenue for the business. While there will always be tension from the pull toward risk and business, it is a positive tension to be managed, not something that should be eliminated.</p><p>Experience is also necessary in key positions to evaluate risk properly, address legal concerns, and build efficient operations. While consulting can assist in building foundational competency, constantly relying on outside counsel and consultants is not an effective business strategy. These expenses will always drive down the margins and create concerns about the long-term feasibility.</p><p>These conversations will not be easy, as they often require leadership and others to be very transparent and honest about their strengths and weaknesses, as well as those of themselves, colleagues, and employees. While this is true of every business, it is a make-or-break situation for partner banking. Competencies can be learned, but there is not always time to build competency, especially depending on the time frames associated with the strategy.</p><p><em>Now What?</em></p><p>The following is a general guide to putting together a partner banking strategy:</p><ol><li>North Star: Define what types of results would be needed to have the most impact on the FI. For example, if the FI would benefit most from increased deposits and fee revenue from payments activity but is not interested in offering credit, that sets the guiding parameters for the strategy and eliminates items that will not support those results. To accomplish this step, include business leadership and FI executives responsible for or influencing the overall enterprise strategy (e.g., Chief Executive Officer, Chief Operating Officer, Chief Revenue Officer, Chief Banking Officer, Chief Deposits Officer, etc.).</li><li>Strategic Approach: Based on the North Star, further detail the specific products offered. For example, where deposits and payments fee revenue are the focus, the products could be DDA with debit card BIN sponsorship, domestic ACH and wire, and RTP (depending on the FI’s capabilities). To accomplish this step, business leadership and executives should be included to form the overall enterprise strategy.</li><li>Target Market: Define a target market to focus on once the products and services are live. Continuing the example above, this could be neobanks (business or consumer), merchant services, payments facilitation, savings, etc. As with the above steps, business leadership and executives tied to the overall enterprise strategy should be included in this decision.</li><li>Broaden the Strategy: With the products and target market defined, more specific details of how to approach risk, compliance, IT, account management, and governance can be determined. This is where a journey map of sales, evaluation, onboarding, implementation, relationship management, oversight, change management, escalation, suspension, and termination can be vital to building a complete strategy, including tactical specifics required to drive that strategy. For this step, a broader audience will be needed, including risk, compliance, IT, operations, and other business units, to ensure adequate input from all groups.</li><li>Document: Fully document the strategy, journey map, and input in the broad approach. This should move into more tactical specifics, such as staffing for risk, compliance, and operations. This should also include high-level volume estimates that correlate to risk tolerances for growth, as well as at what point staffing should increase as volumes increase. If automation is going to be utilized in the place of staffing, how that specifically mitigates the need for additional staff should also be noted. The documentation should be thorough enough to guide policy and process documentation as the creation of the business segment is executed.</li><li>Regulators: Now that a comprehensive strategy has been formed with parameters and well-thought-out details, it is a good time to meet with regulators to present the plan of action and collaborate on any feedback they may have. Once feedback is received, it should be incorporated, and the strategy&#39;s execution is ready to begin.</li></ol><p>A well-thought-out strategy will save time and position the FI for success in partner banking as a business segment, risk, compliance, and regulatory oversight. It may take more time, but the market has shown that participation in this area will require a methodical and holistic approach.</p><p>Stay tuned for the next installment that covers infrastructure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd9dc3b65a69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-finserv-minute/lessons-in-partner-banking-part-1-strategy-fd9dc3b65a69">Lessons in Partner Banking — Part 1: Strategy</a> was originally published in <a href="https://medium.com/the-finserv-minute">The Finserv Minute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rose-Colored BaaSes]]></title>
            <link>https://medium.com/the-finserv-minute/rose-colored-baases-c739ee432655?source=rss----92fb042c14f0---4</link>
            <guid isPermaLink="false">https://medium.com/p/c739ee432655</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[baas]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[financial-services]]></category>
            <dc:creator><![CDATA[Chris Rigoni]]></dc:creator>
            <pubDate>Wed, 12 Apr 2023 15:31:28 GMT</pubDate>
            <atom:updated>2023-04-12T15:47:35.679Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*70bBWCnk4MgMXAWkvML7sA@2x.jpeg" /></figure><p>Banking-as-a-Service (BaaS) has quickly become the focal point of many banks looking to spark growth and additional revenue in today’s market. While BaaS can add revenue and provoke growth for financial institutions (FIs), it seems some looking to get into the segment may have some unrealistic expectations. It is important for any FI looking to add BaaS as a product to understand what is needed to support it as well as what realistic expectations for results should be.</p><h3>Infrastructure</h3><p>BaaS is not a plug and play service for FIs. It requires strategy and planning around the architecture as well as potential development for backend systems to supply a file-based or API service. It also will require some secure way for the BaaS partners to integrate to the FI via API, which is typically an API gateway. The API gateway some FIs use may be only currently configured to allow internal use of APIs, or have very specific use cases for certain vendors. The typical setup for most institutions is not designed for supporting BaaS immediately.</p><p>The reporting and monitoring requirements for supporting BaaS will also be different than what the current infrastructure supports for internal uses. Whether an intermediary (e.g., Treasure Prime, Unit, Synctera, etc) is used or the FI chooses to support everything internally, access to the data in the proper systems and tools to produce reports and monitoring as well as feed dashboards is imperative to supporting BaaS for IT, risk, compliance, and operations.</p><p>Payments is an important part of BaaS, and will need special attention to ensure a good experience for any partners, and ease of operation for the FI. How will the partners integrate? Is file-based integration possible? Do any current FI clients use file-based integration that can be reused? Some partners may want real-time data for certain payment methods because it feeds the specific customer experience they are seeking to create. It is also important to understand what payment methods are an expectation. ACH and wire are likely an expectation at this point, but RTP is quickly gaining traction and FedNow is on the horizon. Does the FIs current payment services include all of the expected payment methods? Does the product supplied by the payments vendor the FI uses support the necessary fields, data availability, and real-time processing to support the BaaS product the FI is seeking to create?</p><h3>Risk and Compliance</h3><p>It is no secret that BaaS offers some additional considerations for risk and compliance. While third-party risk guidance is a solid guideline for BaaS partners, the implementation of such policies in a BaaS product can be new territory for FIs. Not only is this new, but the constructs of the contracts between the FI, the BaaS partner, and any vendors the BaaS partner is using can become complex very quickly. Risk and compliance teams (and legal too for that matter) may be currently uneducated on what BaaS is much less able to fully analyze and give recommendations on the constructs, integrations, and contracts.</p><p>There also may be a need to hire more resources for risk and compliance reviews. Current teams may be at capacity with current work and new personnel would be needed to support additional reviews from a BaaS product. This can be a good opportunity to hire risk and compliance professionals with some experience in the BaaS space to give the FI a head start on creating policies, procedures, approval committees, and documentation that will support audits, internal reporting, and monitoring.</p><h3>Operations</h3><p>Operations is an area that will need significant preparation and most likely new procedures for payments, tracking and billing, account management, file processing, monitoring, downtime, and more. Situations that are commonly handled today will need additional support, review, and communication to support a BaaS construct. For example, maybe the ACH system has a failure to process a file and that file is automatically reprocessed with a file being sent to clients (including BaaS partners) may not be currently designed with BaaS partners in mind. So either the FI changes procedures internally to accommodate BaaS or works with the BaaS partner to align their processes to meet the FIs operations. Either way, work will need to be done to support BaaS.</p><p>As with Risk and Compliance, operations may be at capacity with the current clients for each segment the FI supports. Adding BaaS will require either more personnel in each existing area, or specific personnel in a dedicated BaaS operations team. In either case, it could be an opportunity to look for candidates with previous BaaS experience to give the FI an advantage in starting their program.</p><h3>Size Matters</h3><p>Aside from the areas of planning and development, FIs should have realistic expectations for revenue and growth. Once these expectations are defined, they can be used to filter the strategy and approach the FI takes to launch a successful BaaS segment.</p><p><strong><em>Large FI</em></strong></p><p>Expecting BaaS to move the needle in a meaningful way at large FIs is unrealistic. BaaS is a numbers game where some of the partners do really well. Taking on additional risk as well as supporting dedicated resources and expense just for BaaS will not produce the expected results for revenue or growth.</p><p>For larger FIs, BaaS is going to be a very niche product. A large team supporting 100s of BaaS partners will likely be a waste of time and resources for these institutions. They are far better suited to focus on well-established partners with significant deposits and fee income, as well as embedded finance players that can add a financial services offering to a thriving business in another industry.</p><p>Another avenue for BaaS at a large FI is as an innovation incubator. To partner with strategically chosen fintechs and technology providers offering a BaaS product while simultaneously vetting the service or product for internal use by the FI to its own customers can produce better customer experiences, new products, and enhancements to existing FI products.</p><p><strong><em>Regional/Super-Regional FI</em></strong></p><p>Regional and Super-Regional FIs are in an in between area for BaaS where they could benefit from a full BaaS offering and support the cost and risk in revenue and growth, while also being able to compete in embedded finance offerings to non-financially based companies. In addition to using BaaS as a innovation incubator, these institutions can also support credit needs of certain BaaS partners as well as deposit overflow for smaller FIs.</p><p>The main consideration for an FI of this size will be strategy. The BaaS product will not be able to be everything to every partner, so the FI will need to define what offerings will be the focus and what types of partners will be the target. Given the other initiatives within the FI, the other products to support, and limited resources a solidified strategy and target market will be crucial to supporting a successful BaaS segment.</p><p><strong><em>Community/Small FI</em></strong></p><p>BaaS is ready-made for the smaller FI and community bank. Whether partnering with an intermediary or building infrastructure internally, the investment in BaaS will result in deposit growth, revenue, innovation, and overall benefit for many areas of the FI. For these institutions, their position in the market makes them prime candidates for playing the numbers game with many partners and benefiting from those that even perform moderately well.</p><p>That is not to say that smaller FIs do not need BaaS strategy. They also will benefit from a target market and offerings aimed at specific industries or segments of partners; however, they can be more broad in their approach to gain the most benefit, which includes using BaaS as an innovation incubator.</p><p>Smaller FIs may not be best suited for some credit offerings, as well as larger embedded finance plays due to limitations in credit availability and deposit capacity. Smaller FIs will need to pay close attention to the growth in deposits as that will trigger additional regulatory requirements as well as potentially change interchange capabilities as they grow.</p><h3>So What?</h3><p>While BaaS is an amazing opportunity for FIs of all sizes, going into it with realistic expectations and fully understanding the investment is necessary to properly communicate the new segment to all levels of the FI, especially those c-suite and executive sponsors. This will position those advocating for BaaS for success not only in obtaining the necessary capital and resources, but also in setting and maintaining expectations for how the new segment will perform. BaaS is not a get-rich-quick gimmick, it is a segment that is providing innovation and necessary support to customers FIs may not be currently reaching.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c739ee432655" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-finserv-minute/rose-colored-baases-c739ee432655">Rose-Colored BaaSes</a> was originally published in <a href="https://medium.com/the-finserv-minute">The Finserv Minute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>