> 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/guides/readme.md). # Guides Practical, end-to-end walkthroughs for building with PeakCommerce. Where the product docs explain *what* each feature is, the guides show *how* to put them together to solve a real problem — each one a concrete, worked example you can adapt. ## Feature Guides Hands-on builds, grouped by what you're trying to do: * [**Build & launch**](/guides/feature-guides/build-and-launch.md) — stand up a checkout journey, design its pages, and put it on your own domain. * [**Acquire & convert**](/guides/feature-guides/acquire-and-convert.md) — trials, usage-based signups, guided-offer quizzes, gifts, and quote-to-cash closes. * [**Retain & manage**](/guides/feature-guides/retain-and-manage.md) — retention saves, pause, win-back, dunning recovery, and CSR-assisted plan changes. * [**Billing setup**](/guides/feature-guides/billing-setup.md) — the Zuora order model, payment gateways, and trial products your journeys build on. ## More guides * [**Administration Guides**](/guides/administration-guides/guide-managing-users-roles-and-profiles.md) — access control and platform administration (users, roles, and profiles; GDPR readiness). * **RevOps Guides** — subscription strategy: the pricing models and platform capabilities that matter most. * **Monetization Guides** — protecting and growing revenue across the customer lifecycle and the partner channel. ## Looking for something else? * **Building components with code?** See the **Component Cookbook** and the **Building Custom Components** reference in the developer documentation. * **Step-by-step feature reference** lives in the product documentation. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/guides/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.