> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synscribe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create the kickoff document

> Build the client-facing kickoff document with Pi — the strategy and the month-1 timeline — after research is done and the keywords are in.

The kickoff document is the client-facing strategy and month-1 timeline you present on day 4/5. It walks the strategy — landing pages and blogs, built on the right keywords — and the cycle's timeline. It's distinct from the internal [onboarding document](/sops/create-onboarding-doc). Build it once Pi is initialized, the research and product bible are done, the keywords are imported, and the onboarding-call transcript is in Pi.

## Lead with the top keywords

The strategy leads with the keywords you already picked in [Starting the first keywords](/sops/first-keywords): the top 5 and top 10, in customer language, with the top 5 capturing the client's USP or a competitor alternative. Pull that set into the strategy before you draft the timeline — one keyword can carry both a landing page and a blog.

## Draft it with Pi

```text theme={null}
help me create a kickoff document — the client-facing strategy and timeline (distinct from the internal onboarding doc). use this reference structure:

## Month 1
### Week 1 — Audit & setup
- getting access to tools, tracking setup, SEO audit and fixes, hook up the blog CMS and create the /uses template + hub
### Week 2 — First pages live
- publish the first wave of landing pages and blog posts, technical-check each, submit for indexing, verify they appear
### Week 3 — Scale up
- publish the second wave, set a blog cadence, share the first ranking wins
### Week 4 — Review
- monthly review; set the recurring date
### Month 2 — What comes next
- more competitor and comparison pages, deeper clusters, expand the library — planned together from the data
```

## Before you present

* [ ] Access confirmed against the onboarding checklist
* [ ] Invoice paid
* [ ] Recurring monthly review set
* [ ] Feature inventory signed off; see [Feature inventory sign-off](/sops/feature-inventory-signoff)

## After the kickoff call

Dump the call transcript into Pi and have it fold in whatever the client changed or clarified, the
same way you did with the sales-call transcript earlier:

```text theme={null}
here's the transcript from the kickoff call: [paste the transcript]. update your memory, then refresh
the company info, org profile, product bible, refiners, and pillar prompts wherever the call changed
something.
```

Pi updates the account so the content it generates next reflects what was agreed. Review its changes,
especially to the product bible and the pillar prompts, since everything downstream reads from those.

**Next:** [Month-1 onboarding](/sops/onboarding-month-1) · [The Quality Gate](/sops/quality-gate)