> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brilo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Do I need a developer?

> What you can set up in Brilo yourself, the few things that need someone technical, and roughly how long each takes.

You do not need a developer to set up Brilo. Creating an agent, teaching it about your business,
connecting a calendar, and taking it live are all done in the dashboard by clicking and typing. Three
things do need someone technical, and each is about an hour of work.

## What you can do entirely yourself

* **Create and edit an agent**, including its voice, language, tone, and everything it says.
* **Teach it about your business** by uploading documents or pointing it at your website.
* **Buy a phone number** and attach it, or forward your existing number to Brilo.
* **Connect Google Calendar** and let your agent book appointments.
* **Connect your CRM** through the app store, including HubSpot.
* **Set up transfers** so callers reach a person when they ask.
* **Turn texting on** and have your agent answer messages.
* **Run campaigns**, import contacts, and read every report.

That is the whole product for most businesses. If you can use a booking system or a website builder,
you can do all of this.

## What needs someone technical

| What                                                 | Why                                                                | Roughly                   |
| ---------------------------------------------------- | ------------------------------------------------------------------ | ------------------------- |
| [A custom action](/actions/build-a-custom-action)    | Your agent reads from or writes to your own software during a call | An hour                   |
| [Webhooks](/actions/send-data-to-your-systems)       | Call details are sent to your own system after every call          | An hour                   |
| [The API](/api-reference/introduction)               | You want to create agents or start calls from your own software    | Depends on what you build |
| [Choose your AI model](/agents/choose-your-ai-model) | You want a different model, transcriber, or thinking effort        | Ten minutes               |
| [The website widget](/channels/website-widget)       | Pasting a snippet into your site, if you cannot edit it yourself   | Ten minutes               |

The widget is the borderline one. If you can edit your website, you can do it yourself. If your site is
managed by an agency, send them the snippet.

## What to send your developer

Send them three things and they will not need to ask you anything:

1. **The page for the thing you want.** Each of the pages linked above ends with the developer
   reference.
2. **What you want to happen, in your words.** For example: "when a caller asks about an order, the
   agent should look it up in our system and read back the status".
3. **API keys, if they need them.** They are in your dashboard under developer settings.

## What it is fair to expect

A custom action or a webhook is a small piece of work for anyone who has built an integration before.
If a developer tells you it is a multi week project, either the requirement is bigger than described or
something has been misunderstood. Ask them to show you the reference page first.

## What else you can do here

* [Buy a phone number](/phone-numbers/buy-a-phone-number) with no technical help at all.
* [Connect your tools](/actions/connect-your-tools) and see which need a developer.
* [Read what your agent can do](/supported/what-your-agent-can-do), which marks the developer parts.
* [Send your developer the API reference](/api-reference/introduction).

## FAQ

<AccordionGroup>
  <Accordion title="Do I need a developer to set up Brilo?">
    No. Creating an agent, teaching it, connecting a calendar or CRM, buying a number, and going live are
    all done in the dashboard. Only custom actions, webhooks, the API, and your own model key need
    someone technical.
  </Accordion>

  <Accordion title="Can I connect Brilo to my CRM without a developer?">
    Yes, if your CRM is in the app store, which includes HubSpot. You sign in to the tool and choose what
    your agent may do. A CRM that is not in the app store needs a custom action, and that needs a
    developer. See [Connect your tools](/actions/connect-your-tools).
  </Accordion>

  <Accordion title="Do I need a developer to change what my agent says?">
    No. Your agent's instructions are plain text you edit in the dashboard, and so is everything you
    upload for it to learn from. This is the part of Brilo you should expect to change yourself, often.
    See [Write what your agent says](/agents/write-what-your-agent-says).
  </Accordion>

  <Accordion title="How long does the developer part usually take?">
    About an hour each for a custom action or a webhook, for someone who has built an integration before.
    Ten minutes for the website widget if it is just pasting a snippet into your site.
  </Accordion>

  <Accordion title="What do I actually need a developer for?">
    Three things: letting your agent reach your own software during a call, sending call details into your
    own systems afterwards, and building on the API. Everything a customer experiences on a call can be
    set up without one.
  </Accordion>

  <Accordion title="Can Brilo support set it up for me?">
    Support can walk you through the dashboard and point you at the right reference page, and
    [support@brilo.ai](mailto:support@brilo.ai) is the place to ask. Writing code inside your systems is
    not something support does, since only your side has access to them.
  </Accordion>

  <Accordion title="Do I need a developer to put Brilo on my website?">
    Only if you cannot edit your own website. The widget is a snippet you paste in, which most site
    builders allow you to do yourself. If an agency manages your site, send them the snippet. See
    [Website widget](/channels/website-widget).
  </Accordion>
</AccordionGroup>

## Related

* [Answer your first call](/quickstart) to see how little setup needs help
* [Build a custom action](/actions/build-a-custom-action) for the main developer task
* [Send data to your systems](/actions/send-data-to-your-systems) for webhooks in plain language
* [What your agent can do](/supported/what-your-agent-can-do), which marks the developer parts
* [API reference](/api-reference/introduction) to hand straight to a developer
