> For the complete documentation index, see [llms.txt](https://docs.allshore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allshore.ai/clients-and-pipeline/rate-cards.md). # Rate cards A **rate card** is your firm's standing price list: a default bill rate per role. It's the answer to "what do we charge for a senior engineer" before any particular deal exists. ## Managing the card Rate cards live in **Settings**. Any partner staff member can read the card; **adding, updating, and archiving entries is a partner admin action** — it's your firm's pricing, not a per-deal decision. Archiving an entry retires a role from the card without touching anything already priced from it. ## Where the card flows The card feeds two places, and it's worth being precise about the difference: * **The pricing estimator** — quoting a prospect defaults role rates from the card. Nothing about that binds a client (see [Estimates & pricing](/clients-and-pipeline/estimates-and-pricing.md)). * **Seeding a contract's bill rates** — applying the card to a commercial contract **copies** its current figures in as real effective-dated rates. That's the convenience path, not the only one: you can also set a contract's rates directly, which is what you do for anything the card doesn't cover. The thing to remember either way: once a rate is on a contract it's independent. **Changing the card later does not re-price any contract** — contract rates are their own effective-dated history from the moment they're written. See [Bill rates & rate history](/clients-and-pipeline/bill-rates-and-rate-history.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 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.allshore.ai/clients-and-pipeline/rate-cards.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.