RecoveryOS helps crypto exchanges prevent dormant customer balances from falling into state-custody limbo.

1. Dormant-balance exposure has reached a scale where manual exception handling no longer works.
2. State-by-state escheatment logic is colliding with crypto products that do not fit legacy bank or brokerage workflows.
3. Buyers now have evidence that software can materially prevent balances from being lost before state custody, making ROI easier to justify.
4. Fresh category funding means compliance leaders can credibly budget for purpose-built infrastructure instead of bespoke legal projects.

Catalyst. Eisen's funding round and reported 31 percent prevention rate show dormant-asset prevention is becoming a budgeted infrastructure category just as crypto accounts expose the sharpest gap in state-by-state rules.

RecoveryOS connects the exchange ledger, CRM, communications vendors, and compliance policy engine to maintain a live inventory of accounts approaching dormancy thresholds. It scores accounts by state-specific clock, asset type, contactability, and documentation gaps, then launches the right outreach cadence before an account tips into escheatment. For accounts that still age out, the product produces an auditable decision trail and orchestrates approved liquidation, remittance, tax forms, and customer-claim workflows instead of forcing ops teams to stitch them together manually. A white-label recovery portal lets customers verify identity, see eligible balances, and reclaim funds without generating bespoke support work.

What's different. Generic unclaimed-property vendors mostly begin at reporting time, after the risky decisions have already happened. RecoveryOS starts months earlier and is built around crypto-specific realities such as omnibus ledgers, token liquidation policies, and customer recovery workflows that mix compliance, tax, and support. Over time, its moat becomes a combination of state-rule decision logs, dormant-account benchmarks, and deeply embedded ledger and messaging integrations that are painful for a platform to rip out.

Jobs to be done

flowchart LR
  Buyer[Crypto compliance team] --> Pain[Inactive balances nearing dormancy]
  Pain --> Product[RecoveryOS orchestration layer]
  Product --> Outcome[Prevented losses and audit-ready filings]

Executive takeaways

• The wedge is real because most incumbents begin at reporting time, while crypto exchanges need a live control plane for inactivity detection, outreach evidence, and asset-treatment decisions before balances tip into escheatment.
• Buyer urgency is concentrated but severe: a small number of large U.S.-serving exchanges and custodians carry multistate dormant-balance exposure, and mistakes can trigger asset loss, customer anger, audits, and taxable forced liquidation.
• Competitive intensity is moderate-high in generic unclaimed-property software, but low in crypto-native dormant-account prevention; that leaves room for a specialist workflow system rather than a broad compliance suite.
• The first product should stay U.S.-first and custody-first, because state fragmentation is the core source of pain and the main reason generic reporting tools do not solve the problem end to end.

Market definition

Software and managed-workflow infrastructure for U.S.-serving custodial crypto platforms that identifies dormant accounts early, orchestrates compliant owner outreach, and produces an auditable path for liquidation, remittance, or recovery. The market is narrower than generic unclaimed-property reporting and narrower than broad regtech; the job is to operationalize dormant-asset decisions inside exchange and wallet operations.

Customer and buyer

Primary users are dormancy, compliance-operations, finance-operations, and customer-operations teams inside U.S.-serving crypto exchanges and custodial wallet platforms. The economic buyer is typically the Chief Compliance Officer, General Counsel, VP Operations, or equivalent executive who owns abandoned-property risk, audit exposure, and support-heavy recovery workflows.

Buying triggers

• Annual holder-reporting calendars and due-diligence windows turn dormant-balance cleanup into a recurring audit event rather than a one-off legal memo. [6][24][25][27]
• State treatment of digital assets is moving from ambiguity toward explicit rules, which forces exchanges to revisit policy, controls, and customer communications. [17][26][28][29]
• Customer harm becomes concrete when an exchange may have to convert dormant crypto to USD and trigger a taxable event before remittance. [17][30]

Willingness to pay

