3 picks · 90 days · 1 named owner
Spark DayKveikja
One day, on-site at your office. The morning is a strategy session with the C-suite: score candidate use cases, pick the two or three that should ship in the next ninety days, name an owner per pick. The afternoon is a live build with the executive team and four to six operating leaders: an Alvio principal builds two or three reference prototypes in your Microsoft 365 tenant — Copilot Studio agents, Power Platform apps, Azure AI Foundry components — alongside the named owners. Each prototype clears a thirty-minute risk and controls review before it leaves the room.
By the close of the day, your team has reference prototypes they can study, a one-page 90-day plan to take forward, and named owners ready to start.
- Duration
- 8 hours, on a single day, on-site
- Format
- Fixed scope
- Next step
- Sprint — the guide-first ship
Scoped engagement · 1 capability shipped · Team trained
SprintSprettur
A scoped engagement to put one production AI capability live in your tenant. Policy drafted, ratified, and communicated alongside the build. Your team trained at three levels — executive, manager, frontline — so the people who run it understand it. KPI baseline before go-live; a written measurement report on completion.
Guide-first is the default and the point: your named owners build the production capability, the Alvio principal coaches. A regular working session reviews progress, unblocks decisions, and gates the controls — Microsoft Purview, Microsoft Defender for AI, Microsoft Entra. Your people own the code, the deployment, the operation, so the capability outlives the engagement.
Optional add-on
Steer — monthly continuity
After the sprint, an optional monthly retainer keeps the rhythm and the controls in place: a fractional Chief AI Officer at your executive team and audit committee, regulatory horizon scanning across ISO/IEC 42001 and NIST, and an annual independent AI risk audit. Six-month minimum. Steer does not ship capabilities — your team keeps shipping, Alvio steers.
If you want us to write the code instead of coaching your team, we quote that on request — the exception, not the catalogue.
- Scope
- Fixed-scope engagement, sized to your goal
- Format
- Guide-first — your team ships, Alvio coaches
- Add-on
- Optional monthly Steer (6-month minimum)
- Next step
- Steer to keep the controls in place, or Forge to widen your makers
5 first makers · 1 maker community · 6 weeks fixed
ForgeSmiðja — companion
Microsoft has been making the low-code / no-code promise — Power Apps, Power Automate, Power Platform — for the better part of a decade. The promise was always real; adoption was always disappointing because the people who knew which workflow they wanted to automate did not have the technical confidence to ship it. AI coding assistants close that gap. The promise is finally workable. The job now is to capture the value with controls, not as shadow IT.
Forge is the operating playbook that does that. Sanctioned tooling, light governance gates, named maker roles, training at three levels, a community model. Forge does not turn your employees into software publishers. It gives the people who already know what their workflow needs a framework to ship what they always could have built and never did. Forge is what makes guide-first Sprint possible.
- Duration
- 4–6 weeks, fixed fee
- Format
- Standalone, companion to Sprint, or foundation of a Steer retainer
- Next step
- Sprint, with the first cohort of makers in place