Workshops | Copilot Spark Day, Sprint and Makers

One day. Two or three working agents.

Copilot Spark DayKveikja

One day on-site with your leadership team and the people who will own the results. The morning is a working session: which tasks in your organization Copilot should take on first, scored and picked. The afternoon is a live build: an Alvio principal builds two or three Copilot agents in your Microsoft 365 tenant, alongside the people who will own them. Each agent clears a short risk and controls review before the day ends.

Who it is for. Organizations on Microsoft 365 that want to see Copilot working on their own data before committing to more. An executive sponsor and four to six operating leaders in the room.

What you leave with. Two or three working Copilot agents in your tenant. A one-page 90-day plan with a named owner per pick. A short controls note for each agent.

How long: One day, on-site, fixed scope
What happens next: Most teams take one pick into a Copilot Sprint. The agents are yours either way.

One capability in production. Your people build.

Copilot SprintSprettur

A scoped engagement that takes one pick from the Spark Day plan into production: a Copilot agent in Teams, a Microsoft 365 Copilot extension, or a Power Platform app with Copilot inside it. Your named owners build. The Alvio principal coaches in a regular working session that unblocks decisions and gates the controls.

Who it is for. Teams that have picked a capability and named an owner, and want to own it after we leave.

What you leave with. One Copilot capability live in your tenant. An AI use policy drafted, ratified and communicated. Microsoft Purview and Microsoft Entra controls in place. Your people trained at three levels: executive, manager, frontline. A KPI baseline and a written measurement report.

If you want us to write the code instead of coaching your team, we quote that on request.

How long: Sized to the capability. Fixed scope, quoted after a one-hour scoping call.
What happens next: Ongoing advisory support on request, or the Makers Program to widen who can build.

Four to six weeks. Your own makers, governed.

Makers ProgramSmiðja

Four to six weeks to stand up a governed group of makers who build with Copilot Studio and Power Platform, without shadow IT. Sanctioned tooling, light governance gates, named maker roles, training at three levels, and a community that keeps going after we leave.

Who it is for. Organizations where the people who know the workflow are not the people who know the platform. Copilot Studio and Power Platform close that gap. The program puts controls around it.

What you leave with. A first cohort of makers with named roles. A sanctioned toolset and an environment strategy in Power Platform. A light approval gate for what makers ship. A maker community with an owner.

How long: Four to six weeks, fixed fee
What happens next: A Copilot Sprint with the first cohort in place.

How every workshop runs.

Our first job is to coach your own people to ship the Copilot capability your organization needs: sanctioned tooling, named owners, and a controls pattern they can reuse without us. We deliver hands-on only when you ask, and the price reflects it. Four principles run the work.

Guide-first.

Your team has had the training and the decks. What is missing is shipping something real. So we coach your people to ship, and leave them the capability, not a dependency on us. Alvio-led delivery is the exception, and it is priced as one.

A named owner, every time.

Responsible AI starts with clear ownership: someone inside your organization accountable for each Copilot capability, not a vendor. Every engagement starts with that named owner. They take part in the Spark Day, help shape the plan, run the build, and stay responsible for it long after we leave.

A plan agreed together.

Every Spark Day ends with a one-page 90-day plan: the picks, the named owners, the milestones, the controls, and a measurement baseline, shaped together with your executive sponsor. No long proposal to wait for. You leave the day with a plan you can act on.

Controls built in.

Every capability ships with the platform's own controls: Microsoft Purview for data classification and loss prevention, Microsoft Defender for AI for threat protection, Microsoft Entra for identity and access. An AI use policy and the literacy training for EU AI Act Article 4 ship with the build, not as a separate workshop.

Questions buyers ask first.

What is a Copilot Spark Day?

One day on-site. By the end of it your team has two or three working Copilot agents in your own Microsoft 365 tenant and a 90-day plan with a named owner. Fixed scope.

Do we need Microsoft 365 Copilot licenses for everyone?

No. Copilot agents are licensed through Copilot Studio capacity, which your tenant may already have. Microsoft 365 Copilot licenses are needed only for the people who use Copilot inside Word, Outlook and Teams. We map this on the Spark Day.

Does it work in our existing Microsoft 365 tenant?

Yes. Everything is built in your tenant, on your data, under your identities. Nothing leaves it.

Who does the building?

On the Spark Day, an Alvio principal builds alongside your owners. In a Sprint and the Makers Program, your people build and we coach.

What does guide-first mean?

Your team ships and owns the result. We coach, unblock decisions and gate the controls. Alvio-led delivery is available on request and priced as the exception.

What governance ships with it?

An AI use policy, Microsoft Purview and Microsoft Entra controls, and AI-literacy training that meets EU AI Act Articles 4 and 50. Our own AI inventory and conformity statement are public.

What does it cost?

Every workshop is fixed scope, quoted on request after a short call. No hourly billing.

Three workshops that put Microsoft Copilot to work in your organization.

Built and shipped on Microsoft Copilot and Copilot Studio.