top of page

Financial Services

FinTech

Expense Management Software

Melio

Won by letting U.S. small businesses pay vendors through their preferred funding method while vendors received conventional payment rails, monetizing payment choice and embedded distribution despite BILL, banks, and accounting-platform incumbents.

1

MODEL

BUSINESS MODEL

Transaction-Based Platform

- Founded in 2018 by Matan Bar, Ilan Atias, and Ziv Paz to simplify SMB AP and AR around cash-flow control. [20][17][19] - The core mechanism separates how a business pays from how a vendor is paid: a payer can fund with bank transfer or card while the vendor receives ACH or check. [18] - It offers a free entry tier with limited ACH payments, then charges subscriptions and transaction fees for card funding, extra ACH, checks, expedited rails, and international payments. [21][18] - Melio embedded its AP/AR workflows into QuickBooks, Xero, Amazon Business, Capital One, Shopify, Gusto, Clover, and Fiserv. [20][22][23][24] - By FY25, it served more than 80,000 customers, processed over $30 billion in payments, and generated $153 million revenue. [25]

1. Find a transaction where the buyer and recipient prefer incompatible payment methods or timing. 2. Build an intermediary that translates between the two sides without forcing either side to change behavior. 3. Give away the basic transaction path to create volume, then monetize convenience, speed, funding flexibility, and control. 4. Embed the workflow into platforms that already own the customer relationship, while retaining the transaction and data layer. 5. Expand only into adjacent cash-flow workflows once payment volume proves retention and unit economics. Avoid monetizing only the free baseline transaction; the model requires a high attach rate on value-added payment options. [21][18][19]

DISTRIBUTION MODEL

Small businesses lacked finance teams and needed to manage vendor bills, cash timing, and payment methods without enterprise AP systems. Melio addressed the frequent pain of paying a vendor by card while the vendor accepted only ACH or check; its platform decoupled payer funding from vendor receipt and reduced manual payment work. [17][18][19]

HOW THEY BUILT IT

HOW TO ARCHITECT IT

Embedded Distribution, Partnerships, Product Integrations, Self-Serve / Website

HOW THEY OPERATIONALIZED

HOW TO REPLICATE WHAT WORKED

dm

- QuickBooks partnership in 2020 supplied “Bill Pay powered by Melio” to QuickBooks users. [22] - Capital One, Shopify, Gusto, Clover, and Fiserv embedded or syndicated Melio’s AP/AR capability to their SMB audiences. [20][22][24] - Fiserv’s CashFlow Central reached more than 3,500 financial-institution clients. [23] - Direct self-serve acquisition captured U.S. SMBs through melio.com, while accountants and bookkeepers served as trusted referral partners. [26][25]

What worked: Melio treated its payment engine as embeddable infrastructure, letting banks and vertical SaaS platforms distribute it under their own brands. Trap if copied blindly: embedded distribution can commoditize the vendor if the host owns branding, customer data, pricing, and the end-customer relationship; retain proprietary workflow depth and transaction economics. [20][27][18]

|  PATTERNS OF THIS MODEL

PATTERNS IN EMBEDDED B2B PAYMENTS PLATFORMS: 1. Payment-method translation creates a monetizable wedge. The platform earns when it removes a mismatch between payer funding and recipient acceptance; Melio’s card-to-check/ACH capability is the clearest example. [18] 2. Embedded distribution trades brand for reach. Bank and SaaS syndication lowers CAC but can reduce pricing power and customer ownership. [20][27] 3. Free baseline volume finances selective monetization. Standard ACH can be low- or no-fee while card funding, speed, and international rails carry higher fees. [21][18] THE WEAKNESS: revenue depends on the share of transactions that choose paid rails, making attach rate—not total payment volume—the true growth metric. [18][19]

What companies with this model reveal

|  OPPORTUNITY INTELLIGENCE

