> For the complete documentation index, see [llms.txt](https://docs.varbase.vardot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varbase.vardot.com/content-designers/from-client-needs-to-a-varbase-plan/estimate-a-varbase-project.md).

# Estimate a Varbase Project

Estimate from the requirement map, item by item, and say what each number assumes. An honest estimate names the risks and phases the project, so the first launch is a good one.

## How to Estimate

* Estimate from the requirement map, item by item. Label every number as an estimate and list its assumptions.
* **AI-assisted delivery**: configuration and much build work now take days rather than weeks. Discovery, client reviews, decisions, content writing, translation, outside dependencies and testing still take real time.
* **Phase the project**: phase one launches well (content model, key pages, workflow, roles, main language, launch essentials); later phases add languages, integrations, AI and improvements from real use.
* **Name the risks early**, each with an owner: content not ready (the most common), integrations that depend on other teams, slow decisions, messy migration data.
* **The proposal** follows the same structure: needs in the client's words, the requirement map, the starting point, phases, the estimate with assumptions, exclusions and risks.

With Varbase the site is often ready before the content. Plan content from week one: who writes, translates and approves, by when.
