Transfer-agency AI for evergreen private-credit and real-estate funds that clears subscriptions, redemptions, and cash breaks.

1. Evergreen structures and new investor channels are making private markets operationally more complex, which turns transfer-agency and cash workflows into an immediate scaling bottleneck.
2. The labor answer is breaking because qualified accountants are down while private markets are projected to triple, so automation now protects throughput rather than just saving a few analyst hours.
3. The needed context already spans ERP, banking platforms, email, and documents, which makes a cross-system case-building product more viable than another rip-and-replace back-office suite.
4. Nomerra's audit-trail framing and review-first workflow suggest buyers will adopt agents that prepare and route work before they trust fully autonomous posting.

Catalyst. Nomerra's funding and the sources' repeated emphasis on evergreen structures, new investor channels, accountant shortages, and audit-ready agents show that private-markets firms now have a near-term scaling problem in back-office workflow rather than a vague future AI ambition.

The product sits above a manager's existing ERP, banking portals, email queues, and document repositories to build a live case file for every subscription, redemption, cash movement, or investor instruction mismatch. It reads forms, notices, prior investor records, and procedure docs, then proposes the next action, creates reviewer checklists, and drafts outbound notices or internal handoffs with citations. Humans approve every action before anything is posted or sent, preserving the audit trail private markets need. The first ROI is not "AI chat"; it is faster turnaround on exception-heavy investor operations with fewer rekeys and fewer misses at month-end or reporting time. As the system sees more resolved cases, it learns which edge conditions, counterparties, and procedures drive the most operational drag.

What's different. Legacy fund-accounting and transfer-agency systems become systems of record only after someone has already assembled the right case and reconciled the exception. Outsourcers add people to that last mile, but they do not create reusable operational intelligence. This company owns the procedure-and-exception layer between ERP, bank, document, and inbox systems, building a proprietary graph of how each firm actually resolves edge cases across evergreen-fund operations.

Jobs to be done

flowchart LR
  Buyer[Fund ops leader] --> Pain[Subscriptions redemptions and cash breaks across ERP bank and email]
  Pain --> Product[Transfer-agency workflow agent]
  Product --> Outcome[Faster audited investor processing]

Executive takeaways

• Evergreen private-market wrappers have moved from niche to core distribution infrastructure: Dakota tracks 252 active registered evergreen vehicles with $431B in net assets, while Preqin counted 520 evergreen funds and $350B NAV by end-2023, so operational tooling is now a scale bottleneck rather than a pilot problem [3][20].
• The beachhead pain is not ledgering; it is lifecycle coordination across subscriptions, redemptions, KYC/AML, cash, and valuation workflows that legacy point tools and outsourced handoffs still fragment [2][13][29][37].
• Competition is real but diffuse: incumbents own systems of record and servicing scale, while AI-native challengers and onboarding tools attack slices of the workflow; no dominant vendor yet owns evergreen exception-resolution across email, portals, bank flows, and docs [1][8][10][12][13][21].
• The best initial wedge is approval-gated case assembly for transfer-agency and cash exceptions, because regulation increasingly widens retail access but also tightens liquidity, investor-protection, and audit expectations [16][17][18][19].

Market definition

The relevant market is evergreen private-markets operations workflow software: systems that sit between investor onboarding, transfer agency, fund administration, treasury, and reporting stacks to prepare and route subscription, redemption, and cash-exception work with a defensible audit trail [2][3][20].

Customer and buyer

Day-to-day users are fund operations, transfer-agency, treasury, and investor-services teams at managers or administrators handling continuous subscriptions, redemptions, and cash exceptions. The budget owner is usually the COO, CFO, or head of operations when a firm is launching a new evergreen product or expanding into RIA/private-bank distribution [2][6][37].

Buying triggers

• Launch of a new evergreen or semi-liquid vehicle forces managers to redesign subscriptions, liquidity, valuation, and investor-service operations. [2][16][17]
• Expansion into RIAs or private banks raises transaction count, reporting expectations, and operational scrutiny from wealth channels. [5][6][35]
• Redemption queues, quarter-end spikes, or ongoing fund-finance and cash exceptions expose the limits of spreadsheets, inboxes, and handoffs. [14][21][39]

Willingness to pay

Willingness to pay is credible because the budget already exists inside transfer agency, retail-alts operations, fund administration, and digital workflow modernization. The startup is not creating a new category so much as redirecting spend away from manual exception labor and fragmented service-provider coordination. [7][13][21][27]

Category dynamics

Growth signal 27% annualized U.S. perpetual fund AUM growth (Q4 2014-Q4 2024)

Validation signals

