Skip to main content
The onboarding document is the internal alignment and prework doc you build in Week 1 and share with the client before the kickoff. It captures their goals, the access and prework you need from them, and how you’ll work together. It’s distinct from the kickoff document, which is the client-facing strategy and timeline. Draft it with Pi, fill in the specifics, get it reviewed, then share it.

Draft it with Pi

Dump this into Pi, modeled on a previous client’s onboarding document:
Pi drafts the document. Review it, fill in the specifics from the sales calls, and add the feature inventory for the client to check; see Feature inventory sign-off.

What it should include

  • 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.
Next: Feature inventory sign-off · Create the kickoff document · Month-1 onboarding