Process automation and intelligent apps

Automate the work that has been waiting.

The tools to automate rule-based work have existed for ten years. Agents now handle the parts that were too variable to automate. We build workflows and agents on Microsoft Power Platform, in your tenant, and have done so for six years.

What changed

For years the barrier to automating a process was that every path it could take had to be written down first, and most processes have too many. The predictable work was automated. The rest stayed with people, often a team working from a shared mailbox.

Agents remove that barrier. An agent can read what arrives, work out what it is and decide what to do with it, without every case being scripted in advance. Not every step should be an agent. Most of a process is ordinary fixed steps, and a workflow should run those because it is cheaper and predictable. The agent takes the steps that need judgement, and a person handles the exceptions. Copilot Studio has recently been rebuilt around this combination of workflows and agents.

The harder part is knowing where the value is. Productivity uses are easy to see, which is why most agents so far help individuals write and search faster. Process uses are harder to see, because few people in an organisation see a whole process end to end. Every engagement starts with an analyst working alongside the team that does the work, before anything is built.

Four ways in

Most clients take them in this order. Any of the four can be the starting point. How each one works

Trusted by

From our thinking

Tell us what your team is still doing by hand.

The first conversation is thirty minutes with Tony Brooks, no deck. Describe the job and you will get a straight answer on which of the four fits, or that none does yet.