> 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/2.-getting-ready-for-your-peakcommerce-project.md).

# 2. Getting Ready for Your PeakCommerce Project

The single biggest factor in a smooth implementation is how prepared you are when the project starts. PeakCommerce builds on your existing Salesforce and Zuora systems, so the configuration we do together is only as good as the data, pricing, and decisions you bring into it. Time spent preparing now is time you won't lose to rework later.

To help, our Implementation Team has captured its best practices in the **Getting Ready Guide** — a structured walkthrough of everything to line up before kickoff. We strongly recommend reviewing it as a team while there's still room to gather what's missing.

**What the guide helps you prepare**

* **Your data** — clean, current customer, account, and subscription records, and a clear picture of what lives in Salesforce versus Zuora.
* **Your catalog and pricing** — the plans, products, add-ons, and pricing models you intend to sell, so they can be reflected in your catalog.
* **Your project team** — the people who'll own decisions during the project: an executive sponsor, a project lead, and the business and technical contacts who know your billing and CRM setup.
* **Your commerce experiences** — a rough sense of the checkout, self-service, and sales-assisted flows ("journeys") you want to launch first.

**Who and when:** review this before your onboarding call, ideally with your full project team in the room. Bring open questions to your Customer Success Manager or Implementation Team — that's exactly what kickoff is for.

**Gotcha:** don't wait for the platform to be provisioned to start this. Data cleanup and team alignment are the long poles; they can and should begin immediately.

**Next step →** Once your team and data are lined up, move on to [Org Provisioning & Adding Users](/product/getting-started/project-prep/3.-org-provisioning-and-adding-users.md).


---

# 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/2.-getting-ready-for-your-peakcommerce-project.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.