Step 1: Inventory your systems
Make a simple table: system name, what it holds, years of history and rough volume.
| System | Holds | History | Volume |
|---|---|---|---|
| Help desk (e.g. Zendesk) | Tickets, macros | 6 years | ~180,000 tickets |
| Wiki (e.g. Notion) | SOPs, onboarding | 4 years | ~650 pages |
| CRM (e.g. HubSpot) | Deals, activities | 7 years | ~40,000 deals |
Example rows are illustrative.
Step 2: Confirm what you own
- Your own SOPs, wikis and training materials: usually yours.
- Records about your clients' customers: check client contracts.
- Regulated data (health, financial account data): usually excluded.
Details: client data vs. company data.
Step 3: Gather your written processes
- Collect SOPs scattered across drives, wikis and email into one folder.
- Note which SOPs are current and which are outdated. Both can be useful, but label them.
- Link SOPs to the systems where the work happens (e.g. "Refund SOP → Zendesk refund tag").
Step 4: Flag sensitive material
- Pricing models, margins and vendor contracts
- HR records and compensation
- Legal matters and disputes
- Anything under NDA
Step 5: Line up internal approvals
Know who must sign off: owner or CEO, legal counsel, IT or security, and department heads whose data is included.
How to raise your data's value
- Connect the dots: data that links process → action → outcome is worth more.
- Cover several teams: multi-team participation is what micro1's $500K+ tier is built around.
- Show history: longer time spans show how decisions evolve.
- Document judgment: exception handling and escalation rules are gold.
When you're ready: get your estimate and apply.
Frequently asked questions
How do I get my data ready to sell to AI companies?
Inventory your systems, confirm ownership, gather SOPs in one place, flag sensitive material and line up internal approvals before the discovery call.
Do my SOPs need to be up to date?
No, but label which are current. Older versions can still show how processes evolved.