Enterprise DNA

Instead of FADEL LicenSee

Stop renting FADEL LicenSee. Own your licensing desk.

We build your version around your licensed products and reporting cycle, map your LicenSee source records, and run it for you through Omni by Enterprise DNA.

FADEL LicenSee has no numeric subscription price on the product page reviewed. Compare your actual contract and implementation bill with an owned version.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

Six jobs behind the LicenSee bill

LicenSee combines royalty operations and reporting. Start with the work your own agreements require, then decide what belongs in your version.

description

Agreement terms

A catalogue of properties, deal terms, royalty rates and payment rules.

event

Reporting deadlines

Contract dates and notifications for the people responsible.

upload_file

Sales intake

Sales records brought in through a spreadsheet template.

calculate

Royalty processing

Calculations across contract terms, including advances and minimum guarantees.

fact_check

Licensor statements

Formatted royalty statements for major licensors.

bar_chart

Review and performance

Contract performance, compliance checks and audit records.

Your owned version

A royalty review you can trace to the source

Agreements

Keep permission beside the sale

The free base records a specific property, country, product category, currency and flat royalty rate for each agreement.

  • check Signed agreement evidence stays with the terms.
  • check Each product has dated approval evidence.
  • check Sales before approval are flagged for review.
  • check Wrong-country sales remain visible and cannot enter a closed statement.

Reporting

Close a period with evidence

The free base calculates eligible net-sales royalties and keeps the reviewed result with its supporting sales.

  • check Reporting periods cannot overlap.
  • check Amounts round to cents on each sale.
  • check A different named reviewer records the reconciliation.
  • check Closed statements retain a frozen copy of the sales and terms used.

Monday review

Join deadlines, exceptions and follow-ups

Ask which late statement is blocked, which product lacks approval and who owns the next action, in one review built from your records.

  • check Overdue statements show their unresolved sale count.
  • check Follow-ups carry an owner, due date and outcome.
  • check Upcoming licence expiries appear together.
  • check Whole-term minimum exposure stays separate by currency and is labelled as a working comparison.

Ownership

Keep the evidence when systems change

Your original sales import, mapping, review notes and activity stay in the database with your working records.

  • check Repeated identical imports do not duplicate sales.
  • check Changed records cannot silently overwrite live work.
  • check Private branded reports cover licence terms, royalties and evidence.
  • check Your own fields and review rules can be added with a tested change.

Make it yours

Design your own FADEL LicenSee replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from FADEL LicenSee. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your FADEL LicenSee replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your FADEL LicenSee data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Licensed Products for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Licensed Products for Claude Code

Connected to your own database

Which royalty statements are overdue and still need review?

DEMO-Q1

Agreement
DEMO-FOREST
Due on
2026-11-05
Status
overdue
Sale count
3
Exception count
2
Currency
NZD
Earned
1520.00

DEMO-Q2

Agreement
DEMO-FOREST
Due on
2026-12-30
Status
open
Sale count
1
Exception count
0
Currency
NZD
Earned
800.00

Ask it anything

Questions your own licensing records answer

Ten questions answered by the working demo, with your agreements, approvals and sales available to inspect.

chat_bubble Which reporting periods are overdue and still contain exceptions?
chat_bubble Which sales were made outside the licensed territory?
chat_bubble Which products were sold before their approval date?
chat_bubble Which sales use a different currency from the agreement?
chat_bubble How much eligible royalty has each period earned?
chat_bubble How much of each whole-term minimum remains unearned?
chat_bubble Which licences expire in the next sixty days?
chat_bubble Which follow-ups are overdue and who owns them?
chat_bubble Which licence records need a retention or purpose review?
chat_bubble Which sales and evidence supported a closed statement?

Switching

How to switch from FADEL LicenSee

