How the skill sets deploy within your boundary.
Three integration paths run signed skill sets inside the AI your team already uses, under the governance IT already approved. Until one is unlocked, BBN AI Space is your backup.
Compare the paths side by side.
MCP is the default recommendation for most stacks. Copilot Studio fits M365-standardized orgs. The import package covers the environments MCP does not reach yet.
| A Option A MCP | B Option B Copilot Studio | C Option C Import package | |
|---|---|---|---|
| Best for | Most AI stacks. Claude, Copilot, ChatGPT, and custom assistants that speak MCP. | Microsoft-standardized orgs that want agents managed inside their M365 tenant. | Non-MCP runtimes and sovereign cloud setups. |
| Where it shows up | Your AI app's chat surface: Claude, ChatGPT, Salesforce Agentforce, Frontify, or any MCP-compatible assistant. | Copilot chat, Teams, Outlook; anywhere your users already work with Copilot (depending on your specific setup path). | The runtime you import into: Gemini Gems, Copilot Cowork, AWS Bedrock, Azure OpenAI, air-gapped custom setups. |
| Update cadence | Continuous | Monthly | Quarterly |
| IT effort | Low | Medium | High |
| Data leaves your boundary | No | No | No |
| Who owns the files | BBN AI Studio hosts the endpoint; you flip versions. | Your M365 tenant; IT controls every release. | You own the files. Highest control, highest responsibility. |
BBN AI Space.
BBN AI Studio is the service: the skill sets and the people behind them.
BBN AI Space is a workspace: our own production-grade platform with the skill set library preloaded.
Teams use it to demo the skill sets, test them on real briefs, and ship interim production while IT prepares the primary AI.
Skill sets are portable. When your primary AI is ready, the same skill sets move to MCP, Copilot Studio, or import.
How to get started.
From signature to first usable output is days, not a quarter. There is no migration and no training course, because the skill sets run inside the AI your team already uses.
- 1 Day 0
Sign and choose your path.
Sign the monthly subscription and pick the path that fits your stack: MCP, Copilot Studio, or the import package (or start on BBN AI Space). Access runs on your existing SSO.
- 2 Same day
Default skill sets go live.
Default-version skill sets are handed to your team's AI the day the contract is signed.
- 3 First 10 days
First usable results.
First usable output typically lands within the first ten days, once a handful of live briefs have gone through.
- 4 After the onboarding session
Calibration with the practitioner.
A named practitioner tunes the skill sets to your brand, audience, and tone, and the calibrated versions replace the defaults. The practitioner stays forward-deployed and accountable as new skill sets ship every month.
Data, governance, and EU AI Act compliance.
Your infrastructure. Your boundary.
Skill set execution happens inside your AI platform or tenant. Prompts and outputs never pass through BBN AI Studio infrastructure. Model vendor terms and DLP policies apply as you have already configured them.
GDPR-ready, Frankfurt-hosted, restrictable by region.
Skill set artifacts and any optional telemetry are hosted on EU infrastructure. Frankfurt data residency is the default.
Your model. No training on your prompts.
BBN AI Studio ships skill sets: portable instructions that run on the AI platform you already use, under your vendor's no-training terms for prompts, references, and outputs.
Our skill sets do not learn from your usage.
The BBN AI Studio catalog evolves through new authoring sessions with named senior practitioners. Your data is never part of that process, so your prompts and outputs stay yours.
Every change is logged.
Skill sets are versioned. Each change ships with a changelog (what changed, why, who approved). Older versions remain available for rollback. You see exactly what your team's AI is doing on your behalf.
AI declared, humans accountable.
AI use is declared in contracts and in output metadata. Every skill set has a named human accountable for it: the practitioner who built it. Creation processes are logged and auditable, with no black boxes and no unsigned work.
DPA, GTC, and CC included.
BBN AI Studio ships with a Data Processing Agreement, General Terms and Conditions, and Code of Conduct aligned to the EU AI Act. Legal review packs are available for procurement on request.
What IT, security, and procurement ask before go-live.
What happens to our data when we use a BBN AI Studio skill set?
In all three integration options, the skill set executes inside your AI platform or tenant. Prompts and outputs never transit BBN AI Studio infrastructure. Your model vendor’s terms apply.
What if our AI platform does not speak MCP yet?
Use Option C. Skill sets are delivered as import packages that drop into whatever runtime you use: Google Gemini Gems, isolated sovereign setups, air-gapped assistants, and similar all sit on Option C until MCP support arrives.
What if none of the three paths is unlocked yet?
BBN AI Studio is the service: the skill sets and the people behind them. BBN AI Space is a workspace: our own professional platform with the skill set library preloaded. Most teams use it to demo BBN AI Studio, test it on real briefs, and bridge interim production while IT prepares the primary AI platforms. Space is production-grade. Skill sets are portable: when your primary AI is ready, the same skill sets move into it. See BBN AI Space at https://bbn-international.com/b2b-ai-space/.
Can we run BBN AI Studio entirely on our infrastructure?
Yes. Option B (Copilot Studio) and Option C (Import) both run entirely inside your boundary. Option A (MCP) also executes inside your AI platform. For sovereign cloud or air-gapped setups, Option C is the path.
How is identity and access handled?
Authentication uses your existing SSO. Access rules, roles, and audit logs stay in your platform. We do not issue a new identity layer or hold user accounts on our side.
What logs and audit trails do we get when skill sets run?
Skill set execution sits inside your AI platform, so the logs your IT team already collects cover prompts, outputs, identities, and timestamps. On top of that, BBN AI Studio publishes a per-skill-set changelog (what changed, why, who approved) so you can tie output quality back to the skill set version that produced it.
What happens if a skill set update breaks our workflow?
Previous skill set versions stay available. Roll back in minutes. Option A flips the live version, Option B re-imports the prior package, Option C reverts to the prior file set. Changelogs make every revert auditable.