Purpose
The Business Transformation Assistant is the first built-in Role Assistant. It helps an organization turn a business intention into an enterprise Runtime path for measurable improvement. Rather than asking people to assemble an AI solution from tools, prompts, or disconnected setup steps, it starts with the business perspective they want to improve.
The Assistant uses the same Runtime available to customers. It is not a private platform stack or a separate automation model. Like other Role Assistants, it is human-owned and role-scoped: it can recommend, prepare, and request governed work; it cannot grant itself authority.
Business intention → Questions that clarify the goal → Governed connected systems → Role Assistant ready for work
Start with business intention
A business leader may describe an outcome such as improving account retention, reducing review delays, or making a service process more reliable. The Business Transformation Assistant progressively clarifies the role, business information, systems, relationships, and outcomes that matter.
It does not ask the leader to design a workflow or choose technical tools. Its job is to translate the intended improvement into an enterprise path that can be governed, reviewed, and improved over time.
What is the first useful question?
What business perspective should improve, and which role is responsible for that outcome?
Governed connected-system work
As the objective becomes clear, the Assistant uses the governed Builder connected-system surface to establish the business context needed for the work. This includes the relevant business information, connected systems, capabilities, relationships, and evidence needs.
The Assistant uses those governed capabilities like any other Role Assistant. It does not bypass controls, expose a separate wizard, or create a hidden path for changing enterprise information. The resulting Runtime path remains subject to Operational Trust, required human decisions, and evidence capture.
Knowledge and evidence
The Assistant uses two complementary forms of Enterprise Knowledge and Evidence:
- Customer Knowledge describes the organization’s own business reality, systems, roles, and outcomes.
- Platform Knowledge provides generalized, certified know-how about patterns that can help improve a business perspective.
Both are normal Enterprise Knowledge and Evidence. Platform Knowledge does not expose another customer’s information, and Customer Knowledge remains within the organization’s governed boundary.
Example
A service organization wants to reduce time spent resolving contract exceptions. The Business Transformation Assistant asks which role owns the exceptions, where the contract information and related records live, and how the organization defines a successful resolution. It builds a governed path that can support a role-specific Assistant, including the trusted context and evidence needed to measure whether the improvement is working.
The organization can then review the resulting work, approve proposed actions when required, and learn from completed outcomes rather than treating initial setup as a one-time chatbot exercise.
Business value
The Business Transformation Assistant makes the path from intention to practical AI-assisted work easier to understand. It keeps the focus on a measurable business improvement while using the same governed Runtime, connected-system capabilities, Enterprise Knowledge, and evidence model that support customer Role Assistants.
See Role Assistant examples for other role-based patterns and Operate your first Role Assistant for an adoption path.
Limits
The Assistant’s available guidance, connected-system coverage, and automation depth can vary by deployment. It helps establish a governed path for improvement; it does not guarantee that every business objective can be completed without organization-specific review, data preparation, or approvals.