PRODUCTION EXPERIENCE. NEW TRAINING MATERIAL.

Explore licensing your
finance agent’s work.

If your product retains agent traces, tool calls, human corrections or supported outcomes, we can explore a scoped pilot. Loomwell is developing datasets and environments for AI labs and developers from experience authorized for those uses. Any supplier revenue share would depend on attributable buyer payments and a separate agreement.

  1. 01One supplier
  2. 02One buyer
    requirement
  3. 03One accepted
    package
  4. 04Buyer feedback
    guides sourcing

Proposed revenue shareSubject to buyer payment and agreed terms

Seeking initial finance-agent company partners. Source-derived licensing is in development; no earnings are guaranteed.

THE SUPPLIER WORKSPACE

Your scope.
Your releases.
Your agreed terms.

A workspace for onboarded suppliers to review source scope, package status and payment records when available.

Supplier sign in →

LOOMWELL / FINANCE PARTNERSHIP Product workflow

Sources
Bounded access to approved workflows
Datasets
Review and release status
Earnings
Separate allocation, transfer & payout status
Agreement
Permitted uses, authorization & retention

Workspace access follows onboarding. Source access, each release and payment activation require separate approval; a displayed allocation is not a received bank payout.

THE FIRST PILOT

One supplier.
One requirement.
One accepted package.

For finance agent companies, we match one approved source workflow to a buyer’s missing capability. The buyer’s feedback determines which cases we seek next.

01 / Match the need

One source.
One missing capability.

Identify a finance-agent company with useful production evidence and a buyer with a concrete coverage gap. Agree the sample scope, permissions, required format and acceptance criteria before preparation.

02 / Make it useful

Prepare a package.
Let the buyer inspect.

Build a bounded, versioned dataset or environment against that requirement. Track independent case families and total preparation effort. Record the buyer’s decision on the exact package; payment and technical checks alone are not acceptance.

03 / Close the loop

Learn what mattered.
Choose what comes next.

Record why cases were useful, rejected or sent back for rework. Use that feedback and preparation cost to source more of the workflow, refine selection, seek different supply or stop. Share actual licensing revenue under the supplier agreement.

For example, a buyer may need reconciliation exceptions with confirmed ledger outcomes. We would scope an approved accounting-agent sample, prepare one versioned package, and use the buyer’s acceptance or rejection reasons to refine the next sample. Supplier permissions and actual licensing remain separate.

Explore the company partnership

The first pilot is complete when a buyer accepts the agreed package and we record what their feedback says to source next, with a named owner and next action. Preparation effort and useful coverage guide the next cycle.

EXPLORE THE WORKFLOWS

Finance work, made inspectable.

Authored demos across ten segments show possible tasks. The first source partnership will focus on one workflow with usable data and buyer demand.

01Investment bankingInteractive demo

Comps · Precedent transactions · DCF · Merger model · CIM and pitch book drafting

Where agents slip: A comp with a different business model is left in the set.

Open interactive demo
02Private equityInteractive demo

CIM screening · LBO model · Quality-of-earnings review · IC memo

Where agents slip: The same one-time cost is added back twice.

Open interactive demo
03Private creditInteractive demo

Credit memo · Add-back analysis · Covenants · Borrowing base

Where agents slip: Uncapped add-backs are permitted in the covenant EBITDA definition.

Open interactive demo
04Equity researchInteractive demo

Initiation reports · Estimate revisions · Price-target models

Where agents slip: A guidance change is not carried into the estimates.

Open interactive demo
05Hedge fund researchInteractive demo

Earnings model updates · Call and filing analysis · Thesis memos

Where agents slip: A revenue-recognition change in the 10-Q is missed.

Open interactive demo
06Wealth managementInteractive demo

Financial plans · Rebalancing · Suitability · Tax-loss harvesting

Where agents slip: A proposed loss harvest repurchases the same security within the wash-sale window.

Open interactive demo
07AccountingInteractive demo

Month-end close · Reconciliation · Accruals · Revenue recognition

Where agents slip: A documented timing difference is incorrectly flagged as an error.

Open interactive demo
08Banking opsInteractive demo

KYC/AML review · Loan underwriting · Account onboarding

Where agents slip: A beneficial owner is hidden behind two holding companies.

Open interactive demo
09InsuranceInteractive demo

Claims review · Underwriting · Policy comparison

Where agents slip: A claim falls under an exclusion buried in an endorsement.

Open interactive demo
10Trading ops & riskInteractive demo

Backtest hygiene · VaR and Greeks · Pre-trade compliance · Trade reconciliation

Where agents slip: A backtest uses future data: look-ahead bias.

Open interactive demo

Out of scope: alpha generation and trading decisions.

Try a free agent evaluation Explore all environments

DISCUSS THE ECONOMICS

Agree the terms.
Then assess the value.

We have not established supplier earnings or typical license prices. A pilot may produce no licenses or revenue; there is no standard revenue share or earnings forecast on offer.

Define the revenue basis.

Agree the share, which buyer payments qualify, and how fees, costs, refunds, disputes and taxes affect the amount payable.

Define attribution and scope.

Specify the approved material, buyer, uses, duration and any repeat licenses covered by the agreement. Source approval alone does not authorize a release.

Define payment conditions.

Agree payment timing and onboarding requirements. Applying, contributing or passing review alone does not create a right to payment.

A CLEAR SCOPE BEFORE SOURCE ACCESS

Your client relationships
come first.

Define what can be inspected, rebuilt and licensed before a pilot begins.

Discuss your requirements
Do we have to share our entire workflow?

No: start with one bounded failure pattern, not a broad trace export. Agree on the permitted source access, abstraction, derivative creation and lab uses before any connection.

What happens to client names and deal details?

The deliverable may be an approved dataset or a separately authored synthetic world built from a supplier-approved pattern brief. Each format needs specific rights and human privacy review; removing identifiers or rebuilding figures does not guarantee anonymity.

Who decides what can be used?

Your approval must be supported by the necessary company, client and other rights for the source scope, derivatives and intended uses. Operating an agent does not automatically grant rights over client or employer records.

How would the revenue share work?

Your agreement sets attribution, share, payment timing and permitted uses. Applying, submitting or passing review alone does not trigger payment, and earnings are not guaranteed.

What if our contracts restrict data use?

Authority and consent for the specific scope come first. Do not submit client records or credentials through the public contact form.

THE PRODUCT, IN PLAIN LANGUAGE

A practice world
for an AI agent.

An RL environment can give an agent a fictional company, documents, tools and a task. A grader checks its work against specified rules. Our public demos score your structured choices; they do not run or train a model.

Fictional demonstrations for software research, not financial, investment, accounting, tax or legal advice. Demo scores are not professional validation.

01 Numbers right?02 Traps caught?03 Sound decision?
See one in every segment

FOR AI LABS & DEVELOPERS

What does your
finance agent still
need to learn?

Discuss a training package