GOLDMINE 1 — CASH-FLOW-AWARE PAYMENT ORCHESTRATION. SMBs do not merely want to pay bills; they want to choose timing and funding source against receivables and working capital. A platform that recommends “pay now by card, pay later by ACH, or finance this invoice” can monetize optimization rather than execution. GOLDMINE 2 — VERTICAL EMBEDDED AP. Industry software in construction, healthcare, logistics, and franchises can own vendor networks and compliance context that horizontal tools lack. GOLDMINE 3 — ACCOUNTANT-LED CASH COMMAND CENTERS. Accounting firms can productize multi-client AP/AR oversight rather than reselling software seats. THE PIT — FREE PAYMENTS AS A GROWTH STRATEGY. Free ACH builds volume but not necessarily revenue; without paid-rail attach, gross payment volume is vanity. THE SECOND PIT — HOST-PLATFORM DEPENDENCE. If QuickBooks, a bank, or vertical SaaS owns the customer and can internalize payments, the embedded vendor risks disintermediation. MOVE WITH CAUTION — do not build card-funded B2B payments without interchange, fraud, chargeback, settlement, and capital-risk controls; the percentage fee looks attractive only after those costs are understood. [21][22][18][19]

Untapped Business Model / Gaps / Goldmines / Pits

Patterns & Insights

2

MARKET

mkt mt es

Melio entered a market with BILL, banks, accounting software, and conventional AP tools. Its buyer-relevant difference was payment flexibility: a small business could pay by card while the vendor received ACH or check, plus simple AP/AR workflows designed for firms without finance departments. This reframed the decision from “AP automation” to “control how and when cash leaves the business.” [17][18][19]

MARKET TYPE

Red Ocean

ENTRY STRATEGY

Direct Entry

WHY THEY WON

SMB bill pay is a Red Ocean: BILL, banks, accounting platforms, card issuers, and payment processors all compete for related workflows. Melio exploited a structural opening—existing AP tools focused on automation, while small businesses needed cash-flow flexibility and low-friction vendor payment. Its card-funding mechanism created a distinct reason to switch without requiring vendors to adopt new technology. The transferable lesson is that a crowded market can be entered by changing the buyer’s decision criterion from workflow automation to payment choice and cash timing. [17][18][19]

EXECUTION

Melio launched its own U.S. SMB payments product rather than acquiring a customer base or entering solely through a host platform. Its initial product let small businesses enter vendor details, schedule payments, and choose funding and delivery methods; QuickBooks integration followed in 2020. [22][17][19] The critical bet was that payment flexibility, not feature depth, would win the first SMB user. This required payment-rail partnerships, fraud controls, and a simple onboarding experience; it would fail where payment economics could not support free baseline transactions or where regulatory and card-processing costs were underestimated. [17][18][19]

FOOTHOLD STRATEGY

Wedge Strategy

The first wedge was U.S. small businesses paying vendors without an internal finance function. They were reachable through direct web signup, accountants, and QuickBooks; they could pay because late payments, cash constraints, and manual payment administration were immediate problems. Once Melio owned bill payment, it expanded into receivables, accountant tools, and embedded AP/AR infrastructure for banks and SaaS platforms. [26][22][24][19]

GROWTH CAMPAIGN

CAMPAIGNS THAT WORKED

SO WHAT: Melio’s most important campaigns converted existing platforms’ SMB trust into payment volume rather than building awareness from zero. KEY LEARNING: when the product is infrastructure, the highest-leverage campaign is a branded integration that makes the vendor’s capability feel native to the host. HOW TO USE: test one host-platform integration where the host has a large SMB base but lacks your specific workflow; structure economics so both sides gain from transaction volume, not merely lead referral. [22][23][24]

KEY LEARNING