A move usually involves exporting the records your account allows, mapping the sales history and checking the imported records against your existing statements before you switch.

  1. 1

    Export your available records

    Ask FADEL LicenSee how to export the records available in your account. The vendor material reviewed documents spreadsheet sales intake, but not a full account export format. Export what the account allows, usually CSV or Excel, and check with FADEL. Include sales history and, where available, agreements, product approvals, reporting periods and past statements or supporting evidence.

  2. 2

    Map and load the records

    Enter your signed agreement terms and product records before bringing in sales. Map the available sales records to the replacement’s sales fields, keeping source references and original rows. Validate a sample first, and use a test run first if your import process offers one. Then load the mapped sales history. Choose which periods and how much history to bring across based on what you need to review.

  3. 3

    Review flagged sales

    Check each flagged sale against the source records, agreement and product approval evidence. The replacement flags sales outside the recorded country, currency or licence dates, and sales made before product approval. These sales stay outside eligible totals and block period closure. Reconcile imported totals against your existing statements, and resolve mapping gaps or differences before relying on a new statement.

  4. 4

    Run both systems side by side

    Keep LicenSee and the replacement in use together for a short period, including a real reporting cycle before you switch. Enter or compare the same sales and review the exceptions, eligible totals and working statement in both systems. Check that the replacement reflects your signed terms and your chosen history. If totals or treatment differ, trace the difference to its source before moving reporting work.

  5. 5

    Switch off LicenSee

    After you have reviewed the side by side results and reconciled the records, move new reporting work to the replacement and stop entering new records in LicenSee. Keep access to the source records you still need, and confirm with FADEL how to close the service under your agreement. Make sure the imported history and supporting evidence remain available in the database you own.

construction

Where the real effort goes

The work is usually in mapping your own fields and contract rules, then deciding how much sales and statement history to bring across and reconciling it. The base supports a bounded set of terms, so check any tiered rates, advances or required statement formats before relying on it. If Enterprise DNA runs the replacement, they map your source records and scope those requirements with you.

Not ready for a call?

Get your FADEL LicenSee switch plan by email

We will send you the step-by-step plan for moving your business off FADEL LicenSee, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Build it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install.
  2. 2 Run npm run demo with Claude Code, Codex, OpenCode or Cursor.
  3. 3 Enter the signed terms, map your source sales and test the import.
  4. 4 Reconcile a reporting cycle before using your own database for live records.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your properties, agreement terms and approval rules.
  • check Your LicenSee source data mapped across and reconciled.
  • check Your licensor statement layouts and required calculations.
  • check A web front end or a different stack when your team needs it.
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and the reporting cycle set up.
  • check Connected to the sales records your business already keeps.
  • check Exceptions, follow-ups and statement drafts prepared for review.
  • check Operated through Omni by Enterprise DNA as your business changes.
Book a 30-minute call

Questions

Instead of FADEL LicenSee, answered

Is this a replacement for every LicenSee feature? expand_more

The free base handles flat-rate licensed-product records, sales checks and royalty working statements. Enterprise DNA scopes your tiered terms, advances, required statement formats, connections and team screens into the custom version. We check those requirements against a real reporting cycle before you switch.

Can you bring my existing sales and contracts across? expand_more

Yes, with mapping and reconciliation. The vendor material reviewed documents spreadsheet sales intake but does not publish a full-account export format. The free version imports mapped source sales after the agreement and product records are entered. Enterprise DNA maps the available history and checks it against your existing statements.

What stops an incorrect sale reaching a statement? expand_more

The free base flags sales outside the recorded country, currency or licence dates, and sales before product approval. Those sales stay outside eligible totals and block closing. A different named reviewer records the reconciliation. The recorded names are review labels; Enterprise DNA designs staff access for a shared installation.

Does it submit statements or pay royalties? expand_more

It prepares private working records and drafts. Your people review the licence terms, minimum guarantees, advance treatment and final amounts before any submission or payment. Enterprise DNA can build the required statement layouts and approved connections into your version.

What will Enterprise DNA charge, and who owns the records? expand_more

We agree one setup fee and a retainer after reviewing your agreements, sales history and reporting requirements. No price is set here. Your records stay in a database you own, with a complete private export available. The free base has no licence fee; hosting and your chosen assistant are separate costs.

Bring one licence agreement and one royalty statement

Spend 30 minutes with Sam. Bring your LicenSee bill, a signed agreement and a recent statement. We will work through the calculation, the evidence and the reporting cycle, then show what your owned version needs.

Book a 30-minute call Get the free version

Licensed Products for Claude Code is free and open source, published by Enterprise DNA.

Done paying for FADEL LicenSee?

Get your version built