There are two kinds of agent. Agents you talk to help people find and draft things, and Microsoft's own Copilot now does a lot of that out of the box. Agents that run start on their own when something happens: an email arrives, a meeting ends, a report is exported, a date comes round. They do the checking, drafting and filing, then stop for one of your team to approve. The second kind is where a firm gets hours back, and it's what we build.
Both kinds are built around a particular job, source of knowledge, audience or workflow, rather than asking general Copilot to help with whatever is in front of you. Microsoft keeps making Copilot better, and we'll tell you when it already does the job. What it doesn't know is your firm: your clients, your thresholds, your templates, your filing conventions and who signs off what. That's the part we connect, build and look after.
In an accountancy or law firm, an agent you talk to might be a knowledge assistant or a client intake guide. An agent that runs might file the morning post, push WIP exceptions to managers or turn a client meeting into a filed note. The important detail is not that the agent is clever. It is that the scope is narrow enough to trust.
Agents work best when they sit between broad Copilot use and hard automation. They can guide a person through a process, answer from approved material and collect useful context. They should not remove professional judgement, client responsibility or the need to check the output. When the job needs a build, it is built as part of a Firmwide install, one agent per department; when it only needs rule-based steps, a standard automation inside the same install is usually the better route, and Run keeps both working.
For the wider picture of how agent capability grows, the Agent Journey maps five stages from the Copilot licences your firm already has to a team of agents. A Firmwide install builds the skills stage and the agent stages, on a foundation of permissions checked and the firm's templates and procedures in SharePoint.