THE STANDARD: In a Red Ocean, entrants win by making buyers compare a new outcome rather than incrementally better features. RULE 1 — DEFINE THE INCUMBENT’S BLIND SPOT: SMB customers are cash-constrained and understaffed; the gap is payment flexibility and simplicity, not enterprise workflow depth. RULE 2 — EXPECT PRICE PRESSURE: free or low-cost baseline transactions are often necessary to enter. RULE 3 — SUCCESSFUL ENTRANTS EMBED OR FLANK: they attach to trusted platforms instead of fighting banks and accounting systems head-on. RULE 4 — COMMON FAILURE: copying a horizontal feature set without a differentiated transaction mechanism or distribution advantage. MARKET TYPE: Red Ocean (category). [22][17][18]

gc

Market Context

|  MARKET INTELLIGENCE

PATTERNS IN EMBEDDED DISTRIBUTION WITH SELF-SERVE ENTRY: 1. HOST-PLATFORM BORROWED TRUST. QuickBooks, Capital One, and Fiserv reduce the credibility barrier for a payments product. [22][23] 2. FREE ENTRY CREATES TRANSACTION HABIT. The Go plan and limited free ACH make adoption easy before monetized payment options appear. [21][18] 3. SYNDICATION MULTIPLIES REACH WITHOUT BRAND BUILDING. White-label infrastructure lets banks and SaaS firms distribute the capability at scale. [20][27] 4. THE WEAKNESS: embedded channels can suppress direct brand equity and leave the platform exposed if a major host builds payments in-house. [27][18]

|  MARKET ENTRY PLAYBOOK

THE STANDARD: Direct entry is appropriate when the founder can deliver a distinct transaction mechanism and acquire early users without depending on a host’s permission. RULE 1 — Enter only when the target buyer experiences a frequent, costly workflow gap that incumbents do not solve. RULE 2 — Build the minimum trust infrastructure—payments, security, compliance, support—before scaling acquisition. RULE 3 — Use direct entry to learn pricing, activation, and payment-mix economics, then add embedded channels once the engine is repeatable. RULE 4 — Reject direct entry if customer acquisition requires regulatory licenses, capital, or distribution relationships the company cannot yet obtain; Melio’s later bank and SaaS syndication shows the sequence of direct learning followed by embedded scale. [20][17][19]

How to enter

|  FOOTHOLD STRATEGY PLAYBOOK

THE STANDARD: A wedge strategy succeeds when one narrow pain creates habitual usage and a route into adjacent value. RULE 1 — Select a pain with a clear before-and-after: for Melio, “pay any vendor the way that best preserves my cash.” RULE 2 — Expand along the same financial workflow, from AP into AR, accountant services, and partner-embedded infrastructure. RULE 3 — Failure occurs when the wedge is easy to copy and does not create transaction history, vendor relationships, or integration depth. RULE 4 — In payments, add risk and compliance capability before expanding transaction types. [22][24][18]

How to get the first strong position

MARKET PATTERNS & PLAYBOOK

3

MONEY

money rev pri

Melio launched with a free service and monetized when customers selected value-added payment options, initially charging 2.9% for card-funded payments. It later added subscription tiers, per-user charges, ACH overage fees, and premium payment-rail fees; FY25 revenue reached $153 million on more than $30 billion processed volume. [17][25][19]

REVENUE MODEL

Freemium, Subscription, Transaction Fee

PRICING MODEL

Freemium, Tiered Pricing, Transaction Fee

WHY THEY WON

Customers pay nothing or a low subscription for workflow access, then pay transaction fees for card funding, ACH beyond allowances, checks, expedited transfers, international payments, and financing. Revenue expands with payment volume, paid-rail attach rate, additional users, and higher-volume Platinum accounts; gross margin depends on interchange, processing, delivery, and compliance costs. [21][18][25]

Melio’s Go plan is free with five monthly ACH payments; Core is $25/month with 20 free ACH payments, Boost is $55/month with 50, and Unlimited is $80/month with unlimited ACH and seats. Beyond allowances, ACH costs $0.50 per payment, while card-funded payments carry a standard 2.9% fee. [28][21][29]

TARGET AUDIENCE

