---
title: "Blue Prism | Skills We Assign For | Azendo"
description: "Blue Prism for governed RPA — object reuse, audit, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/blue-prism/"
---

[Skills](https://azendo.co/skills/) Automation platforms 

# Blue Prism.

Blue Prism is an enterprise RPA platform with a strong focus on governance: centrally managed digital workers, reusable object libraries, audit logging and separation between process design and object implementation.

## Where Blue Prism fits on a long engagement.

Separating processes from objects is the architectural idea that distinguishes it. An object encapsulates how to interact with one application; a process composes objects into a workflow. When the application changes, one object is updated and every process using it is fixed — where a platform embedding interaction in each process needs every one edited.

That discipline costs upfront time and repays across a portfolio. A first automation is slower to build here than in a platform that lets a developer record and go, and the tenth is considerably faster and far cheaper to maintain.

## What an assigned team does with Blue Prism.

Blue Prism deliberately excludes unattended desktop recording, which is a constraint rather than a missing feature. It forces deliberate design and rules out the quick automation that becomes unmaintainable.

Whether that trade suits an organisation depends on portfolio size and governance requirements, which is assessed at scoping as part of [how the monthly fee is built](https://azendo.co/pricing/).

## What we use Blue Prism for.

* Application changes fixed once One object updated rather than every process that touches the system.
* Audit trails for regulated processes Complete logging of what a digital worker did and when.
* A portfolio that stays maintainable Reuse enforced, so the tenth automation is cheaper than the first.

## How Blue Prism capacity is assigned.

Enterprise RPA capacity is assigned under [software development outsourcing](https://azendo.co/services/software-development/), with object libraries treated as the durable asset rather than individual processes.

## Roles we assign Blue Prism for

* [RPA Developer AI automation engineering](https://azendo.co/services/ai-automation-engineering/rpa-developer/)

## Service lines it sits in

* [AI automation engineering](https://azendo.co/services/ai-automation-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in automation platforms

* [n8n — skill we assign for](https://azendo.co/skills/n8n/)
* [Make — skill we assign for](https://azendo.co/skills/make/)
* [Zapier — skill we assign for](https://azendo.co/skills/zapier/)
* [Power Automate — skill we assign for](https://azendo.co/skills/power-automate/)
* [UiPath — skill we assign for](https://azendo.co/skills/uipath/)
* [Automation Anywhere — skill we assign for](https://azendo.co/skills/automation-anywhere/)
* [Workato — skill we assign for](https://azendo.co/skills/workato/)
* [MuleSoft — skill we assign for](https://azendo.co/skills/mulesoft/)

## Tell us what your roadmap needs Blue Prism for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)