Public pricing is sparse because the serious alternatives sell as enterprise or consultative software: Sovos markets custom-priced reporting and due-diligence automation, NAUPA still points smaller holders to basic reporting tools, and Simple Escheat positions itself as a lighter-weight DIY filing product. That pattern suggests budget exists for multi-state holder compliance, but a crypto-native platform must justify premium spend by preventing losses before the reporting stage. [6][19][20][46]

Category dynamics

Growth signal Policy-led growth; no clean standalone CAGR for crypto dormant-asset software was fetch-verified in this run

Validation signals

• Eisen says it monitors nearly $16B across close to 50 firms and prevented more than 31% of at-risk assets from flowing into state custody in 2025.
• Binance.US publicly warns customers that dormant crypto may be converted to USD and that such conversion may create a taxable event.
• Delaware, Arizona, and Virginia all have official legislative artifacts showing digital assets are becoming an explicit abandoned-property topic rather than a theoretical edge case.

Regulatory & technical constraints

• A holder must identify dormant property, attempt owner contact, and file in the right state-specific process and format; this is not optional back-office housekeeping.
• State treatment of digital assets still diverges across liquidation versus in-kind approaches and across dormancy and reporting calendars.
• Custodial crypto workflows are harder than cash accounts because activity signals, wallet control, valuation, and token treatment are more ambiguous.

The landscape splits into four classes: crypto-native dormant-asset specialists, horizontal unclaimed-property reporting suites, state-program or audit-heavy incumbents, and lightweight filing tools. The proposed startup wins only if it owns the preventive workflow layer inside crypto operations. Generic reporting vendors already prove the budget, but they do not automatically own ledger-native inactivity detection, crypto-specific liquidation decisions, or customer-recovery UX.

Why incumbents do not win by default

• Horizontal reporting suites. Sovos validates that enterprises buy software for due diligence, dormancy calculation, and multistate reporting, but its center of gravity is horizontal reporting breadth rather than crypto-native preventive orchestration.
• State-program and audit incumbents. Kelmar has deep unclaimed-property credibility and state-program presence, but its posture is still rooted in program administration and compliance services rather than exchange-embedded workflow software.
• DIY filing software. Low-end tools can help holders produce reports, but they do not solve ledger integration, contactability scoring, or crypto-specific treatment decisions before property becomes reportable.
• In-house teams and outside counsel. Manual calendar management and legal memos remain the default substitute, yet state deadlines, owner-notice requirements, and asset-handling edge cases make the process too operationally heavy for spreadsheets alone.

RecoveryOS should launch as a U.S.-only dormant-asset control plane for custodial crypto platforms, not as a broad regtech suite or a filing-only vendor. The first customer is a retail crypto exchange or custodial wallet platform with more than 1 million historical funded accounts and an upcoming dormant-property review, compliance exam, or sponsor-bank request. The researched wedge is credible because state-by-state dormancy rules, owner outreach duties, and crypto asset-treatment decisions create an operational burden that spreadsheets, outside counsel, and reporting-first software do not solve well. Product v1 should focus on identifying at-risk accounts, orchestrating notices, capturing audit evidence, and managing approved liquidation, remittance, and claim recovery for custodial balances, with human review for ambiguous state or token cases. Go-to-market should be founder-led and event-driven, selling a paid pilot tied to the next filing cycle and then converting that workflow into an annual platform contract priced on dormant accounts under management plus workflow usage. Research estimates a $20.0M beachhead SAM and a $2.5M year-3 SOM, which is enough for a focused pre-seed wedge but not enough to justify premature expansion. The moat is not generic rule content alone; it is the combination of ledger integrations, state-rule decision logs, and outreach-outcome data that improve prevention and auditability over time. The biggest unresolved question is whether enough exchanges will buy a standalone preventive control plane rather than extending counsel-led or horizontal reporting workflows, so partner-led distribution and pilot conversion are explicit validation work in this plan.

Problem

• U.S.-serving crypto exchanges accumulate inactive customer balances that become legally complex once state dormancy clocks, notice rules, and asset-treatment obligations diverge by jurisdiction.
• Most operators still rely on spreadsheets, SQL pulls, outside counsel, and reporting-time vendors, which creates missed outreach, forced liquidation risk, audit exposure, and preventable customer support escalations.

