White-label BaaS is not core banking. Buying the wrong category is expensive.

Last month, I had a conversation with a founder who was picking between two products for his neobank: a major core banking platform and a white-label orchestration vendor. I told him those are different categories of product. He pushed back. He had a comparison spreadsheet with sixteen criteria, and both vendors were on it. He had spent six weeks on this evaluation, still I recommended him to start over.

This essay is about why.

The category confusion between core banking platforms and BaaS orchestration platforms costs buyers real money, and creates persistent mispricing for vendors. The terms get used interchangeably in marketing copy, in industry analyst reports, and in board decks. They refer to fundamentally different things. A buyer who confuses them ends up either paying for capability they will never use, or buying something that will not do what they actually need.

I run one of the orchestration vendors. My commercial interest in this distinction is obvious. The argument still holds.

The three layers of a modern fintech product

Every modern fintech product, taken apart, has three layers stacked together.

The licence layer. The regulated entity that holds permission to take deposits, issue payment instruments, hold customer funds, and so on. Either you own it (you went through licensing yourself, which takes 12 to 36 months and costs anywhere from low six figures to several million depending on jurisdiction and scope), or you rent it from a BaaS provider that holds the licence and lets you operate as their agent or distributor.

The provider layer. The set of regulated and unregulated services your product depends on. Card issuing and processing. Payment rails. KYC and AML compliance. Treasury and custody. FX. Statements and reporting. None of these you build. All of these you integrate.

The orchestration layer. Everything that sits between the licence plus provider stack on one side, and your customer-facing application on the other. It holds the business logic for your product. Account opening flows. Fee structures. Limits and risk rules. Customer-facing balances and statements. Notifications. Cards lifecycle. Multi-currency wallets. The customer-facing API or app that your users actually touch.

Core banking products live primarily in the orchestration layer, or partly in the licence layer if you are a real bank with your own ledger. They give you a ledger, accounts, transactions, often a configurable product engine. They are built for institutions running their own banking licence and full balance sheet. The implementation cycle is 12 to 24 months. The cost runs into the high six figures or more before you have onboarded a single customer.

White-label BaaS orchestration platforms also live in the orchestration layer, but they make different assumptions. They assume you are connecting an existing licence (yours or a provider’s) to existing providers (cards, KYC, payments) and need to assemble those connections into a customer-facing product fast. They give you the application layer, the integration adapters, the configurable product engine, and the customer-facing UX components. The implementation is six to fourteen weeks. The cost is six figures, on the lower end, with predictable monthly fees from there.

Both produce a working banking product at the end. They get there along very different paths.

What the category confusion costs buyers

A founder building a niche neobank for SMEs in Poland comes to market. She has 18 months of runway, a head of product, three engineers, and no banking licence. Her plan is to use a BaaS provider for the licence and ledger, integrate a card issuer, and ship a clean product to her segment.

She gets pitched by a major core banking platform. She likes the brand. She knows VCs respect it. The sales conversation is professional, the demo is convincing. The implementation timeline is twelve months. The licensing cost alone exhausts a quarter of her runway. Her engineering team starts building integrations between the core banking platform and the BaaS provider she selected.

Six months later, her runway is half gone. She has burned cash on platform seats, on integration work, on a system architect to manage the complexity. She has not shipped to a single customer. She has built a beautiful core banking platform that duplicates the ledger her BaaS provider already runs.

She bought the wrong category.

The mirror case happens too. A neobank founder buys an orchestration platform with the assumption it will give him a full ledger and his own books of record. He discovers, painfully and slowly, that the orchestration platform sits on top of someone else’s ledger by design. If he wanted to be the bank in the legal and regulatory sense, he needed core banking. He bought the wrong category.

In my own pipeline, I see this confusion in 30 to 40% of inbound conversations. The buyer is exploring options without a clear mental model of the layers. The right answer for them might be an orchestration vendor. It might be a core banking platform. It might be a BaaS provider with a thin layer of bespoke development on top, with no platform purchase at all. The category confusion makes the conversation longer, the evaluation messier, and the eventual decision more random.

What the category confusion costs vendors

The mirror cost lands on vendors as mispricing.

When a core banking sales team is benchmarked against an orchestration vendor in a buyer’s spreadsheet, the core banking vendor looks expensive. The buyer asks why €300k for setup when the orchestration vendor does it for €25-30k. The accurate response from any core banking vendor in this position is that they are delivering a different product. The buyer, who wanted to compare and contrast, hears excuses.

When an orchestration vendor is benchmarked against a core banking platform, the orchestration vendor looks cheap to the point of suspicious. Buyers conclude the vendor must be missing something, must be early-stage, must not be safe to depend on. The accurate response, that orchestration vendors are correctly priced for the orchestration layer scope and core banking vendors are correctly priced for the core banking scope, does not fit on a comparison spreadsheet.

