Your summary updates as you type. Use “Save draft on this device” to preserve the full profile and optional context for a later visit.
A useful profile begins with a description, not an upload.
The initial assessment is a way to organize what you know about your company’s working records. You do not need an export, a finished dataset, or an estimate of commercial value to begin. Start with the business process, the tools involved, and the approximate history available. A clear account of what the records explain is more useful than a large storage figure without context.
The form currently prepares a draft or downloadable brief within your browser. It does not submit the information to SellYourAIData, send it to a buyer, or connect to your accounts. This distinction matters when deciding what to include. Keep the description at the system and process level, and leave out raw records, credentials, personal details about other people, and confidential examples.
−Systems and workflow
−History and ownership
+Messages and documents
+Credentials and datasets
Explain one archive that your team understands.
Choose a starting point with a recognizable workflow. That could be support cases linked to resolutions, operating documents with revision history, or opportunities with recorded decision reasons. Explain who uses the system, what the work involves, and how the outcome is captured. If several platforms participate, describe the relationship between them without trying to inventory every field in the first pass.
Approximate history and volume can help establish scale, provided the unit is clear. Distinguish years retained from years the business has operated, and distinguish messages from threads or tickets from individual replies. If a migration removed older context, say so. These details make the profile more informative and reduce the chance that a later conversation begins with an inaccurate picture of the archive.
Include the questions that still need an owner.
An early profile should make uncertainty visible. You may know that a support archive contains customer attachments without yet knowing which can be included. You may control a repository while needing to review third-party code. Describe those conditions and identify who would be responsible for resolving them. An initial profile is not a declaration that the entire archive has been cleared for reuse.
Authority also needs a specific account. Explain your role and whether you can speak for the organization or need another person involved. Portfolio companies, client work, employee communications, and specialist operational records may each involve different decision makers. You can record that a review is needed without supplying sensitive details. The objective is to establish the scope of a possible next conversation. If several people contribute to the profile, distinguish confirmed facts from estimates. One person may know the operational history while another can verify retention dates or contractual responsibilities. The brief should preserve those differences.
| Topic | Known | Unresolved |
|---|---|---|
| History | Years estimated | Retention verification |
| Authority | Owner identified | Restrictions review |
Review the local draft before you use it elsewhere.
Before downloading, check that the description reflects the actual systems and avoids unsupported claims about completeness or ownership. Confirm that date ranges and units make sense, and note any important gaps. A useful brief should allow someone unfamiliar with the company to understand what the archive records, where it lives, and what would need further review.
Saving a draft keeps it on this device where browser storage is available. Downloading creates a file you control; neither action is a submission or an assessment result. Keep that file with the same care as other business planning material. If you later choose to discuss the opportunity, the brief can provide a starting point for agreeing what additional information is necessary and how any further process would work.