Micro and small businesses (Go/Core; want low-cost vendor payments and basic AP); growing SMBs (Boost/Unlimited; want approvals, roles, batch payments, and accounting sync); accountants and bookkeepers (partner plans; want client payment oversight); banks, vertical SaaS, and marketplaces (Platinum/embedded; want white-label AP/AR infrastructure). [21][20][22][23]

CUSTOMER BUYING BEHAVIOUR

A cash-flow or vendor-payment trigger brings the owner to Melio directly or through QuickBooks, an accountant, or a bank; they evaluate ease of setup, payment choices, accounting sync, and fees; adoption often begins on the free plan and expands when transaction volume, approvals, or card funding create paid value. [21][22][19]

|  PRICING INTELLIGENCE

What makes this model effective & make customers pay 

Customers pay for cash-flow optionality, not for the act of sending money. RULE 1 — MONETIZE THE PAYMENT DECISION: card funding, speed, and international delivery are worth more than standard ACH because they change timing, working capital, and convenience. RULE 2 — USE FREE ACH AS ADOPTION, NOT REVENUE: the free rail creates habit and data while paid options capture willingness to pay. RULE 3 — PRICE BY PAYMENT MIX: percentage fees on card funding scale with transaction value but expose the vendor to interchange and chargeback costs. RULE 4 — WATCH THE VENDOR COST TRAP: free baseline transactions plus regulated payment infrastructure can create high fixed costs against a narrow monetized share of volume. The buyer is buying control over when and how cash leaves the business—measured in funded payment volume and paid-rail attach. [21][18][19]

PRICE & REVENUE

|  Revenue Risk - The biggest threat to revenue stability

Low paid-rail attach: most standard ACH volume may generate little direct revenue, making gross payment volume a misleading growth measure. [18][19] Card economics: interchange, chargebacks, fraud, and processor costs can compress the 2.9% card fee. [18] Host dependence: QuickBooks, Xero, Fiserv, Capital One, and Shopify can internalize payments or renegotiate economics. [20][22][27] Incumbent bundling: BILL, banks, and accounting platforms can bundle AP and payments. SMB credit sensitivity: payment volumes and financing demand fall when small businesses face cash stress. Valuation and funding pressure: Melio raised $150 million in October 2024 at about $2 billion, below its prior $4 billion valuation, before Xero agreed in 2025 to acquire it for $2.5 billion upfront plus up to $500 million contingent consideration; FY25 revenue was disclosed at $153 million. [20][27][25]

Where the model can break

4

MOTION

motion ge cs

Melio scaled through QuickBooks, Capital One, Fiserv, Shopify, Gusto, Clover, and other embedded partnerships. The QuickBooks integration created a native bill-pay entry point, while Fiserv alone connected Melio’s technology to more than 3,500 financial institutions. [20][22][23][24]

GROWTH EXPANSION MODEL

Ecosystem Expansion, Product Line Expansion

HOW THEY EXPAND

Melio began with direct SMB bill pay, expanded into AR and accountant offerings, then built a modular AP/AR platform for banks and SaaS partners. It grew within accounts through more users, approvals, payment methods, and transaction volume, while ecosystem partnerships extended reach into accounting, banking, commerce, and payroll platforms. [22][24][25]

COMPETITIVE STRATEGY

Flanking Attack

HOW THEY COMPETE

Against BILL, Melio avoided competing primarily on enterprise AP depth and attacked the SMB cash-flow problem through card-funded flexibility and simpler onboarding. Against banks and accounting platforms, it became their embedded payments infrastructure rather than asking customers to abandon them. [22][17][18]

GROWTH ENGINE

GTM

Content Flywheel

A host platform introduces Melio to an SMB; the business activates bill payment and connects accounting; successful transactions bring vendors into the payment flow; growing volume, multi-user controls, and paid rails expand revenue. The engine compounds when host distribution, accounting sync, and payment-method choice reinforce usage; it breaks if activation is weak, paid-rail attach is low, or the host captures the relationship. [21][22][18]

