Every vendor tells you that your own AI assistant is the future. The honest answer is shorter: it depends on the work. If you occasionally rewrite a piece of text, a regular chat tool is enough. If you run the same tasks every week, handle sensitive data, or want to connect tools, an assistant configured for your work can be more useful. This article lays out the trade-offs, including the points vendors would rather not discuss.
Your own AI assistant is configured for your business environment. The agent knows your projects, agreements, and tools, and works within boundaries you set. Your team talks to it through the channels it already uses: chat, desktop, or email.
At Voltti, we build that environment with Hermes Agent, installed on a system at your business and supported by us.
Want to build an AI assistant without a partner? You can, and for some organizations it is the right choice. There are roughly four options, each with its own limits.
One accessible option is a configured chat tool: a Custom GPT or Copilot instructions with your own documents attached. Instructions and examples help the assistant match your house style. Connections to your CRM, scheduling, or files may be available through apps, actions, or connectors, but require extra configuration and depend on the platform and your subscription. Processing takes place at the provider.
The second option is a no-code platform such as n8n. You build automation flows that connect email, forms, and tools. You get more freedom, but you build and maintain every scenario yourself, and your team handles every change.
The third option is installing an existing open-source agent on your own hardware, such as OpenClaw or Hermes. This comes closest to the traditional idea of an assistant: the agent runs on a system you administer, communicates through channels you already use, maintains memory and skills, and works with your tools. OpenClaw is open source under the MIT license, runs on your own computer, and connects the agent through a gateway to channels such as Discord, Slack, Teams, Telegram, and WhatsApp. Hermes is an open-source agent framework from Nous Research that runs in the terminal, on messaging platforms, and in IDEs, without tying you to one provider. Getting started is technical but has become accessible: an installation script or desktop installer is enough to begin. The limit is the responsibility that comes with it. Installation, permissions, updates, backups, and output review all fall to you or your team. Later in this article, we explain how to install Hermes yourself.
The fourth option is writing your own software against model APIs and your own systems. It gives you the most control and demands the most work: prompts, integrations, security, and monitoring. To depend less on external model providers, you can even run the models yourself, for example with Ollama, but expect to need considerably more hardware, expertise, and maintenance.
One thing people often underestimate: an assistant is never finished. Models change, integrations break, and someone has to keep checking the output. If you build it, you maintain it too.
There is a practical rule of thumb for when DIY stops paying off: if you spend more time building, testing, and fixing the assistant than on the task you wanted to automate, you have reached the limit. Another warning is dependence on one employee. If exactly one colleague knows how the flow works, it is a risk rather than a dependable system. At that point, outsourcing is a decision, not an admission of failure.
| Consideration | Build it yourself | Have it built |
|---|---|---|
In-house expertise | The AI, integration, and security knowledge you need depends on the option | You do not need an in-house expert |
Sensitive data | You decide and configure where data goes | Local or hybrid, agreed in advance |
Maintenance | Entirely your responsibility and time | Support is part of the service |
Time to launch | Depends on your own capacity | A working pilot usually within a few weeks |
Costs | Your time, any hardware, and model or platform usage | Custom quote: installation and support; model usage separate |
Control | Depends on the option and platform used | You set the goals and boundaries; the partner implements them |
Having an AI assistant built is a realistic option for many businesses: a partner provides the expertise, while you stay in charge of day-to-day use. But vendors differ. Ask in advance where your data stays, what permissions the agent gets, and who decides what the assistant may and may not do.
Also ask what happens when something goes wrong. Who fixes a broken integration on Friday afternoon, adapts the assistant when a process changes, and checks the output before anything is sent? With DIY, those are all your people. With a supported service, those responsibilities are written down, with human review built into the process.
Minimum permissions are the starting point, not an afterthought. In our own Hermes installation, each environment has its own credentials. Access to our search data is read-only; publishing requires separate writing permissions in the CMS. Read-only wherever possible, writing access only where it is needed.
Ask what working together looks like too. A pilot around one task tells you more than a platform presentation. Read more about how we set up a pilot, or about what an AI agent costs: always a custom quote, without a standard rate.
What do you contribute? Your partner handles the technical work. You know which processes take time, which tools need to be involved, and which rules the assistant must follow. The more clearly you define that first task, the sooner the pilot can produce something useful.
In 2025, 33 percent of businesses in the Netherlands with ten or more people employed used one or more of eight AI technologies surveyed, according to Statistics Netherlands (CBS) (Digitalisering en kenniseconomie 2025, provisional figures).
Our view: start with the task that recurs most often. Let the assistant work alongside your team for two weeks, evaluate it together, and only then expand. If the task does not work out, you have lost little. If it does, the assistant can grow with your needs.
Working with sensitive data? Consider a local or hybrid setup so that selected information stays within your own environment. Read more about data residency and human review on our pages about security and privacy. Voltti helps businesses in Belgium and the Netherlands move from a first pilot to a fully configured assistant.
A first month might look like this. Week one: choose and define the task. Describe the process as it runs today, including exceptions. Week two: the assistant works in the background without sending anything itself. Your team learns what the agent can and cannot do. Weeks three and four: the first tasks run for real, with a person checking the output and making adjustments. Only then do you decide whether to expand the assistant's role.
You do not need to hire Voltti to get started with Hermes. You can install the agent yourself without first programming your own AI assistant.
For most people, Hermes Desktop is the most convenient place to start. Download the Hermes Desktop installer for macOS or Windows and run it. It installs both the Desktop app and the command-line version: the same agent with a different interface.
Comfortable with Linux and prefer the terminal? You can install the full CLI version with the official command below. It also works on macOS and in WSL2. The script downloads Hermes, creates a Python environment, and makes the hermes command available.
On Linux, check that Git, curl, and xz-utils are available first. Desktop on Linux also requires a C++ compiler. Read the official installation instructions for your system's requirements. The command executes a downloaded script; inspect it first if you want to see what it changes.
$ curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
✓ Cloned via HTTPS
→ Creating virtual environment with Python 3.11...
✓ Virtual environment ready (Python 3.11)
→ Setting up hermes command...
✓ hermes command ready
✓ Installation Complete!After installing the CLI, open a new terminal. Run hermes setup to configure your model, tools, and connections. Want to install and launch the Desktop app afterward? Run hermes desktop. Desktop uses the same configuration, sessions, and skills as the CLI.
Want to start on Windows without Desktop or WSL2? Run the official Windows command in native PowerShell: iex (irm https://hermes-agent.nousresearch.com/install.ps1).
Installation is one step. Deciding which data and tools the agent may use, testing it, and reviewing its output are part of the work too. Start with a clearly defined task and keep human oversight of important actions. Prefer to leave installation, configuration, and support to a partner? That is the support Voltti provides, on a system at your business. You decide the goals, permissions, and points where someone needs to approve an action. Read how we install and support Hermes for your business.
Yes. You can configure a chat tool, use a no-code platform, install an existing agent such as OpenClaw or Hermes, or write your own software. The knowledge and time required differ for each option. Integrations, sensitive data, maintenance, and review still need attention, even when installation is simple.
From the first conversation to a working pilot, usually two to four weeks. The exact timing depends on the chosen workflow and your team's availability.
That depends on your workflow, integrations, and the support you want. We therefore always provide a custom quote, without a standard rate. Read more in what an AI agent costs.
An API or a usable interface may make an integration possible. We assess each situation to see whether the required access and features are available, and whether the integration is useful and safe.
No. We start with one task and one project. The rest can come later. Your own AI assistant grows with your needs.