> For the complete documentation index, see [llms.txt](https://docs.buildbob.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildbob.ai/company/pricing.md).

# Pricing

We offer customized payment plans tailored to different team sizes and usage patterns. The core pricing model is based on two components: Intelligence Units (IU) and Data Units (DU).

* **Intelligence Units (IU)** are consumed when you ask questions or perform AI-driven tasks.
* **Data Units (DU)** are consumed when Bob AI processes and understands documents, such as drawings, contracts, invoices, and BOQs.

Each plan includes a set cap for both IU and DU. This ensures transparent and predictable pricing, allowing teams to scale usage as their projects grow. Additional units can be added if needed, giving organizations flexibility to match their usage with project demands. For projects that require custom capabilities, integrations, or consulting services, these are charged separately based on the specific scope and requirements.

<figure><img src="/files/xxHt8FuRuQptq8DTfg0m" alt=""><figcaption></figcaption></figure>


---

# 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.buildbob.ai/company/pricing.md?ask=<question>&goal=<endgoal>
```

`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.