Data type
Docs, wikis and SOPs
How your company says work should be done. Procedures paired with the conversations and tickets where they were applied let buyers build realistic environments where an agent must follow policy.
Records to assess
- Notion, Confluence or Google Drive wikis
- Standard operating procedures
- Playbooks, checklists and templates
- Onboarding material
Context to describe to buyers
- Coverage of real processes
- Versions over time
- Links to tickets and chat that show the process in use
What stays out
- Client deliverables
- Licensed third-party content
- Trade secrets you want to keep
How to prepare
- Map spaces and folders
- Tag client-owned material
- Decide what is too sensitive to include
Worked example: A 35-person property manager (fictional)
Keystone Residential has a Notion wiki with 900 SOPs, checklists and onboarding pages built since 2019, plus the Slack threads where they were applied. Tenant-facing templates with personal data are excluded; internal procedures are in scope.
When to pause the assessment
- Your documentation is mostly client deliverables or licensed third-party content.
- The docs are your competitive advantage and you would not want them used to train a rival’s agent.
- There is little documentation beyond a handful of policies.
Docs, wikis and SOPs: common questions
Still unsure? Get a free quote
Will licensing our SOPs reveal our trade secrets?
You choose what is in scope. Exclude anything that is a competitive secret. A buyer’s proposed use may still affect competitive interests. Agree on permitted use and disclosure restrictions and consider whether retaining the material is preferable.
Explore what your company’s data could be worth.
Describe your systems and history to see a planning estimate. Request a buyer-fit assessment when you are ready. Free for your company, with no obligation.
