How It Works

Fifteen change-management skills sit on our server: Stakeholder Map, Resistance Playbook, Communication Audit, Leadership Alignment Playbook, Change Champion Network, and the rest. We host them, we maintain them. The skill code, the prompt logic and the methodology never leave. You license the capability without taking custody of the intellectual property behind it.

Your corporate Claude account is your environment: your workspace, your users, your governance. Licensing our skills does not merge the two environments or give either side standing inside the other. That boundary holds from install through everyday use.

Change Essentials AI appears in your Claude admin console as a licensed plugin. Your administrator clicks Add plugin, and it is enabled for the workspace. Every designated employee has it from that moment. No per-person install, no desktop software, no new accounts to create. One administrative action and the deployment is done.

The plugin opens a single authenticated connection between your Claude account and our skills server, credentialed to your license. It is the only channel between the two environments. Nothing is copied across it at install: no skill files land in your tenancy, no library is duplicated on your side. It is a request path, not a delivery truck.

An employee types a real question into the Claude they already use. “Will this restructure announcement land with Ops?” Claude recognizes that a licensed Change Essentials AI skill applies, calls it across the connection, and the skill runs on our server. The answer comes back in the same conversation: a Communication Audit flagging audience specificity, missing WIIFM, and confirming action clarity. No new application, no new login, no context-switch.

Anything your CM practitioners generate stops at the edge of your Claude account. What travels is the request and the result. Your documents, your files and your organizational content stay under your existing Claude governance, retention and security posture. For IT and security review, this is the load-bearing point of the model.

When we build a new skill or sharpen an existing one, we publish it on our side. Because your workspace calls the skills rather than storing them, it is live for your people the next time they ask. No IT ticket, no redeployment, no version pinning, no upgrade project.

Four guarantees define the arrangement. Your administrator installs once. We maintain the skill code. You keep your data. Improvements reach your team without any action on your part. A licensing model with no software project attached.

Consulting firms use the skills on client engagements. Corporate change teams use them on internal transformations. Same library, same license, same connection.

The library does the work either way.