PR

Productfy Financial Model

• Embedded finance platform that lets any company embed financial features (debit/credit card issuance, deposit accounts, ACH, KYC/KYB, data aggregation, credit builder) via UI widgets, GraphQL APIs, and SDKs.
• "FinTech-in-a-Box": unified due diligence, built-in compliance templates, multiple bank sponsors (Stearns Bank NA named), and a marketplace of strategic data/processor partners (Marqeta, Equifax, Envestnet Yodlee).
• Key time-to-market claim: launch in as little as 3 weeks vs. DIY 16–18 months.
• Proprietary omnipurpose general ledger on HADR (High Availability Disaster Recovery) platform with event-sourcing architecture.
• Strategic investors: Point72 Ventures, 500 Startups.

Three monetization streams:

1. Per-unit fees (transaction-based):

• ACH volume fees
• Instant Account Verification (IAV) fees
• KYC fees
• Bank account opening fees

1. Per-MAU platform fees:

• Monthly platform/subscription fee per active user
• Data aggregation fees

1. Interchange / sponsorship fees (BPS):

• Card interchange revenue (basis points on spend)
• Sponsorship fees from bank/network partners

GTM motion: "Land and Expand" - start clients on Money Movement (MM), expand to MM + Banking, then MM + Banking + Cards. Channels: direct outbound to competitor clients, direct outbound to fintechs via leads DB, strategic partner channels.

Future "escape velocity" revenue lines: international remittances, servicing infrastructure, elastic banking infrastructure, investments, bank white labeling, payment network, enablement services.

Competitive positioning:

• Slide 05 frames three weak incumbent archetypes: (1) Technology Only - no bank sponsor, incomplete; (2) Bank Expose APIs - charter limits functionality, can't achieve AWS scale; (3) Thin Veneer on Top of Bank - single charter, high friction and cost.
• Productfy's claimed moat: multi-bank-sponsor model for breadth + redundancy; unified compliance/due diligence layer; marketplace of strategic vendors; proprietary event-sourcing general ledger; AWS-style self-service onboarding.
• Slide 10 references "Our Competitors" section but no named competitors or comparison table is legible in text extraction; no specific competitor names appear in OCR.

• Founder / CEO: Duy Vo (duy.vo@productfy.io).
• No other named team members in the deck.
• Ask: $15M Series A.
• Use of funds - milestones stated:

1. Commercial and Personal Debit and Credit Card Issuance
2. Program Management for KYC, KYB, Credit, Deposit Accounts, and Credit Builder
3. Money Transmittal License and Elastic Banking Infrastructure
4. World-Class DevX and Self-Service Onboarding

• No explicit use-of-funds percentage split (engineering vs. sales vs. compliance) disclosed.

• Archetype + why: B2B SaaS + usage-based / transaction revenue model (sometimes called "platform + consumption"). Productfy has three blended revenue streams - a recurring per-MAU platform fee (SaaS-like), transaction/volume-based fees (usage-based), and interchange BPS (payment economics). The right model captures all three, with a client cohort build-up driving MAU × fee rate + ACH/IAV/KYC volume × unit price + card spend × interchange rate. This is structurally identical to how Marqeta and Galileo are modeled.

• Forecast horizon & granularity: 5-year model (Year 1–5), monthly for Year 1–2, quarterly for Year 3–5. Series A capital implies 18–24 month runway planning is the immediate need.

• Key drivers & assumptions:

*Client acquisition*

• New B2B clients signed per quarter
• Average client ramp time to full utilization
• Client segments: B2C fintech vs. B2B/SMB financial OS (slides 11–12 show two distinct journeys) - model separately

*Per-MAU revenue*

• MAUs per client
• Monthly platform fee per MAU

*Per-unit / transaction revenue*

• ACH transactions per MAU per month
• ACH fee per transaction
• IAV per new user
• KYC checks per new user

*Interchange revenue*

• Card-enabled MAUs as % of total MAUs
• Monthly card spend per active cardholder
• Interchange rate net to Productfy

*COGS / gross margin*

• Bank sponsor fees + partner pass-through costs
• Compliance/program management headcount

*Opex*

• Engineering / DevX headcount ramp
• Sales & GTM
• G&A / compliance / legal

• Scenarios (Base / Bull / Bear - which variables flex):
• Base: 4 new clients/quarter, 1,500 avg MAU/client at steady state, 50% card attach rate
• Bull: faster enterprise client wins (competitor client poaching per GTM slide), higher MAU/client (10,000+), interchange rate at top of range
• Bear: slower client ramp, regulatory/MTL delays push card revenue out 12 months, lower MAU/client (500), higher bank-sponsor COGS

• Required sheets / outputs:

1. Assumptions - all drivers in one tab, flagged vs.
2. Client Cohort Build - quarterly client additions × MAU ramp curve
3. Revenue Schedule - three streams (platform fee, per-unit, interchange) summed by month/quarter
4. P&L (Income Statement) - Revenue → Gross Profit → EBITDA → Net Income
5. Headcount Plan - by function (Eng, Sales, Compliance, G&A)
6. Cash / Runway - $15M raise, monthly cash burn, months to zero
7. Scenario Toggle - Base / Bull / Bear switchable via single input cell
8. Dashboard - KPI summary: clients, MAUs, ARR, gross margin %, cash runway