> 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/how-varbase-is-built/choose-the-starting-point-with-a-client.md).

# Choose the Starting Point With a Client

Every Varbase project starts from a site template or from **Varbase Starter**. Choosing it early, with the client, turns a vague brief into a scope you can estimate.

## Steps

1. Ask the four questions below in an early meeting.
2. If a template matches the client's sector, show its demo early. Ask what they like, what they would change, and what is missing.
3. Turn the answers into scope: what is kept, what is restyled, what is new.
4. If no template matches, start from **Varbase Starter** and build the sector-specific parts on top.
5. List the optional recipes in scope (languages, AI, sign-in, API). Each is a line item in the estimate.

## Questions for the Client

* Which of these sites looks closest to what you have in mind: Varbase Starter, Educare, Horizon Aid or The Rightup?
* Which kinds of content do you publish today, and are any of them news, events or podcasts?
* Which languages do you need at launch, and which later?
* Are you planning to use AI on the site this year, next year, or not at all?

## Questions Clients Ask

* **Can we switch site template later?** Not by re-applying a template. A template is applied at installation; features are added later with individual recipes.

## Planning Notes

* Decide at kick-off which optional recipes are in scope. Each is a line item.
* Demo content helps in the early weeks; removing or replacing it before launch is a task with an owner.

See [Planning a Varbase Project](https://docs.varbase.vardot.com/content-designers/from-client-needs-to-a-varbase-plan.md) for worked examples per sector.
