Playbooks, templates, proposals, and checklists are the distilled version of years of trial and error. A model that reads them learns what a finished piece of work looks like and the steps that produce it. Buyers pay for the ones that are used, revised, and tied to real projects, not the ones written once and filed.
No dataset needed to start. Buyers price from a one-page manifest; nothing leaves your systems until you sign.
Documents on their own are common. Documents paired with the completed instances and revision history that show them in use are not, and that pairing is what buyers pay for.
Every record type carries a weight in the estimator behind /estimate, and the weights are published so you can see the work. Documents & SOPs 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 |
|---|---|---|
| Document | SOW - Pinecrest Orthodontics website rebuild v3.docx | SOW - Client 07 website rebuild v3 |
| Owner | Lena Marsh (Account Director) | Role: Account Director |
| Client | Pinecrest Orthodontics, Boise ID | Client 07, dental practice, US Mountain region |
| Fee | $48,500 fixed | [fixed fee, mid five figures] |
| Scope note | Dr. Alvarez wants the booking widget live before the May open house. | Client stakeholder wants the booking widget live before a [date] event. |
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.
Client names, pricing tied to a named account, and personal details inside documents are replaced or removed; the structure and the method stay.
Documents authored by third parties (vendor manuals, licensed templates, client-supplied materials) are excluded unless you hold the rights.
Confirm who owns work product created by contractors, and check client agreements for clauses that treat deliverables as the client's property.
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.
Client onboarding, project delivery, reusable methods.
Briefs, creative review, client approvals, campaign ops.
Reconciliation, close checklists, approvals, client correspondence.
Dispatch, exception handling, scheduling, and SOPs.
Scheduling, billing, authorizations, and non-clinical ops.
Less than you would think. Buyers value the history of a procedure as much as its current state, and a document that was revised six times is evidence of a process being improved. What matters more is whether the SOPs were actually used, which the completed checklists and the surrounding emails and chats show.
Yes, but the value drops. The template is the form; the completed instances are the examples a model learns from. If client-ownership clauses block the deliverables, the proposals, internal reviews, and process records around them are often still yours to include.
It is either de-identified so the client cannot be recognized from context, or excluded. The preparation rules you approve say which, and your counsel can require exclusion for any class of document, such as anything produced under a standalone NDA.
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.