• Nomerra could raise capital specifically around audited private-markets workflow agents.
• KKR’s RIA survey shows the advisor conversation has shifted from whether to use private markets to how to operationalize them.
• SS&C’s retail-alts case-study and product positioning show that account-volume scaling and wrapper selection are already real operating pain points.
• Allvue says GPs are ramping AI use but still need governance and data controls, which supports a review-first workflow wedge.
• 73 Strings and Chronograph both frame evergreen private credit operations as a breaking-point problem around valuation frequency, liquidity, and reporting.

Regulatory & technical constraints

• LTAF and ELTIF wrappers explicitly require notice periods, liquidity tools, warnings, and investor-protection workflows that must be reflected in day-to-day processing.
• Because investors subscribe and redeem at NAV, valuation support and case evidence become transaction-critical rather than mere reporting artifacts.
• Continuous onboarding, AML, and KYC checks create sensitive investor-data flows that need auditable automation and strong portal hygiene.
• Inbox and document integrations should start with least-privilege permissions and clear review checkpoints before any broader action rights are granted.

Competition is strongest around adjacent layers rather than the exact wedge: Nomerra is closest on AI-native private-markets ops, Juniper and Allvue come from platform-of-record positions, SS&C owns servicing scale, and Passthrough plus Broadridge own workflow slices. The gap is still the evergreen-specific exception layer that assembles a case from documents, portals, cash data, and prior records before a human approves the next step [1][8][10][12][13][21].

Why incumbents do not win by default

• Full-service transfer agents. They win on compliance and scale, but the operating model is often service-heavy and slower to configure around one manager’s evergreen exception playbook.
• GP software platforms. Juniper Square owns investor-facing workflow and administration context, but its breadth makes it more of a platform backbone than a purpose-built evergreen exception engine.
• Private-credit accounting suites. Allvue is deep in private debt books and reporting, yet the product center of gravity remains accounting, portfolio, and portal modules rather than cross-channel case assembly from email, docs, and bank portals.
• Onboarding and KYC point solutions. Passthrough-style tools solve subscription documents and compliance intake well, but they do not by default own redemption queues, cash breaks, or post-subscription exception workflows.
• In-house spreadsheets plus administrators. The default today is still stitched-together operations between internal teams and outsourced providers, which preserves judgment but leaves case history fragmented across inboxes, spreadsheets, and provider portals.

Evergreen private-credit and real-estate funds have turned subscription, redemption, and cash-exception handling into a structural bottleneck: 252 active registered U.S. evergreen vehicles and 520 global evergreen funds now route investor transactions through ERPs, bank portals, email, and spreadsheets, while the qualified-accountant pool has shrunk by a third over the last decade. We are building an approval-gated case-assembly agent that sits above a manager's existing systems, compiles every subscription, redemption, or cash-break case with citations, drafts the next action and outbound notice, and routes it for human sign-off before anything posts. The beachhead is $5B-$25B AUM private-credit and real-estate managers running 2-6 evergreen vehicles through RIA or private-bank channels, sold to the COO or CFO on faster, auditable investor turnaround rather than headcount replacement. Nomerra's $2M raise confirms investor appetite for this workflow layer, but no source names a paying evergreen-transfer-agency customer, discloses pricing, or shows which queue (subscriptions, redemptions, or cash breaks) converts fastest, so the first 90 days must answer that before broader build-out. Our wedge is narrower than Nomerra's stated fund-accounting-treasury-transfer-agency scope: we start with transfer-agency and cash exceptions only, deferring fund-accounting close and treasury forecasting until the first vertical proves out. The moat is a firm-specific procedure-and-exception graph plus a labeled history of accepted and rejected agent actions, which is slow for incumbents and generic AI tooling to replicate. The primary risk is regulatory-accuracy exposure from a bad AI-prepared investor action, which we manage by keeping every posting and notice human-approved through at least the first two years. We are raising a seed round to fund three design-partner deployments, prove exception-resolution turnaround gains, and reach a repeatable $200k+ ACV sales motion before expanding the workflow surface.

Problem

• Private-credit and real-estate managers running evergreen, wealth-channel funds process subscriptions, redemptions, cash movements, and investor notices across disconnected ERP systems, bank portals, shared inboxes, document folders, and spreadsheets, forcing the same data to be retyped and re-checked by fund accounting, treasury, transfer-agency, and administrator teams multiple times per transaction.
• Regulatory tightening and new wealth-distribution channels are raising transaction volume just as the qualified-accountant labor pool shrinks (down roughly a third over the last decade while private markets are projected to triple within five years), so the bottleneck is shifting from ledger entry to exception handling that senior ops staff must assemble by hand.

Solution

• An approval-gated workflow agent builds a live case file for every subscription, redemption, or cash-exception mismatch by reading forms, notices, prior investor records, and procedure documents across a manager's ERP, banking portals, email queues, and document stores, then proposes the next action with citations.
• Every drafted posting, notice, or internal handoff routes to a human reviewer before it is sent or booked, preserving the audit trail private markets require while shifting staff from assembling case files to reviewing AI-prepared work, with each resolved case feeding a firm-specific exception-pattern model.