Melio uses a hybrid GTM: self-serve and free plans acquire small businesses directly; accountants provide trusted distribution; embedded bank, commerce, payroll, and vertical SaaS partnerships supply scale. The primary motion is partner-led embedded distribution, with direct self-serve important for product learning and smaller accounts. [21][20][22][23]

SUSTAINING MOATS

High Customer Lock-In

moat

The moat is Melio’s embedded network of SMB payers, vendors, accountants, banks, and SaaS hosts. Payment histories, vendor records, approval configurations, and accounting connections make replacement progressively harder, while syndication gives Melio reach that a standalone app would struggle to match. [20][27][18]

|  MOAT INTELLIGENCE

THE STANDARD: Moats persist when transaction relationships and workflow configuration accumulate faster than rivals can replicate distribution. RULE 1 — NETWORK DEPENDENCE: vendors, payers, and accounting systems become mutually reinforcing participants. RULE 2 — WORKFLOW DEPTH: approvals, roles, batch payments, W-9/1099 workflows, and ERP/accounting mappings raise migration cost. [28][21] RULE 3 — EMBEDDED REACH: Fiserv’s 3,500+ financial institutions and partnerships with Capital One and Shopify create distribution that is difficult to copy quickly. [20][23][27] THE SIGNAL: More than 80,000 customers and over $30 billion processed in FY25 show scale; the moat does not protect against a host building native payments, low paid-rail attach, or card-cost compression. [27][18][25]

Why this company remains defensible

ARR & TAKEAWAY

ARR Journey - what to do at each stage

PRE-$1M ARR — VALIDATE PAYMENT FLEXIBILITY: Melio spent 2018–19 building an SMB AP product and launched with a free model monetized through card-funded payments. WATCH: whether customers choose paid rails, not merely sign up. [17][19] $1–5M ARR — ESTABLISH DIRECT SMB PULL: By September 2020, Melio emerged from stealth with $144 million raised and reported 700% growth from March amid pandemic-driven digitization. [17][19] $5–10M ARR — ADD ACCOUNTING DISTRIBUTION: The 2020 QuickBooks partnership embedded Bill Pay powered by Melio into a leading SMB accounting workflow. [22] $10–50M ARR — SCALE PARTNER INFRASTRUCTURE: Capital One and Fiserv partnerships extended Melio into bank and embedded channels; Fiserv collaboration began in 2023. [22][23] $50–100M ARR — BROADEN PRODUCT AND CUSTOMER BASE: Expansion into medium-sized businesses, AR, accountant tools, and syndication supported 10x revenue growth over three years. [23] $100M+ ARR — PROVE EMBEDDED PLATFORM SCALE: Melio reached $153 million FY25 revenue, more than 80,000 customers, and over $30 billion processed payments; Xero agreed to acquire it in 2025 for $2.5 billion upfront. [20][25] Rule: validate a differentiated transaction behavior first, then use host-platform distribution to convert product usage into volume and revenue.

COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid

THE STANDARD: Build a payment or workflow intermediary that removes a mismatch between buyer and recipient behavior, then distribute it through platforms that already own trust. SEQUENCE: 1. Identify a frequent transaction where the two sides prefer different methods, timing, or records. 2. Build the smallest mechanism that completes the transaction for both sides, with free or low-cost baseline usage to establish habit. 3. Add a host-platform or intermediary channel only after direct users prove activation, retention, and paid-option economics. WORKED: Melio’s card-to-ACH/check translation created a clear reason to adopt, while QuickBooks and Fiserv distribution scaled reach efficiently. [22][23][18] CAUTION: Do not treat processed volume as revenue; measure paid-rail attach, interchange-adjusted margin, and host concentration. Also avoid embedded distribution before retaining enough workflow and data ownership to prevent the host from replacing you. [27][18][19]

bottom of page