The market has not standardized vocabulary for the layers, and until it does, every vendor in this space spends sales cycles correcting the framing before they can price. Honest vendors lose deals to better-positioned ones. Less honest vendors take advantage of buyer confusion to oversell. Both outcomes hurt the buyer, the second more than the first.

When each category is the right answer

Roughly four buyer profiles, in my experience, with rough rules.

A bank or licensed institution building its own ledger from scratch with full deposit-taking and balance sheet operations. Buy core banking. The implementation cost and timeline are justified because you are operating the most regulated and balance-sheet-intensive layer of the stack. Cutting corners here creates regulatory and operational risk that exceeds the savings.

A regulated EMI or payment institution with a licence, building product on top of provider relationships. Use white-label orchestration. The orchestration layer is what you actually need. Core banking is overkill and slow. A direct BaaS provider integration is too thin and gives you no platform leverage as you grow.

An early-stage fintech without a licence, prototyping product. Use a BaaS provider with whatever thin glue they offer. Do not buy a platform yet. Spend the cash on customer acquisition and product validation. Once you have validated the product and have a clearer picture of which provider relationships are core vs replaceable, evaluate orchestration.

A large bank or scaled fintech moving off legacy systems. The decision is harder and depends on the appetite for transformation. Often hybrid: core banking for the ledger, orchestration for the customer experience. The interesting recent shift in this segment is buyers willing to combine layers from different vendors instead of going all-in on one stack.

The fast tell: if you do not hold a deposit-taking licence and do not intend to within 24 months, you do not need core banking. You need orchestration plus a BaaS provider.

Why the conflation persists

Three reasons.

Marketing language overlaps. Every vendor in this space describes itself as a “banking platform” or “banking infrastructure” because those terms test best in B2B fintech buyer surveys. Vendors do not differentiate themselves by saying “we are orchestration, not core” because most buyers do not know what those words mean and the marketing team does not want to teach them. So everyone describes themselves at the same abstraction level.

Industry analysts have not standardized the taxonomy. BaaS reports, banking platform surveys, vendor maps. They use overlapping categories. “BaaS platform” can mean a provider holding the licence, an orchestration vendor, a core banking provider, or a card issuer. Buyers reading these reports do not get a clean mental model.

Buyers come from non-technical backgrounds. The CEO of a fintech is often not the architect. They have raised the round, they have hired the team, but they do not always have a layered mental picture of what they are buying. The first vendor that explains the layers clearly often wins the business because they made the buyer feel competent. The first vendor to confuse the buyer further often loses, regardless of product fit.

This will not resolve quickly. The taxonomy is still forming. In the meantime, every buyer evaluation should start with a layer diagnosis, before a vendor list.

A five-minute diagnosis for buyers

When a founder asks me where to start, I run a short diagnostic before the vendor question even comes up. Four questions.

Question 1: Do you hold or intend to hold a banking, EMI, or payment institution licence? If no, you are a BaaS provider buyer plus probably an orchestration buyer. If yes, you need to know what the licence permits and what your ledger requirements look like.

Question 2: Where does your customer-facing differentiation live? UX, product features, fee logic, segment-specific flows. If those are core to your value proposition, you are an orchestration buyer. If your value sits in regulated infrastructure itself (rare for new entrants), you might be a core banking buyer.

Question 3: What is your time to launch? If under six months, you are not buying core banking. The implementation cycle alone makes that impossible. You are either buying orchestration or going direct to a BaaS provider.

Question 4: What is your customer concentration? Highly concentrated, regulated B2B customer? Probably orchestration with custom development on top. Highly fragmented retail? Off-the-shelf orchestration plus standard providers will do.

These four questions resolve the category for 80% of cases. The remaining 20% are interesting and need real work. You do not need to look at vendor demos to do this diagnosis. You need to look at your own business.

What I tell founders to do this quarter

If you are early in evaluation, write down the layers you actually need before you take a single vendor call. Decide whether you are a licence holder or a licence renter. Decide whether your differentiation lives in the orchestration layer or below it. Decide your launch window.

If you have already started evaluations and your spreadsheet has core banking and orchestration vendors on the same comparison, throw the spreadsheet away. Diagnose first. Compare like-for-like in the second pass. You will save weeks of evaluation time and you will end up with a better decision.

If you have already bought the wrong category, the answer is rarely “rip and replace.” The answer is usually to limit losses, ship what you can on what you bought, and make a cleaner second decision when the time comes. Sunk cost is real. Compounding the mistake is worse than living with it.

The category distinction matters because the layers are real. The costs of the mismatch are real. The vendor landscape is going to keep getting more crowded, not less. Buyers who learn the layers buy better products at fairer prices, get to market faster, and waste less of the runway investors gave them. That is the whole game.