Maybern sells fund-management software to the finance teams of private-fund general partners—the CFOs, controllers, and fund accountants who must calculate how money flows among a fund's investors every quarter. The core problem is that these calculations—capital calls, distributions, management fees, and profit-sharing waterfalls—are governed by dense legal agreements (limited partnership agreements and side letters) that differ fund by fund and investor by investor. Finance teams commonly maintain these calculations in spreadsheets and reconcile them each quarter, a process that is slow, error-prone, and difficult to audit.

A controller using Maybern begins by encoding the fund's legal terms into the platform using MXL, a custom formula language Maybern built to express fee bases, waterfall tiers, and side-letter provisions as deterministic, versioned rules. Once configured, the system can execute a capital event—say, a distribution after a portfolio company is sold. The controller triggers the distribution in Maybern; the engine allocates cash across every investor according to the encoded waterfall and preference terms, applies fee breaks and offsets, and produces an audit-ready Excel export where every output traces back to the inputs and logic that produced it. The controller then compares Maybern's figures against the external fund administrator's books and reviews any breaks before approving the final numbers.

Beyond the core Fund Intelligence product, Maybern ships Scenario Modeling, which lets investment committees ask hypothetical questions—what happens to carry and LP returns if an exit date shifts or an assumption changes—and receive answers computed from the same encoded fund logic rather than a one-off spreadsheet.

In July 2026 Maybern launched an MCP (Model Context Protocol) server, the open standard that lets external AI agents connect to other software. With the MCP live, a team can point Claude, ChatGPT, or a custom agent at Maybern's engine. The agent can query live fund data, draft new MXL calculations, and build reports, but every write lands as a draft; nothing finalizes until a human completes it inside Maybern. Maybern also offers its own packaged agents—deployed capabilities for administrator reconciliation, investor-request responses, and quarter-end package preparation—accessible through email, Microsoft Teams, or the Maybern interface. When the agent encounters an ambiguous side-letter clause or an unresolvable break, it stops and routes the item to a person with the reason attached.

As of the Series B announcement, Maybern reported supporting more than $80 billion in assets under management across over 150 fund vehicles. The platform is in production across private equity, real estate, real estate credit, private credit, and growth equity strategies. Seven institutional fund managers with $2 billion to $250 billion in AUM served as design partners during product development. Deal-by-deal American waterfalls, multi-currency support, and certain alternative-investment-vehicle configurations are described as in active development.

Maybern sells enterprise SaaS to GP finance organizations. The buyer is typically the CFO or head of fund operations at a private-fund manager; the day-to-day users are controllers and fund accountants. No public pricing or per-fund/per-AUM rate has been disclosed.

Implementation is labor-intensive by design. Maybern's Forward Deployed Engineers work alongside a customer's controller to encode the fund's waterfall, allocation, and fee logic in MXL, then validate outputs against several historical close periods before go-live. This configuration cost is a barrier to entry for competitors but also a real expense for Maybern on each new deployment. Once a fund's terms are encoded and versioned, however, the logic is reusable across quarters and extensible to new fund vehicles within the same family, which should reduce the marginal cost of serving additional funds at an existing customer relative to the initial setup.

Maybern does not replace the fund administrator; the administrator continues to produce the official books. Maybern positions itself as the parallel verification and performance-economics layer, which means it must integrate with—not displace—the administrator's data. The company's agents and MCP surface value by reducing the hours controllers spend on quarterly reconciliation and investor reporting, creating retention through workflow dependency rather than data lock-in alone.

Maybern competes against a combination of incumbent fund-accounting platforms, outsourced fund administrators, and the spreadsheets that remain the default tool for complex waterfall and allocation work. The central contest is whether a purpose-built, deterministic calculation engine with AI agent capabilities can displace deeply entrenched manual and semi-automated workflows at firms that have historically tolerated spreadsheet risk because no software could faithfully encode their bespoke terms.

These are the large incumbent platforms serving alternative-asset managers. They offer broad fund-accounting, portfolio-management, and investor-reporting suites and benefit from long-standing integrations with fund administrators and auditors. Maybern competes on configurable fund-level economic calculations and reconciliation alongside the administrator. The incumbents offer broader suites, established customer relationships, and adjacent functionality that can reduce the appeal of another specialized system.

