Loan-certification rail for investor-property lenders to place DSCR and bridge loans onto tokenized funding buyers without custom tape ops.

1. Figure is moving a named private-credit asset class onto blockchain rails with $7 billion-plus of added annual flow, so this is now a production onboarding problem rather than a tokenization thought experiment.
2. Figure publicly naming Adaptor and originator-data standardization as the first use case shows the first missing layer is lender-data onboarding, which creates room for a focused infrastructure startup.
3. More than $100 million per month flowing into Democratized Prime implies recurring secondary liquidity that will punish manual loan-tape work and reward machine-readable delivery.
4. Kiavi's reported scale and profitability mean the category already has enough gross profit and operational complexity to support dedicated workflow software, not just services.

Catalyst. Figure's acquisition shows investor-property lending is moving from bespoke secondary sales into blockchain-linked funding rails, and it explicitly names originator-data standardization as the first workflow that must be solved.

The product sits between the lender's LOS, document stack, and buyer destinations such as warehouse providers, private-credit funds, and tokenized funding programs. It builds one canonical loan record from originator exports, property and borrower documents, and servicing fields, then maps that record against each buyer's eligibility, concentration, and documentation rules. When data is missing or contradictory, the system opens a structured exception workflow with the exact field, document, or policy conflict instead of sending another round of spreadsheet comments. When a loan passes, it generates a buyer-ready certification packet, machine-readable tape, and audit log. That makes a new funding program feel like activating another rail rather than running a fresh onboarding project.

What's different. Incumbent LOS vendors and loan buyers each see only one side of the transaction, while generic data rooms and diligence vendors do not own the machine-readable eligibility decision. This startup becomes the neutral translation and certification layer between many originators and many funding destinations. Its moat compounds through buyer rulebooks, lender data maps, and exception-resolution history that make each additional funding rail faster to activate than the last.

Jobs to be done

flowchart LR
  Buyer[Capital markets lead] --> Pain[Custom loan tape and diligence rework]
  Pain --> Product[Investor loan certification rail]
  Product --> Outcome[Faster funding-channel onboarding and cleaner loan delivery]

Executive takeaways

• Figure’s Kiavi acquisition is strong evidence that tokenized investor-property lending has moved from concept to operational rollout: the company cited a $200B annual origination opportunity, $7B of added first-lien flow, $100M+ monthly Democratized Prime volume, and Adaptor as the first-originator standardization layer. [1][4][8][9]
• The startup wedge is credible because the bottleneck has shifted from finding capital to normalizing loan data, validating eligibility, and packaging audit-ready evidence across multiple funding counterparties. MISMO, ULDD, Loan Closing Advisor, and ICE’s developer tooling show the industry is already standardizing machine-readable data, but not buyer-specific pass/fail certification. [17][18][20][21][35]
• Competition is real but fragmented across rails, underwriting automation, warehouse platforms, and capital-markets ops software. No retained source clearly shows an independent vendor already owning neutral, multi-buyer certification for DSCR/RTL deliveries headed to both traditional and tokenized outlets. [2][24][27][33][34]

Market definition

[1][10][13][17][20][24] The relevant market is workflow software that converts DSCR, bridge, and fix-and-flip originations into buyer-ready certified loan packets for warehouse lenders, private-credit buyers, securitization prep, and tokenized funding rails. The job is narrower than LOS or underwriting: normalize originator data, apply buyer-specific rules, resolve exceptions, and evidence why each loan is deliverable.

Customer and buyer

[5][9][19][24][25][27] Daily users are capital-markets, secondary-marketing, and loan-ops teams at U.S. investor-property lenders. The economic buyer is usually the Chief Capital Markets Officer, COO, or head of secondary marketing because the pain surfaces as delayed fundings, extra headcount, missed buyer SLAs, and slower onboarding of new funding channels.

Buying triggers

• A lender signs a new warehouse, takeout, or tokenized funding relationship and discovers its current tape, document, and exception process cannot support recurring delivery without more people. [1][19][24][27]
• eMortgage and GSE-style data standards raise expectations for machine-readable delivery, making ad hoc spreadsheets look increasingly non-compliant and slow. [17][18][20][21][35]
• Institutional investor appetite for RTL and DSCR credit remains strong, so growth is gated more by originator readiness and loan quality than by demand. [10][13]

Willingness to pay

