> 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/getting-started/common-tasks.md).

# Common Tasks

Jump to the first setup, estimating, and customer-facing actions most teams handle in PaintScout.

Use this page when you want the fastest path to the tasks most teams complete first.

## Common tasks

1. [Set up your account](/support/getting-started/implementation-guide.md) — Configure company details, team access, estimate settings, and integrations
2. [Update your hourly rate](/support/customization/pricing-and-rates/how-to-update-your-hourly-rate.md) — Set the core rate behind your estimate pricing
3. [Build your production rates](/support/customization/pricing-and-rates/production-rates-section-overview.md) — Define how PaintScout calculates labor and price
4. [Add products](/support/customization/products/adding-products.md) — Create your material library and coverage settings
5. [Create a new estimate](/support/estimating/creating-estimates/how-to-create-a-new-estimate.md) — Start your first quote from scratch or from a template
6. [Send an estimate](/support/estimating/sending-and-acceptance/sending-estimates.md) — Share the estimate with the customer by email or text
7. [Create and send an invoice](/support/invoicing-and-payments/invoices/creating-invoices.md) — Turn sold work into a bill and request payment

## Recommended next steps

* [Getting Started Overview](/support/getting-started/readme.md) — Review the full onboarding section
* [Customization Overview](/support/customization/customization-overview.md) — Set up pricing, templates, and customer-facing defaults
* [Estimating Overview](/support/estimating/estimating-with-paintscout.md) — Learn the full estimate workflow

  


---

# 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/getting-started/common-tasks.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.