Everyman Brand Archetype
Automotive
Billing Software
Swan
Built a European embedded-banking position by making regulated accounts, cards, and payments embeddable through developer-first APIs, despite the capital, compliance, and operational complexity of financial infrastructure.
• BUSINESS MODEL
• REVENUE
• MARKET TYPE
• MARKET ENTRY
• GROWTH MODEL
• MOAT
• EDGE
1
MODEL
Swan had to prove that embedded finance could scale without becoming a services business. It built its own core banking system, obtained an e-money license, productized compliance and risk management, and scaled from sandbox testing to more than 150 customers processing over €1.5 billion monthly by 2025; this showed that regulated financial infrastructure could be delivered as repeatable software rather than bespoke bank integrations.
Question this model answers
We need to know whether our business model can scale.
BUSINESS MODEL
Platform Ecosystem
HOW THEY BUILT IT
'- Swan was founded in 2019 within eFounders to let companies embed banking features through APIs. → It removed the need for each software company to obtain licenses, build banking rails, or manage compliance independently. → Its first product let businesses offer accounts, cards, IBANs, and payments.
- It obtained a French e-money license from the ACPR and built compliance, KYC, fraud, authentication, and risk controls into the platform. → This made regulated financial functionality available as a productized service. → Swan operates across 30 European countries.
- It built its own core banking system rather than relying entirely on a third-party core. → This gave Swan control over product velocity, reliability, and unit economics. → By 2025, Swan processed more than €1.5 billion in monthly transactions.
- It monetized through account fees, card issuing, payment volume, interchange sharing, interest income, and subscription or platform fees. → Revenue scales with embedded financial activity rather than one-time implementation. → Customers include Pennylane, Factorial, Agicap, Sesame, and Lucca.
HOW TO ARCHITECT IT
1. Identify a regulated capability that many software companies need but cannot economically build themselves; validate that the existing workaround is slow, expensive, or compliance-heavy.
2. Secure the regulatory prerequisite before promising broad distribution, because licenses, capital, and compliance controls determine what can be sold.
3. Build a developer-first integration layer so customers can embed the capability without becoming financial institutions.
4. Productize risk, identity, fraud, reconciliation, and reporting; otherwise every customer becomes a bespoke compliance project.
5. Choose a revenue model tied to ongoing financial activity—accounts, transactions, cards, or balances—rather than implementation alone.
6. Avoid launching broad financial products before unit economics and risk controls are proven; the common mis-build is acquiring customers with cheap implementation while underestimating compliance, fraud, and capital costs.
DISTRIBUTION MODEL
Developer/API-Led, Direct Sales, Enterprise Sales, Partnerships
HOW THEY OPERATIONALIZED
'- Swan offered a self-serve sandbox so developers could begin testing without a sales process, lowering technical adoption friction.
- Direct and enterprise sales targeted SaaS companies, HR platforms, accounting tools, and marketplaces that wanted embedded financial features.
- Partnerships with Mastercard, banking partners, and European financial infrastructure providers enabled card issuing, payments, and compliance at scale.
- Named customers such as Pennylane, Factorial, Agicap, Sesame, and Lucca created credibility with other European software platforms.
HOW TO REPLICATE WHAT WORKED
What Worked
Let developers test quickly, then use enterprise sales to convert validated integrations into regulated, revenue-generating deployments.
Trap if Copied Blindly
Developer-led adoption fails if the product cannot pass compliance, risk, and operational review; the cost is long implementation cycles and unprofitable custom work.
Insight on Untapped Business Model / Gaps / Pitfalls
GOLDMINE
GOLDMINE 1 — VERTICAL EMBEDDED FINANCE. Generic accounts and cards are becoming commoditized; the opportunity is embedding finance into a specific workflow such as healthcare payments, construction subcontractor payouts, logistics factoring, or marketplace seller capital.
GOLDMINE 2 — COMPLIANCE AS A PRODUCT. Many BaaS providers treat KYC, AML, and transaction monitoring as back-office cost; packaging explainable, auditable compliance workflows can become a premium enterprise capability.
GOLDMINE 3 — BALANCE-SHEET-LIGHT FINANCIAL PRODUCTS. The larger opportunity is orchestrating lending, insurance, and savings through partners while retaining the customer relationship and data layer, avoiding the capital intensity of direct lending.
THE TRAP TO WATCH
THE PIT — API COUNT AS A PROXY FOR VALUE. A broad API catalog does not create revenue unless customers activate end users and generate ongoing financial activity.
THE SECOND PIT — IMPLEMENTATION-LED REVENUE. Custom integrations can create headline customers but consume engineering capacity and reduce scalability if not converted into productized modules.
MOVE WITH CAUTION
Do not enter BaaS without a clear answer on who bears fraud, compliance, capital, and reconciliation risk; a partner-bank dependency can turn a software business into a regulated operations business.
2
MARKET
MARKET TYPE
Emerging Market
WHY THEY WON
Embedded finance was an emerging market when Swan launched. SaaS companies wanted to offer accounts, cards, and payments, but most lacked licenses, banking relationships, compliance teams, and core infrastructure. Swan reframed the opportunity from “payments integration” to “become a fintech without becoming a bank.” This changed the buyer from a payments manager to a product and executive team seeking new revenue and retention. The market later matured as regulators scrutinized BaaS, partner banks tightened controls, and customers demanded predictable unit economics. The transferable lesson is that emerging regulated markets reward entrants that turn compliance from a barrier into a productized capability, but only if they can control risk and unit economics.
Swan entered European BaaS against Solaris, Railsr, Modulr, Mangopay, and bank-led embedded-finance programs. Its wedge was a developer-first API combined with a self-built core, productized compliance, and localized European banking capabilities, rather than simply reselling another bank’s infrastructure.
Question this model answers
We are entering a crowded market.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
Swan entered by building a new embedded-banking infrastructure layer rather than acquiring a bank or launching as a consumer neobank. It targeted European software companies that wanted to offer financial features inside their own products. The critical bet was that a developer-friendly API, combined with a regulated e-money license and managed compliance, could unlock demand from SaaS platforms. This required regulatory approval, banking and card-network relationships, risk systems, and technical reliability. The founder-level lesson is that greenfield entry in regulated markets works when the entrant removes both technical and regulatory barriers. It fails if the company treats licensing as a checkbox rather than an operational capability.
FOOTHOLD STRATEGY
Wedge Strategy
THE HOW
Swan’s first wedge was European SaaS companies needing embedded accounts, cards, IBANs, and payments. Developers could test through a sandbox, while product leaders saw a way to add financial features without becoming regulated entities. These customers could pay because embedded finance created interchange, interest, subscription, and retention upside. The expansion path moved from API access to enterprise deployments across payroll, accounting, expense management, and marketplaces.
MARKET TYPE PLAYBOOK
RULE 1 — EDUCATE THE BUYER ON THE OPPORTUNITY. SaaS companies can offer accounts, cards and payments without becoming banks.
RULE 2 — PROVE THAT RISK IS MANAGED. Regulatory, fraud and operational risks must be controlled.
RULE 3 — DO NOT RELY ON TECHNICAL EASE. APIs alone do not convince a regulated buyer.
RULE 4 — EXPECT MISSING CAPABILITIES. Most SaaS companies lack licences, banking relationships and compliance teams, so the infrastructure must provide them.
In an emerging regulated market, the entrant must educate buyers on the opportunity while proving that regulatory, fraud, and operational risks are managed.
Technical ease alone is insufficient.
GENERAL RULES
WHAT HAPPENS IN THIS MARKET TYPE
RULE 1 — Enter when you can create a new infrastructure layer. Embeddable accounts and cards sit between banks and software.
RULE 2 — Control the regulatory prerequisite. A licence is the foundation.
RULE 3 — Productize compliance, risk and support before scaling acquisition. Customers rely on them.
RULE 4 — Reject greenfield entry when the regulatory prerequisite cannot be controlled. The layer then depends on others.
Use greenfield entry when you can create a new infrastructure layer and control the regulatory prerequisite.
Ensure compliance, risk, and support are productized before scaling customer acquisition.
Target customers whose product becomes more valuable when financial activity is embedded.
Start with a narrow financial capability, then expand only after activation and unit economics are proven.
HOW TO APPLY FOOTHOLD STRATEGY
RULE 1 — Target customers whose product becomes more valuable when financial activity is embedded. Embedded accounts raise their revenue.
RULE 2 — Start with a narrow financial capability. Accounts, cards, IBANs and payments come first.
RULE 3 — Expand only after activation is proven. Customers must use what they integrate.
RULE 4 — Expand only after unit economics are proven. Regulated products carry cost.
Swan’s wedge was European SaaS companies needing embedded accounts, cards, IBANs and payments, with developers testing through a sandbox; failure occurs when it expands beyond the narrow capability before activation and unit economics are proven.
HOW TO APPLY MARKET ENTRY STRATEGY
Swan built a new embedded-banking infrastructure layer for European software companies rather than acquiring a bank or launching a consumer neobank; failure occurs when compliance, risk and support are not productized before scaling acquisition.
PATTERNS OF THIS MARKETING MODEL
PATTERNS IN DEVELOPER-FIRST REGULATED INFRASTRUCTURE:
1. SANDBOX ACCESS CREATES TECHNICAL QUALIFICATION. Developers can validate feasibility before compliance and procurement enter.
2. REFERENCE CUSTOMERS REDUCE REGULATED RISK PERCEPTION. Named platforms demonstrate that the infrastructure works in production.
3. REGULATORY EXPERTISE BECOMES A SALES ASSET. Buyers pay for the vendor’s ability to manage licensing, KYC, fraud, and reporting.
WEAKNESS
Implementation complexity. Regulated integrations often require legal, risk, and operational work beyond the developer’s initial API test.
GROWTH CAMPAIGNS
Developer sandbox and API documentation; customer case studies with Pennylane, Factorial, Agicap, Sesame, and Lucca; Mastercard partnership; European expansion campaigns; embedded-finance education and regulatory thought leadership; Series B and €42 million growth funding announcements.
| So What
Swan’s strongest commercial proof is not the API itself but the fact that operating platforms such as Pennylane and Factorial embedded financial activity into their products.
| Key Learning
Regulated infrastructure sells best when the customer can see a direct revenue or retention mechanism, not merely technical capability.
| How to Use
If you sell infrastructure, quantify the customer’s incremental revenue, retention, or cost reduction per activated end user, then use that model as the core enterprise-sales proof.
3
MONEY
REVENUE MODEL
Transaction Fee, Interest, Subscription
Swan monetizes across account fees, card issuing, payment volume, interchange sharing, interest income, and subscription fees. Its revenue scales with the financial activity of end users rather than implementation alone, aligning platform income with embedded-product usage.
Question this model answers
We need to choose the right pricing metric.
PRICING STRATEGY
Flat Rate Pricing, Transaction Fee, Revenue Sharing
WHY THEY WON
Customers pay platform and account fees, while Swan earns transaction and interchange economics from card usage and payments. Interest on balances and financial products can add revenue where applicable. The meter is active accounts, payment volume, card transactions, and balances; revenue expands as customers activate more end users and financial flows. Margin depends on compliance, fraud, capital, and partner-bank costs.
TARGET AUDIENCE
SaaS platforms and marketplaces (custom BaaS contracts; want embedded accounts, cards, and payments); HR and payroll platforms (enterprise contracts; want salary, expense, and payout workflows); accounting and expense-management platforms (enterprise contracts; want payment automation and financial controls); fintech builders (usage-based contracts; want regulated infrastructure without licenses).
Swan uses custom pricing based on accounts, cards, transactions, and embedded financial products. Customers may share interchange, earn interest-related economics, or pay platform and subscription fees. The strategic consequence is scalable upside, but pricing must account for compliance and risk costs.
CUSTOMER BUYING BEHAVIOUR
A product or executive team identifies embedded finance as a revenue or retention opportunity, evaluates APIs and regulatory coverage, then involves legal, risk, compliance, and security stakeholders. A sandbox test may precede a commercial pilot and enterprise contract; deployment often includes KYC, card issuing, and payment-flow integration.
WILLINGNESS TO PAY
CORE INSIGHT
Customers are not buying APIs; they are buying a regulated revenue and retention layer inside their own product.
RULES OF ADOPTION
RULE 1 — PRICE THE FINANCIAL ACTIVATION. An account or card has value only when end users transact, hold balances, or use financial workflows.
RULE 2 — SELL NEW REVENUE, NOT INFRASTRUCTURE. Customers justify spend through interchange, interest, subscription, or retention upside.
RULE 3 — CHARGE FOR REGULATORY CERTAINTY. Licensing, KYC, fraud, and reporting reduce the customer’s need to become a financial institution.
RULE 4 — WATCH THE VENDOR COST TRAP. Compliance, fraud losses, capital requirements, and partner-bank fees can rise faster than transaction revenue.
The buyer is really buying embedded financial monetization, evidenced by the active-account, transaction-volume, and interchange budget.
REVENUE RISK
Regulatory tightening: BaaS oversight, AML enforcement, and partner-bank requirements can slow onboarding and raise compliance cost.
Fraud and compliance losses: identity fraud, transaction abuse, or sanctions failures can create direct losses and regulatory exposure.
Partner-bank dependency: changes in banking partners, capital requirements, or risk appetite can interrupt product delivery.
Low end-user activation: customers may integrate accounts or cards but fail to generate transaction volume, limiting revenue.
Commoditization: card issuing and payment APIs are increasingly standardized, pressuring fees.
Customer concentration: reliance on a small number of high-volume platforms creates renewal and volume risk.
Swan is privately held; it raised a €42 million extension in 2025, and standalone ARR is not publicly disclosed.
4
MOTION
Swan depends on partnerships with banking and card-network infrastructure to deliver regulated accounts, cards, and payments. Its Mastercard relationship, banking partnerships, and embedded deployments with Pennylane, Factorial, Agicap, Sesame, and Lucca show that partners provide both regulated capability and market access.
Question this model answers
We need to use partnerships to reach customers.
GROWTH EXPANSION MODEL
Geographic Expansion, Ecosystem Expansion
HOW THEY EXPAND
Swan expanded from France into European markets through regulatory coverage, localized products, and API-led distribution. It expanded its ecosystem through card networks, banking partners, and embedded deployments in accounting, HR, expense-management, and marketplace platforms.
COMPETITIVE STRATEGY
Partnership Growth
HOW THEY COMPETE
A developer tests Swan in a sandbox → a SaaS platform embeds accounts, cards, or payments → end users activate financial features and transact → Swan earns account, transaction, interchange, and subscription economics → customer success and regulatory reliability lead to expansion across the customer’s markets and products. The compounding trigger is end-user financial activation: more active accounts and transactions increase revenue without proportional sales cost. The engine weakens if activation is low, fraud rises, or regulatory constraints slow onboarding. A founder can reproduce this by selecting customers whose core workflow naturally produces financial transactions.
GTM
Swan uses a developer-led, partnership-supported, enterprise-sales GTM.
$5–10M ARR
Developers begin with sandbox access and documentation; product and executive stakeholders evaluate embedded-finance upside; compliance, legal, and risk teams validate the regulatory model. Enterprise sales converts pilots into commercial contracts, while banking and card-network partnerships enable delivery. The primary motion is enterprise sales supported by developer-led technical validation. The founder-level implication is that regulated infrastructure requires a dual motion: technical ease to start and operational credibility to scale.
SUSTAINING MOATS
Regulatory Advantage
The moat is Swan’s regulatory and operational infrastructure: its e-money license, compliance systems, risk controls, banking relationships, and self-built core. These make it difficult for a software company to replicate embedded banking quickly without accepting regulatory and capital complexity.
| Why This Moat Lasts
A regulatory moat lasts when licenses, compliance operations, and risk controls are embedded in the product rather than outsourced entirely.
| Standard Rules
RULE 1 — LICENSES CREATE A TIME BARRIER. Obtaining and maintaining regulatory permissions takes capital, expertise, and ongoing oversight.
RULE 2 — COMPLIANCE OPERATIONS COMPOUND WITH SCALE. KYC, fraud, sanctions, and reporting systems improve with transaction data and operational learning.
RULE 3 — CORE CONTROL CREATES PRODUCT VELOCITY. Owning more of the stack enables faster localization and iteration than a thin reseller model.
| The Signal
Swan operates in 30 European countries, processes more than €1.5 billion monthly, and serves more than 150 companies. The moat does not protect against regulatory change, partner-bank failure, fraud losses, or customers choosing a bank-led alternative.
ARR
JOURNEY
Pre-$1M ARR
SECURE THE REGULATORY PREREQUISITE. Founded in 2019, Swan obtained an e-money license from France’s ACPR and built APIs for accounts, cards, IBANs, and payments.
WATCH: whether compliance could be productized rather than handled as bespoke work.
$1–5M ARR
PROVE DEVELOPER-LED ADOPTION. Swan launched sandbox access and targeted European SaaS platforms seeking embedded financial features.
WATCH: whether API tests converted into production deployments.
$5–10M ARR
LAND REFERENCE CUSTOMERS. Swan signed platforms such as Pennylane, Factorial, Agicap, Sesame, and Lucca, creating credible proof for other European software companies.
WATCH: implementation complexity and customer concentration.
$10–50M ARR
SCALE EUROPEAN INFRASTRUCTURE. The company raised a €37 million Series B in 2023, expanded across Europe, and scaled card issuing and payment volumes.
WATCH: fraud, compliance, and partner-bank dependencies.
$50–100M ARR
NOT REACHED based on available public evidence. The likely strategic requirement is increasing end-user activation and financial-product revenue per customer.
$100M+ ARR
NOT REACHED based on available public evidence.
BREAKDOWN
THE STANDARD
Build regulated infrastructure by turning a compliance barrier into a productized capability, then monetize the customer’s ongoing financial activity.
THE SEQUENCE
1. Identify a regulated capability that many software companies need but cannot build; prerequisite: a clear regulatory pathway and risk model.
2. Build a developer-first integration layer and productized compliance workflow; decision gate: customers can move from sandbox to production without bespoke regulatory work.
3. Expand into adjacent financial products only after accounts, cards, or payments generate recurring activity; prerequisite: proven activation, fraud control, and unit economics.
Swan combined a self-built core, e-money licensing, and developer sandbox access to scale embedded banking across European SaaS platforms.