> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/customization/customization-overview.md).

# Customization Overview

Configure pricing, products, templates, presentations, and defaults so PaintScout matches your business.

Customization is where PaintScout starts to feel like your system. Set your pricing logic, product library, estimate defaults, and customer-facing presentation so every quote stays consistent.

{% hint style="info" %}
Most teams should complete [Implementation Guide](/support/getting-started/implementation-guide.md) first, then return here to refine their setup.
{% endhint %}

## In This Section

* [Pricing & Rates](/support/customization/pricing-and-rates.md) — Configure hourly rate, production rates, and coverage logic
* [Products](/support/customization/products.md) — Build your product library and assign materials to rates
* [Templates & Presets](/support/customization/templates-and-presets.md) — Set estimate types, templates, defaults, area names, and line items
* [Presentations & Terms](/support/customization/presentations-and-terms.md) — Control how proposals look and what contract language they include

## Recommended first reads

* [Update Your Hourly Rate](/support/customization/pricing-and-rates/how-to-update-your-hourly-rate.md) — Set the pricing baseline used across estimates
* [Production Rates Overview](/support/customization/pricing-and-rates/production-rates-section-overview.md) — Organize the rates your team uses every day
* [Estimate Types](/support/customization/templates-and-presets/what-are-estimate-types.md) — Create project-specific defaults for rates, terms, and presentations

  


---

# 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://help.paintscout.com/support/customization/customization-overview.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.