> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/getting-started/project-prep.md).

# Project Prep

Project Prep is the short, ordered sequence that gets you and your team ready to start your PeakCommerce implementation — before the real configuration work begins. The goal is simple: arrive at your kickoff call with your data, your project team, and your platform access already in place, so the first working sessions go straight to building instead of setup.

Work through these four steps in order:

1. [What Should I Expect During Onboarding?](https://docs.peakcommerce.com/product/getting-started/project-prep/1.-what-should-i-expect-during-onboarding.md) — the shape of onboarding, from the Success email cadence through your requirements review.
2. [Getting Ready for Your PeakCommerce Project](https://docs.peakcommerce.com/product/getting-started/project-prep/2.-getting-ready-for-your-peakcommerce-project.md) — prepare your data, materials, and project team ahead of kickoff.
3. [Org Provisioning & Adding Users](https://docs.peakcommerce.com/product/getting-started/project-prep/3.-org-provisioning-and-adding-users.md) — claim your tenant and invite your team in **Settings → Users**.
4. [Intro to Support](https://docs.peakcommerce.com/product/getting-started/project-prep/4.-intro-to-support.md) — how help works during implementation and after you go live.

New to the platform? Start with [What is PeakCommerce?](https://docs.peakcommerce.com/product/getting-started/what-is-peakcommerce.md) for the bigger picture first.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.peakcommerce.com/product/getting-started/project-prep.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
