Consulting and recruiting
Licensing consulting methodologies and frameworks: rights you need
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
To license a consulting methodology, a firm must show it owns every component, that no client confidentiality attaches to it, that everyone who created it assigned their rights, and that someone can authorize the specific use. The quickest check sorts each artifact by origin: authored in-house, derived from client work, co-developed, or acquired with another firm.
Key takeaways
- A methodology is rarely one asset; it is a bundle of templates, playbooks, worked examples and tools, each with its own rights.
- In-house artifacts are usually cleanest, but contractor and departed-partner contributions need written assignments.
- Artifacts derived from client work carry the client's contract terms with them.
- Licensing to an AI developer adds questions about training use, derivative models and attribution.
- Each artifact should map to provenance, licensing rights, permitted use, privacy record and release authorization.
What rights do you need to license a consulting methodology?#
Licensing a consulting methodology requires four things: ownership or a right to sublicense every component, freedom from client confidentiality obligations, signed assignments from the people who created it, and clear authority to approve the license. Missing any one can stall a deal or create a claim later.
Start by breaking the methodology into artifacts. A pricing method, for example, may include a diagnostic questionnaire, a scoring workbook, a playbook, training slides and a set of worked examples. Each artifact has its own history, and the rights answer often differs between them.
Rights by origin: authored, derived, co-developed or acquired#
The origin of each artifact predicts most of its rights questions. Sort your methodology library by origin before reading any contract, then focus legal review where the origin signals risk.
Artifacts often change origin over time. A template drafted in-house can absorb client-specific content during an engagement and come back to the library as a derived artifact without anyone noticing.
| Origin | Typical artifacts | Main rights question | Evidence to gather |
|---|---|---|---|
| Authored in-house | Templates, training decks, internal playbooks | Were authors employees acting within their role? | Employment agreements, authorship dates, version history |
| Derived from client work | Worked examples, benchmarks, refined models | Did the client MSA assign or restrict this material? | MSA and SOW clauses, de-identification record |
| Co-developed | Joint frameworks with a client, alliance partner or university | Who owns it, and can either side license alone? | Partnership or joint development agreement |
| Acquired | Methods from a merged or purchased firm | Did the acquisition transfer these rights? | Purchase agreement, IP schedules, prior client terms |
| Third-party content | Licensed data, published frameworks, stock images | Does our license allow sublicensing? | Vendor license terms |
Who created it: employees, contractors and departed partners#
Creator rights depend on the relationship between the firm and the person who did the work. Under 17 U.S.C. 201(b), the employer is treated as the author of a work made for hire and owns the copyright unless a signed writing says otherwise, so material produced by employees within the scope of their jobs generally belongs to the firm. But material produced by independent consultants, subcontractors or partners under a partnership agreement may not, unless a written agreement assigns it.
Departed partners are the most frequent surprise. A founder who built the core framework years ago may never have signed an assignment, and partnership agreements written for a smaller firm may say nothing about IP. Find these gaps early and resolve them with counsel, through confirmatory assignments where needed.
Which methodology artifacts are worth licensing?#
The methodology artifacts worth licensing are the ones that show how a decision gets made, not just what the framework is called. A two-by-two matrix on a slide teaches a model very little; a playbook that walks through intake questions, decision points, common failure modes and how practitioners resolved them teaches a great deal.
Rank your library on that basis. Step-by-step playbooks with worked cases, diagnostic questionnaires with scoring logic, review checklists with reviewer comments and SOPs with exception handling usually rank highest. Marketing versions of the framework, slogans and conference decks rank lowest and rarely justify the rights work.
Version history adds value too. Successive revisions of a playbook show how the method changed after real engagements, which is evidence of practice rather than theory.
What licensing to an AI developer adds#
Licensing a methodology to an AI developer adds questions that client and franchise licenses rarely raise. The developer may want to use playbooks and worked examples to train or evaluate models, which raises scope questions about derivative models, outputs that resemble your materials and use of your trademarks.
Licensing can also affect trade secret protection. Under 18 U.S.C. 1839(3), information qualifies as a trade secret only if its owner takes reasonable measures to keep it secret and it derives independent economic value from not being generally known. A license without confidentiality, access and use limits may weaken that status for the licensed playbooks, so counsel should review those terms before signing.
Documenting these rights in a structured way makes review easier. The Data and Trust Alliance's Data Provenance Standards, for instance, include Use elements for license to use, intended data use, and copyright, patent and trademark status, alongside confidentiality classification. A methodology package that already answers those fields is easier to review.
The rights checklist mapped to the SourceX Evidence Packet#
The SourceX Evidence Packet organizes rights evidence into five fields, and each methodology artifact should have an answer for every field before it is licensed. SourceX uses this packet in the Rights and Approval steps of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery.
Work through the table artifact by artifact. Where an answer is missing, either fix it or drop the artifact from the package; a smaller package with clean evidence is easier to license than a larger one with gaps.
| Evidence Packet field | Question for each artifact | Records that answer it |
|---|---|---|
| Provenance | Who created it, when, and from what sources? | Version history, authorship records, source engagement list |
| Licensing rights | Does the firm own it or hold a right to sublicense? | Employment and contractor agreements, assignments, partnership terms |
| Permitted use | What may the licensee do: train, evaluate, reference, redistribute? | Draft license scope, client contract limits, third-party terms |
| Privacy record | Were client and personal details removed or excluded? | Preparation log, de-identification checks, reviewer sign-off |
| Release authorization | Who approved this artifact for release? | Partner or board approval, signer authority |
License terms to settle before signing#
License terms for a methodology need more precision than a typical client agreement, because the licensee may use the material in ways the firm never does. Agree on scope in writing before any files move.
Review these terms with counsel. The right answer depends on the licensee, the use and how central the methodology is to your client work.
- Licensed materials: an exact list of artifacts and versions.
- Field of use: training, evaluation, internal reference or redistribution.
- Exclusivity: whether you can license the same materials to others or keep using them with clients.
- Term and territory, and what happens to copies when the license ends.
- Derivative works and model outputs: what the licensee may claim or publish.
- Trademarks and attribution: whether your framework names may be used.
- Warranties and indemnities: what you promise about ownership and non-infringement.
Illustrative: a pricing consultancy licenses its playbook library#
Illustrative: a fictional pricing consultancy wants to license its playbook library and diagnostic workbooks. The library lives in Confluence, with version history going back to the firm's early years, and worked examples drawn from past engagements.
The audit finds three problems. One founding partner who wrote the original playbooks left without signing an assignment, several worked examples reproduce a client's actual price lists, and a scoring model was co-developed with an alliance partner. The firm obtains a confirmatory assignment from the departed partner and replaces the client examples with composite cases. It drops the co-developed model from the package.
The final package covers authored playbooks and workbooks only, licensed non-exclusively for model training and evaluation. The firm keeps full use of the materials in its own client work.
Frequently asked questions
Can we license a methodology whose name is trademarked?
Usually yes, and the trademark and the content are licensed separately. You can license the playbooks without granting any right to use the brand name, or include limited attribution rights. Decide which you want before negotiating, because trademark use can imply endorsement of the licensee's product.
Do we need to register copyright before licensing?
Copyright generally exists without registration, so registration is not usually a precondition for licensing. In the US, registration can matter if you ever need to enforce your rights in court. Ask counsel whether registering key works makes sense for your firm.
Can we license a methodology and keep using it with clients?
Yes, if the license is non-exclusive or the exclusivity is limited to a field your client work does not touch. State in the agreement that the firm keeps full rights to use, adapt and deliver the materials in its own services. Also confirm that the licensee cannot later claim rights in improvements you make for clients.
Do client case examples inside our playbooks need client consent?
If the examples reveal a client's identity or confidential information, they generally fall under that client's confidentiality and ownership terms. The safer approach is to replace them with composite cases built from several engagements, or to seek written consent from the client.
What if a former partner claims they created the framework?
Gather the evidence first: drafts, version history, partnership agreements and any IP clauses. Many firms resolve these claims with a confirmatory assignment, sometimes with consideration. Do not license disputed material until the question is settled with counsel.
Sources
- The Use group of the Data & Trust Alliance Data Provenance Standards includes elements for confidentiality classification, consent documentation location, privacy-enhancing technologies applied, allowed and excluded processing and storage geographies, license to use, intended data use, and copyright, patent and trademark status. Source
- 17 U.S.C. 201(b) provides that in the case of a work made for hire, the employer or other person for whom the work was prepared is considered the author and, unless the parties have expressly agreed otherwise in a written instrument signed by them, owns all of the rights comprised in the copyright. Source
- Under 18 U.S.C. 1839(3), information qualifies as a trade secret only if the owner has taken reasonable measures to keep it secret and it derives independent economic value from not being generally known. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.