Draft it with Pi
Dump this into Pi, modeled on a previous client’s onboarding document:What it should include
Onboarding document checklist
Onboarding document checklist
- Points of contact on both sides
- The client’s goals, and what “winning” looks like to them
- Any product confusion or inaccuracies to correct
- How we work: monthly cycles, working in the client’s codebase via PRs where possible
- Publishing and compliance workflow: publish directly, or review-before-publish? Any compliant-language rules? See compliant content
- Competitors (Direct, Incumbent, Adjacent) for verification
- The feature inventory for verification and sign-off; ask for images
- Brand / design guidelines and product docs, if they have them
- Access: web platform (GitHub / Framer / Webflow / WordPress / …), Google Search Console (add sam@synscribe.com and raymond@synscribe.com), PostHog (or set one up; Mixpanel or another is fine)
Review and share
- Send the document to the
internal-<client>Slack channel for Raymond to review, and revise on his feedback. - After the onboarding call, share it with the client with full edit access, so they can correct the feature inventory and fill in their side.