For a founder or operator preparing a first discussion about company data licensing.
You do not need a dataset export to begin assessing an opportunity. You need a reliable description of what exists, the questions that could restrict participation, and the outcome your company would consider worthwhile.
Avelence uses a preparation framework called Profile, Permission, Path. It is a practical checklist, not a legal clearance, valuation model, or prediction of acceptance.
What is Profile, Permission, Path?
| Stage | Establish | Do not confuse it with |
|---|---|---|
| Profile | The systems, history, context, and business activity represented | A verified dataset or a valuation |
| Permission | Who can authorize the next step and what restrictions need review | Unrestricted rights in every record |
| Path | The type of opportunity and next action worth considering | A guaranteed buyer or payment |
The order matters. A commercial proposal is difficult to assess when the company cannot describe the asset or identify who can approve a discussion.
1. Can you describe the business context?
Record the business model, approximate company size, main operating geographies, and the teams whose work the relevant systems reflect. Use a short description a person outside your company could understand.
For an initial assessment, a size band and broad geographic picture are more useful than collecting employee names or customer lists. If your operations span several regions, say so rather than using headquarters as a substitute for the data's geographic exposure.
Prepared answer: a company profile with no personal customer or employee details.
2. Do you know where the history lives?
List systems and categories. For example: support, CRM, project management, internal documentation, engineering, or operations. Separate what you know is available from what you assume might exist.
Do not take an inventory by exporting everything. A platform owner may be able to confirm the approximate coverage and known retention gaps without moving records.
Prepared answer: a short systems map with 'confirmed' and 'not yet checked' clearly distinguished.
3. Can you explain the history and its limits?
Estimate years covered, major gaps, rough volume where readily known, and whether records preserve context about actions and outcomes. A migrated system may contain only part of the company's operating history.
Use approximate values honestly. 'Around four years, subject to retention settings' is more useful than an exact-looking count nobody has checked.
Prepared answer: a history summary with estimates labeled and no raw examples attached.
4. Who can approve the conversation?
Identify the person responsible for discussing the opportunity and the colleagues likely to be needed for commercial, legal, privacy, security, or systems review.
The contact making an introduction may not be the person who can approve a transfer or sign a license. An external consultant's system access is not necessarily authority to commercialize the company's information.
Prepared answer: named internal responsibilities, retained internally where appropriate, and a clear authorized contact for the introduction.
5. What restrictions are already known?
Check for customer confidentiality, employee-related information, third-party content, regulated records, prior licenses, exclusivity, and any systems the company does not want to consider.
This is an issue-spotting exercise, not legal advice. Mark unknowns for review rather than deciding that a record is safe because names could be removed. The ICO's pseudonymisation guidance explains why that distinction matters for personal information.
Prepared answer: a high-level exclusions and open-questions list. Do not attach the sensitive material that led to the restriction.
6. What kind of arrangement would you consider?
State your commercial preferences and operating constraints. Is the company prepared to review only a one-time historical contribution, an ongoing contribution, or either? How much internal work is realistic? Which uses or rights would be unacceptable?
You do not need to choose an exact license structure before meeting a partner. You do need to distinguish your objectives from the intermediary's commission or a promotional maximum.
Prepared answer: preferences and hard boundaries, not an invented valuation target.
7. What would make the next step worthwhile?
Define the information you need from a proposed partner: role, use, scope, review process, payment trigger, rights, data-handling approach, and expected involvement.
A good next action might be a scoping conversation. It might also be to resolve an internal permission issue before any introduction. Avelence should not send a profile onward simply because a form is complete.
Prepared answer: a named next decision and what must be known to make it.
What should the first profile contain?
A compact profile can include the following:
| Include | Leave out |
|---|---|
| Business model, size band, operating geographies | Customer and employee lists |
| Systems and broad categories | Actual tickets, emails, chat excerpts, or documents |
| Approximate history and known gaps | Credentials, API keys, access tokens, or repository links |
| High-level restrictions and preferences | Sensitive project names or attachments |
| An authorized contact and role | Unsupported promises about rights or valuation |
This is the asset for the first conversation. Preparing it should not itself create a data-transfer event.
How should you classify readiness?
Use three working outcomes instead of a percentage score:
Ready for an initial discussion: enough profile information is available, there is an appropriate contact, and material restrictions have been identified for review.
Needs clarification: some information or authority is missing. Record the question and who will resolve it.
Pause: the company does not have permission to pursue the discussion, an apparent restriction conflicts with the proposed route, or the company is not comfortable proceeding.
These outcomes do not mean a partner has accepted the data. They describe readiness for the next conversation only.
How does Avelence use the profile?
We review it against relevant, current partner requirements and the company's stated preferences. If a potential pathway appears suitable, we identify the proposed partner, explain the next step, and ask permission before a named introduction.
Completing an assessment does not license the operational records. A selected partner's review and proposed agreements remain separate.
Start an assessment or read how the process works.
Method and limitations
Profile, Permission, Path is an original Avelence preparation framework developed for the initial assessment process. It is not based on claimed conversion results or a validated statistical model. The checklist organizes questions; it does not resolve legal obligations or predict a commercial outcome.