Skip to main content
BJ Unlimited
Book a consultation

Copilot & Copilot Studio

I've been building on Copilot since before it was generally available.

Most Copilot consultants are either AI generalists who don't know the Microsoft business-application stack, or Dynamics veterans who've barely opened Copilot Studio. I'm neither. I've been hands-on with Copilot since its pre-GA days, and I've architected Power Platform professionally for nine years — which is the ecosystem Copilot Studio actually lives inside.

Start with a Copilot Readiness Assessment

What I do

Five areas. Most engagements touch several.

Copilot work on this practice falls into five capability areas. Where an engagement starts is almost always different from where it ends up.

Copilot Studio custom agents

Designing and building custom agents in Copilot Studio: connected to your Dataverse, your line-of-business systems, and your security model. I scope agents around a specific business outcome, not a demo. That means knowing when a topic belongs in generative orchestration, when it belongs as an explicit flow, and when the whole thing should live in Power Automate instead.

Microsoft 365 Copilot rollout

Planning and executing the rollout of Microsoft 365 Copilot across an organization: licensing strategy, phased deployment, champions program, training content, and measurement. A rollout is a change-management project wearing a licensing hat — I treat it as such.

Governance, data, and security preparation

Before any serious Copilot deployment, your data estate needs to be ready. That means sensitivity labels, oversharing remediation, SharePoint hygiene, Purview policies, and the governance model that keeps Copilot from surfacing content people shouldn't see. This is where most stalled pilots stalled.

Licensing and entitlement planning

Copilot licensing is a moving target, and the wrong assumption early costs real money later. I help you size and stage entitlements around the users and workloads that produce measurable value first.

Power Platform integration

Copilot and Copilot Studio sit inside the Power Platform. Most meaningful Copilot work touches Power Automate, Dataverse, and Power Apps — and that is the surface I have architected professionally since well before Copilot existed. Integrations that other teams treat as an afterthought are where I start.

Where Copilot lives

Copilot Studio is not a separate product. It's a layer.

Copilot Studio sits inside the Power Platform. That's the ecosystem I've architected professionally for nine years — which is why Copilot work on this practice integrates cleanly with the rest of your Microsoft footprint rather than bolting onto the side.

Flagship engagement

The Copilot Readiness Assessment

A focused 2–3 week engagement that produces a defensible Copilot roadmap: current-state assessment of your data, security, and licensing posture; a prioritized use-case backlog scored on value and feasibility; a 90-day implementation plan; governance and adoption recommendations; and an executive-ready deck to sell it internally.

If you're stuck at "we bought licenses and now what," this is the engagement that ends that sentence.

Start with a Copilot Readiness Assessment

Common questions

The three fears most buyers bring in.

How do I stop Copilot from leaking sensitive data?
You prepare the data estate before you turn Copilot on. Sensitivity labels, oversharing remediation on SharePoint and OneDrive, Purview data loss prevention, and a governance model that matches your tenant's reality — not a generic template. Copilot respects the permissions it finds; the job is to make sure what it finds is correct. This is a normal workstream inside a Copilot Readiness Assessment.
How do I know Copilot will actually produce ROI?
You don't, until you've picked the right use cases and measured them. That's the whole point of a prioritized use-case backlog scored on value and feasibility — I start with workloads where the ROI math is defensible, not with the demos that looked good on stage. I'd rather ship three agents with measurable lift than a “Copilot strategy” document that never touches a user.
We bought Copilot licenses. Where do we even start?
You start by getting a clear picture of where you are and where the first real win lives. Not a roadmap that lists every feature — a roadmap that names the next three things to do and who owns each one. The Copilot Readiness Assessment exists for exactly this moment.

You don't need another AI generalist who will hand you off to a junior in month two.

You need a senior Microsoft architect who has been building on this stack for 26 years and on Copilot since before GA.

Start with a Copilot Readiness Assessment