Solution

• Provide a custody-aware workflow system that monitors dormant-account risk continuously, determines the allowed action path by state and asset type, and launches compliant outreach before balances become reportable.
• For balances that still age out, generate an auditable trail for liquidation, remittance, tax documentation, and claimant recovery, plus a white-label recovery portal that reduces bespoke support work.

Why we win

• The company is targeting the preventive operating layer inside exchange workflows, where incumbent reporting suites and counsel-led processes are weakest and where ROI appears before filing day.
• If the startup owns ledger normalization, outreach history, and state-specific decision logs for dormant crypto balances, it can build switching costs and performance data that filing-only vendors do not capture.

Milestones

flowchart LR
  Wedge[Crypto dormant-account wedge] --> MVP[Dormant control plane MVP]
  MVP --> Proof[Prevention and audit proof points]
  Proof --> Expansion[Adjacent digital-balance expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 10-15 large U.S.-serving custodial crypto platforms have dormant-balance exposure severe enough to justify a six-figure annual software budget.
• A pilot can integrate core ledger, CRM, and notice data within one compliance cycle rather than a multi-quarter enterprise services project.
• Customers using the product can prevent at least 15-20% more at-risk balances from reaching state custody than their prior spreadsheet-and-counsel process.
• Exchanges will pay for a preventive operating layer even if they keep downstream reporting, tax, or legal vendors in place.
• Crypto-native workflow data and integrations will compound into better prevention and audit outcomes before horizontal incumbents add equivalent functionality.

Open diligence questions

• How many exchanges in the target ICP actually exceed the pain threshold for six-figure annual spend?
• Which states and asset classes create the first must-have workflow, and where does legal ambiguity still force manual review?
• What implementation effort and security review are required to connect to exchange ledgers and communication systems?
• Who owns the budget in practice: compliance, operations, finance, or a sponsor-bank-driven remediation project?
• Why would a buyer choose this system over Eisen, Sovos, counsel-led operations, or an internal reporting workbench?

Model sanity

• Revenue engine. The base case reaches the researched $2.5M Y3 SOM by getting five beachhead exchanges live and expanding each toward roughly $500K ACV.
• Must go right. Paid pilots have to convert within one filing cycle because the model only carries one dedicated GTM hire before Y3.
• Model breaks if. Cash turns negative if conversions slip toward 12 months and gross margin stalls near 68%, which is the core downside case.
• Next-round proof. A credible seed case appears once Q4Y2 shows five production customers, one full filing-cycle proof point, and partner-sourced pipeline without services creep.

Scenarios

Sensitivity

flowchart LR
  Leads[Target exchanges] --> Pilots[Paid pilots]
  Pilots --> Customers[Production customers]
  Customers --> Revenue[Platform + usage revenue]
  Revenue --> GrossProfit[Gross profit after workflow ops]
  GrossProfit --> Cash[Cash runway]

Flags: The market is concentrated, so losing even one target exchange materially changes the outcome. · The model assumes exchanges buy a standalone control plane before incumbent reporting vendors bundle similar workflows. · Gross margin only clears the BP target if manual policy exceptions fall fast enough to avoid a services-heavy delivery model.

• Regulatory ambiguity. Some states may treat specific digital assets inconsistently, making default liquidation or remittance policies hard to standardize. Mitigation: Start with custodial cash and stablecoin flows, keep policy logic configurable by jurisdiction, and partner with specialist unclaimed-property counsel.
• Urgency concentration. Smaller platforms may not feel enough dormant-asset pain to buy until an exam or filing failure forces action. Mitigation: Focus initial sales on exchanges with million-account back books and price against prevented losses and filing-cycle labor savings.
• Incumbent expansion. Generic unclaimed-property software vendors could move upstream into prevention once the category proves attractive. Mitigation: Win on crypto-native ledger integrations, customer recovery workflows, and a better evidence system before horizontal vendors adapt.