Carta has expanded from cap-table management into fund administration, offering a vertically integrated service that combines software with administrator-of-record status. This bundling appeals to emerging and mid-market managers who want a single vendor. Maybern takes a different approach—it does not serve as the fund administrator and instead positions itself as the GP's own verification layer alongside whichever administrator the fund uses. The purchasing choice is between an integrated administration relationship and a separate calculation and verification platform that works alongside existing providers.

The most common competitor is the status quo: Excel models maintained by senior accountants, sometimes supplemented by internal engineering teams at larger managers. Spreadsheets are flexible, but maintaining consistent versions, traceable changes, and reconciled outputs requires additional controls and manual work. Some large managers have attempted to build proprietary systems, creating key-person risk around the engineer who built them. Maybern's pitch is that it provides the deterministic, auditable foundation an internal team would spend substantial effort building, but the implementation effort required to encode a fund's full term set means the switching cost from spreadsheets is a meaningful implementation project.

Maybern's core market is the back-office finance function at private-fund GPs—controller-level users performing quarterly closes. The company has described the global alternatives market as exceeding $16 trillion in AUM, projected to reach $32 trillion by 2030. Expanding beyond the back-office close process into adjacent budgets and buyer types would meaningfully enlarge the addressable opportunity.

Maybern already ships scenario modeling that lets users change exit dates or return assumptions and see the impact on carry, LP returns, and fund IRR. If this capability becomes trusted enough for real-time use during investment-committee meetings and deal-evaluation sessions, the buyer shifts from the back-office controller to the front-office deal team and general partner—a different purchasing constituency. The advantage is that scenarios run on the same encoded fund logic used for official reporting, so scenarios use the same configured economic terms as reporting. The dependency is proving that the models are fast and flexible enough for live deal discussions, and that front-office users will adopt a tool built for the back office.

Maybern's agents and MCP can draft investor replies, fill track-record templates, and prepare tear sheets from verified fund data. If these workflows mature beyond controller supervision into a reliable, semi-autonomous investor-relations function, the platform moves into the budget of the IR and fundraising team—departments that today rely on manually assembled pitch books and DDQ responses. The capability advantage is that agent-generated answers trace to deterministic fund logic rather than ad hoc spreadsheet pulls, which matters for institutional LPs performing due diligence. This path depends on agents reaching sufficient reliability that IR professionals trust draft outputs with minimal revision, and on Maybern's MCP ecosystem attracting enough third-party agent builders to cover the variety of LP reporting formats in the market.

Maybern's Fund Intelligence product already includes a Credit Facility module for tracking drawdowns, paydowns, interest expenses, and borrowing bases. Private credit funds and interval funds involve ongoing facility-level operations—interest accruals, borrowing-base compliance, and periodic liquidity calculations—that are distinct from the episodic capital-call-and-distribution cycle of traditional private equity. If Maybern extends its deterministic engine to handle the continuous, facility-driven economics of direct lending and private credit vehicles, it could expand into ongoing lending operations served by a patchwork of loan-administration systems and spreadsheets. The advantage is that the MXL framework is designed to encode arbitrary financial rules, so credit-facility covenants and waterfall provisions could in principle be expressed in the same language. The dependency is building the specific credit-facility logic, validating it against the operational cadence of credit funds, and winning implementation engagements with credit-focused managers who may have different administrator relationships and data formats than equity-focused GPs.

Encoding errors propagate with consistency: Because Maybern's engine runs the same deterministic logic every quarter, a term encoded incorrectly in MXL will produce consistently wrong numbers across every affected investor and period. Human approval gates exist, but reviewers may trust the system precisely because it is deterministic, reducing the scrutiny that would catch a subtle misinterpretation of an ambiguous LPA clause.

High implementation cost limits velocity: Each new customer requires Forward Deployed Engineers to configure fund-specific waterfall, allocation, and fee logic and validate against historical closes. This labor intensity constrains how quickly Maybern can onboard new accounts and raises the cost of serving smaller managers, potentially capping the addressable market to firms large enough to justify the setup investment.

Incumbent administrator integration is a gating dependency: Maybern's reconciliation and agent workflows depend on ingesting data from the fund administrator's files. Administrators such as SS&C and Citco control the format, timing, and accessibility of those files, so changes to their exports or service arrangements could disrupt reconciliation.