Everyman Brand Archetype
Automotive
Data Integration
Codat
Became the data-connectivity layer between SMB financial systems and banks, lenders and fintechs by standardizing accounting, banking and commerce integrations—despite Plaid’s consumer-data dominance and direct integrations by large financial institutions.
• BUSINESS MODEL
• REVENUE
• MARKET TYPE
• MARKET ENTRY
• GROWTH MODEL
• MOAT
• EDGE
1
MODEL
Codat was founded in 2017 by Peter Lord, Alex Cardona and David Hoare after building repeated accounting integrations at MarketFinance. Rather than continue building one-off connections, they created a universal API for consented SMB financial data. Codat raised $10 million in 2020, $40 million in 2021 and $100 million in 2022 from investors including JPMorgan, Shopify, Plaid, PayPal and American Express. It grew from roughly 30 customers in 2020 to more than 200 in 2022 and more than 300 by 2024, with more than 350,000 SMB connections reported by 2026.
Question this model answers
We need to know whether our business model can scale.
BUSINESS MODEL
PaaS
HOW THEY BUILT IT
'- Standardized data model: Codat normalized accounting, banking, commerce and POS data from systems such as QuickBooks, Xero, Sage, NetSuite, Shopify, Square and Stripe.
- Consent-based connectivity: SMBs authorize access, allowing banks, lenders and fintechs to retrieve live financial data without building every integration.
- Read-and-write infrastructure: beyond data retrieval, Bank Feeds, Sync for Commerce, Sync for Expenses and Sync for Payables write transactions and operational data back into accounting systems.
- Decision-layer expansion: Assess enriched financial data into credit metrics, reports and data-integrity checks for lenders.
- Enterprise-grade operations: security, consent management, refresh scheduling and normalization made the API usable by regulated banks and lenders.
HOW TO ARCHITECT IT
1. Find a workflow where every customer must integrate with the same fragmented set of systems.
2. Build one normalized data model before adding connectors, because schema consistency is the product.
3. Make consent, security and refresh reliability first-class capabilities, especially when serving regulated buyers.
4. Start with read access to prove value, then add write-back workflows once customers depend on the data layer.
5. Price around connected entities and usage, so revenue grows with customer adoption and data volume.
6. Avoid the mis-build: treating integration as a feature rather than an operating system; without normalization, monitoring and consent infrastructure, each new connector increases cost without compounding value.
DISTRIBUTION MODEL
Direct Sales, Enterprise Sales, Partnerships, Developer/API-Led
HOW THEY OPERATIONALIZED
'- Direct and enterprise sales targeted banks, lenders, payments companies and SMB fintechs that needed accounting connectivity.
- Developer documentation and APIs enabled technical evaluation and implementation inside customer products.
- Strategic investors—including JPMorgan, Shopify, Plaid, PayPal and American Express—provided credibility and potential distribution alignment.
- Accounting-platform and commerce-system connections made Codat valuable wherever SMB customers already kept financial records.
HOW TO REPLICATE WHAT WORKED
What Worked
Sell infrastructure to the institution that owns the SMB relationship, while making the SMB’s consent the activation event; this avoids building a consumer brand from scratch.
Trap if Copied Blindly
Enterprise data infrastructure requires long sales cycles, security review and ongoing connector maintenance; developer-led adoption alone will not create a scalable financial-data business.
Insight on Untapped Business Model / Gaps / Pitfalls
GOLDMINE
GOLDMINE 1 — DECISION-READY FINANCIAL DATA. Raw connections are commoditizing; the opportunity is packaged underwriting, cash-flow, fraud and advisory intelligence built on normalized data.
GOLDMINE 2 — EMBEDDED FINANCE OPERATIONS. Banks and platforms need not only data access but workflows for onboarding, monitoring, reconciliation and collections.
GOLDMINE 3 — AI ADVISORY FOR SMB BANKING. Consent-driven financial data can power proactive cash-flow, tax, procurement and working-capital guidance.
THE TRAP TO WATCH
THE PIT — CONNECTOR-ONLY PRICING. Selling access alone invites competition from direct integrations, open banking aggregators and unified-API vendors.
THE SECOND PIT — SOURCE-PLATFORM DEPENDENCY. Accounting and banking providers can change APIs, pricing or access rules, directly affecting unit economics.
MOVE WITH CAUTION
Do not build a universal financial API without a clear regulated buyer, consent architecture and maintenance economics; connector breadth without reliability becomes an operational liability.
2
MARKET
MARKET TYPE
Emerging Market
WHY THEY WON
SMB financial-data connectivity was emerging as open banking, embedded finance and digital lending expanded. The structural blind spot was that consumer open-banking platforms did not adequately solve business financial data across accounting, commerce and banking systems. Codat reframed the problem from “bank-account access” to “consented SMB operating data,” creating a new integration layer for lenders and fintechs. The transferable lesson: when an emerging market is defined by data access, the winner standardizes the data model and workflow—not merely the connection.
Banks, lenders and fintechs previously built direct integrations with QuickBooks, Xero, Sage and banking systems or relied on manual document collection. Codat gave them one standardized API, consent flows, normalized data and ongoing connector maintenance. Its customer base expanded from about 30 in 2020 to more than 200 by 2022 and over 300 by 2024, including banks, lenders, payment providers and SMB software companies.
Question this model answers
We need to know why customers should switch.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
Codat entered by creating a universal SMB financial-data API rather than replacing an incumbent core system. Its founders had repeatedly built accounting integrations at MarketFinance and recognized that lenders and fintechs duplicated the same work. The initial bet was that financial institutions would pay for standardized, consent-based access to SMB accounting and banking data rather than maintain direct integrations. This was viable because SMB lending, payments and expense products increasingly needed live financial context. It required robust security, consent management and connector reliability; it would fail if institutions insisted on direct integrations or if source platforms restricted data access.
FOOTHOLD STRATEGY
Beachhead Strategy
THE HOW
Codat’s first beachhead was UK and European SMB lenders that needed accounting data for invoice finance, working-capital and COVID-era lending decisions. These lenders were reachable through the founders’ MarketFinance network and had a direct economic incentive: faster, better-informed credit decisions. By 2020, Codat was helping banks process tens of thousands of loans tied to COVID-related programs, creating proof for expansion into payments, banking and fintech infrastructure.
MARKET TYPE PLAYBOOK
RULE 1 — IDENTIFY THE DATA THAT DECISIONS DEPEND ON. Lenders needed accounting, banking and commerce signals, not just a connection.
RULE 2 — BUILD TRUST BEFORE BREADTH. Consent, security and reliability matter more than connector count in regulated financial infrastructure.
RULE 3 — PRICE THE CONNECTED RELATIONSHIP, NOT THE API CALL. A connected SMB represents recurring decision value across underwriting, monitoring and advisory.
RULE 4 — EMERGING MARKETS REWARD EARLY STANDARD-SETTERS BUT PUNISH PREMATURE BREADTH. Too many connectors before reliability and demand can destroy economics.
In an emerging market, the entrant must define the data standard and workflow before alternatives harden into category expectations.
GENERAL RULES
WHAT HAPPENS IN THIS MARKET TYPE
RULE 1 — Confirm that buyers already make expensive manual workarounds for the underlying problem.
RULE 2 — Define a normalized data model and operating workflow before scaling connectors.
RULE 3 — Win a concentrated early segment whose urgency creates references and operational learning.
RULE 4 — Reject greenfield entry if incumbents can bundle the capability quickly and the entrant cannot establish a data, trust or workflow advantage.
Greenfield entry is appropriate when a new data, regulatory or technology shift creates demand for infrastructure that did not previously exist as a product category.
A beachhead strategy dominates one urgent segment deeply enough to create proof, references and expansion permission.
HOW TO APPLY FOOTHOLD STRATEGY
RULE 1 — Choose buyers with a recurring, high-stakes decision that depends on the data you standardize.
RULE 2 — Make the first use case measurable: faster decisions, lower default risk, lower operating cost or higher conversion.
RULE 3 — Expand into adjacent use cases only after the first segment validates reliability and economics.
RULE 4 — A beachhead fails when the segment’s need is episodic or when the vendor cannot convert early proof into repeatable enterprise sales.
Codat’s beachhead was fintechs and lenders that urgently needed SMB financial data; failure occurs when the segment’s need is episodic or early use does not convert into repeated connections.
HOW TO APPLY MARKET ENTRY STRATEGY
Codat created infrastructure to standardise accounting, banking and commerce data when a data shift created demand that did not exist before; failure occurs when incumbents can bundle the capability quickly.
PATTERNS OF THIS MARKETING MODEL
PATTERNS IN ENTERPRISE-API AND PARTNER-LED DISTRIBUTION:
1. STRATEGIC INVESTORS SIGNAL TRUST. Backing from JPMorgan, Shopify, Plaid, PayPal and American Express reduced perceived risk for banks and fintechs evaluating a data dependency.
2. REGULATED BUYERS REQUIRE PROOF, NOT SELF-SERVE ALONE. Security reviews, consent architecture and operational reliability drive adoption more than free trials.
3. EMBEDDED USE CASES CREATE DISTRIBUTION. When a lender or payments platform embeds Codat in its customer onboarding, every new SMB customer can become a Codat connection.
WEAKNESS
Enterprise API sales are slow; without an embedded or partner-led activation mechanism, customer acquisition remains constrained by sales capacity.
GROWTH CAMPAIGNS
'- Founder-led sales into UK SMB lenders and invoice-finance providers.
- COVID-era lending-enablement positioning for banks processing government-backed loans.
- Developer documentation and API specifications for Accounting, Banking, Commerce and Assess APIs.
- Strategic-investor announcements featuring JPMorgan, Shopify, Plaid, PayPal and American Express.
- Product launches for Bank Feeds, Sync for Commerce, Sync for Expenses, Sync for Payables and Assess.
- “Internet for business data” category positioning.
| So What
Codat’s COVID lending work shows that a crisis can compress adoption cycles when the vendor removes a regulatory and operational bottleneck—in this case, verifying SMB financials at scale.
| Key Learning
Infrastructure companies accelerate when they solve an urgent compliance or decision bottleneck, not merely a convenience problem.
| How to Use
If your product supports a regulated decision, identify the event that forces many institutions to act simultaneously, then package your capability as the fastest compliant path through that bottleneck.
3
MONEY
REVENUE MODEL
Subscription, Usage-Based, Licensing Fees
Codat monetizes through a platform fee plus charges tied to connected companies and usage. Public pricing is customized, but industry estimates place connected-company costs around $30–$50 per month depending on volume, with annual platform fees often starting around $12,000–$24,000. The economic unit is the connected SMB: each connection creates data-refresh, maintenance, support and compliance costs, so profitability depends on connection durability, data volume and product expansion.
Question this model answers
We need to know whether our unit economics work.
PRICING STRATEGY
Custom Enterprise Pricing, Usage-Based Pricing, Tiered Pricing
WHY THEY WON
Financial institutions and fintechs pay a recurring platform fee for access to Codat’s infrastructure, plus usage-based charges for connected companies, data refreshes and product modules. Revenue expands as customers connect more SMBs, add banking, commerce or lending products, and move from raw data access to decision intelligence.
TARGET AUDIENCE
Banks and commercial lenders (enterprise contracts; want faster, data-rich SMB underwriting and monitoring); Fintechs and neobanks (usage/platform contracts; want embedded cash-flow, expense and accounting products); Payments and commerce platforms (Sync products; want merchant transaction-to-accounting automation); Insurance and B2B SaaS providers (custom contracts; want financial context for underwriting and workflow automation).
Codat uses custom pricing based on integration scope, product mix and expected connection volume. The commercial structure combines a platform commitment with per-connected-company or usage charges; third-party estimates indicate roughly $30–$50 per connected company monthly and platform fees beginning around $12,000–$24,000 annually. This aligns price with the customer’s deployed SMB base, but makes margin sensitive to connection churn and data-refresh frequency.
CUSTOMER BUYING BEHAVIOUR
A product or lending leader identifies an integration bottleneck, then technical and security teams evaluate data coverage, normalization quality, consent flows and reliability. Procurement follows, with pricing tied to expected connected SMBs and product scope; adoption expands as the customer embeds Codat in onboarding, underwriting or reconciliation workflows.
WILLINGNESS TO PAY
CORE INSIGHT
Customers are not buying API calls; they are buying faster, safer decisions about SMB credit, cash flow and financial relationships.
RULES OF ADOPTION
RULE 1 — PRICE THE CONNECTED BUSINESS, NOT THE REQUEST. A connected SMB represents recurring underwriting, monitoring and advisory value.
RULE 2 — CHARGE FOR RELIABILITY AND COVERAGE. Banks pay for normalized data, consent handling, refresh reliability and connector maintenance—not merely access.
RULE 3 — WRITE-BACK RAISES WILLINGNESS TO PAY. Products that change accounting records create operational dependence beyond analytics.
RULE 4 — CONNECTOR CHURN IS THE HIDDEN COST. A disconnected SMB stops generating revenue but may still have consumed onboarding, support and integration cost.
The buyer is really buying decision-grade SMB financial intelligence, proven by the credit, risk and product budgets allocated to data and underwriting.
REVENUE RISK
Connection churn: SMBs change accounting systems, close, or revoke consent; each lost connection removes recurring revenue and may leave unrecovered acquisition and support cost.
Source-platform dependency: QuickBooks, Xero, Sage, banks and commerce platforms control APIs, pricing and access rules; changes can raise cost or reduce coverage.
Customer concentration: Large banks and lending platforms can drive a disproportionate share of connections and revenue.
Commoditization: Unified APIs, open-banking aggregators and direct integrations can erode the value of basic connectivity.
Regulatory and consent risk: Financial-data access depends on authorization, privacy and jurisdictional rules; compliance failures can halt deployment.
Codat raised $100 million in 2022 and reported more than 350,000 connections by 2026; current ARR is not publicly disclosed and remains unverified.
4
MOTION
Codat sold high-value, security-sensitive data infrastructure to banks, lenders and payments companies through a structured enterprise motion. Its buyers included JPMorgan, Virgin Money, Brex, Clover, Pipe and Jeeves; deals required technical evaluation, security review, procurement and integration planning. The 2022 $100 million round, with JPMorgan, Shopify, Plaid, PayPal and American Express participating, reinforced enterprise credibility.
Question this model answers
We need to build an enterprise sales motion.
GROWTH EXPANSION MODEL
Platform Expansion, Market Development
HOW THEY EXPAND
Codat expanded from accounting-data access for lenders into banking, commerce, payroll, expenses, payables and bank-feed write-back products. It then moved from raw connectivity into Assess, a decision-intelligence layer for credit assessment, and later positioned itself as advisory intelligence for commercial banking. The dependency is that every expansion uses the same consented SMB connections and normalized financial-data layer.
COMPETITIVE STRATEGY
Sales-Led Growth
HOW THEY COMPETE
Enterprise sales wins a bank, lender or fintech; the customer embeds Codat in onboarding, underwriting or reconciliation. Each SMB that consents becomes a connected company, generating recurring usage and data. Successful deployments create references that help win similar financial institutions. The engine depends on reliable connectors, consent conversion, data freshness and customer product adoption; it weakens if SMB consent rates are low or connections churn quickly.
GTM
Codat uses an enterprise-led GTM with developer enablement.
$5–10M ARR
Sales targets banks, lenders and fintechs; solution engineers support data-model, security and integration evaluation; the SMB end user authorizes connection; customer success expands use from lending into payments, expenses and advisory workflows. The primary motion is enterprise sales, while embedded customer products create downstream connection growth. The founder-level implication is that data infrastructure needs both an institutional buyer and an end-user activation mechanism.
SUSTAINING MOATS
Data Advantage
The moat is Codat’s normalized SMB financial-data model, connector reliability and accumulated connection behavior. It strengthens as more SMBs connect and more institutions use the data for underwriting, reconciliation and monitoring; it weakens if source platforms restrict access, connection churn rises, or rivals achieve equivalent normalization at lower cost.
| Why This Moat Lasts
A data moat lasts when the data is consented, continuously refreshed and embedded in recurring decisions.
| Standard Rules
RULE 1 — NORMALIZED DATA BEATS RAW ACCESS. Standardized financial objects reduce customer integration work and create switching costs.
RULE 2 — WRITE-BACK CREATES OPERATIONAL DEPENDENCE. Bank feeds, expenses and commerce sync make Codat part of the customer’s accounting workflow.
RULE 3 — DECISION MODELS IMPROVE WITH OUTCOMES. Lending and risk use can improve data enrichment and scoring over time.
| The Signal
Codat’s growth to more than 350,000 connections and adoption by major banks and fintechs shows data-network depth; the moat does not protect against source-platform policy changes or a customer migrating its highest-volume integrations in-house.
ARR
JOURNEY
Pre-$1M ARR
VALIDATE THE INTEGRATION PAIN. Founded in 2017 by former MarketFinance operators, Codat initially served lenders that repeatedly needed accounting integrations for SMB credit decisions.
WATCH: The company had to prove that standardized data could support real lending decisions.
$1–5M ARR
WIN THE SMB LENDING BEACHHEAD. By 2020, Codat had more than 30 customers and was helping banks process tens of thousands of COVID-related loans worth billions of dollars.
WATCH: Crisis-driven demand needed conversion into durable, recurring data connections.
$5–10M ARR
EXPAND DATA COVERAGE. The 2020 $10 million Series A supported expansion from accounting into banking, commerce and payroll data.
WATCH: Each new source increased maintenance burden and required robust normalization.
$10–50M ARR
BUILD THE ENTERPRISE PLATFORM. Codat raised $40 million in 2021 and expanded to more than 200 clients, including Brex, Virgin Money, Zettle and Clover.
WATCH: Enterprise security, procurement and implementation capacity became the constraint.
$50–100M ARR
MOVE FROM ACCESS TO INTELLIGENCE. In 2022, Codat raised $100 million at increased scale, added Assess and expanded write-back products such as Bank Feeds and Sync for Commerce.
WATCH: The company needed to prove that decision intelligence could raise ARPU beyond connectivity.
$100M+ ARR
NOT REACHED or NOT APPLICABLE based on available public disclosure. Codat reported more than 300 clients in 2024 and more than 350,000 connections by 2026, but its current ARR milestone is not publicly verified.
BREAKDOWN
THE STANDARD
Standardize fragmented data into a decision-ready layer, win one high-stakes buyer segment, then expand from access into write-back and intelligence.
THE SEQUENCE
1. Prove one data type can improve a high-stakes recurring decision.
2. Build consent, security and normalization before scaling connector breadth.
3. Add write-back workflows and decision products only after customers depend on the data layer.
Codat’s SMB-lending beachhead created urgent demand and references; its expansion into Bank Feeds, commerce sync and Assess increased account value beyond raw data access.