Budget likely sits in capital-markets ops, warehouse onboarding, or loan-manufacturing transformation rather than an experimental blockchain line item. Adjacent vendors already sell underwriting automation, reporting, and funding-workflow tooling on the promise of faster closings, fewer defects, and less manual labor, which implies room for a high-trust certification layer. [21][27][33][34] [21][27][33][34]

Category dynamics

Growth signal 4.0% YoY growth in private-lender originations in Q1 2026, with stronger bridge growth than DSCR

Validation signals

• Figure explicitly identified originator-data standardization via Adaptor as the first workflow to productize when bringing Kiavi assets onto its rails.
• NPLA reported the strongest Q1 on record for private lending, while saying the limiting factor is high-quality RTL supply rather than investor appetite.
• Freddie and MISMO already require or support machine-readable loan, closing, and eMortgage artifacts, which lowers the integration barrier for a certification layer.
• Setpoint and FirstFunding both market faster funding and reporting workflows, signaling buyer willingness to pay for operational speed in adjacent steps.

Regulatory & technical constraints

• Any cross-counterparty workflow must handle nonpublic borrower information under Regulation P and related mortgage-process rules.
• Mortgage data still has to line up with established reporting and delivery schemas such as HMDA and ULDD, even if funding rails evolve.
• Tokenization does not change the underlying legal treatment of the asset if the rights are unchanged, so “on-chain” does not remove compliance work.
• State licensing and supervisory expectations remain relevant because mortgage origination and nonbank lending are governed across multiple jurisdictions.

[2][4][24][27][33][34] The field is crowded with adjacent tools rather than direct substitutes. Figure owns a rail-and-liquidity narrative, Candor automates loan manufacturing and QC, warehouse platforms bundle reporting and transaction processing, and Setpoint targets capital-markets operations. The white space is the neutral control layer that sits across many buyers and many lenders, not inside one rail or one warehouse line.

Why incumbents do not win by default

• Blockchain rails. Rail operators like Figure can embed onboarding helpers, but their economic center is maximizing flow on their own network rather than acting as a neutral referee across every counterparty and data schema.
• Mortgage manufacturing automation. Candor-class vendors reduce underwriting and QC work, but the retained evidence centers on borrower manufacturing and loan quality, not multi-buyer delivery certification for investor-property capital markets.
• Warehouse and correspondent platforms. FirstFunding and warehouse lenders can streamline funding and reporting for their own facilities, yet they are structurally tied to a specific funding partner model rather than a cross-buyer certification graph.
• Capital-markets operations platforms. Setpoint improves diligence, reporting, and funding speed, but its positioning is broader capital-operations enablement rather than a DSCR/RTL rulebook engine that every buyer trusts as source of truth.

Investor Loan Certification Rail targets a specific operational bottleneck at U.S. residential investor lenders: getting DSCR, bridge, and fix-and-flip loans accepted by multiple funding counterparties without rebuilding loan tapes and diligence workflows each time. The first customer is a $1B+ annual originator with three or more warehouse or takeout relationships and a live project to add a more automated or tokenized funding channel in the next 12 months. The product is not a new marketplace or issuer; it is a neutral certification layer that creates one canonical loan record, applies buyer-specific eligibility logic, and generates an auditable certification packet before delivery fails. This wedge is timely because Figure's Kiavi deal and Adaptor positioning indicate that standardizing originator data is now the gating workflow for scaled investor-property flow on new rails. The go-to- market system is coherent: sell a first deployment around one new funding program, price by active buyer programs plus funded-loan volume, and expand only after the lender uses the control layer on recurring deliveries. The strongest evidence supports pain, workflow urgency, and adjacent willingness to pay, but two core uncertainties remain unresolved in the inputs: which exception categories drive the most lender pain today, and whether non-Figure buyers will trust a neutral third-party certification packet enough to reduce their own diligence burden. Market sizing in the research is estimate-based and modest on the narrow beachhead, so the company only becomes venture-scale if the beachhead expands into the operating layer for warehouse reporting, securitization prep, servicing-transfer readiness, and portfolio surveillance. This is worth tracking closely, but investor conviction should increase only after the first design partners prove reusable rulebooks, paid deployment, and measurable acceleration from pilot to production funding.

Problem

