Operational systems record the unglamorous middle of a business: a job is scheduled, a part is ordered, an invoice goes out, a payment is late, someone decides what to do about it. Buyers value these records for the exceptions and approvals, not the ledger totals.
No dataset needed to start. Buyers price from a one-page manifest; nothing leaves your systems until you sign.
Ledger totals are not what buyers want. The exceptions, approvals, and work-order histories around them are, and they are worth more when paired with the communication about them.
Every record type carries a weight in the estimator behind /estimate, and the weights are published so you can see the work. Billing & operations sits at the steady end of the eight.
Indicative range observed across the market for single-company operational data licenses. Not a quote. Actual value depends on buyer demand, data quality, rights, and exclusivity.
Open the estimator →A fictional record, prepared the way a buyer would receive it. The workflow survives. The people, companies, and identifiers do not.
| Field | Your record | De-identified copy |
|---|---|---|
| Work order | WO-20931, HVAC no-cool, 2024-07-22 | WO-001, HVAC no-cool, 2024-Q3 |
| Customer | Rosa Delgado, 1427 Juniper Ln, Mesa AZ | Residential customer, suburban US Southwest |
| Dispatch | Tech: Jamal Pierce, ETA 2:30pm, parts: capacitor 45/5 | Tech 04, ETA mid-afternoon, parts: capacitor 45/5 |
| Exception | Customer disputed the $189 diagnostic fee; manager Carla approved waiving it after a warranty check | Customer disputed the $189 diagnostic fee; manager approved waiving it after a warranty check |
| Invoice | $412.00, paid by card ending 4471 | $412.00, [payment details removed] |
Fictional example for illustration. Names, companies, and identifiers are made up; no real record is shown. The signed license specifies the de-identification standard, who performs it, who verifies it, and the remedy if it is missed.
What gets removed, what gets excluded by rule, and what to confirm about your rights. Your counsel signs off on scope before any buyer sees it.
Customer and vendor names, tax IDs, bank details, and addresses are replaced with consistent fictional values. Totals can be kept, bracketed, or scaled at your choice.
Payment-card numbers and bank account numbers are removed outright, which keeps PCI-scoped data out of any sample.
Confirm customer and vendor contracts do not treat pricing or terms as confidential in a way that blocks licensing, and check your accounting software's terms for export rights.
We help you build the manifest and we ask these questions, but we do not provide legal advice. Whether a specific set of records can be licensed is a decision for your counsel.
Dispatch, exception handling, scheduling, and SOPs.
Reconciliation, close checklists, approvals, client correspondence.
Transaction coordination, leasing, maintenance workflows.
Scheduling, billing, authorizations, and non-clinical ops.
Client onboarding, project delivery, reusable methods.
No. Buyers are not interested in your P&L. They want the workflow around transactions: how an invoice is raised, approved, disputed, collected, and closed. Totals can be scaled or bracketed without losing that.
Card numbers are. They are removed outright, along with bank account numbers, before a sample is built, so no PCI-scoped data is ever in the licensed copy. If your systems store full card numbers, that is worth fixing regardless of licensing.
It is normal, and it is part of what buyers want to see: a work order in one system, the approval in email, the invoice in accounting. The manifest describes each system and the identifiers that connect them, and buyers value sets where a job can be followed across all three.
Seven questions. No dataset. First offer in 24 to 48 hours of a complete manifest.
Measured from a complete data manifest. A first offer is a process target, not a guarantee; buyers decide eligibility, price, and terms.