Mutree SolutionsTalk to sales

Copilot Studio, n8n or custom code: how we choose where an agent lives.

Mutree SolutionsBuilding agents3 minute read

Most agent projects that stall do not stall on the model. They stall on a decision made in week one and never questioned: where the agent runs. That choice sets who can maintain it, what data it can reach, and what happens the first time it gets something wrong.

We build on three routes. Each one is the right answer for some company and the wrong answer for the one next door.

Illustration from a Mutree AI strategy workshop showing an opportunity assessment card.
From a Mutree AI strategy workshop. The route is chosen in the room, before anything is built.

Microsoft Copilot Studio

Pick this when the company already lives in Microsoft 365. Sign-in, permissions and data rules are in place, and the agent can be published into Teams where people already work. Your IT team can own it without learning a new stack.

The cost is that you work inside the platform’s limits. When a requirement falls outside them, you wait or you work around it.

n8n

Pick this when the job is a workflow across several systems and you want every step visible. An operations lead can open the flow and read what it does. It can be self-hosted, which matters when data must stay on your own infrastructure.

The cost is that someone has to run and watch it. Long chains of reasoning also get awkward when each thought is a box on a canvas.

A custom agent in code

Pick this when the agent is close to being the product, or when it needs behaviour no platform gives you: tight response times on a phone call, your own test suite, a strict audit trail.

The cost is the highest of the three, to build and to keep. You own every part, including the parts that break.

The platform is a consequence of the diagnosis. It is never the starting point.
RouteFits whenOwner after launchMain cost
Copilot StudioCompany runs on Microsoft 365Your IT teamPlatform limits
n8nMulti-system workflow, visible stepsOperations, with some technical helpRunning and monitoring it
Custom codeUnusual behaviour or strict auditEngineers, yours or oursBuild and upkeep

Three questions we ask before choosing

  1. Where does the data live, and who is allowed to see it? The agent should inherit existing permissions. It should not need new ones invented for it.
  2. Who owns it after we leave? If the answer is a team with no developers, a code-only build is a liability from day one.
  3. What happens when it is wrong? Every route needs a person it hands to and a record of what it did. If we cannot draw that path, we do not build.

Often the honest answer is a mix: a Copilot Studio agent in Teams that calls an n8n workflow, with one custom service for the part neither handles well. That is fine. What matters is that the choice was made on purpose.

Read next

CallTalk to sales