Documentation · Adoption
CRM Team Training & SOPs
A CRM is only as useful as the team's discipline in using it. After leading three CRM implementations, I noticed the same pattern: the platform was great, but six months in, half the team had drifted back to spreadsheets. I built a documentation and training system that prevents the drift.
SOP library · screenshot-rich walkthroughs in Scribe
What the system covers
- Screen-capture walkthroughsStep-by-step SOPs built in Scribe — auto-captured screenshots with annotations, for every common task.
- Video walkthroughs in LoomShort Loom videos for processes that benefit from voiceover or judgement calls a checklist can't capture.
- Notion playbookHome base for everything — searchable, role-tagged, version-tracked.
- Decision treesFor the parts of the process where the right action depends on the situation (e.g. "what stage does this deal belong in?").
- Quarterly refreshSOPs reviewed every quarter against actual practice. Outdated steps get flagged and updated — not left to rot.
The toolchain
ScribeLoomNotionConfluence
Outcome
100%
Team adoption
Six months post-rollout.
Quarterly
Refresh cadence
SOPs stay true to reality.
1
Source of truth
Notion as the canonical reference.