Everyman Brand Archetype
Automotive
Expense Management Software
BILL (formerly Bill.com)
Won by converting paper-based SMB bill payment into a networked payments-and-workflow platform, monetizing both software seats and transaction volume despite entrenched accounting-software and bank incumbents.
• BUSINESS MODEL
• REVENUE
• MARKET TYPE
• MARKET ENTRY
• GROWTH MODEL
• MOAT
• EDGE
1
MODEL
SMBs faced frequent, labor-intensive AP work: receiving paper invoices, manual data entry, check writing, approval chasing, and reconciliation. BILL replaced this with cloud invoice capture, approvals, ACH/check payments, and accounting sync; customers such as Supporting Strategies reported cutting bill-payment time by 50%. [1][2]
Question this model answers
We need to prove that customers have an urgent problem.
BUSINESS MODEL
Transaction-Based Platform
HOW THEY BUILT IT
'- Founded in 2006 to remove manual SMB back-office payment work, then built AP automation before expanding into AR and spend.
- Product architecture combines workflow software with payment rails: invoice capture, approvals, accounting sync, and ACH/check/international payment execution.
- It operates a two-sided B2B network: businesses pay vendors, while vendors receive invoices and payments through BILL; the network reached 8.3 million members in 2025.
- Bank and accountant partnerships embedded BILL inside trusted financial workflows, including a 2017 JPMorgan Chase relationship.
- Acquisitions of Divvy, Invoice2go, and Finmark extended the platform from AP into spend, mobile invoicing, and financial planning.
HOW TO ARCHITECT IT
1. Identify a high-frequency operational task where the customer currently pays in labor, error, delay, or compliance risk.
2. Build the smallest workflow that owns the task end to end, including the action or transaction—not merely tracking it.
3. Make each completed transaction create a second-side relationship or reusable data, so usage compounds.
4. Establish trust-critical infrastructure—payments, compliance, security, or integrations—before scaling acquisition.
5. Add adjacent workflows only after the core transaction creates switching costs and distribution permission. Avoid building a workflow tool without control of the value-creating transaction; software alone is easier to commoditize.
DISTRIBUTION MODEL
Partnerships, Product Integrations, Direct Sales, Self-Serve / Website
HOW THEY OPERATIONALIZED
'- Accountant and bank partnerships provided trusted SMB access: CPA2Biz in 2008, two of the top five U.S. banks by 2013, and JPMorgan Chase in 2017.
- QuickBooks, Xero, NetSuite, and Sage Intacct integrations placed BILL in the accountant’s existing system of record.
- Self-serve signup and free trials captured smaller businesses directly, while sales covered larger and multi-entity accounts.
- The payments network itself created vendor-side pull as payers invited suppliers into BILL.
HOW TO REPLICATE WHAT WORKED
What Worked
Embedding into a trusted intermediary’s workflow—accountants, banks, and accounting platforms—reduced trust and acquisition friction for a financial product.
Trap if Copied Blindly
Partner-led distribution fails when the partner owns the customer relationship, captures the economics, or can replace the vendor; retain the workflow, data, and payment relationship.
Insight on Untapped Business Model / Gaps / Pitfalls
GOLDMINE
GOLDMINE 1 — AI-NATIVE AP OPERATIONS FOR MID-MARKET. AP remains fragmented across invoice capture, procurement, approvals, payments, and reconciliation; an AI agent that owns exception handling and close-cycle outcomes can monetize resolved work, not seats.
GOLDMINE 2 — EMBEDDED FINANCE FOR VERTICAL SOFTWARE. Industry platforms with trusted SMB relationships can add payments, lending, and cash-flow tools without becoming horizontal fintechs.
GOLDMINE 3 — SUPPLIER-SIDE FINANCIAL PRODUCTS. The payer network creates data and access for early-payment, receivables, and working-capital products.
THE TRAP TO WATCH
THE PIT — SEAT-BASED PRICING IN AUTOMATION. As AI reduces human users, per-user pricing can penalize the very automation customers want.
THE SECOND PIT — PAYMENTS-ONLY WEDGES. Payment execution without workflow ownership invites accounting-platform and bank displacement.
MOVE WITH CAUTION
Do not enter regulated B2B payments without funds-handling, fraud, compliance, and reconciliation capability; transaction growth can conceal weak unit economics.
2
MARKET
MARKET TYPE
Red Ocean
WHY THEY WON
SMB financial operations is a Red Ocean: many credible substitutes exist, from banks and accounting systems to expense cards and AP tools. BILL won by exploiting a structural blind spot—incumbents owned records or payment rails but did not own the end-to-end invoice-to-payment-to-reconciliation workflow for SMBs. Its integration and partner strategy made the existing accounting system the entry point while BILL captured the operational layer. The transferable lesson is that crowded markets remain winnable when the entrant changes the unit of comparison from a feature to a completed business outcome. [3][7]
BILL entered SMB financial operations against banks, accounting platforms, paper processes, and later AP/AR and expense tools. It differentiated through an integrated AP-to-payment workflow and accounting sync, rather than selling standalone bill pay; its QuickBooks integration and bank partnerships changed the buying frame from “software” to “financial operations infrastructure.” [3][7][8]
Question this model answers
We are entering a crowded market.
ENTRY STRATEGY
Brownfield Entry
EXECUTION
BILL did not create a greenfield category; it modernized an existing manual AP process and competed against established accounting and banking workflows. Its initial product targeted SMBs roughly between $5 million and $100 million in revenue, replacing check-writing and manual reconciliation with cloud-based AP and payments. [2][8] The critical bet was to integrate with, rather than replace, QuickBooks and other accounting systems, lowering switching risk while capturing the payment workflow. This required reliable accounting sync, payment execution, and accountant trust; it would fail where the incumbent system already fully owned payments or where integration access was blocked. [3][8]
FOOTHOLD STRATEGY
Wedge Strategy
THE HOW
The initial wedge was SMB accounts payable: a recurring, painful, check-and-paper workflow with clear time savings. Accountants and small businesses were reachable through CPA channels and accounting integrations, and they could pay because AP labor and payment errors were visible costs. Once embedded in AP, BILL expanded into AR, spend, international payments, and planning. [3][1][8]
MARKET TYPE PLAYBOOK
RULE 1 — DEFINE THE INCUMBENT’S BLIND SPOT: customers are like businesses with fragmented systems; the opening is the handoff between systems.
RULE 2 — EXPECT PRICING PRESSURE: pricing must be tied to avoided labor, error, risk, or transaction value, not feature count.
RULE 3 — SUCCESSFUL ENTRANTS FLANK: they enter through integrations, niches, or workflow ownership rather than frontal feature wars.
RULE 4 — COMMON FAILURE: entering with a thin point solution in a market where incumbents can bundle it.
Red Ocean entry succeeds by reframing the buying decision around an underserved workflow, not by claiming broad superiority.
GENERAL RULES
WHAT HAPPENS IN THIS MARKET TYPE
RULE 1 — Enter only when the incumbent workflow has measurable friction, such as manual labor, delay, error, or compliance exposure.
RULE 2 — Build interoperability before replacement; integrate with the incumbent system of record to make adoption incremental.
RULE 3 — Capture a workflow the incumbent treats as adjacent, then expand only after proving retention and economics.
RULE 4 — Reject this approach if the incumbent controls the integration layer, owns the customer relationship, or can bundle your function at near-zero marginal cost; an example of the risk is vertical software platforms adding embedded payments themselves.
Brownfield entry is appropriate when customers already have a workable but inefficient solution and switching risk can be reduced through compatibility.
A wedge strategy wins by owning one narrow pain deeply enough to earn expansion rights.
HOW TO APPLY FOOTHOLD STRATEGY
RULE 1 — Select a segment where pain, willingness to pay, reachable channels, and reference value overlap; BILL’s AP wedge met all four through accountants and accounting integrations.
RULE 2 — Expand along the customer’s existing workflow, not into unrelated products; AP led naturally to AR, spend, and cash-flow tools.
RULE 3 — Failure occurs when the wedge is narrow but does not create data, transaction flow, or switching costs.
RULE 4 — In regulated or financial markets, add trust infrastructure before broadening the wedge.
BILL’s wedge was SMB accounts payable and approvals; failure occurs when trust infrastructure is not added before the wedge broadens in regulated finance.
HOW TO APPLY MARKET ENTRY STRATEGY
BILL replaced paper-based bill payment for SMBs that already had a workable but inefficient process; failure occurs when the incumbent controls the integration layer or owns the customer.
PATTERNS OF THIS MARKETING MODEL
PATTERNS IN PARTNER-LED, INTEGRATION-DRIVEN SMB DISTRIBUTION:
1. TRUSTED-INTERMEDIARY ACCESS. Accountants and banks convert skeptical SMB buyers by lending their own credibility.
2. SYSTEM-OF-RECORD INTEGRATION. Integrations with QuickBooks and similar platforms reduce migration fear and make the product part of daily work.
3. NETWORK-INITIATED EXPANSION. Payment recipients become future users, creating a second acquisition surface.
WEAKNESS
Partner dependence can cap pricing and control; if the partner owns the customer, the vendor risks becoming interchangeable infrastructure.
GROWTH CAMPAIGNS
'- Accounting-partner and bank channel programs, including CPA2Biz and JPMorgan Chase.
- QuickBooks/Xero/NetSuite integration and marketplace presence.
- Mid-market AP/AR launch in 2019, including purchase orders and international payments across 130+ countries.
- Case-study-led proof points, such as Supporting Strategies’ 50% reduction in bill-payment time.
- Acquisition-led expansion through Divvy, Invoice2go, and Finmark.
| So What
BILL’s strongest campaigns did not merely generate leads; they inserted the product into a pre-trusted financial workflow.
| Key Learning
In trust-sensitive categories, integration and intermediary endorsement can outperform direct persuasion because they reduce perceived implementation and compliance risk.
| How to Use
If your product touches money, compliance, or operational records, test one integration or channel partnership that places you inside the customer’s existing system before spending heavily on standalone acquisition.
3
MONEY
REVENUE MODEL
Subscription, Transaction Fee, Interest
BILL prices direct AP/AR subscriptions per user—$49 Essentials, $65 Team, and $89 Corporate per user/month—while charging separately for payment transactions; FY25 transaction fees were $1.03 billion versus $272 million subscription fees. This aligns revenue with both workflow access and payment activity. [6][10][5]
Question this model answers
We need to choose the right pricing metric.
PRICING STRATEGY
Tiered Pricing, Transaction Fee, Usage-Based Pricing
WHY THEY WON
Customers pay subscriptions for platform access, transaction fees for payments such as ACH and checks, and BILL earns float revenue on customer funds during clearing. Revenue expands with users, payment volume, cross-border activity, and added spend products; transaction volume is the dominant growth meter but carries variable payment and funding costs. [5][9]
TARGET AUDIENCE
SMB finance owners (Essentials/Team; want faster AP and cash control); mid-market finance teams (Corporate/Enterprise; want approvals, multi-entity controls, and ERP sync); accountants and bookkeeping firms (partner/self-serve; want client workflow standardization); suppliers/vendors (network; want faster invoice payment). [6][1][7]
BILL charges per user for software access and per transaction for payment execution; in 2025, Essentials began at $49/user/month, with ACH/ePayment transactions at $0.59 and mailed checks at $1.99. The meter matches value: seats reflect workflow participation, while transactions reflect money moved. [6][10]
CUSTOMER BUYING BEHAVIOUR
A cash-flow or AP pain trigger leads the buyer to search for AP automation or ask their accountant; they evaluate accounting sync, approval controls, payment methods, and security; smaller firms often start with a trial or self-serve plan, while larger firms require demos, procurement, and implementation. [6][1]
WILLINGNESS TO PAY
CORE INSIGHT
Customers pay for removed back-office labor and payment risk, not for “bill pay.”
RULES OF ADOPTION
RULE 1 — PRICE THE OPERATIONAL OUTCOME: the comparison budget is AP staff time, late fees, errors, and reconciliation work.
RULE 2 — USE A DUAL METER: seats capture workflow value; transactions capture money movement and scale with customer success.
RULE 3 — KEEP THE TRANSACTION VISIBLE: separate payment fees prevent software pricing from absorbing variable payment costs.
RULE 4 — WATCH THE VENDOR COST TRAP: payment processing, compliance, fraud, support, and float sensitivity can rise faster than subscription revenue. The buyer is ultimately buying faster, controlled cash conversion—measured in payment volume and finance hours saved.
The buyer is really buying removed back-office labour and payment risk, proven by a per-user software fee plus a payment-volume charge.
REVENUE RISK
Payment-volume concentration and macro sensitivity: transaction fees depend on B2B payment activity, which slows with SMB stress. Float and rate risk: interest earned on customer funds varies with rates and clearing time. [9] Commoditization: payment execution is increasingly bundled by banks, accounting platforms, and spend-management rivals. Customer concentration: larger customers and partner channels can influence volume and pricing. AI-driven seat compression: automation may reduce the number of paid workflow users. Regulatory and fraud cost: money movement creates compliance, fraud, and capital requirements. BILL reported FY25 total revenue of $1.46 billion, with subscription and transaction revenue disclosed; company-level ARR is not the primary disclosed metric. [5]
4
MOTION
BILL’s early growth relied on accountant and bank partnerships: CPA2Biz in 2008, two top-five U.S. banks by 2013, and JPMorgan Chase in 2017. These partners provided trusted access to SMB finance buyers and embedded BILL in business-banking and accounting workflows. [3][8]
Question this model answers
We need to use partnerships to reach customers.
GROWTH EXPANSION MODEL
Land & Expand, Product Line Expansion
HOW THEY EXPAND
BILL landed through AP automation, expanded within accounts as more users, entities, and payment volume moved onto the platform, then added product lines through AR, spend, international payments, and planning. Ecosystem expansion came from accounting integrations and bank partnerships, while Divvy and Invoice2go acquisitions added expense management and mobile AR. [3][2][7]
COMPETITIVE STRATEGY
Partnership Growth
HOW THEY COMPETE
Accountants and banks introduce BILL to SMBs; integration with QuickBooks and similar systems activates the workflow; successful payment runs bring vendors into the network; expanded AP/AR/spend usage increases seats and transactions. The engine compounds when payment volume, supplier participation, and accounting integrations reinforce one another; it weakens if activation is poor, integration access is restricted, or transaction economics deteriorate. [3][5][8]
GTM
BILL runs a hybrid GTM: self-serve and free trials acquire smaller SMBs; accountant, bank, and integration partnerships provide trusted distribution; direct sales handles mid-market, multi-entity, and enterprise accounts.
$5–10M ARR
The primary motion is partner-and-product-led adoption, with sales becoming important as buyer complexity, procurement, and implementation needs rise.
SUSTAINING MOATS
Network Effects
The moat is BILL’s connected financial-operations network: payers, suppliers, approvers, banks, and accounting systems all participate. Each new payment relationship and workflow configuration raises switching costs, while the ecosystem makes BILL harder to replace than a standalone AP tool. [3][5]
| Why This Moat Lasts
Durable moats come from accumulated relationships and workflow dependence, not feature parity.
| Standard Rules
RULE 1 — NETWORK DENSITY: more than 8 million network members and hundreds of thousands of business customers make supplier-side participation valuable.
RULE 2 — WORKFLOW CONFIGURATION: approval chains, ERP/accounting mappings, payment controls, and historical transaction data create migration work.
RULE 3 — INFRASTRUCTURE BARRIER: payments, compliance, fraud controls, and bank relationships are costly to replicate.
| The Signal
BILL processed about $300 billion in total payment volume in 2024 and generated $1.46 billion FY25 revenue; the moat does not protect against interest-rate declines, bundled bank payments, or AI-driven seat compression.
ARR
JOURNEY
Pre-$1M ARR
VALIDATE THE AP WEDGE: BILL spent its early years proving that SMBs would move bill payment online; by roughly five years in, it had only about 1,500 small customers, showing a slow trust-and-integration build.
WATCH: partner enablement and product reliability.
$1–5M ARR
DEEPEN ACCOUNTANT DISTRIBUTION: the 2008 CPA2Biz link and accounting sync made the channel repeatable.
$5–10M ARR
PROVE BANK-GRADE INFRASTRUCTURE: by 2013, two of the top five U.S. banks selected its payments platform.
$10–50M ARR
SCALE PARTNER LEDGER: the 2017 JPMorgan relationship and $100 million financing supported platform scale.
$50–100M ARR
EXPAND WORKFLOW COVERAGE: 2018 international payments and 2019 mid-market AP/AR launches widened the use case; revenue reached about $65 million in 2018.
$100M+ ARR
PLATFORMIZE AND ACQUIRE: after its 2019 IPO, BILL acquired Divvy, Invoice2go, and Finmark, then crossed $1 billion annual revenue in 2023 and reached $1.46 billion FY25 revenue.
BREAKDOWN
THE STANDARD
Win by owning a high-frequency operational transaction, then use trusted distribution and adjacent workflows to compound.
THE SEQUENCE
1. Choose one manual workflow with measurable labor, error, or cash cost, and build the full execution path rather than a tracking dashboard.
2. Establish one trusted integration or intermediary channel before scaling paid acquisition; the gate is repeatable partner-sourced activation.
3. Add adjacent products only when the core creates transaction data, retention, and distribution permission.
BILL’s accountant/bank partnerships and QuickBooks integration reduced trust friction, while transaction fees let revenue scale with customer activity.