• Mid-sized investor-property lenders still onboard each new warehouse, takeout, or tokenized buyer through bespoke CSV tapes, diligence checklists, and email-heavy exception clearing.
• Capital-markets and loan-ops teams become the manual integration layer because each counterparty wants different fields, concentration tests, and supporting documents before loans can fund.
• As secondary liquidity becomes more recurring, the bottleneck shifts from finding capital to proving each loan is complete, eligible, and machine-readable on every delivery.

Solution

• Build one canonical loan record from LOS exports, document stacks, and servicing fields for DSCR, bridge, and fix-and-flip loans.
• Apply buyer-specific rulebooks for eligibility, concentration, and documentation, then open structured exception workflows with source-linked evidence instead of spreadsheet comments.
• Generate a buyer-ready certification packet, machine-readable tape, and audit log so adding a funding program looks like activating another rail rather than starting a new onboarding project.

Why we win

• The company is neutral across many lenders and many buyers, while rails, warehouse platforms, and LOS vendors are structurally optimized for their own ecosystems.
• The buying trigger is concrete and budgeted: a lender signs a new funding program and needs recurring delivery without adding operations headcount.
• Defensibility compounds through reusable buyer rulebooks, lender field mappings, and exception-resolution data that make each additional counterparty faster to support.

Milestones

flowchart LR
  Wedge[Beachhead funding-program wedge] --> MVP[Certification MVP]
  MVP --> Proof[First accepted recurring deliveries]
  Proof --> Expansion[Multi-buyer and reporting expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• Lenders adding a new funding channel will pay for a neutral control layer before they consolidate on one rail or warehouse platform.
• At least one non-incumbent buyer will accept the certification packet as enough to reduce duplicate diligence work.
• The first 3 buyer rulebooks will share sufficient reusable logic to preserve software-like gross margins.
• A first deployment can reach recurring production delivery in less than 90 days on supported source systems.
• The product can expand from pre-delivery certification into adjacent reporting and surveillance workflows without losing its neutral positioning.

Open diligence questions

• Which exact DSCR and bridge exception categories create the most frequent buyer fallout today?
• How much of the customer's pain is data normalization versus buyer-side policy ambiguity?
• Which counterparties would trust a third-party certification packet enough to change their current diligence process?
• What implementation burden sits in lender integrations versus buyer rulebook encoding?
• How many lenders in the beachhead are adding new funding channels each year?

Model sanity

• Revenue engine. Base-case Y3 revenue is driven by reaching 12 active lender accounts at roughly $270K blended ACV as first-program deployments expand into additional buyer programs.
• Must go right. The first 3 buyer rulebooks must stay reusable enough to keep deployment under 90 days and protect the 70% gross-margin target.
• Model breaks if. If production conversion slips by about one quarter or ACV falls toward $240K, Y3 revenue drops roughly $300K-$440K and the downside cash curve turns negative.
• Next-round proof. A credible seed story appears once the company exits Y2 with about 7 recurring customers, 2 multi-program expansions, partner-sourced pipeline, and the first adjacent module live.

Scenarios

Sensitivity

flowchart LR
  DesignPartners --> ProductionCustomers
  ProductionCustomers --> MultiProgramExpansion
  MultiProgramExpansion --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: The base case depends on existing lenders expanding from one funded channel into multiple buyer programs; single-program usage alone does not support the $270K blended ACV. · The beachhead is narrow, so the venture case still needs adjacent reporting or securitization workflows to open more spend per customer over time. · Cash stays positive because hiring is disciplined; pulling forward compliance or delivery hires before rulebook reuse is proven compresses the low point by more than $100K. · The downside case turns cash negative before the end of Y3, so the company should start the seed process well before buyer-trust risk is fully resolved.

• Counterparty fragmentation. Buyer rulebooks may vary enough across warehouse lenders, funds, and tokenized programs that implementation becomes services-heavy. Mitigation: Start with one asset family and a small set of repeat buyer templates, then productize the most common eligibility and documentation patterns before widening coverage.
• Data-quality liability. If originator source data is inconsistent, the startup could be blamed for certification errors even when the bad input came from the lender. Mitigation: Make every certified field traceable to source data, expose confidence and exception states clearly, and begin with human approval on all pass-fail decisions.
• Incumbent channel capture. Figure, major warehouse lenders, or LOS vendors could bundle basic onboarding tools once the use case is proven. Mitigation: Win as a neutral multi-buyer control layer that works across counterparties and accumulates cross-network exception intelligence no single rail or lender naturally owns.