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.
01One supplier
02One buyer requirement
03One accepted package
04Buyer feedback guides sourcing
←Proposed revenue shareSubject to buyer payment and agreed terms
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.
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.
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.
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.