Why we win

• We are narrower than Nomerra's stated fund-accounting/treasury/transfer-agency scope: a single evergreen-transfer-agency and cash-exception wedge lets us prove turnaround-time ROI on one queue before a manager has to trust us with core ledgers or forecasting.
• Full-service transfer agents and GP platforms (Juniper Square, Allvue, SS&C) own systems of record or servicing scale but are structurally slower to configure around one firm's exception playbook; we own the procedure-and-exception layer between their systems rather than competing to replace them.
• Read-only ingestion from inbox, portal, and document-store connectors lets us start deployments in weeks, not the quarters a core-system replacement requires, matching the technology landscape's finding that OCR/IDP and mail-permission tooling are already mature enough for preparation-not-autonomy workflows.

Milestones

flowchart LR
  Wedge[Evergreen transfer-agency and cash-exception wedge] --> MVP[Read-only case-assembly MVP]
  MVP --> Proof[Design-partner turnaround-time proof]
  Proof --> Expansion[Cash-break and accounting-close expansion]
  Expansion --> Channel[Administrator and TA-consultant channel]

Founding team

Risk assessment

What must be true

• A $5B-$25B evergreen manager will name and prioritize budget for one exception queue within a single fiscal cycle.
• Read-only inbox/document ingestion produces enough context to draft accurate, citable case resolutions without deep ERP or bank API access.
• Reviewers will trust and approve a majority of agent-drafted actions within the first two pilot quarters rather than rejecting most of them.
• At least one fund administrator or transfer-agent consultant will refer or co-sell a paid pilot within the first 12 months.
• The chosen first queue (subscriptions, redemptions, or cash breaks) shows a measurable turnaround-time improvement without an increase in reopened or escalated cases.

Open diligence questions

• Which specific managers or administrators have been interviewed, and did any confirm a budget figure or timeline for a pilot?
• What evidence exists that reviewers will accept agent-drafted actions at a rate high enough to justify the subscription price versus current staffing?
• How does the product's read-only ingestion approach handle firms whose exception data lives primarily in systems without exportable records?
• What is the realistic timeline and cost to add a second design partner's procedure set without re-building the case-assembly logic from scratch?
• How defensible is the wedge if Nomerra or a GP platform incumbent ships a narrower evergreen-exception feature within 12 months?

Model sanity

• Revenue engine. Base-case revenue is driven by moving from one paid pilot in Y1 to 8 active customers by Q4Y2 and 15 by Q4Y3 at roughly $240K exit ARR per customer.
• Must go right. Pilot-to-annual conversion plus one productive administrator referral must show up by Y2 because sensitivity shows sales-cycle slippage is the fastest way to consume the seed buffer.
• Model breaks if. The downside case appears if Y2 exits closer to 6 than 8 customers and gross margin stalls below 72%, because cash turns negative before Y3 ends.
• Next-round proof. The next financing is justified once the company reaches 5-8 paying accounts, 80%+ reviewer acceptance, and a repeatable $200K+ ACV motion with referral evidence.

Scenarios

Sensitivity

flowchart LR
  Leads[Evergreen launch triggers] --> Pilots[Paid pilots]
  Partners[Administrator referrals] --> Pilots
  Pilots --> Customers[Annual customers]
  Customers --> Revenue[Subscription + case fees]
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> Cash[Ending cash]

Flags: Quarterly Y2-Y3 revenue assumes customers that appear in a quarter go live early enough to contribute for that quarter, so a one-quarter sales slip would pressure cash materially. · The base case needs the company to hit the high end of the BP’s 5-8 customer milestone by Q4Y2; landing only 5-6 accounts likely requires slower hiring or extra capital. · Gross margin only reaches the 75% target once implementation and integration work standardize, so persistent bespoke work would weaken payback and burn multiple.

• Regulatory-accuracy risk. A bad AI-prepared subscription, redemption, or notice workflow could create investor harm and shut down expansion inside regulated fund operations. Mitigation: Start with approval-gated case assembly and reviewer routing, keep citations for every field and action, and avoid autonomous posting in the first deployments.
• Integration drag. ERP, banking, email, and document systems are fragmented enough to slow deployments and make pilots feel expensive. Mitigation: Begin with read-only ingestion for one evergreen fund, support inbox and file-drop connectors first, and deepen systems integration only after proving exception-resolution value.
• Incumbent and admin inertia. Managers may prefer adding administrator hours or waiting for existing fund-accounting vendors instead of buying a new workflow layer. Mitigation: Sell into evergreen launches or channel expansions, quantify turnaround gains on one exception queue, and position the product as additive to administrators and core systems.